public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	rml@ximian.com, stan@ccs.neu.edu, Jari.Soderholm@edu.stadia.fi
Subject: Re: DEVFS is very good compared to UDEV
Date: Wed, 24 Dec 2003 13:40:27 -0500	[thread overview]
Message-ID: <20031224184027.GA5836@thunk.org> (raw)
In-Reply-To: <1072236794.1743.244.camel@cube>

On Tue, Dec 23, 2003 at 10:33:15PM -0500, Albert Cahalan wrote:
> How quickly we forget where those names came from!
> Richard Gooch originally used the traditional names.
> Linus ordered the names changed as a condition for
> acceptance into the kernel. Of course, that led to
> devfsd being a requirement, which kind of took away
> the whole point of using devfs.
> 
> The Linus-approved names made devfs a pain to use,
> so few people used devfs and fewer helped out.
> 

And this is **precisely** why putting the device names in the kernel
via devfs was such a mistake.  Naming is policy, and should not be in
the kernel.  Yes, the new style names were Linus's idea, but the
problem was that while he has extremely good taste with respect to
code, unfortunately he had exquisitely bad taste with respect to devfs
device names.  And when one person's taste (even if that person is
Linus) about names can cause such grief, it should be an object lesson
about why putting that kind of user-visible naming policy in the
kernel is such a bad idea.

> Richard is only to blame for his inability to spell
> /dev/disk correctly. For that, he belongs in "jail"
> with a "j". It was enough of an eyesore to make me
> give up on devfs.

Shouldn't that be "jail" with a "g"?  (As in "gaol"?  :-)

					- Ted


  reply	other threads:[~2003-12-24 18:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24  3:33 DEVFS is very good compared to UDEV Albert Cahalan
2003-12-24 18:40 ` Theodore Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-23 21:20 Jari Soderholm
2003-12-23 21:50 ` Stan Bubrouski
2003-12-23 22:01 ` Rob Love
2003-12-23 22:21   ` Hua Zhong
2003-12-23 22:30     ` Rob Love
2003-12-23 23:00       ` Hua Zhong
2003-12-23 23:03         ` Rob Love
2003-12-23 23:14         ` Greg KH
2003-12-23 23:26         ` viro
2003-12-24  0:00           ` Mike Fedyk
2003-12-23 23:03     ` grundig
2003-12-23 23:05     ` viro
2003-12-24  2:24     ` Paul Jackson
2003-12-23 22:24 ` Felipe Alfaro Solana
2003-12-27 11:57 ` Ian Kent

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=20031224184027.GA5836@thunk.org \
    --to=tytso@mit.edu \
    --cc=Jari.Soderholm@edu.stadia.fi \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ximian.com \
    --cc=stan@ccs.neu.edu \
    /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