Hi Khalid, My request was that the behaviour be documented somewhere.
For example, "man kexec" tells me to kexec -l and then kexec -e. But actually I should, depending on a debconf setting, do something like kexec -l; reboot. The kexec man page might not be the right place to say that, but it's the only documentation you ship.
Khalid Aziz wrote:
Please see <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426506> that led to this change in behavior. kexec-tools 20080227 added a debconf option to ask the user if they want kexec to handle reboots or not.
Not documented either, as far as I can see.
Current version in leeny has this debconf option. This should address your concern. If kexec reboots are enabled, a kexec reboot will load the kernel /vmlinuz. Unless a user has built custom kernels,
A significant group of users for fast reboot are those who are in the edit-run-debug cycle with custom kernels.
the last kernel installed by a debian package would update /vmlinuz link to point to the kernel installed by it which is typically the latest kernel and which is what most typical users want to boot. This default can be changed in /etc/default/kexec.
It would be great to get a menu. In practice, I find that the time saved by kexec does not make up for the convenience of the grub menu. I'll see if I can come up with something.
Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
