|| ||"Adam J. Richter" <firstname.lastname@example.org>|
|| ||Patch: 2.5.62 devfs shrink|
|| ||Tue, 25 Feb 2003 02:23:18 -0800|
|| ||email@example.com, firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org|
Here is an update to my patch to shrink devfs for linux-2.5.62.
The patch is a net deletion of 2407 lines. It contains the following new
- Maneesh Soni submitted a patch for operation with the
read-copy-update code, which was extremely good timing,
as that code apparently got integrated into 2.5.62.
- Fixed a bug reported by Alistair Strachan where
pseudo-terminals could not be allocated by non-super-user
processes (devfs needed to set CAP_DAC_OVERRIDE in a couple
- Restore the devfs=nomount option, to accomodate a distribution
compatability problem reported by Steven Cole. devfs=nomount
suppresses the effect CONFIG_DEVFS_MOUNT--that is, mounting
of /dev before the kernel invokes /sbin/init. Note: perhsps
we should eliminate CONFIG_DEVFS_MOUNT entirely. I'll have
to check to see if it is needed by systems that boot directly
to a hardware device rather than to an initial ramdisk.
Presumably because of the size of all of the "-" lines in the
patch, the linux-kernel mailing list filters it out, so I'll just post
a URL for it:
Also, here is the URL for the latest devfs_helper user level
program (version 0.2, unchanged). It is a reduced functionality
replacement for devfsd.
I'll also describe my "to do" list for this software, in case
anyone spots something I've forgotten:
- Submit a patch to the -mm kernels, as Andrew has been
kind enough to distribute this change in his -mm kernels.
- Write a small FAQ list on moving from old devfs.
- Remove CONFIG_DEVFS_MOUNT?
- Probably request integration after linux-2.7.0.
Adam J. Richter __ ______________ 575 Oroville Road
email@example.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."
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/