On Thu, May 02, 2002 at 04:49:48PM +0200, Michael Meskes wrote:
> I see. But AFAICT ext2 is compiled into the kernel and not as module,
> so I guess it will always be mounted as ext2, or did I get that wrong?
IIRC, the only filesystem that is compiled into the "Official" Debian
kernels is cramfs. The rest of the necessary modules are loaded in the
initrd image. The 'mkinitrd' script relies upon the filesystem being
specified in the /etc/fstab file, which makes the use of 'auto'
undoable, at least during kernel installation.
Why is "auto" fs-type nice? Backwards compatibility for kernels
w/different abilities. i.e. When /etc/fstab is auto, the kernel can
pick out ext3 or ext2 on its own, so kernels w/o ext3 support can still
mount root and allow you to repair discs, filesystems, etc.
OK. Have you looked at /etc/mkinitrd/modules?
# /etc/mkinitrd/modules: Kernel modules to load for initrd.
#
# This file should contain the names of kernel modules and their
# arguments (if any) that are needed to mount the root file system,
# one per line. Comments begin with a `#', and everything on the
# line after them are ignored.
#
# You must run mkinitrd(8) to effect this change.
#
# Examples:
#
# ext2
# wd io=0x300
If this doesn't work for you, I'm not sure what the problem would be.
--
Chad Walstrom <chewie@wookimus.net> | a.k.a. ^chewie
http://www.wookimus.net/ | s.k.a. gunnarr
Attachment:
pgpguGWuykJ3r.pgp
Description: PGP signature