Ataraid and Lilo version: upgrade needed

antvr · 04-15-2003, 03:45 PM

found here:

http://brun.dyndns.org/pub/linux/lilo

Changes from version 21.7.5 to 22.0 (29-Aug-2001) John Coffman [released 9/27]
...
- Add HPT370 controller (major device 114)

To Sharky and all: Redhat installs an old Lilo and if you move from the 2.4.20-8 kernel to the 2.4.20-9 you can't run /sbin/lilo anymore. It complains about "Sorry, dont'know how to handle device..0x72... which is my /boot partition.

I'll try tonight with the new lilo...

antvr · 04-16-2003, 03:16 AM

OK, good news!

lilo 22.5.1 solved my boot problem.
My boot partition on /dev/ataraid/dop8 is now reachable !

sharkyr0lz · 04-16-2003, 06:22 AM

I know,... but rethat use an old version.

(They want to stop including lilo inside redhat,... don't know why)

Whell,... the new readme based in your posts are ready

I will upload here: http://ocr812manager.sf.net/rh9_hpt37x.tar.gz (i need to delete that file as soon as get some mirrors because sf doesn't want binaries inside the webs of the projects)

RHrulz · 04-16-2003, 07:37 AM

Sharky,

Thanks for the new README, but is there an error?

Step 2.5.3 "Update /etc/lilo.conf (ONLY IF YOU USE LILO)
Edit /etc/lilo.conf"

Step 2.5.4 "Update /etc/grub.conf (ONLY IF YOU USE LILO):
Edit /etc/lilo.conf"

Do these contradict each other? If you use LILO dont you have only lilo.conf, and if you use GRUB dont you only have grub.conf?

Should step 2.5.3 be for LILO and step 2.5.4 be for all GRUB?

sharkyr0lz · 04-16-2003, 08:22 AM

Quote:

Originally posted by RHrulz
Sharky,

Thanks for the new README, but is there an error?

Step 2.5.3 "Update /etc/lilo.conf (ONLY IF YOU USE LILO)
Edit /etc/lilo.conf"

Step 2.5.4 "Update /etc/grub.conf (ONLY IF YOU USE LILO):
Edit /etc/lilo.conf"

Do these contradict each other? If you use LILO dont you have only lilo.conf, and if you use GRUB dont you only have grub.conf?

Should step 2.5.3 be for LILO and step 2.5.4 be for all GRUB?

yep,... i "copy & paste" a lot :P

sharkyr0lz · 04-16-2003, 09:34 AM

Well it's corrected now.