public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: module-init-tools/udev and module auto-loading
Date: Sun, 1 Feb 2004 21:21:00 -0800	[thread overview]
Message-ID: <20040202052100.GA21753@kroah.com> (raw)
In-Reply-To: <1075674718.27454.17.camel@nosferatu.lan>

On Mon, Feb 02, 2004 at 12:31:58AM +0200, Martin Schlemmer wrote:
> Hi
> 
> A quick question on module-init-tools/udev and module auto-loading ...
> lets say I have a module called 'foo', that I want the kernel to
> auto-load.

Wait, stop right there.  When do you want the module autoloaded?

If you want it loaded when the device is plugged in, then great, the
hotplug scripts will do that.

If you want the module loaded when you try to access the /dev node, then
see the FAQ about udev for that :)

> Then a distant related issue - anybody thought about dynamic major
> numbers of 2.7/2.8 (?) and the 'alias char-major-<whatever>-* whatever'
> type modprobe rules (as the whole fact of them being dynamic, will make
> that alias type worthless ...)?

Yes, it will make the char-major-* stuff worthless, however the distro
I use has not used that style of alias for years, why would yours?  :)

Rusty had it correct in that you need to try to load for the type of
module:
	alias eth1 tulip
	alias usb-controller usb-ohci
and so on.  That's the much better way.

thanks,

greg (I hate kmod) k-h

  parent reply	other threads:[~2004-02-02  5:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 22:31 module-init-tools/udev and module auto-loading Martin Schlemmer
2004-02-02  0:10 ` Rusty Russell
2004-02-02 19:02   ` Martin Schlemmer
2004-02-03  0:55     ` Rusty Russell
2004-02-03  4:55       ` Martin Schlemmer
2004-02-03 17:48       ` Martin Schlemmer
2004-02-03 19:33         ` viro
2004-02-03 20:47           ` Martin Schlemmer
2004-02-03 20:53             ` viro
2004-02-03 21:34               ` Martin Schlemmer
2004-02-04  1:22         ` Rusty Russell
2004-02-04  2:04           ` viro
2004-02-04  3:43             ` Rusty Russell
2004-02-02  5:21 ` Greg KH [this message]
2004-02-02 18:12   ` Jamie Lokier
2004-02-02 19:14     ` Martin Schlemmer
2004-02-02 19:13   ` Martin Schlemmer
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02  7:20 "Andrey Borzenkov" 
2004-02-02  7:34 ` Greg KH
2004-02-03 15:00 "Andrey Borzenkov" 

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040202052100.GA21753@kroah.com \
    --to=greg@kroah.com \
    --cc=azarah@nosferatu.za.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox