Alan Wilter Sousa da Silva wrote on Mon, Sep 30, 2002 at 01:08:34PM -0300 : > > >tunefs -j /dev/hdxx > then, > >mkinitrd /boot/initrd-2.4.18-6mdk.img 2.4.18-6mdk > >reeboot > Note that you have to have (a link) > initrd=/boot/initrd.img > in your lilo.conf file.
Because he didn't give us enough information, it is a good assumption
that he has not modified his lilo.conf, which means it's using the
symlink instead of the real file, so your comment was right on the
money.
> On 28 Sep 2002, Rick Friedman wrote:
> > I want to convert my filesystems from ext2 to ext3. However, currently,
> > kernel support for ext3 is built in as module support. I'm running
> > kernel 2.4.19 which I built from the source.
> > My question is, does ext3 support need to be built directly into the
> > kernel itself rather than as a module?
To the original poster, that's your choice. Two roads to take:
1) If you make it a module, the system has to be configured specially to
be able to load the module to actually access the filesystems. Since
the module resides normally on one of the filesystems, it has to load it
*BEFORE* it can read the filesystem (where the module resides). The
solution is to make a ram disk image that the kernel can access (because
ram disk support is built in). This is what the initrd does and it is
created with the mkinitrd command and its options.
2) If you build it in to the kernel, then you are set as it can read the
filesystems as soon as it is finished starting up.
I rarely build my own kernels anymore. The stock Mandrake kernel comes
with so many drivers precompiled as modules that it's usually easier to
add a line to /etc/modules.conf to make some module autoload rather than
compile a whole new kernel (or even a module for that matter).
Blue skies... Todd
--
MandrakeSoft USA http://www.mandrakesoft.com
Easy things should be easy, and hard things should be possible.
--Larry Wall
Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk
msg58326/pgp00000.pgp
Description: PGP signature
