On Thu, 2004-09-02 at 04:41 +1200, Oliver Hunt wrote:
> If the reiserfs module is compiled as, well, a module, rather than
> built in to the kernel you won't be able to boot.
>
> To load modules kernel needs access to modules, but as these reside on
> a reiserfs partition it needs to load the reiserfs module... hence it
> isn't possible to do that.
>
> Note: If you've other filesystems you can load them as modules, the
> important one is your root file system needs to be mounable without
> modules.
Maybe I am a bit confused here but I take the above statement to mean
one of two options
1) If I choose to compile the required file system modules "reiserfs"
monolithicaly into my 2.8.1 kernel I can NOT also allow the kernel to
see a module in initrd for reiserfs.ko? If this is what you mean .. my
question is why would the kernel even care? The mount request would be
called and the proper module (reiserfs) would be present to parse said
request. Please correct
2) If I choose to compile the kernel with reiserfs as a modules (ie not
monolithicaly in the kernel) then I will have issues as the kernel has
to have the driver reiserfs to mount the root file system to be able to
load /lib/modules/..../reiserfs.ko. If this is what you meant then
again, I am a bit confused. I thought that was the whole point of the
initrd image in that those modules (RAID, FC, USB, Network
etc....)required to get the OS to the state that it has a / they must be
compiled in the initrd which is called and referaned in grub or lilo.
Again, please correct me if I am wrong.
--
Thanks,
Jeremey Wise
[email protected]
All opinions or information expressed here are personal in nature and do
not reflect the official position of Agilysys Inc.
On Wed, 01 Sep 2004 15:40:12 EDT, "Wise, Jeremey" said:
> 2) If I choose to compile the kernel with reiserfs as a modules (ie not
> monolithicaly in the kernel) then I will have issues as the kernel has
> to have the driver reiserfs to mount the root file system to be able to
> load /lib/modules/..../reiserfs.ko. If this is what you meant then
> again, I am a bit confused. I thought that was the whole point of the
> initrd image in that those modules (RAID, FC, USB, Network
> etc....)required to get the OS to the state that it has a / they must be
> compiled in the initrd which is called and referaned in grub or lilo.
> Again, please correct me if I am wrong.
A somewhat subtle gotcha that I got bit by once - very bad things
happen if you try to load reiserfs off an ext2-formatted initrd image,
and your kernel doesn't have ext2 built in. (Feel free to substitute
any 2 filesystem formats - I actually got nailed by ext2/ext3)...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 2 Sep 2004 [email protected] wrote:
> A somewhat subtle gotcha that I got bit by once - very bad things
> happen if you try to load reiserfs off an ext2-formatted initrd image,
> and your kernel doesn't have ext2 built in. (Feel free to substitute
> any 2 filesystem formats - I actually got nailed by ext2/ext3)...
Well, in my case that's not the problem...
Marcos Marado
- --
/* *************************************************************** */
Marcos Daniel Marado Torres AKA Mind Booster Noori
http://student.dei.uc.pt/~marado - [email protected]
() Join the ASCII ribbon campaign against html email, Microsoft
/\ attachments and Software patents. They endanger the World.
Sign a petition against patents: http://petition.eurolinux.org
/* *************************************************************** */
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFBOH+3mNlq8m+oD34RAkhUAKC4+wdzMHzHqoRCecFGOXvAzF9NqwCg8DSh
EcL7JMsoNNgL3D534efCWsA=
=3soR
-----END PGP SIGNATURE-----