public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Greg KH <greg@kroah.com>
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: Mon, 02 Feb 2004 21:13:41 +0200	[thread overview]
Message-ID: <1075749221.6931.23.camel@nosferatu.lan> (raw)
In-Reply-To: <20040202052100.GA21753@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]

On Mon, 2004-02-02 at 07:21, Greg KH wrote:
> 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 :)
> 

Whoa, stop the horses :)  I do not want to start another devfs/udev
argument 8)

As I said - this feature _does_ work of autoloading the module _if_
the device node and alias exists.  If the node is deleted however it
does not.  So this tells me there functionality is half way there,
and I was wondering if it could be completed without too much extra
overhead.

You can check the mail to Rusty for more what I mean (hopefully it
comes through correctly).

> > 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.
> 

Stupid question - is there a complete list of all these aliases?


Thanks,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-02-02 19:13 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
2004-02-02 18:12   ` Jamie Lokier
2004-02-02 19:14     ` Martin Schlemmer
2004-02-02 19:13   ` Martin Schlemmer [this message]
  -- 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=1075749221.6931.23.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --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