public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: module-init-tools/udev and module auto-loading
Date: Sun, 1 Feb 2004 23:34:51 -0800	[thread overview]
Message-ID: <20040202073451.GA23181@kroah.com> (raw)
In-Reply-To: <E1AnYNT-0002Tp-00.arvidjaar-mail-ru@f17.mail.ru>

On Mon, Feb 02, 2004 at 10:20:15AM +0300, "Andrey Borzenkov"  wrote:
> 
> so there are cases when "action on access" makes sense.

Yes, there are cases like this where that might make sense.  However
there's no real way for udev itself to solve those cases.  You will have
to rely on some other method to do this (script to load module, making
the /dev node yourself, script to make dev node and then access it which
causes kmod to load the module, etc.)

thanks,

greg k-h

  reply	other threads:[~2004-02-02  7:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02  7:20 module-init-tools/udev and module auto-loading "Andrey Borzenkov" 
2004-02-02  7:34 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-03 15:00 "Andrey Borzenkov" 
2004-02-01 22:31 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

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=20040202073451.GA23181@kroah.com \
    --to=greg@kroah.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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