I've never understood how you manage kernel modules at boot time

[Jeff Liu]

Check /etc/modules.conf on old redhat version and /etc/modprobe.conf
on RHEL4, RHEL5, FC2 and newer.

Cheers,
Jeff Liu

On Mon, Feb 25, 2008 at 2:47 AM, Mike Oliver <moliver-fC0AHe2n+mcIvw5+aKnW+Pd9D2ou9A/h at public.gmane.org> wrote:
> I've been looking through the documentation for modprobe and modprobe.conf
>  and modprobe.d and so on and I just don't understand what's supposed
>  to be the correct, intelligent way to cause a kernel module to be loaded
>  at boot time.  The documentation for modprobe.conf and modprobe.d all
>  seems to be about configuring what *happens* when you invoke
>  "modprobe my-module", but doesn't seem to say anything about what
>  *causes* that command to be invoked at boot time.
>
>  Also I don't get how the "alias" command comes into this.  I've seen
>  various howtos that talk about putting an "alias" line into one of these
>  config files, but they don't explain just why the aliased name gets
>  probed in the first place.
>
>  --
>  The Toronto Linux Users Group.      Meetings: http://gtalug.org/
>  TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>  How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists