From: Chris Friesen <cfriesen@nortelnetworks.com>
To: David T Hollis <dhollis@davehollis.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: udev for dummies
Date: Thu, 11 Dec 2003 21:49:08 -0500 [thread overview]
Message-ID: <3FD92CA4.20606@nortelnetworks.com> (raw)
In-Reply-To: 1071183521.5900.36.camel@dhollis-lnx.kpmg.com
David T Hollis wrote:
> On Thu, 2003-12-11 at 17:16, J.A. Magallon wrote:
>>What am I missing / misunderstanding ?
> You may be overthinking it a bit. I just set up udev on my box and it's
> working quite well. It's not really intending to completely replace
> /dev, rather it provides a dynamic device structure based on hotplugged
> devices.
Greg can speak to this better than I, but udev is most certainly
intended to completely replace /dev. The thing is that not everything
exports the required information in /sys just yet.
If you start up udev and then run the script that comes with it that
parses all the pre-existing /sys entries, it will build a pretty decent
set of device nodes. Eventually it is intended that this will be
mounted at /dev, which could be an on-disk filesystem or else a
tmpfs-based one.
Once all the information is in /sys, then static /dev will go away
forever. (Which is good, since device numbers will be random in 2.7.)
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-12-12 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 22:16 udev for dummies J.A. Magallon
2003-12-11 22:59 ` David T Hollis
2003-12-12 2:49 ` Chris Friesen [this message]
2003-12-12 21:32 ` Greg KH
2003-12-12 4:43 ` Bob
2003-12-12 21:31 ` Greg KH
2003-12-14 18:36 ` 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=3FD92CA4.20606@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=dhollis@davehollis.com \
--cc=jamagallon@able.es \
--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.