Ok, so why bothering for being able to specify some more parameters to ``savedefault'' and asking for a ``showdefault''?
Well, as you probably already know, grub provides the ability to remember the last entry we used to boot and to automatically use it on the next reboot.
A while ago, I was looking for a nice, clean and reliable way to upgrade the kernel of a remotely installed machine I don't have physical access to.
Let's see... we need to compile the new kernel, possibly test it, transfer it on the remote server and install it.
This is not quite an error free procedure: human errors may happen, the compiler or some system library may just be sick when compiling the kernel and our test might just be not enough to ensure the kernel will work at the first shot on the remote server.
Even if I use something like ``make-kpkg'' I may just forgot to apply some fundamental patch or to disable/enable some brand new kernel feature.
The purpose of this patch is to provide a nice way to have more than ``one shoot'' when trying to upgrade a remotely installed linux kernel.
So, if something bad happens, the system can be rebooted and the error corrected without having to ``be there''.