According to aoc2: While burning my CPU. > > On Sat, 5 Dec 1998, Richard Adams wrote: > > > > I'm having trouble with lilo and would be grateful for any help. > > > For some inexplicable reason, it stopped updating lilo.conf. To be > > > specific, last night, I changed my lilo password to something else. > > > I reran /sbin/lilo, rebooted the machine, entered the new password, and > > > was instantly greeted by 'Incorrect password. try again'. So I did, this > > > time using the old password. Only then was I allowed in. > > > Another problem, pretty much related to the first, is I cannot run the new > > > kernel (2.0.36) on account of lilo failing to update its configuration > > > file. How do I fix this? > > > > Quite possably you have made a typo in /etc/lilo.conf, to check where lilo > > is stopping you could use. > > > > lilo -v -v >file.txt > > and below is the output: > > LILO version 19, Copyright 1992-1996 Werner Almesberger > > Caching device /dev/hda (0x0300) > Caching device /dev/hda1 (0x0301) > Caching device /dev/hda2 (0x0302) > <snipped> > Reading boot sector from /dev/hda > Merging with /boot/boot.b > Secondary loader: 8 sectors. > Boot image: /boot/vmlinuz > Setup length is 9 sectors. > Mapped 747 sectors. > Added linux * > /boot/boot.0300 exists - no backup copy made. > Map file size: 7168 bytes. > Writing boot sector. > > there doesn't seem to be anything wrong. No indeed it all seems ok, the only thing i can think of is it has something to do with /etc/lilo.defines if you have one. Or you are making a typo at the lilo boot prompt, all i can say is it works here, but thats of no use to you there. > > here are the contents of /etc/lilo.conf: > > boot=/dev/hda > map=/boot/map > install=/boot/boot.b > password=xxxxxxx > prompt > linear > timeout=50 > image=/boot/vmlinuz > label=linux > root=/dev/hda2 > read-only > -- Regards Richard. [EMAIL PROTECTED]
