public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: devfs vs. udev
Date: Tue, 07 Oct 2003 14:38:27 +0200	[thread overview]
Message-ID: <yw1xad8dfcjg.fsf@users.sourceforge.net> (raw)


I noticed this in the help text for devfs in 2.6.0-test6:

	  Note that devfs has been obsoleted by udev,
	  <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
	  It has been stripped down to a bare minimum and is only provided for
	  legacy installations that use its naming scheme which is
	  unfortunately different from the names normal Linux installations
	  use.

Now, this puzzles me, for a few of reasons.  Firstly, not long ago,
devfs was spoken of as the way to go, and all drivers were rewritten
to support it.  Why this sudden change?  Secondly, that link only
leads me to a package describing itself as an experimental
proof-of-concept thing, not to be used for anything serious.  How can
something that incomplete obsolete a working system like devfs?
Thirdly, udev appears to respond to hotplug events only.  How is it
supposed to handle device files not corresponding to any physical
device?  Finally, I quite liked the idea of a virtual filesystem for
/dev.  It reduced the clutter quite a bit.  As for the naming scheme,
it could easily be changed.


-- 
Måns Rullgård
mru@users.sf.net

             reply	other threads:[~2003-10-07 12:38 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 12:38 Måns Rullgård [this message]
2003-10-07 13:41 ` devfs vs. udev 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
  -- strict thread matches above, loose matches on Subject: below --
2003-12-23 11:51 DevFS " 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:28           ` Martin Schlemmer
2003-12-23 21:59 ` Greg KH
2003-12-24  1:52   ` Ian Kent
2003-12-24  2:03     ` Rob Love
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

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=yw1xad8dfcjg.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