On Sat, 2008-04-05 at 10:08 +0100, Justin B Rye wrote: > Khalid Aziz wrote: > > "Please choose whether to enable kexec-tools to load a new kernel > > automatically on reboots and kexec into the new kernel instead of > > rebooting into firmware." > > > > Any thoughts? > > Mainly, again, "what's new about them?" - kexec _can_ be used to > load a specified kernel, but that's not the behaviour you get from > automatic reloads handled by kexec-tools. What it does by default > is load /vmlinuz, and that's usually an _old_ kernel. > > Also, I'm not keen on "firmware" (too technical) or "reboots" (when > you mean restarts that avoid the bootstrapping process). And this > is too much work for one sentence. > > How about: > > Should kexec-tools handle reboots? If you accept this option, > invocations of "shutdown -r" will trigger a restart into a kernel > loaded by kexec instead of going through the full system bootloader > process. >
I like this wording except for specifying "shutdown -r". I would suspect a number of users simply issue a "reboot" command or use reboot option from gdm menu, and "shutdown -r" may not be as familiar to all users as reboot might be. Plus I do not want to try to enumerate all possible commands that could result in kexec reboot. How about this instead: Should kexec-tools handle reboots? If you accept this option, a system reboot will trigger a restart into a kernel loaded by kexec instead of going through the full system bootloader process. -- =================== Khalid Aziz [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]