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

[Robert P. J. Day]

On Mon, 25 Feb 2008, Mike Oliver wrote:

> Quoting Lennart Sorensen <lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org>:
>
> > Another way to make things load is with aliases such as:
> > alias char-major-195-* nvidia
> >
> > That means whenever something tries to open a /dev node for major 195
> > then load the module named nvidia to try and provide such a device.
>
> OK, this is the exact spot where neither the documentation nor anyone
> else ever seems to explain what's going on.  Exactly *why* does
> "something try to open a /dev node for major 195"?  How can I predict
> that that's going to happen -- or make it happen if it otherwise wouldn't --
> so
> that the alias command will make the module load?

i'm not sure if this is addressing your question, but you *seem* to be
asking exactly what it is that attempts to create a special device
file.  is *that* what you're asking?

rday
--



========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
--
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