Hi Rich,

I removed the default LILO (came with Redhat 6.2), and then installed the new version 
again. It did the same.  Here is what I received:

1) lilo -v:
LILO version 21.4-3, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
2) lilo -v 4:
LILO version 21.4-3, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Released 06-May-2000 and compiled at 12:05:51 on May 31 2000.

Caching device /dev/hda (0x0300)
Caching device /dev/hda1 (0x0301)
Caching device /dev/hda2 (0x0302)
Caching device /dev/hda3 (0x0303)
Caching device /dev/hda4 (0x0304)
Caching device /dev/hda5 (0x0305)
Caching device /dev/hda6 (0x0306)
Caching device /dev/hda7 (0x0307)
Caching device /dev/hda8 (0x0308)
Caching device /dev/hdb (0x0340)
Caching device /dev/hdb1 (0x0341)
Caching device /dev/hdb2 (0x0342)
Caching device /dev/hdb3 (0x0343)
Caching device /dev/hdb4 (0x0344)
Caching device /dev/hdb5 (0x0345)
Caching device /dev/hdb6 (0x0346)
Caching device /dev/hdb7 (0x0347)
aching device /dev/hdb8 (0x0348)
Caching device /dev/sda (0x0800)
Caching device /dev/sda1 (0x0801)
Caching device /dev/sda2 (0x0802)
Caching device /dev/sda3 (0x0803)
Caching device /dev/sda4 (0x0804)
Caching device /dev/sda5 (0x0805)
Caching device /dev/sda6 (0x0806)
Caching device /dev/sda7 (0x0807)
Caching device /dev/sda8 (0x0808)
Caching device /dev/sdb (0x0810)
Caching device /dev/sdb1 (0x0811)
Caching device /dev/sdb2 (0x0812)
Caching device /dev/sdb3 (0x0813)
Caching device /dev/sdb4 (0x0814)
Caching device /dev/sdb5 (0x0815)
Caching device /dev/sdb6 (0x0816)
Caching device /dev/sdb7 (0x0817)
Caching device /dev/sdb8 (0x0818)
Caching device /dev/loop0 (0x0700)
Caching device /dev/loop1 (0x0701)
Caching device /dev/loop2 (0x0702)
Caching device /dev/loop3 (0x0703)
Caching device /dev/loop4 (0x0704)
Caching device /dev/loop5 (0x0705)
Caching device /dev/loop6 (0x0706)
Caching device /dev/loop7 (0x0707)

(I have one IDE (2GB) and 2 SCSI on the system.)

Also, I found that the size of /sbin/lilo is smaller than the one I compiled (the 
original
-rwxr-xr-x    1 root     root       195714 May 31 12:06 /tmp/lilo/lilo-21.4.3/lilo
-rwxr-xr-x    1 root     root        74096 Jun  1 07:36 /sbin/lilo

Jieming


-----Original Message-----
From:   Richard Bollinger [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, June 01, 2000 11:40 AM
To:     [EMAIL PROTECTED]
Cc:     linux raid mailing list
Subject:        Re: strange error with lilo: "open /tmp/dev.0: No such device"?

Whenever I made the same LILO upgrade, I found that I had to forcibly remove
the old LILO first (very carefully) or it would refuse to install itself;
though I got a error message indicating failure.  Odd your seeing no output
at all!  Have you tried "lilo -v"?

Rich B
----- Original Message -----
From: "Jieming Wang" <[EMAIL PROTECTED]>
To: "'Richard Bollinger'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: "linux raid mailing list" <[EMAIL PROTECTED]>
Sent: Thursday, June 01, 2000 9:17 AM
Subject: RE: strange error with lilo: "open /tmp/dev.0: No such device"?


> Hi Rich,
>
> 1) The version of lilo was 0.21-15 (came with Redhat 6.2);
> 2) /etc/lilo.conf
> boot=/dev/md0
> default=linux
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> image=/boot/vmlinuz-2.2.14-5.0
>         label=linux
>         root=/dev/md0
>         initrd=/boot/initrd-2.2.14-5.0_raid.img
>         read-only
> image=/root/vmlinuz-2.2.14-5.0
>         label=linux_ide
>         root=/dev/hda1
>         initrd=/boot/initrd-2.2.14-5.0.img
>         read-only
> 3) Output from /proc/mounts:
> /dev/root / ext2 rw 0 0
> /proc /proc proc rw 0 0
> automount(pid371) /misc autofs rw 0 0
> none /dev/pts devpts rw 0 0
> /dev/md2 /users ext2 rw 0 0
> /dev/md4 /var ext2 rw 0 0
>
> Also, I just downloaded the newer version of lilo, lilo-21.4.3.tar.gz
> (http://www.elliott-turbo.com/lilo/). After compiling/getting installed,
> lilo didn't complain anymore, but too quiet - it didn't generate any
output
> when I run lilo (with or without options).  I am not sure if I have to
> remove the older version before installing the new one.
>
> JW

Reply via email to