public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hpa@transmeta.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: initrd help -- umounts root after pivot_root
Date: 31 Oct 2003 13:59:09 -0800	[thread overview]
Message-ID: <bnulvd$fps$1@cesium.transmeta.com> (raw)
In-Reply-To: 1067604362.5526.15.camel@tweedy.ksc.nasa.gov

	From: H. Peter Anvin <hpa@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Comment-To: Bob Chiodini <robert.chiodini-1@ksc.nasa.gov>
Disclaimer: Not speaking for Transmeta in any way, shape, or form.
Copyright: Copyright 2003 H. Peter Anvin - All Rights Reserved

Followup to:  <1067604362.5526.15.camel@tweedy.ksc.nasa.gov>
By author:    Bob Chiodini <robert.chiodini-1@ksc.nasa.gov>
In newsgroup: linux.dev.kernel
> 
> John,
> 
> It does not appear that the kernel(s) will support the root fs on
> tmpfs.  Looking through the init kernel code:  It boils down to a block
> device with real major and minor number or NFS.
> 

Baloney.  See the SuperRescue CD, for example, for a distro which uses
exactly this.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

  parent reply	other threads:[~2003-10-31 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31 12:46 initrd help -- umounts root after pivot_root Bob Chiodini
2003-10-31 18:13 ` Maciej Zenczykowski
2003-10-31 21:59 ` H. Peter Anvin [this message]
2003-11-03 13:47   ` Bob Chiodini
  -- strict thread matches above, loose matches on Subject: below --
2003-10-31  0:18 John R Moser
2003-10-31 18:47 ` Chris Lingard

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='bnulvd$fps$1@cesium.transmeta.com' \
    --to=hpa@transmeta.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