On 2023-07-06 11:06, Daniele Granata wrote:
Hi Carlos, "My advice is to only run zypper dup when you intend to reboot or power off your machine afterwards." Are yours not mine. I'm aware that only specific updates need a reboot and that is a thing. I'm not saying "the machine should update without reboot", but "the machine should update before power off or on the next power on".
My advice can be understood as "only update at the times that if zypper says at the end says that you should reboot, you can do so right then". If it doesn't say to reboot, then fine, don't reboot; but run "zypper ps" and restart everything affected that is on the list, if you know how. If you don't know how, then just reboot because it is easier and faster. So, it is not that I advise you to reboot everytime you update, but only update if you are prepared to accept a reboot if the system advises you to. If a reboot will not be convenient even if recommended, then just don't update.
An example: KDE updates every month, after zypper dup I'm not able to logout because the greeter crashes so I need to CTRL+ALT+DELETE to close X losing the current session.
There is another recommendation to run zypper dup in text mode, never in graphical mode :-p
The same will not occur if the installation goes on on reboot or before power off. Better if the greeter asks me if I want to install the updates or reboot without. These are little stupid things but made life easier. With zypper we have snapshots but we use them only to go back. Why not use them to go forward? Patrick, my use case is similar, sometimes I reach a peak of 2 month uptime, I'm on NVIDIA and so I skip kernel's upgrade very often.
Please do not use an innocent request to become aggressive.
Sorry, I'm not, not intended :-) It is only that I know Patrick and what he does, which is a not recommended method, and I'm not willing to argue with him about this, again ;-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)