From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, kai@tp1.ruhr-uni-bochum.de
Subject: Re: Kernel setup() and initrd problems
Date: Fri, 14 Mar 2003 15:04:07 -0500 [thread overview]
Message-ID: <3E7235B7.5050407@nortelnetworks.com> (raw)
In-Reply-To: 3E7230D2.7010309@zytor.com
H. Peter Anvin wrote:
> Chris Friesen wrote:
>
>>
>> Below is the script that I used to pivot from a standard ramdisk (for
>> with
>> the infrastructure is already in place in our build environment) to a
>> tmpfs
>> filesystem. This requires no changes to the boot args.
> ... which means that you either have boot args or rdev so that /dev/ram0
> is the root filesystem (or it wouldn't work.)
Yes, but after the pivot, /dev/ram0 isn't the real filesytem, its tmpfs
mounted at /. Isn't that what the original poster was talking about,
where the root on the final running system is not the same as what the
machine was booted with?
Maybe I'm just confused.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-03-14 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 8:42 Kernel setup() and initrd problems Oliver Tennert
2003-03-13 17:16 ` Kai Germaschewski
2003-03-13 18:05 ` Kevin P. Fleming
2003-03-14 19:12 ` H. Peter Anvin
2003-03-14 19:27 ` Chris Friesen
2003-03-14 19:43 ` H. Peter Anvin
2003-03-14 20:04 ` Chris Friesen [this message]
2003-03-14 20:42 ` H. Peter Anvin
2003-03-14 20:53 ` Chris Friesen
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=3E7235B7.5050407@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=hpa@zytor.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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