On Monday 31 March 2008 01:25:49 pm Eben King wrote:
> On Mon, 31 Mar 2008, Paul M Foster wrote:
> > On Sun, Mar 30, 2008 at 11:25:24PM -0400, Eben King wrote:
> >> There's either a kernel flag for it supplied by the bootloader, or the
> >> kernel expects / to be mounted when it's invoked, I can't figure out
> >> which. /etc/fstab has an entry for / , but it must be dummy, since by
> >> that time / is already mounted. The kernel needs support for /'s
> >> filesystem, either modular (and in the initrd) or in the kernel. If the
> >> module to access / is on /, you have a nice catch-22.
> >
> > I don't think so. Once configured properly, grub knows how to load your
> > *boot* filesystem. The entry in /etc/fstab takes over, loading the
> > *root* filesystem once grub has loaded the boot filesystem and booted the
> > machine.
>
> What's in the boot filesystem? I have no initrd, so that isn't necessary.
A friend asked the Linux guru at his workplace about this. This guy talked
about the requirement for the correct filesystem module to be stored
in the "/lib" directory of the initial RAM disk (initrd). He
surmised that the Suse distribution builds initrd during the install
process and only includes the file system it needs to load onto the
partition specified. In this case, the "other" filesystem wouldn't
exist as a module to be loaded from initrd.
This indicates that the problem may be distribution-dependent.
Don
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:33:28 EDT