[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: /usr/lib vs /usr/libexec

GOMBAS Gabor <gombasg@sztaki.hu> writes:

> On Tue, May 10, 2005 at 11:16:54AM +0200, Bernd Eckenfels wrote:
>> the bootloader does not need to access the root filesystem. It only loads
>> the kernel and the initrd from /boot.
> (I assume that /boot is on /. If not, the following still applies to
> /boot.)
> Well, grub _does_ access the filesystem directly so it needs explicit
> support for every filesystem you want to boot from. I think reiserfs is
> OK nowadays (I do not use it so I'm not sure). xfs + lilo (from the
> 	No, for root partition installations because the XFS superblock
> 	is written at block zero, where LILO would be installed. This is
> 	to maintain compatibility with the IRIX on-disk format, and will
> 	not be changed.

That only applies to the bootloader on the partition or the FS on the
drive directly. With partitions and the bootloader in the mbr that
should not matter. What I was talking about is using a block to store
the tail end of multiple files more efficiently. Didn't xfs do that?

> lvm, raid0, raid5: the boot loader must understand the lvm/raid
> descriptors to be able to determine where to load the kernel/initrd from
> (and in case of raid5, it has to be able to reconstruct the data using
> the parity disk if one of the non-parity chunks is inaccessible). AFAIK
> neither lilo nor Grub supports these.

It would be nice enough if it would work with a working raid. The
problem there (raid 0 and 5) is that it would need to gather the
scattered blocks from multiple devices.

> Gabor

Reply to: