* Carlos E. R. <robin.listas@telefonica.net> [02-03-23 08:58]:
On 2023-02-03 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [02-03-23 08:00]:
On 2023-02-02 18:30, Andrei Borzenkov wrote:
On 02.02.2023 20:10, Per Jessen wrote:
I really don't dabble much with Tumbleweed, so this might be a stupid question.
On my newly dup'ed system "office24", I just ran another zypper dup - the output is here:
https://files.jessen.ch/office24.zypperdup.txt
When the initrd is being rebuilt, surely a reboot should be suggested/recommended or is that not standard practice?
zypper is not aware of initrd at all. It suggests reboot if patch has reboot_suggested flag. Only patches have this flag and Tumbleweed does not have patches.
Ow! That's an important bit of information to know. Thanks.
So that's why some users think they don't have to reboot TW after a zypper dup ;-)
no, that is not accurate. rebooting is recommended but not necessary when dbus and/or kernel is updated. services may be restarted using "systemctl restart <service>" for the most part in other instances, rebooting is a personal choice.
If you don't reboot, the kernel update has not been applied. Time wasted doing an update that you do not apply.
A reboot is absolutely necessary when the kernel is updated.
Reat my reply again! -- (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