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.
> Error messages will be written on the screen, other succesfull commands go
> to the file file.txt.
>
> It could also be that you have changed permissions of /etc/lilo.conf in such
> a way that it cant be read.
> Remember if you use the password parameter in lilo and the file
> /etc/lilo.conf is readable by users, then a warning message will be written
> to the screen, have you changed permissions.???.
after changing the password and running /sbin/lilo, i chmod'ed the
configuration file back to 600, as i always do.
> Another thing is, if you have deleted any files in /boot or / such as an
> old image and the entry is still in lilo.conf that will also cause lilo to
> fail.
about the only thing that has been updated in /boot is vmlinuz, map, and
System.map. the rest of the files are unchanged.
lrwxrwxrwx 1 root root 17 Aug 30 13:44 System.map ->
System.map-2.0.30
-rw-r--r-- 1 root root 84657 Dec 3 01:24 System.map-2.0.30
-rw-r--r-- 1 root root 204 Sep 10 1996 any_b.b
-rw-r--r-- 1 root root 204 Sep 10 1996 any_d.b
-rw-r--r-- 1 root root 512 Aug 30 13:52 boot.0300
-rw-r--r-- 1 root root 4416 Sep 10 1996 boot.b
-rw-r--r-- 1 root root 88 Sep 10 1996 chain.b
-rw------- 1 root root 7168 Dec 5 23:34 map
lrwxrwxrwx 1 root root 18 Aug 30 13:44 module-info ->
module-info-2.0.30
-rw-r--r-- 1 root root 192 Sep 10 1996 os2_d.b
lrwxrwxrwx 1 root root 14 Aug 30 13:44 vmlinuz ->
vmlinuz-2.0.30
-rw-r--r-- 1 root root 381152 Dec 4 11:45 vmlinuz-2.0.30
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]
>
