On Wed, 2013-02-20 at 15:14 -0500, Ken Schneider - openSUSE wrote:
On 02/20/2013 01:37 PM, Claudio Freire pecked at the keyboard and wrote:
On Wed, Feb 20, 2013 at 12:22 PM, Michal Kubecek
wrote: But again - 24x7 is *NOT* something that can be achieved with single system. Period. If you *really* need 24x7 you have to build high available system where applications can be moved over to allow maintenance work on a node. At which point there is no practical argument against offline updates.
No idea why are you bringing this here. I wasn't talking about 24x7 or high availability. Just about desktop users using the feature of having more than one session open and switching between them - which is a standard feature we offer and provide a comfortable user interface for. And with memory prices being what they are, this scenario is likely to get more and more common.
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. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org