From: Rob Love <rml@ximian.com>
To: Ian Kent <raven@themaw.net>
Cc: Greg KH <greg@kroah.com>,
akpm@osdl.org, "Bradley W. Allen" <ULMO@Q.NET>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DevFS vs. udev
Date: Tue, 23 Dec 2003 21:03:57 -0500 [thread overview]
Message-ID: <1072231437.3826.3.camel@fur> (raw)
In-Reply-To: <Pine.LNX.4.33.0312240938450.890-100000@wombat.indigo.net.au>
On Tue, 2003-12-23 at 20:52, Ian Kent wrote:
> It certainly seems like a good project for a someone, such as myself, that
> is new to kernel development.
Please take no offense to this, but it is an awful project for someone
new to kernel development. Plenty of knowledgeable/semi-knowledgeable
kernel hackers looked at devfs and given up on it. Despite what some
people say about Richard, he is a good guy, and he did not succeed
either.
devfs is hard to get right and, worse, you will be starting with a bad
base of code that I would not want to touch with an 18.72 foot pole.
Greg, via udev, has made it so easy to just back up, slowly, and walk
away from devfs. devfs is not going anywhere in 2.6, I do not think,
but let sleeping piles of crap sleep and let's just jettison this thing
as soon as we can.
Just my two cents - I am warning you ;)
Rob Love
next prev parent reply other threads:[~2003-12-24 2:04 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 11:51 DevFS vs. udev Bradley W. Allen
2003-12-23 12:06 ` Duncan Sands
2003-12-23 12:12 ` Xavier Bestel
2003-12-23 12:37 ` Marcelo Bezerra
2003-12-23 13:02 ` Ed Tomlinson
2003-12-25 12:11 ` Kai Henningsen
2003-12-23 14:30 ` Paul Dickson
2003-12-23 23:23 ` Bradley W. Allen
2003-12-23 23:46 ` Brett
2003-12-24 4:01 ` alex.g.goddard.1
2003-12-23 16:19 ` Ian Kent
2003-12-23 17:34 ` Mark Mielke
2003-12-23 22:02 ` Greg KH
2003-12-23 22:13 ` Tomasz Torcz
2003-12-24 0:45 ` Martin Schlemmer
2003-12-24 1:07 ` Greg KH
2003-12-24 1:22 ` memory mapping help - oracle stack dumps Paul
2003-12-27 21:13 ` Francois Romieu
2003-12-24 1:28 ` DevFS vs. udev Martin Schlemmer
2003-12-23 21:59 ` Greg KH
2003-12-24 1:52 ` Ian Kent
2003-12-24 2:03 ` Rob Love [this message]
2003-12-24 2:21 ` Ian Kent
2003-12-24 2:22 ` Rob Love
2003-12-24 2:32 ` Stan Bubrouski
2003-12-24 2:39 ` Rob Love
2003-12-24 2:38 ` Andrew Morton
2003-12-24 3:41 ` viro
2003-12-24 11:33 ` Witukind
2003-12-24 4:13 ` Rusty Russell
2003-12-24 4:38 ` Stan Bubrouski
2003-12-24 11:15 ` Xavier Bestel
2003-12-24 13:44 ` Ian Soboroff
2003-12-24 14:17 ` Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 12:38 devfs " Måns Rullgård
2003-10-07 13:41 ` Andreas Jellinghaus
2003-10-07 14:07 ` Måns Rullgård
2003-10-07 14:23 ` Robert L. Harris
2003-10-07 14:29 ` Måns Rullgård
2003-10-07 16:06 ` Andreas Jellinghaus
2003-10-07 16:11 ` Måns Rullgård
2003-10-07 16:14 ` Robert L. Harris
2003-10-07 16:54 ` Hugo Mills
2003-10-07 17:19 ` Måns Rullgård
2003-10-07 17:47 ` Greg KH
2003-10-07 17:49 ` Greg KH
2003-10-07 17:58 ` Hugo Mills
2003-10-07 18:10 ` Greg KH
2003-10-09 13:43 ` Ian Kent
2003-10-09 20:54 ` Greg KH
2003-10-07 17:55 ` Greg KH
2003-10-14 13:51 ` Ian Kent
2003-10-17 4:34 ` Greg KH
2003-10-07 17:54 ` Greg KH
2003-10-07 14:01 ` tabris
2003-10-07 17:53 ` Greg KH
2003-10-07 18:24 ` viro
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=1072231437.3826.3.camel@fur \
--to=rml@ximian.com \
--cc=ULMO@Q.NET \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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