You wrote:
>
[..]
>
> 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.
No actual harm done, since the filesystems, when loaded as modules,
weren't really registred! The function "register_filesystem" (ought to have)
returned -EBUSY, so the only result was some wasted kernel memory :-(
>
> - Doesn't modprobe check, if filesystems or other drivers are already supported
> by the kernel ?
No, that's the responsibility of the individual module.
>
> - 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 ???
/proc/filesystems
Another solution is to use kerneld, which would never have loaded
the file system modules in the first place (plug, plug, plug :-) )
Bjorn <bj0rn@blox.se>
>
> 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
> ===========================================================