From: Greg KH <gregkh@suse.de>
To: "Mathieu Therrien, VE2TMQ" <ve2tmq@rac.ca>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Patch: Remove devfs from 2.6.13
Date: Thu, 13 Oct 2005 16:53:58 -0700 [thread overview]
Message-ID: <20051013235358.GA4443@suse.de> (raw)
In-Reply-To: <434E9D48.70306@rac.ca>
On Thu, Oct 13, 2005 at 01:45:44PM -0400, Mathieu Therrien, VE2TMQ wrote:
> Hello every one! I read this document : <a
> class="moz-txt-link-freetext"
> href="http://lwn.net/Articles/151174/">http://lwn.net/Articles/151174/</a><br>
> but I don't understand the reason to remove devfs from the kernel
> selection.
Please search the archives for the reasons why. In short:
- It had unfixable bugs.
- It was unmaintained for many years.
- It has been marked OBSOLETE for about 1 1/2 years
- It has been documented that it would be removed for over a
year.
- It puts naming policy into the kernel, where it is not needed.
- It is not LSB compliant.
- there are numerous userspace solutions that do the same thing,
in much better ways.
thanks,
greg k-h
parent reply other threads:[~2005-10-13 23:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <434E9D48.70306@rac.ca>]
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=20051013235358.GA4443@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=ve2tmq@rac.ca \
/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