From: Christoph Hellwig <hch@lst.de>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] mark devfs obsolete
Date: Sat, 16 Aug 2003 13:41:02 +0200 [thread overview]
Message-ID: <20030816114102.GA6026@lst.de> (raw)
The person listed as maintainer hasn't touched it for alomost a year
and after that only some odd fixes and my interface fixes went it.
With udev we also have a proper replacement.
--- 1.166/MAINTAINERS Thu Aug 14 21:17:45 2003
+++ edited/MAINTAINERS Sat Aug 16 11:56:20 2003
@@ -558,10 +558,7 @@
S: Maintained
DEVICE FILESYSTEM
-P: Richard Gooch
-M: rgooch@atnf.csiro.au
-L: linux-kernel@vger.kernel.org
-S: Maintained
+S: Obsolete
DIGI INTL. EPCA DRIVER
P: Digi International, Inc
--- 1.28/fs/Kconfig Thu Aug 14 02:20:32 2003
+++ edited/fs/Kconfig Sat Aug 16 12:03:57 2003
@@ -762,7 +762,7 @@
programs depend on this, so everyone should say Y here.
config DEVFS_FS
- bool "/dev file system support (EXPERIMENTAL)"
+ bool "/dev file system support (OBSOLETE)"
depends on EXPERIMENTAL
help
This is support for devfs, a virtual file system (like /proc) which
@@ -780,6 +780,13 @@
Note that devfs no longer manages /dev/pts! If you are using UNIX98
ptys, you will also need to enable (and mount) the /dev/pts
filesystem (CONFIG_DEVPTS_FS).
+
+ Note that devfs has been obsoleted by udev,
+ <http://http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
+ It has been striped down to a bare minimum and is only provided for
+ legacy installations that use it's naming scheme which is
+ unfortunately different from the names normal Linux installations
+ use.
If unsure, say N.
next reply other threads:[~2003-08-16 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 11:41 Christoph Hellwig [this message]
2003-08-18 17:51 ` [PATCH] mark devfs obsolete Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 18:40 Christoph Hellwig
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=20030816114102.GA6026@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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