Messages in this thread |  | | Date | Sun, 26 Nov 2000 19:45:43 -0700 | From | "Jeff V. Merkey" <> | Subject | Re: initdata for modules? |
| |
On Mon, Nov 27, 2000 at 10:45:34AM +1100, Keith Owens wrote: > On Sun, 26 Nov 2000 17:01:35 -0700, > "Jeff V. Merkey" <jmerkey@vger.timpanogas.org> wrote: > >insmod ppp_deflate (should trigger load of all these modules). I > >know it's works this way if there's a modules.dep file laying > >around, but it would be nice for it to work this way without > >needing the external text file. > > There is a clean split between modprobe and insmod, modprobe is the > high level command that does all the fancy checking for inter module > dependencies, handling aliases and extracting options from > modules.conf. insmod is the low level command that does exactly what > you tell it to do, no more, no less. The only smarts that insmod has > is the ability to take a module name without '/' and find it using the > patchs in modules.conf. That split between high and low level commands > is too useful to contaminate. > > modules.conf already supports "above" and "below" commands for > non-standard dependencies. The problem of not having a module.dep on > the first boot of a new kernel was addressed in kernel 2.4.0-test5 or > thereabouts, make modules_install runs depmod to build modules.dep > ready for the first boot.
Good. I am glad this is being addressed.
Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |