I compiled two kernels at a time for 1.2.13 and for 1.3.35. One for each kernel
version, which has all support for filesystems of interest (e.g hpfs.o) built
into the kernel, and one for each version, with module support for these
filesystems, except for ext2, that I need while booting.
Then I created a 'rc.module' script invoked by 'rc.S' at boot time, where I
check for existing module versions in '/lib/modules/x.x.xx' for the currently
booting kernel, and load them, if found, using 'modprobe -v <module basename>'.
It happend to me, that when I booted the kernels with all filesystems BUILT-IN,
this script 'rc.module' naturally found the corresponding modules for the
relevant kernel version as well, and loaded them SUCCESSFULLY with modprobe!!!
At least lsmod showed all modules as loaded.
Here my questions for the experts:
- Does it make any harm to my filesystems when I do have a filesystem build
into the kernel and ADDITIONALLY load a module with the very same filesystem?
Do they interfere ?
BTW, this is possible with SCSI support (e.g. st.o), as well.
- Doesn't modprobe check, if filesystems or other drivers are already supported
by the kernel ?
- Ok, I use rmmod in the meantime, because I don't want to waste memory as
well. But, is there a way to find out at BOOT TIME, IF a filesystem is
already BUILT INTO the booting kernel ???
Thanks in advance,
Michael
-- =========================================================== The opinions expressed above are solely those of the author and are not necessarily those of Schering. =========================================================== NAME: Dr. Michael Grimm ADDRESS: Schering AG EMAIL: michael.grimm@schering.de PCH-TCH PHONE: +49-30-468-5477 D-13342 Berlin FAX: +49-30-4691-6741 Germany ===========================================================