On Thu, 2004-08-05 at 19:51, netmask wrote: > >> Also, you must use initrd to use labels in fstab > > > > This is not true. An initrd is only _required_ if you have not compiled > > into the kernel a module necessary for boot. > > I'm sorry, but that's just not the case. > > You /must/ have a ram disk to use a label on your boot partition. Think about > it for a second, it makes perfect sense. > > http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-kernel-initrd.html > > If the system uses the ext3 file system, a SCSI controller, or uses labels to > reference partitions in /etc/fstab, an initial RAM disk is needed. The initial > RAM disk allows a modular kernel to have access to modules that it might need > to boot from before the kernel has access to the device where the modules > normally reside. Please note that part of what I said was "not compiled into the kernel a module necessary for boot." Then you said "allows a modular kernel to have access to modules that it might need to boot". Compiling those modules into the kernel obviates the need for loading a module. I regularly build custom kernels and never use an initrd with them. I have never tried specifying a partition label for the boot, but I know I have mounted partitions via labels with no initrd. -- C. Linus Hicks <lhicks@xxxxxxxxx>
