On Mon, 8 Feb 2010 01:17:04 +0100 (CET) Eberhard Moenkeberg firstname.lastname@example.org wrote:
Nice. Please do it and report here. I'm sure it works, at least it should this way.
Actually, the more I think about it, I'm not sure if it makes such a big difference if the system is "live" or "offline" updated. The RPM postinstall scripts still run in a chroot()ed environment, don't they?
If you will experience show stoppers, they have to get solved.
I agree, but I am not the product manager :)
OTOH, similar problems could be experienced during an update to a completely incompatible libc version (not likely to happen, but still...) and similar, so it is a good Idea to solve them.
It might be hard to impossible to implement the "online" upgrade to an incompatible architecture (x86_64->i386 or x86->ppc), but "offline" should be possible (the new installation also must cope with the "no compatible libc present" problem for bootstrapping).
I really have to try this ;)