I wrote:
> The Fedora kernels have an initrd, a RAM disk that gets mounted as a
> root filesystem early in the boot process. This contains the modules
> needed for the system to boot [1], and the mount command that can mount
> filesystems by label [2]. This means that with the Fedora kernels,
> specifying the real root filesystem is done with userspace tools.
>
> Without an initrd, the kernel mounts the root filesystem itself. It
> doesn't know about ext3 labels.
>
> You can either investigate mkinitrd, or carry on the way you're doing
> things.
Juan L. Pastor asked:
> Where does the /boot/initrd-2.6.6-1.435.2.3custom.img file and the line
> initrd /initrd-2.6.6-1.435.2.3custom.img
> enter in this story? Are they not supposed to make the translation of
> the label name into the real filesystem?
They're made by mkinitrd.
As the name suggests, they need to be custom-made for the kernel you're
running. Is that really the kernel you're running? (Any reason why
you're not on 2.8.1?) Otherwise they won't work...
James.
--
E-mail address: james | Legacy (adj):
@westexe.demon.co.uk | an uncomplimentary computer-industry epithet that
| means 'it works'.
| -- Anthony DeBoer
