On 13.02.2011 17:02, Paul Goyette wrote: > On Sun, 13 Feb 2011, Jean-Yves Migeon wrote: > >> ... >> For order of preference, see module(7): >> >> The loader will look first for a built-in module with the specified >> name that has not been disabled (see module_unload() below). If a >> built-in module with that name is not found, the list of modules >> prepared by the boot loader is searched. If the named module is >> still not found, an attempt is made to locate the module within the >> file system. > > There should be one additional qualification here. > > Searching for modules within the file system can only occur after > the root file system has been mounted by the initialization code.
Sorry, this part is from module(9). For module(7), there is a mention in the CAVEATS section: If an attempt is made to boot the operating system from a file system for which the module is not built into the kernel, the boot may fail with the message ``Cannot mount root, error 79''. On certain architectures (currently, i386 and amd64), one may be able to recover from this error by using the ``load xxxfs'' command before trying to boot. This command is only available on newer bootloaders. Wording seems a bit redundant, so I condensed this into: Index: man/man9/module.9 =================================================================== RCS file: /cvsroot/src/share/man/man9/module.9,v retrieving revision 1.26 diff -u -p -u -p -r1.26 module.9 --- man/man9/module.9 9 Jan 2011 05:05:10 -0000 1.26 +++ man/man9/module.9 13 Feb 2011 16:39:01 -0000 @@ -175,7 +175,8 @@ If a built-in module with that .Fa name is not found, the list of modules prepared by the boot loader is searched. If the named module is still not found, an attempt is made to locate the -module within the file system. +module within the file system, provided it has been mounted by the +initialization code. .Pp The .Fa flags -- Jean-Yves Migeon jeanyves.mig...@free.fr