Charles Steinkuehler wrote:
> > Only thing I'd possibly like to do in Oxygen is to move
> > /var/boot/modules to /lib/modules/boot (the standard location, I
> > understand).
>
> I settled on putting my boot-time modules in /boot/lib/modules, following
> the layout of my HDD machines, which create a /boot partition for stuff
> required to bootstrap the system. Where did /lib/modules/boot come from?
In modules.conf(5), it says:
[...snip...]
DEFAULT CONFIGURATION
If the configuration file '/etc/modules.conf' is missing,
or if any directive is not overridden, the following
defaults are assumed:
depfile=/lib/modules/`uname -r`/modules.dep
path[boot]=/lib/modules/boot
[...snip...also of note:]
path[fs]=/lib/modules/`uname -r`/fs
path[net]=/lib/modules/`uname -r`/net
[...snip...]
path[fs]=/lib/modules/`kernelversion`/fs
path[net]=/lib/modules/`kernelversion`/net
[...snip...]
path[fs]=/lib/modules/default/fs
path[net]=/lib/modules/default/net
[...snip...]
path[fs]=/lib/modules/fs
path[net]=/lib/modules/net
With a nice clean-up of modules, I can forsee a tree like this:
/lib/modules/boot/* (in root.lrp)
/lib/modules/2.2.16/* (in a modules.lrp)
/lib/modules/2.2.19/* (in an alternate modules.lrp)
...and so forth. However, be wary of symbolic links; I don't think that
busybox insmod follows them, but in any case, busybox and GNU, symbolic
links are a problem.
I also noted recently in the busybox list, someone said that he used
modprobe to generate modules.dep (in a build environment) then used a
shell script to analyze modules.dep and create the appropriate module
load in the appropriate order. Thoughts?
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
