From: Kurt Wall <kwall@kurtwerks.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: devfs to be obsloted by udev?
Date: Tue, 2 Sep 2003 19:56:56 -0400 [thread overview]
Message-ID: <20030902235656.GD17232@kurtwerks.com> (raw)
In-Reply-To: <3F54A9F4.4020705@wmich.edu>
Quoth Ed Sweetman:
>
> i didn't think udev was responsible for the lack of development, I
> assumed that was due to the lack of devfs adoption in the main stream.
>From here, devfs seemed simply to orphaned. I know lots of people
using it, but it's getting kinda crufty...
Kurt
--
Leibowitz's Rule:
When hammering a nail, you will never hit your finger if you
hold the hammer with both hands.
next prev parent reply other threads:[~2003-09-02 23:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 14:09 devfs to be obsloted by udev? Ed Sweetman
2003-09-02 18:20 ` Greg KH
2003-09-02 14:32 ` Ed Sweetman
2003-09-02 18:44 ` Greg KH
2003-09-02 23:56 ` Kurt Wall [this message]
2003-09-02 20:19 ` Bartlomiej Zolnierkiewicz
2003-09-03 9:38 ` Justin Cormack
2003-09-03 18:41 ` Greg KH
2003-09-03 19:06 ` Bryan O'Sullivan
2003-09-03 19:17 ` Sam Ravnborg
2003-09-03 21:09 ` Bryan O'Sullivan
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=20030902235656.GD17232@kurtwerks.com \
--to=kwall@kurtwerks.com \
--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