linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric <ebrower@usa.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [Q] pivot_root and initrd
Date: Mon, 05 Nov 2001 16:05:34 -0800	[thread overview]
Message-ID: <3BE7294E.5050905@usa.net> (raw)
In-Reply-To: <p05100304b80cbe9cf127@[10.128.7.49]>

Andreas wrote:

>> linuxrc does 'exec chroot', chroot does 'exec sh', 
>> sh does 'exec init'.
>> Thus init should end up with the same pid as linuxrc.

Exactly, but if init does not have PID 1, we fail.  Kai,
it works for HPA because of the magic kernel command line
incantation:

	root=/dev/ram0 (apparently with or without devfs)

Without this, init does NOT get PID 1 and therefore it
all goes south rather quickly.  The pivot_root syscall
is handy, but its operation under 2.4.x is disingenuous
at best.

E


       reply	other threads:[~2001-11-06  0:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <p05100304b80cbe9cf127@[10.128.7.49]>
2001-11-06  0:05 ` Eric [this message]
     [not found] <p05100328b7fb8dcb9473@[207.213.214.37]>
2001-10-23 21:54 ` [Q] pivot_root and initrd Eric
2001-10-24  0:20   ` Werner Almesberger
2001-10-23 17:42 Eric
2001-10-23 18:14 ` H. Peter Anvin
2001-10-23 19:54   ` bill davidsen
2001-10-23 19:59     ` Rik van Riel
2001-10-23 20:21       ` bill davidsen
2001-10-23 21:00         ` H. Peter Anvin
2001-10-23 20:37   ` Werner Almesberger
2001-10-23 20:46     ` Richard B. Johnson
2001-10-23 20:52       ` H. Peter Anvin
2001-10-23 21:05         ` Richard B. Johnson
2001-10-23 21:06           ` H. Peter Anvin
     [not found] <p05100300b7f2b3b94b17@[10.128.7.49]>
2001-10-17 18:34 ` Eric
2001-10-17 21:17   ` H. Peter Anvin
2001-10-27 12:45   ` Kai Henningsen
2001-11-05 21:52     ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2001-10-17  2:16 Eric
2001-10-17  3:30 ` H. Peter Anvin

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=3BE7294E.5050905@usa.net \
    --to=ebrower@usa.net \
    --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;
as well as URLs for NNTP newsgroup(s).