Re: Controlling which modules are loaded at boot
On 2005-07-10, Doofus <doofus@bulldoghome.com> wrote:
> Dell Inspiron
> sarge/2.4.27
>
> Not strictly a laptop question this, but...
> The last time I spent my quality time playing with debian this subject
> mostly came down to the contents of /etc/modules. I've just compiled a
> new kernel and although it's highly modular and I've emptied
> /etc/modules, all manner of guff is auto-loaded that I really just want
> to load manually as and when needed -
>
> Can someone tell me where things have changed and what I should be doing
> to prevent auto-loading of anything I choose (or what I should be
> reading). At first glance it seems to be a mixture of the hotplug
> subsystem and some new hardware discovery utility? Does /etc/modules
> even have a worthwhile function anymore[?]
I'm not qualified to tell you what you should do, but I have just
put Sarge on an old PC which had been running Woody, and this is
what I have done.
I compiled a kernel without hotplug (and kmod) support and put
"exit 0" at the beginning of /etc/init.d/discover. Hotplug could
also be disabled this way as well.
Before doing all this I saved a copy of the output of lsmod so I
could refer to it when adding modules to /etc/modules.
Howard E.
Reply to: