From: Bill Davidsen <davidsen@tmr.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.16
Date: Tue, 28 Mar 2006 17:30:04 -0500 [thread overview]
Message-ID: <4429B8EC.3040008@tmr.com> (raw)
In-Reply-To: <20060323212945.GE22727@stusta.de>
Adrian Bunk wrote:
> On Thu, Mar 23, 2006 at 12:33:13PM +0900, Kalin KOZHUHAROV wrote:
>> Greg KH wrote:
>>> They are the same "delete devfs" patches that I submitted for 2.6.12 and
>>> 2.6.13 and 2.6.14 and 2.6.15. It rips out all of devfs from the kernel
>>> and ends up saving a lot of space. Since 2.6.13 came out, I have seen
>>> no complaints about the fact that devfs was not able to be enabled
>>> anymore, and in fact, a lot of different subsystems have already been
>>> deleting devfs support for a while now, with apparently no complaints
>>> (due to the lack of users.)
>>>
>>> It's also been over 8 months past the date when we said we would delete
>>> devfs from the kernel tree in the file,
>>> Documentation/feature-removal-schedule.txt, and over one and one half
>>> years since we publicly announced to the world that devfs would be
>>> removed from the kernel tree. So, I think people have had plenty of
>>> advance notice that this was going to happen by now :)
>>>
>>> Please pull from:
>>> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/devfs-2.6.git/
>>> or if master.kernel.org hasn't synced up yet:
>>> master.kernel.org:/pub/scm/linux/kernel/git/gregkh/devfs-2.6.git/
>>>
>>> I've posted all of these patches before, but if people really want to look at them, they can be found at:
>>> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-05-devfs/
>>>
>>> Also, if people _really_ are in love with the idea of an in-kernel
>>> devfs, I have posted a patch that does this in about 300 lines of code,
>>> called ndevfs. It is available in the archives if anyone wants to use
>>> that instead (it is quite easy to maintain that patch outside of the
>>> kernel tree, due to it only needing 3 hooks into the main kernel tree.)
>> OK, I completely agree with that, but shouldn't there be left something in
>> the Documentation at least? A note like "devfs was superseded by udev since
>> 2.6.?? and was completely removed since 2.6.??" or something along the same
>> line of thought? It will just make life easier for people finding lots of
>> old pages and HOWTOs on the Net mentioning devfs.
>>
>> Unfortunately I couldn't find a proper place for that note...
>> Maybe a new file Documentation/filesystems/devfs.txt instead of the
>> Documentation/filesystems/devfs directory present now?
>
> There's already a note in Documentation/Changes.
I really don't think that's the most likely place people would look. The
suggested few lines in a file with a dead-obvious name would undoubtedly
save people time, as they would look there first.
No complaint about getting rid of the feature, but there are lots of
mentions of devfs, putting in a definitive explanation wouldn't be out
of place.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2006-03-28 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 21:23 [GIT PATCH] Remove devfs from 2.6.16 Greg KH
2006-03-20 21:32 ` Randy.Dunlap
2006-03-20 21:34 ` H. Peter Anvin
2006-03-20 21:40 ` Randy.Dunlap
2006-03-20 22:02 ` Greg KH
2006-03-20 23:58 ` Olivier Galibert
2006-03-21 0:05 ` Dave Jones
2006-03-21 7:15 ` Arjan van de Ven
2006-03-21 12:47 ` Olivier Galibert
2006-03-23 3:33 ` Kalin KOZHUHAROV
2006-03-23 21:29 ` Adrian Bunk
2006-03-28 22:30 ` Bill Davidsen [this message]
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=4429B8EC.3040008@tmr.com \
--to=davidsen@tmr.com \
--cc=bunk@stusta.de \
--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