> thought it might be a bogus lilo. script is a handy way to capture a
> console session to a file, and I wanted to remind you of that, too.
> Or you could have said, lilo -v &>file_to_include_in_the_mail
> (bash only, other shells like ">file 2&>1", which bash also likes).
> That way you don't make typos. :-)
Problem was that the troublesome machine is elsewhere, and not on
line, so pasting impossible unless I happened to remember to bring
along a diskette. As it was, I scribbled notes with a pencil on scrap
paper, so the problem was more illegible handwriting than a type. ;-(
> I don't know how to make lilo segment fault, so I don't know how to fix
> it. Could you be dead flat out of space in /boot? I would expect that
> to get error 28, but maybe not. df to see.
I can't remember the space I gave /boot, and adding the various images
might have made it crowded. I'll follow your suggestion. This machine
was a cheap box with Windows on it, and I wondered if there's trouble
in the MBR due to contamination by the previous resident. Yet I can
install the old lilo.conf, and so perhaps not.
Haines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
