All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Art Boulatov <art@ksu.ru>, linux-kernel@vger.kernel.org
Subject: Re: pivot_root & linuxrc problem
Date: Thu, 15 Mar 2001 22:41:25 +0000	[thread overview]
Message-ID: <20010315224125.C7500@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3AB0C09A.1020505@ksu.ru> <Pine.LNX.4.33.0103152143320.928-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0103152143320.928-100000@mikeg.weiden.de>; from mikeg@wen-online.de on Thu, Mar 15, 2001 at 10:11:55PM +0100

On Thu, Mar 15, 2001 at 10:11:55PM +0100, Mike Galbraith wrote:
> On Thu, 15 Mar 2001, Art Boulatov wrote:
> 
> > How can I "exec /sbin/init" from "/linuxrc", whatever it is,
> > if "linuxrc" does not get PID=1?
> >
> > Actually, why does NOT "linuxrc" get PID=1?
> 
> That's the question.. the first task started gets pid=1, and when
> that is true, exec /sbin/init has no problem.  What else is your
> system starting?.. it must be starting something.

Linux always forks from PID1 before executing /linuxrc automagically.
Check init/main.c.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-03-15 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 13:16 pivot_root & linuxrc problem Art Boulatov
2001-03-15 21:11 ` Mike Galbraith
2001-03-15 22:41   ` Russell King [this message]
2001-03-16  8:54     ` Mike Galbraith
2001-03-16 12:34       ` Art Boulatov
2001-03-16 14:05       ` union mounts WAS: " Art Boulatov
2001-03-16 17:37         ` Guest section DW
2001-03-16 23:33       ` Bernd Eckenfels
2001-03-17 10:54         ` Mike Galbraith

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=20010315224125.C7500@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=art@ksu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.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 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.