From: Steve Youngs <sryoungs@bigpond.net.au>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: linux-hotplug-devel@lists.sourceforge.net, Greg KH <greg@kroah.com>
Subject: udev - please help me to understand
Date: Fri, 02 Jan 2004 11:48:36 +0000 [thread overview]
Message-ID: <microsoft-free.87r7yiinaj.fsf@eicq.dnsalias.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Hi Greg!
I've been looking at this "udev" thingy and I can't for the life of me
see why I'd need it. There doesn't appear to be _any_ advantages of
using udev in my present situation.
No, I don't use devfs.
I have zero hot-pluggable devices (that might change somewhere in the
distant future, but for now I don't have any). And never in my wildest
dreams could I ever imagine running out of device numbers.
Reading through the documentation that I've found about udev, your
main points seem to be about:
- udev vs devfs
- running out of device major/minor numbers
- not having to worry about major/minor numbers
For me, the first point is moot because I don't use devfs. The second
point is just plain ridiculous, there is just _no_ way that it could
happen (remember that I'm talking about my own situation).
As for the third point, well, I don't worry about device numbers now.
In the years that I've been using Linux (since 2.0.something) you
could probably count the number of times I've had to worry about
major/minor numbers on the fingers of one hand. The _only_ times
have been on those incredibly rare occasions when I've needed to
create a new device file in /dev/.
So, Greg, is there _any_ reason why I'd want to be using udev?
I have other questions, but they can wait until I know whether or not
I need the thing in the first place.
Thank you very much for your time and patience.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2004-01-02 11:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 11:48 Steve Youngs [this message]
2004-01-02 13:00 ` udev - please help me to understand Michael Buesch
2004-01-03 3:52 ` Steve Youngs
[not found] ` <20040102123636.GA29909@mark.mielke.cc>
2004-01-02 20:21 ` Greg KH
2004-01-02 20:39 ` T'aZ
2004-01-03 3:56 ` Steve Youngs
2004-01-02 20:23 ` Greg KH
2004-01-03 1:00 ` J.A. Magallon
2004-01-03 12:54 ` Witukind
2004-01-03 21:56 ` Greg KH
2004-01-04 16:02 ` Kevin P. Fleming
2004-01-03 3:28 ` Steve Youngs
2004-03-29 15:39 ` T'aZ
2004-03-29 15:39 ` J.A. Magallon
2004-03-29 15:39 ` Steve Youngs
2004-03-29 15:39 ` Steve Youngs
2004-03-29 15:39 ` Steve Youngs
2004-03-29 15:40 ` Witukind
2004-03-29 15:40 ` Greg KH
2004-03-29 15:42 ` Kevin P. Fleming
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=microsoft-free.87r7yiinaj.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).