From: "Mark Chambers" <markc@mail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>,
"Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: what is the status of devfs?
Date: Fri, 9 Jul 2004 08:05:18 -0400 [thread overview]
Message-ID: <003301c465ad$04db1230$0301a8c0@chuck2> (raw)
In-Reply-To: Pine.LNX.4.60.0407081035280.32470@localhost.localdomain
>
> probably should send this to the main kernel list, but in playing
> around, i noticed that DEVFS_FS is labelled as both OBSOLETE and NEW,
> but in the Kconfig file, it depends on EXPERIMENTAL.
>
> it seems a bit inconsistent for anything to be simultaneously
> EXPERIMENTAL, NEW and OBSOLETE, no?
>
I found the following in udev-FAQ:
Q: Why was devfs marked OBSOLETE if udev is not finished yet?
A: To quote Al Viro (Linux VFS kernel maintainer):
- it was determined that the same thing could be done in userspace
- devfs had been shoved into the tree in hope that its quality will
catch up
- devfs was found to have fixable and unfixable bugs
- the former had stayed around for many months with maintainer
claiming that everything works fine
- the latter had stayed, period.
- the devfs maintainer/author disappeared and stoped maintaining
the code.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-09 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 14:38 what is the status of devfs? Robert P. J. Day
2004-07-09 11:17 ` Christian Tröster
2004-07-09 12:05 ` Mark Chambers [this message]
2004-07-09 12:18 ` Robert P. J. Day
2004-07-09 12:49 ` David Woodhouse
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='003301c465ad$04db1230$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.