On Wed, Jul 04, 2012 at 05:45:23PM -0300, Claudio Freire wrote:
On Wed, Jul 4, 2012 at 5:41 PM, Roman Bysh <rbtc1@rogers.com> wrote:
On 07/04/2012 04:25 PM, Jan Engelhardt wrote:
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. ... Well if you put it that way. I have to agree with you. It's better to do a hard reboot for true changes to appear.
But, honestly, mid-install is not the time to test that. It makes fixing it harder - because the system isn't fully configured yet.
If I was installing a server, I'd reboot it at least once. To be sure.
Yeah, you would hope so, but as someone who currently has a machine that the 12.2 beta will install properly, and "reboot" into the working system afterward, yet fails to boot from a cold reboot due to it being a EFI-based system, it is really annoying. I'd much rather find out the install failed earlier... But as I'm not working on the installer, I really don't have much to say about it :) Now if only we shipped a EFI-stub-enabled kernel, that would solve a lot of my issues, but that's a different topic... greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org