On 2/3/23 23:52, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [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.
Many applications and services that use dbus do not handle dbus going away and coming back again, which is why the service files shipped with openSUSE specifically disable allowing the service to be rebooted. If you feel like changing that because you don't notice issues with the set of apps that run thats fine but please don't encourage other users to attempt an approach that is known to cause issues, thanks your friendly dbus maintainer. Regardless of that not rebooting after any tumbleweed update will probably leave your machine in a inconsistent state which may or may not work. Leap is a bit different in that updates should retain binary ABI. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B