mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@digeo.com, alistair@devzero.co.uk, cloos@jhcloos.com,
	elenstev@mesatop.com, jordan.breeding@attbi.com,
	maneesh@in.ibm.com, scole@lanl.gov, solarce@fallingsnow.net
Subject: Patch: 2.5.62 devfs shrink
Date: Tue, 25 Feb 2003 02:23:18 -0800	[thread overview]
Message-ID: <200302251023.CAA01067@adam.yggdrasil.com> (raw)

	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
changes:

	- 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
	  of places).

	- 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:

ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/smalldevfs-2.5.62-v10.patch

	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.

ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/devfs_helper-0.2.tar.gz


	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
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."

             reply	other threads:[~2003-02-25 10:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 10:23 Adam J. Richter [this message]
2003-02-25 21:50 ` Andrew Morton
2003-02-26  0:51   ` Dave Jones
2003-02-26  2:47 miltonm
2003-02-27 23:13 Adam J. Richter
2003-02-28  0:00 ` Miquel van Smoorenburg
2003-02-28  1:37 ` Andrew Walrond
2003-02-28  2:49 Adam J. Richter
2003-02-28  3:14 Adam J. Richter
2003-02-28  4:03 ` Miles Bader
2003-02-28  8:08 ` Andreas Jellinghaus
2003-02-28 12:50 ` Helge Hafting

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=200302251023.CAA01067@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=akpm@digeo.com \
    --cc=alistair@devzero.co.uk \
    --cc=cloos@jhcloos.com \
    --cc=elenstev@mesatop.com \
    --cc=jordan.breeding@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=scole@lanl.gov \
    --cc=solarce@fallingsnow.net \
    /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®