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

[Kristian Erik Hermansen]

On Sun, Feb 24, 2008 at 11:47 PM, 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
>  nd 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.

If you really want to learn about the internals of Linux and security,
you should try Hardened Linux from Scratch (HLFS).  The HLFS tutorial
covers the older devfs and newer udev systems...
http://www.linuxfromscratch.org/hlfs/view/unstable/glibc-2.6/chapter07/udev.html
-- 
Kristian Erik Hermansen
--
"It has been just so in all my inventions. The first step is an
intuition--and comes with a burst, then difficulties arise. This thing
gives out and then that--'Bugs'--as such little faults and
difficulties are called--show themselves and months of anxious
watching, study and labor are requisite before commercial success--or
failure--is certainly reached" -- Thomas Edison in a letter to
Theodore Puskas on November 18, 1878
--
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