mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org, 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: Re: Patch: 2.5.62 devfs shrink
Date: Tue, 25 Feb 2003 13:50:32 -0800	[thread overview]
Message-ID: <20030225135032.7c9663da.akpm@digeo.com> (raw)
In-Reply-To: <200302251023.CAA01067@adam.yggdrasil.com>

"Adam J. Richter" <adam@yggdrasil.com> wrote:
>
> 	Here is an update to my patch to shrink devfs for linux-2.5.62.

Adam, could you please provide a description of the incompatibilities between
this implementation and the present one?  For both kernel and userspace.

And would you also please provide a list of operations which people need to
perform to migrate existing setups to the new code.

And should I drop the below patch?

diff -puN init/do_mounts.c~devfs-fix init/do_mounts.c
--- 25/init/do_mounts.c~devfs-fix	2003-01-16 19:39:56.000000000 -0800
+++ 25-akpm/init/do_mounts.c	2003-01-16 19:39:56.000000000 -0800
@@ -853,11 +853,6 @@ void prepare_namespace(void)
 {
 	int is_floppy;
 
-#ifdef CONFIG_DEVFS_FS
-	sys_mount("devfs", "/dev", "devfs", 0, NULL);
-	do_devfs = 1;
-#endif
-
 	md_run_setup();
 
 	if (saved_root_name[0]) {

_


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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 10:23 Adam J. Richter
2003-02-25 21:50 ` Andrew Morton [this message]
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=20030225135032.7c9663da.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=adam@yggdrasil.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®