On Wednesday 2012-07-04 22:08, Roman Bysh wrote:
All that just to run "Automatic Configuration"! Isn't running "kexec" part of the automatic configuration process?
Why even use kexec? Modern systems could just chroot into the just-installed system! However, doing a total system reboot has its benefits: it tests that the bootloader is working properly. Because sometimes, it has occurred that there was some error installing grub, and if you don't reboot but kexec or chroot, you may never know. Think of it: system has not been rebooted ever since, is now in deep production, gets a kernel update. Instead of 5 minutes downtime, you're going to have in the excess of 30 to get grub straight again using a rescue image. And grub2 being on the horizon means: testing it all over again.
I don't remember doing this with Ubuntu do you?
Better a safe system than a ship playing fanfares while it is about to sink. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org