All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael do N. Pereira" <gotrooted@pop.com.br>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Future devfs plans
Date: Sun, 25 Jul 2004 21:21:43 -0300	[thread overview]
Message-ID: <1090801303.19924.15.camel@osts> (raw)
In-Reply-To: <200407261445.i6QEjAS04697@freya.yggdrasil.com>

On Mon, 2004-07-26 at 11:45, Adam J. Richter wrote:
> 	Do not delete devfs.
> 
> 	devfs allows drivers to be loaded when user level programs
> need them,


I think it can asnwer your question:

Q: But wait, I really want udev to automatically load drivers when they
   are not present but the device node is opened.  It's the only reason I
   like using devfs.  Please make udev do this.
A: No.  udev is for managing /dev, not loading kernel drivers.

Q: Oh come on, pretty please.  It can't be that hard to do.
A: Such a functionality isn't needed on a properly configured system. All
   devices present on the system should generate hotplug events, loading
   the appropriate driver, and udev will notice and create the
   appropriate device node.  If you don't want to keep all drivers for your
   hardware in memory, then use something else to manage your modules
   (scripts, modules.conf, etc.)  This is not a task for udev.

It was taken from http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ


 Rafael.


  parent reply	other threads:[~2004-07-26  0:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 14:45 Future devfs plans Adam J. Richter
2004-07-26  0:00 ` Jim Gifford
2004-07-26  0:17   ` Ed Sweetman
2004-07-26  0:29     ` Lee Revell
2004-07-26  0:59     ` Lee Revell
2004-07-26 18:09     ` Adrian Bunk
2004-07-26 21:44       ` Ed Sweetman
2004-07-26 23:01         ` CaT
2004-07-27 21:24         ` Lee Revell
2004-07-27 22:35           ` Adrian Bunk
2004-07-27 22:39             ` Lee Revell
2004-07-26  0:21 ` Rafael do N. Pereira [this message]
2004-07-26  0:31 ` Ramón Rey Vicente
2004-07-26  0:35   ` Ramón Rey Vicente
2004-07-26  5:35   ` Andreas Jellinghaus
2004-07-26  6:58     ` Erik Steffl
2004-07-27 16:55       ` David Bryson
2004-07-27 18:44         ` Erik Steffl

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=1090801303.19924.15.camel@osts \
    --to=gotrooted@pop.com.br \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.