El 2020-09-09 a las 14:42 +0200, jdd@dodin.org escribió:

Le 09/09/2020 à 14:18, Carlos E. R. a écrit :

...

No, you must reboot ASAP if the reboot is reccomended, or don't update.

I'm not sure of that. It's usually because a new kernel. As I shutdown my computer at night, I usually ignore those warnings.

/If/ you get the warning that you must reboot after the update from YaST or zypper, then it is true. It means that whatever was updated can not (automatically at least) be restarted, and the easiest way is a reboot. For example, something may want to load a lib, module, plugin, whatever, and the version it will load is not the one that the code is expecting. The results can not be predicted. Things may not work right.

I wonder why some servers can have so high uptime :-(

By not updating, I guess. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))

El 2020-09-09 a las 15:42 +0200, jdd@dodin.org escribió:

Le 09/09/2020 à 15:26, Carlos E. R. a écrit :

...

/If/ you get the warning that you must reboot after the update from YaST or zypper, then it is true. It means that whatever was updated can not (automatically at least) be restarted, and the easiest way is a reboot.

I don't say it's not true, it's not mandatory/immediate, apart may be for a server exposed to the net (and so never rebooted in normal life)

else it's not a warning :-) it's a order :-)

Well, you risk malfunctions, even a crash. If you are not going to reboot ASAP, better do not update. -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith))

Hi again, all -- ...and then jdd@dodin.org said... % % Le 09/09/2020 à 14:18, Carlos E. R. a écrit : % % >No, you must reboot ASAP if the reboot is reccomended, or don't update. Thanks for lots of input. Yay! :-) This is the problem I have, though ... I'd be happy to not update now, but after accepting the 38 selected of 100 updates to apply and saying "go" to only THEN see "you'll have to reboot", it's already updating. I'd much rather accept the lot and be told "hey, you'll have to reboot if you continue" and have the opportunity to cancel the update until I'm ready. Is that an option anywhere? I'm lazy and using the "Software Updates" KDE taskbar control; if there's another way, I'd certainly look at changing my habits :-) % % I'm not sure of that. It's usually because a new kernel. As I % shutdown my computer at night, I usually ignore those warnings. Oh, I might go an hour or two before rebooting because it's such a royal PITA to reboot and start over. I definitely don't shut down on any regular basis. % % I wonder why some servers can have so high uptime :-( Ah, those were the days :-) I remember watching one of my SunOS servers break 1000 days when I was working in college ... % % jdd Thanks again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Carlos, et al -- [Leaving the patch & reboot question aside for a moment, although I'm very grateful for the input!] ...and then Carlos E. R. said... % % El 2020-09-09 a las 07:45 -0400, David T-G escribió: % ... % >Is there a [presumably] GRUB config that will skip the splash and stay in % >text mode until login time? % % Certainly. % % /etc/default/grub: ... % % GRUB_CMDLINE_LINUX_DEFAULT="splash=verbose resume=/dev/disk/by-label/nvme-swap mitigations=auto" % % Notice the "splash=verbose" and the absence of the word "quiet". Woo hoo! I had =silent; I'll try no splash= at all. % % I also uninstall and taboo plymouth. Hmmmm... It seems davidtg@gezebel:~> rpm -qa plymouth plymouth-0.9.4+git20190304.ed9f201-lp151.2.3.1.x86_64 that I have that installed, too. I'll have to dig into that more later. % % -- % Cheers % Carlos E. R. Thanks! :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

ne... composed on 2020-09-09 13:39 (UTC+0100):

David T-G wrote:

...

Is there a [presumably] GRUB config that will skip the splash and stay in text mode until login time?

Edit /etc/default/grub and change the GRUB_CMDLINE_LINUX_DEFAULT. Remove the 'splash=silent' so that it resembles what is below:

GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/disk/by-uuid/<my disk id goes here> showopts mitigations=auto verbose"

That's what I use.

Verbosity is default behavior. It equates to "" IOW, it's inert. showopts does nothing in Grub2, works in Grub Legacy in conjunction with gfxboot. splash= is an option. I don't know whether defeating plymouth via cmdline is necessary also, as I never keep it installed. IMO it's essentially bloatware. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org