On Mon, 2017-09-11 at 23:11 -0700, Samuel Sieb wrote: > On 09/11/2017 08:34 PM, Tim wrote: > > With the way Linux is getting worse and worse about this kind of thing, > > I wonder if we're getting more and more programmers coming over from > > the Windows world, where they just don't understand what's wrong with > > that philosophy of computing. That, or it's sabotage. > > Why are you being so difficult about this? Are you deliberately trying > to not understand? You *don't* have to reboot to do updates. >From what Tim wrote, I cannot see that he didn't see this as well .. > You are > completely free to run dnf yourself and do live updates. That's what I > do most of the time, but I also tend to reboot after the updates are > finished. Just don't complain if something goes wrong when you do live > updates instead of doing them offline. That's exactly the point: You don't have to reboot, as you say a few lines earlier, but it's simply safer to do just that. That's his - and others - whole point. Apart from kernel updates there wasn't a need, IIRC, to reboot in earlier times. Read Tim: " ...rebooting has rarely been necessary after updates (beyond kernel updates), ever since I started using Linux (before Fedora existed)." Is he right or not? We have a choice: let Linux - or Fedora Linux at least - keep being what it is, namely a system (with what some see as an annoyance) that you better reboot after updates, or we try to find a way back to its status quo pro ante where there was no need to reboot. Our choice: I definitely won't complain, no matter what the Linux coders' or the Fedora management's choices will be. But let us at least get the fact straight: Linux, from how I understand the results of this debate, now *better* is getting rebooted after updates. This wasn't necessary in earlier times. Would you agree on these last two sentences, Sam, or anyone else? Regards Wolfgang _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
