From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: devfs and udev
Date: Wed, 08 Oct 2003 02:03:28 +0200 [thread overview]
Message-ID: <yw1x3ce4wq7j.fsf@users.sourceforge.net> (raw)
In-Reply-To: <20031007232706.GA3621@kroah.com> (Greg KH's message of "Tue, 7 Oct 2003 16:27:06 -0700")
Greg KH <greg@kroah.com> writes:
> Hey look, documentation, a presentation, and wow, a statement saying
> that the code sucks, and is merely a proof of concept, and that it will
I never meant to say that udev never will be a viable solution. I
also understand now that devfs has problems that nobody is willing
solve. Thus the marking as obsolete may be justified. However, the
statement that it has been obsoleted *by* udev, is, IMHO, a little
bold.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-10-08 0:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 13:17 devfs and udev Bradley Chapman
2003-10-07 13:32 ` Måns Rullgård
2003-10-07 18:28 ` insecure
2003-10-07 18:44 ` viro
2003-10-07 19:41 ` Greg KH
2003-10-07 20:47 ` insecure
2003-10-07 20:52 ` Greg KH
2003-10-07 21:17 ` Chris Meadors
2003-10-07 21:48 ` Greg KH
2003-10-08 7:30 ` Andreas Jellinghaus
2003-10-08 12:07 ` [2.6 patch] document that udev isn't yet ready Adrian Bunk
2003-10-07 21:27 ` devfs and udev Måns Rullgård
2003-10-07 21:37 ` Greg KH
2003-10-07 22:01 ` Måns Rullgård
2003-10-07 22:12 ` Bryan O'Sullivan
2003-10-07 22:49 ` Måns Rullgård
2003-10-07 23:27 ` Greg KH
2003-10-08 0:03 ` Måns Rullgård [this message]
2003-10-09 22:09 ` bill davidsen
2003-10-13 20:15 ` Tom Rini
2003-10-07 20:57 ` David Lang
2003-10-08 22:34 ` H. Peter Anvin
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=yw1x3ce4wq7j.fsf@users.sourceforge.net \
--to=mru@users.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