> On Fri, May 17, 2002 at 10:48:21AM -0400, Richard B. Johnson wrote:
> > Where there is a will, there is a way. As others have reported, you
> > can have an old "always-on" machine at the remote site. You can have
> > LILO redirect kernel messages out the serial port to be viewed
> 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
Of course there is a 'default' entry to be booted by LILO. But
this is what it will boot if there's nobody at the remote site
to hit the ALT key and change to another.
LILO could be modified to look for a printer-port bit pattern
to decide which entry it will boot. This is trivial but makes
it incompatible with systems that don't have anything connected
(which could cause any random bit-pattern to be latched.
LILO could also be modified to use the BIOS int 0x14 RS-232C
interface to send prompts out there as well as the screen/keyboard.
This allows an always-on remote computer to do the boot configuration.
Nevertheless, there is no way for LILO to keep track of boots and
decide for itself if it should try the 'next' kernel because the
previous didn't work. This would require that it write something
into media that is not always writable. The PC, itself, has no
where to store such information except in the CMOS, all locations
of which may already have been 'taken' or, at least included in
the checksum, resulting in no boot sequence at all because the
BIOS will say "CMOS Checksum failure... hit [F2]..." or whatever
else non-standard may exist.
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/