From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Subject: Patch: linux-2.5.59/fs/devfs shrink
Date: Fri, 17 Jan 2003 19:02:14 -0800 [thread overview]
Message-ID: <200301180302.TAA04272@baldur.yggdrasil.com> (raw)
An updated version of my patch to shrink devfs by replacing
its filesystem operations with code derived from ramfs is now FTPable
from the following URL. Christoph Hellwig got my fs/devfs/util.c
changes integrated in to 2.5.59 along with some other cleanups of his,
so there no longer any change to util.c in my patch, and now only one
line is changed in include/linux/fs/devfs_fs_kernel.h. The patch is a
net deletion of 2447 lines.
ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/smalldevfs-2.5.59-v8.patch
Also, there is a new 0.2 version of devfs_helper (partial
devfsd replacment) FTPable the following URL. The only difference is
a fix to a bug where an extra character was being copied in rules that
involved expanding regular expression matches.
ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/devfs_helper-0.2.tar.gz
Although I'd personally like to see my patch integrated into
2.5, the only bug that I think it fixes is extremely obscure (a module
unload race for character devices that probably nobody will hit), and
nothing else relies on it. I'm happy to keep people updated by
posting new versions of this patch as necessary until 2.7 opens up,
although, as I said, I also wouldn't mind seeing it integrated
earlier.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-01-18 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 3:02 Adam J. Richter [this message]
2003-01-18 5:08 Adam J. Richter
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=200301180302.TAA04272@baldur.yggdrasil.com \
--to=adam@yggdrasil.com \
--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
all inboxes | Powered by JetHome®