On Wed, Feb 20, 2013 at 5:19 PM, Dimstar / Dominique Leuenberger
Yeah, in fact, it happens a lot at home, and everything you say is true: I have a hard time finding a way to "politely" reboot (ie: without killing everyone else's session).
And why are we trying to make linux into MS windows in regards to a reboot every time a package gets an update? Why not instead teach users how to use 'zypper ps' to check which processes need to be restarted amd how to restart them. I never reboot except for kernel updates as there is no need.
Guys,, really.. this thread is getting out of control and really boring to read!
offline-updates is an OPTION! Nobody (I repeat: NOBODY) forces you to use it... if you wish to do so: use zypper.. or if you wish: use rpm. you prefer yast? Go for it! Or better Apper? be my guest! Or shall it be gpk-applications? Then by all means! BUT GET YOUR LIFE TOGETHER and choose your option.
No, it's not about that. You're bored because you don't understand what the discussion is about. It's about what unkowledgable users are offered by the default update app. Why offer them a reboot process when none is necessary? Is that correct? Can it be improved? Some people argue the very risk of malfunctioning apps is undesirable, where others (me included) prefer to minimize that risk, but still maximize the number of updates that can be applied without such a reboot. I agree, if an average user is faced with such failures as they happen with apps broken by online updates, they'd be very confused and would infer linux to be unstable. So yes, it has to be safe. But many updates are marked as requiring a reboot or relogin, so we are discussing the possibility to transfer that knowledge to gnome's updater, packagekit or whatever. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org