Chaning Bootloaders, from Grub to Lilo

MasterC · 04-07-2003, 08:48 PM

Just to let you know...

I'm gonna research tonight, however:
1. I've definitely ran lilo while using ext2 filesystems. Definitely. Furthermore, lilo stands for "Linux Loader", how odd it would be for the "Linux Loader" to not load a standard linux filesystem (more than that, THE linux filesystem...).

2. LBA. Linux used to have that limitation. However, since (I am probably slightly off) 22.3 (at least) LBA has been a part of LILO.

Cool

MasterC · 04-07-2003, 09:27 PM

Ok, from the man page:

Code:

       -L     Generate 32-bit Logical Block Addresses instead  of
              C:H:S  addresses, allowing access to all partitions
              on disks with more than 1024 cylinders.

Still looking for info on ext2...

MasterC · 04-07-2003, 09:30 PM

Again, from the man:

Code:

INCOMPATIBILITIES
       lilo is known to have problems with  the  reiserfs  intro-
       duced  with  the  2.2.x kernels, unless the file system is
       mounted with the 'notail' option.  This incompatibilty has
       been resolved with reiserfs 3.6.18 and lilo 21.6.

So... It would appear that it works fine with ext2 (for several reasons, one if which is that it's not addressed in the "known issues" nor it is in the "todo" (which one would think that if the Linux Loader is having problems with THE native linux filesystem would be high on the TODO list..).

Cool

MasterC · 04-07-2003, 09:36 PM

Something everyone should read, fire up your xterm:
cd /usr/doc/lilo (then press tab). Read the INCOMPAT file. It describes the old LBA problems, how they've been fixed, and what you can do to fix them.

If /usr/doc/lilo(tab) doesn't exist, use locate to find your documentation directory and then read up on the lilo.

HTH

Cool

tktim · 04-08-2003, 06:12 PM

Redhat Quote:

LILO versus GRUB
In general, LILO works similarly to GRUB except for three major differences:

· It has no interactive command interface.

· It stores information about the location of the kernel or other operating system it is to load on the MBR.

· It cannot read ext2 partitions.

The first point means the command prompt for LILO is not interactive and only allows one command with arguments.
The last two points mean that if you change LILO's configuration file or install a new kernel, you must rewrite the Stage 1 LILO boot loader to the MBR by using the following command:

/sbin/lilo -v –v

This method is more risky than the method used by GRUB because a misconfigured MBR leaves the system unbootable. With GRUB, if the configuration file is erroneously configured, it will default to its command line interface where the user can boot the system manually.

======

· GRUB can read ext2 partitions. This functionality allows GRUB to access its configuration file, /boot/grub/grub.conf, every time the system boots, eliminating the need for the user to write a new version of the first stage boot loader to MBR when configuration changes are made. The only time a user would need to reinstall GRUB on the MBR is if the physical location of the /boot partition is moved on the disk.

MasterC · 04-08-2003, 07:12 PM

I see, and agree

I guess the wording, or mis-wording is what I disagree with. It cannot read ext2 partitions is quite misleading, unless one knows how grub works and what exactly they are comparing at that point

Thanks for the clarification though, maybe you should suggest a re-wording to RH about their docs

Cool