From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel setup() and initrd problems
Date: 14 Mar 2003 11:12:06 -0800 [thread overview]
Message-ID: <b4t9i6$eon$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0303131051160.7342-100000@chaos.physics.uiowa.edu
Followup to: <Pine.LNX.4.44.0303131051160.7342-100000@chaos.physics.uiowa.edu>
By author: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
In newsgroup: linux.dev.kernel
>
> I think whoever came up with that just got the idea of pivot_root wrong.
> The idea was to get rid of the initrd special case. It should be possible
> to do the following, though I didn't work out the details:
>
> Tell the kernel that our root dev is /dev/ram and give it an initrd which
> isn't really a classical initrd (with /linuxrc on it), but instead has a
> /sbin/init which is similar to the linuxrc above.
>
It *is* possible, but you need to pass "root=/dev/ram0" to the kernel,
for backwards compatibility reasons. That will incidentally make it
run /sbin/init, not /linuxrc, unless you pass init=/linuxrc as well.
See SuperRescue for an example of working use of pivot_root.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-03-14 19:01 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 [this message]
2003-03-14 19:27 ` Chris Friesen
2003-03-14 19:43 ` H. Peter Anvin
2003-03-14 20:04 ` Chris Friesen
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='b4t9i6$eon$1@cesium.transmeta.com' \
--to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.