LEAP 15.2 selecting only non-reboot updates
Hi, all -- I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot? TIA & Happy New Year :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
On Sun, Jan 9, 2022 at 6:25 PM David T-G <davidtg-robot@justpickone.org> wrote:
Hi, all --
I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot?
I am not sure I understand the question. Reboot does not happen automatically, at least I have not seen it, You are notified that reboot is recommended; whether you follow this recommendation or not is up to you.
* David T-G <davidtg-robot@justpickone.org> [01-09-22 10:27]:
Hi, all --
I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot?
not that I a aware, but ... just delay rebooting until it is convenient. there is no need to immediately reboot when a new kernel is installed or dbus changes. you just don't get whatever advantage those apps requiring a reboot provide. mething you worry needlessly :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
Hi, all --
I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot?
not that I a aware, but ... just delay rebooting until it is convenient. there is no need to immediately reboot when a new kernel is installed or dbus changes. you just don't get whatever advantage those apps requiring a reboot provide. mething you worry needlessly :) Andrei and Patrick are correct; it's not a big deal. I sometimes go a week or more before rebooting (though it's probably better just to delay updating in that case). The only problem with delaying after a kernel update (as I understand it) is if you plug in a USB device you haven't used since the last boot that needs a kernel module that hasn't been loaded. In that case, the old kernel may not be able to load the module it needs from the updated location, and you won't be able to use the device. FWIW, I've been using openSUSE (and before that SuSE) GNU/Linux systems at home and at work for nearly 20 years now, up to 20-30 of them at a time, clients and servers, updating some of them no more than every month or two, and as far as I can tell (knock on wood here), none of them has ever been rooted. YMMV, and there isn't much on those networks that is publicly accessible, so that may not be saying much. Still, based on that experience, I believe that updating openSUSE clients more than once per week for security purposes is overkill. -- Bob Rogers http://www.rgrjr.com/
* Bob Rogers <rogers-suse@rgrjr.homedns.org> [01-09-22 12:34]:
Hi, all --
I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot?
not that I a aware, but ... just delay rebooting until it is convenient. there is no need to immediately reboot when a new kernel is installed or dbus changes. you just don't get whatever advantage those apps requiring a reboot provide.
mething you worry needlessly :)
Andrei and Patrick are correct; it's not a big deal. I sometimes go a week or more before rebooting (though it's probably better just to delay updating in that case).
The only problem with delaying after a kernel update (as I understand it) is if you plug in a USB device you haven't used since the last boot that needs a kernel module that hasn't been loaded. In that case, the old kernel may not be able to load the module it needs from the updated location, and you won't be able to use the device.
FWIW, I've been using openSUSE (and before that SuSE) GNU/Linux systems at home and at work for nearly 20 years now, up to 20-30 of them at a time, clients and servers, updating some of them no more than every month or two, and as far as I can tell (knock on wood here), none of them has ever been rooted. YMMV, and there isn't much on those networks that is publicly accessible, so that may not be saying much. Still, based on that experience, I believe that updating openSUSE clients more than once per week for security purposes is overkill.
much agreement ... but one frequently updates not for security purposes but the delayed reboot still holds. I began using SuSE pre 2000 and cannot remember every being bit by delaying boot. and using Evergreen/Tumbleweed since conception. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On Sun, Jan 9, 2022 at 8:32 PM Bob Rogers <rogers-suse@rgrjr.homedns.org> wrote:
The only problem with delaying after a kernel update (as I understand it) is if you plug in a USB device you haven't used since the last boot that needs a kernel module that hasn't been loaded. In that case, the old kernel may not be able to load the module it needs from the updated location, and you won't be able to use the device.
What gave you this idea? Currently running kernel remains and is not deleted (old kernels are purged on next reboot).
From: Andrei Borzenkov <arvidjaar@gmail.com> Date: Sun, 9 Jan 2022 21:22:54 +0300 On Sun, Jan 9, 2022 at 8:32 PM Bob Rogers <rogers-suse@rgrjr.homedns.org> wrote:
The only problem with delaying after a kernel update (as I understand it) is if you plug in a USB device you haven't used since the last boot that needs a kernel module that hasn't been loaded. In that case, the old kernel may not be able to load the module it needs from the updated location, and you won't be able to use the device.
What gave you this idea? Currently running kernel remains and is not deleted (old kernels are purged on next reboot). That used to be the way it worked. I knew that old kernels are now purged after rebooting, but I wasn't sure when the modules were updated. -- Bob
On 09/01/2022 16.25, David T-G wrote:
Hi, all --
I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot?
No, there is no such feature. YaST will tell you in advance that a reboot will be required, but that's it. And there are many updates that don't nominally require a reboot, but the easiest way to activate them is a reboot. With experience, you will learn which updates do not require a reboot or a difficult restart. For example, those of applications. IMO, doing the update and then not reboot is pointless. The system is not as stable (yes, I have been hit by it), and those updates are not activated till the reboot, so why update at all? So, just delay updating until the day in which you can afford to reboot. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Hi, all -- ...and then Carlos E. R. said... % % On 09/01/2022 16.25, David T-G wrote: % > % > I would love to keep my system more up to date, but I can't always plan % > for a reboot in the middle of what I'm doing. Is there a way (KDE % > updates menu, zypper, YaST, ...) to select all updates that won't require % > a reboot? % % No, there is no such feature. YaST will tell you in advance that a reboot ... % % So, just delay updating until the day in which you can afford to reboot. This is typically what I do, but "afford" is a pretty fleeting thing. Getting logged in again is a time-consuming process *sigh* I would be happy to apply patches that can happily be immediately useful and hold off on those that need a reboot, but there's no way to differentiate. I do indeed worry about breaking my system and then having to reboot at an inconvenient time. So far, it appears that that "just doesn't happen", so I'll let everyone know if it does :-) Thanks again :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
On 2022-01-29 17:35, David T-G wrote:
Hi, all --
...and then Carlos E. R. said... % % On 09/01/2022 16.25, David T-G wrote: % > % > I would love to keep my system more up to date, but I can't always plan % > for a reboot in the middle of what I'm doing. Is there a way (KDE % > updates menu, zypper, YaST, ...) to select all updates that won't require % > a reboot? % % No, there is no such feature. YaST will tell you in advance that a reboot ... % % So, just delay updating until the day in which you can afford to reboot.
This is typically what I do, but "afford" is a pretty fleeting thing. Getting logged in again is a time-consuming process *sigh* I would be happy to apply patches that can happily be immediately useful and hold off on those that need a reboot, but there's no way to differentiate. I do indeed worry about breaking my system and then having to reboot at an inconvenient time. So far, it appears that that "just doesn't happen", so I'll let everyone know if it does :-)
Thanks again
:-D
It is really simple. The day you say "today I will reboot the machine because it is raining" (or whatever reason fits you. Well, that day run the update. Don't even look other days. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
* David T-G <davidtg-robot@justpickone.org> [01-01-70 12:34]:
Hi, all --
..and then Carlos E. R. said... % % On 09/01/2022 16.25, David T-G wrote: % > % > I would love to keep my system more up to date, but I can't always plan % > for a reboot in the middle of what I'm doing. Is there a way (KDE % > updates menu, zypper, YaST, ...) to select all updates that won't require % > a reboot? % % No, there is no such feature. YaST will tell you in advance that a reboot .. % % So, just delay updating until the day in which you can afford to reboot.
This is typically what I do, but "afford" is a pretty fleeting thing. Getting logged in again is a time-consuming process *sigh* I would be happy to apply patches that can happily be immediately useful and hold off on those that need a reboot, but there's no way to differentiate. I do indeed worry about breaking my system and then having to reboot at an inconvenient time. So far, it appears that that "just doesn't happen", so I'll let everyone know if it does :-)
David, it is not *necessary* nor required to reboot, only recommended. I reboot when convenient and to my knowledge have never experienced a problem from delaying reboot. Interum actions: I have aliased zpss to 'zypper ps -ss' and I run: systemctl restart <results from "zpss"> several of the results from zpss cannot be restarted as above but I just delay until a reboot is convenient. other apps I just ignore, such as firefox. I sometimes restart the graphical display but that does not require reboot. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
David T-G composed on 2022-01-09 10:25 (UTC-0500):
I would love to keep my system more up to date, but I can't always plan for a reboot in the middle of what I'm doing. Is there a way (KDE updates menu, zypper, YaST, ...) to select all updates that won't require a reboot?
Is the subject a typo? 15.2 won't ever be up-to-date any more, or depending on point of view, always will be, since its support ended 2021-12-31. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Felix, et al -- ...and then Felix Miata said... % % David T-G composed on 2022-01-09 10:25 (UTC-0500): % % > I would love to keep my system more up to date, but I can't always plan % > for a reboot in the middle of what I'm doing. Is there a way (KDE % > updates menu, zypper, YaST, ...) to select all updates that won't require % > a reboot? % % Is the subject a typo? 15.2 won't ever be up-to-date any more, or depending on % point of view, always will be, since its support ended 2021-12-31. No, it isn't a typo; it's habit to try to provide all needed information. I expect[ed] the same concerns with the next iteration, too :-) Thanks again & HANW :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
participants (6)
-
Andrei Borzenkov
-
Bob Rogers
-
Carlos E. R.
-
David T-G
-
Felix Miata
-
Patrick Shanahan