On Tue, Jun 22, 2021 at 10:58 AM Joe Zeff <joe(a)zeff.us> wrote:
>
> On 6/22/21 10:29 AM, George N. White III wrote:
> > The Gnome software manager has the added advantages
> > that it a) forces a reboot and b) offers flatpak versions of
> > major
> > applications.
>
> The forced reboot is only an advantage if some of the upgrades
> require a
> reboot to get them started. Most upgrades only need to have their
> package restarted, and that only if it was running when the upgrade
> occurs. This is what needs-restarting is for, but if you don't
> know how
> to use dnf (and don't want to) it's not going to do you any good.
> And,
> for that matter, what do people like that do if they're not set up
> with
> Gnome? My personal opinion is that people like that should be
> using
> Ubuntu, as that distro is specifically designed for Windows
> refugees.
> (I've set two people up with Linux because they wanted to get away
> from
> Windows, and both of them are happily running Xubuntu.)
>
> Sorry for ranting, but forced reboots are a pet peeve of mine and
> you
> just petted it.
https://lwn.net/Articles/702629/
Kindof an old argument at this point. One of the things I'm curious
about right now:
https://pagure.io/libdnf-plugin-txnupd
https://kubic.opensuse.org/documentation/transactional-update-guide/trans...
It's a more sophisticated variation on on I came up with by (rw)
snapshotting the 'root' subvolume, mounting it, and using chroot to
do
a full system update (and upgrade). It's an out of band or side car
update. No reboot to a special environment. If it goes wrong, just
delete it. If there's a crash or power fail, you still boot the
untouched current root. Only once it completes, and optionally passes
some tests, would the root be switched to the updated snapshot, and
reboot. And the user can choose when that happens.
Interesting. That sounds superficially similar to Android's A/B system
update method. Is there work being done on getting this into Fedora?
poc