At 5:21 PM -0500 12/8/00, Jonathan D. Proulx wrote:
Hi,
the fix:
lilo was writing boot.b and map to my HD rather than FD, switching to
relative paths fixed it.
-Jon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
UNSUBSCRIBE
Hi,
the fix:
lilo was writing boot.b and map to my HD rather than FD, switching to
relative paths fixed it.
-Jon
An off group source pointed out:
:>From the massive LILO man page from hell:
:
:
:When LILO loads itself, it displays the word "LILO". Each letter is printed
:before or after performing some specific action. If LILO fails at some
:point, the letters printed so far can be used to identify the pro
Hi,
I seem to be in a catch22 situation.
According to the Boot-disk-HOWTO:
lilo -v -C bdlilo.conf -r /floppy/
but according to my machine:
LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Reading boot sector from /dev/f
4 matches
Mail list logo