On Mon, 2008-05-05 at 22:53 -0400, Sam Clemens wrote:
Linda Walsh wrote:
Joe Morris wrote:
On 05/06/2008 05:39 AM, Linda Walsh wrote:
This topic is not intended at those who only upgrade a system by running the "official" upgrade procedure ... "offline" (not usable for other tasks). <snip> Anyone else interested in this subject? Is there a better place to find people who might be interested or know about such tools?
I don't think this would be possible (or so far from ideal as to not be too useful). Several limitations come to mind, i.e. newer versions of rpm needed, or glibc, which affect every rpm package in a new distribution. From what I have learned over the years is replacing glibc on a live system is not a good idea. That is why the offline upgrade is best. Upgrading a live system has a lot of pitfalls that would probably make it a nightmare in practice.
And when offline upgrading is not an option or when it is too costly? You just tell people "too bad?" What about people who don't want to do it the Windows way?
Most companies will spend the time to setup redundancy so that they can take 1 server down at a time during upgrades and still be available so there is no cost hit. This is also smart if being down for any period of time is costly to you in case of hardware failures and the such. But with that said, openSUSE 11 with the latest zypper now supports doing Live updates via the dup arguments. But I think you should reconsider your setup and if its truly costly for you to be down during an upgrade, proper load balancing and fail over should be put in place. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org