It strikes me that this is also in part a LILO 'problem'. We could
use some way to tell LILO to only boot a given image _once_ as the
default, and thence reboot to the normal default. Combine this with any
of the methods for remote reboot (hardware watchdog, other machine wired
to reset, whatever) and you can easily recover from a futzed new kernel.
I'm sure LILO can find room for a single byte 'flag' for such things
and an extra per-config option in /etc/lilo.conf.
-Ath, checking the LILO docs to see if it does something like this
-- - Athanasius = Athanasius(at)miggy.org.uk / http://www.clan-lovely.org/~athan/ Finger athan(at)fysh.org for PGP key "And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence." Paula Cole - ME - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/