В Wed, 20 Feb 2013 12:25:20 +0100
Michal Kubecek
solution to. The user logging into KDE/Gnome and running an update from there is not a problem - he knows to run "zypper ps" (and zypper actually tells him to do so when it is needed) and can decide what to do according to the result.
No, you are wrong here. Typical user does not even know how to start command line, and of course is not aware of "zypper" or how to understand "zypper ps" output. Subscribers to -devel lists are in no way typical users. So for a desktop targeted at typical user offline update is the least evil solution. Let's face it - there are no resources to guarantee error-free online updates under any combination of installed software and its configuration. And desktop users did reboot to install updates for quite some time, so there is nothing new here. The best thing that can be done here is what Solaris did for years with Live Update. Prepare clone of current system, update it and reboot. Of course technical savvy server admins should have a choice. No question. 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. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org