From: Greg KH <greg@kroah.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev - please help me to understand
Date: Fri, 02 Jan 2004 20:23:16 +0000 [thread overview]
Message-ID: <20040102202316.GD4992@kroah.com> (raw)
In-Reply-To: <microsoft-free.87r7yiinaj.fsf@eicq.dnsalias.org>
On Fri, Jan 02, 2004 at 09:48:36PM +1000, Steve Youngs wrote:
> 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.
Ok, great. Then don't use it, I'm not forcing you to for 2.6 :)
> 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).
If you never have any hotpluggable devices, nor any need to move disks
around in your system, then you don't need udev.
Hope this helps,
greg k-h
-------------------------------------------------------
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=click
_______________________________________________
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 20:23 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
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 [this message]
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=20040102202316.GD4992@kroah.com \
--to=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).