From: Steve Youngs <sryoungs@bigpond.net.au>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev - please help me to understand
Date: Sat, 03 Jan 2004 03:52:38 +0000 [thread overview]
Message-ID: <microsoft-free.87n095k7sp.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <200401021400.29569.mbuesch@freenet.de> (Michael Buesch's message of "Fri, 02 Jan 2004 14:00:19 +0100")
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
|--==> "MB" == Michael Buesch <mbuesch@freenet.de> writes:
MB> _You_ have to decide if you need udev or don't.
Precisely why I sent the post, to find out whether or not I need it,
or if there are any benefits (for me) to using it. I don't, there
aren't, so I won't. Pretty easy decision, actually. :-)
And just so there's no confusion, I'm not against the concept of
udev, I think it is a _very_ good idea. I just don't have a need for
it right now, that's all.
--
|---<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 prev parent reply other threads:[~2004-01-03 3:52 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 [this message]
[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.87n095k7sp.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
--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).