mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Michael Schroeder <mls@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 early userspace init
Date: Wed, 12 Nov 2003 08:45:19 -0800	[thread overview]
Message-ID: <1068655518.14435.37.camel@camp4.serpentine.com> (raw)
In-Reply-To: <20031112115021.GA24875@suse.de>

On Wed, 2003-11-12 at 03:50, Michael Schroeder wrote:

> how about adding something like this to init/do_mounts.c?

It's not a bad idea, but surely you should be using the init= boot
parameter instead of hard-coding a path.

In any case, I don't think you should expect a patch to be accepted. 
There's not much point in further crufting up do_mounts.c in generic
kernels during 2.6, until do_mounts moves completely out of the kernel. 
Some people are happy enough with root=0:0, so there's not obviously a
consensus about which stopgap measure will do for now.

	<b


  reply	other threads:[~2003-11-12 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 11:50 Michael Schroeder
2003-11-12 16:45 ` Bryan O'Sullivan [this message]
2003-11-12 16:53   ` Michael Schroeder
2003-11-13 21:32   ` H. Peter Anvin
2003-11-14 16:39     ` Michael Schroeder

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=1068655518.14435.37.camel@camp4.serpentine.com \
    --to=bos@serpentine.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mls@suse.de \
    /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

Powered by JetHome