From: Michael Buesch <mbuesch@freenet.de>
To: Steve Youngs <sryoungs@bigpond.net.au>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev - please help me to understand
Date: Fri, 02 Jan 2004 13:00:19 +0000 [thread overview]
Message-ID: <200401021400.29569.mbuesch@freenet.de> (raw)
In-Reply-To: <microsoft-free.87r7yiinaj.fsf@eicq.dnsalias.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 02 January 2004 12:48, Steve Youngs wrote:
> 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.
Yea, _you_ can't imagine this. :) But Kernel developers can... .
> 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).
I don't think so.
Every new device needs a unique number, that _no other_ device uses.
As more and more devices are developed, we are running out of device
numbers. (well, that may take a while with 32-bit device numbers,
but it may appear so).
> So, Greg, is there _any_ reason why I'd want to be using udev?
(Hm, I'm not Greg, but...)
Because it's cool. :)
No, you're right.
I am not going to use udev or devfs on my server
for example. The reason is quite simple. This server will be running
linux-2.4 until it dies and I will never add some more device to it.
So there is no point of using udev or devfs on it. I know the hardware,
create all nodes for it and it runs (without all the problems devfs
and udev still provide).
But on my main Computer I am going to use udev, because I love it's
flexibility.
_You_ have to decide if you need udev or don't. Nobody else can decide
it for you.
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQE/9WtsFGK1OIvVOP4RAoD2AKCMOAVWp226hzMQxju9Yo7t8uO7FQCguSJe
7XksJs4zqwCeFyBQkcBOn98=chS9
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-02 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 11:48 udev - please help me to understand Steve Youngs
2004-01-02 13:00 ` Michael Buesch [this message]
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=200401021400.29569.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sryoungs@bigpond.net.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;
as well as URLs for NNTP newsgroup(s).