Hi,
Thanks for this. I am familiar with initrd images but never understood
their purpose. Now I do :) This indeed was the problem: apparently
the kernel did not have ext3 compiled into it nor did this particular
system have an initrd to load the ext3 module before mounting the root
file system. A
mkinitrd initrd-2.4.20-20.8 2.4.20-20.8
solved the problem. Thanks alot!
Paul
->>In response to your message<<-
--received from Alexander Rink--
>
> I remember that i had the same problem when using ext3fs as a module and no
> initrd. This is because the kernel can only load the ext3 module AFTER the
> root partition is mounted and the only way to mount it is using ext2
> (compatibility). Without the compabilitiy you wouldnt be able to mount your
> root partition in this case. Just compile ext3fs into your kernel (doesnt
> make sense to make a initrd just containing a module u need for your root
> partition). Hope this helps...
>
> Greetings
> Alex
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Paul Yeatman (858) 534-9896 [EMAIL PROTECTED]
==================================
==Proudly brought to you by Mutt==
==================================
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
