Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


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

Ext3 as module



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 20 Jan 2002, jbk wrote:

> if you compile this as a module be aware that the
> file system for your root partition cannot be
> compiled as a module..."

   This isn't entirely true.  I'd say something like, "The file system and 
drive interface for your root partition SHOULD NOT be compiled as modules."


> On my standard install of RH7.2  an 'lsmod' shows
> ext3 and jbd loaded as modules and in fstab '/' is
> mounted as an ext3 partition.

   Red Hat (and many other vendors) ship a kernel with very little 
compiled statically, and almost every option built as a module.  The 
installer builds an Initial RamDisk (initrd) with the modules for SCSI 
controllers, RAID, and non-ext2 filesystems, if you need them.

   In your case you'd need a command like:
# /sbin/mkinitrd --with=jbd --with=ext3 /boot/initrd-[kernel-version] \ 
 [kernel-version]

  You'd also have to have a line in your bootloader config file such as:
        initrd /boot/initrd-[kernel-version]

   All of this is unnecessary if you compile the options into your kernel, 
which is really the right way to do things.


- -- 
     -Matt

It's lonely at the bottom too, just more crowded.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Suovc8/WFSz+GKMRAlIRAJ4/XLsfrOZxjdUQgRluUnEFZNkccgCdGQdP
PvOj/uR6NYH37D0m125lWqc=
=Lb/1
-----END PGP SIGNATURE-----





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org