From: "Christian Tröster" <please.see.sig@gmx.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: what is the status of devfs?
Date: Fri, 9 Jul 2004 13:17:45 +0200 [thread overview]
Message-ID: <200407091317.46128.please.see.sig@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0407081035280.32470@localhost.localdomain>
Hi Robert!
Am Donnerstag, 8. Juli 2004 16:38 schrieb Robert P. J. Day:
> 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 assume you are talking about 2.6.x :)
See Documentation/Changes line 115:
"DevFS has been obsoleted in favour of udev
(http://www.kernel.org/pub/linux/utils/kernel/hotplug/)"
Bye, Christian
--
| c dot troester at gmx dot de | PGP-Id: FA006C74 |
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-09 11:17 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 [this message]
2004-07-09 12:05 ` Mark Chambers
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=200407091317.46128.please.see.sig@gmx.de \
--to=please.see.sig@gmx.de \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).