From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Paul Powell <moloch16@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linuxrc runs with PID 7
Date: Thu, 1 Feb 2001 10:01:03 +0100 (MET) [thread overview]
Message-ID: <200102010901.KAA05572@cave.bitwizard.nl> (raw)
In-Reply-To: <20010131192338.19211.qmail@web117.yahoomail.com> from Paul Powell at "Jan 31, 2001 11:23:38 am"
Paul Powell wrote:
> This is a followup question to my previous question
> "Why isn't init at PID 1."
>
> Previoulsy I was calling init from within linuxrc.
> Linuxrc was a sash script, so the sash script
> supposedly had PID 1. Now I've removed the script and
> have a C program for linuxrc.
>
> I'm still not running at PID 1 but at 7. The linuxrc
> program looks like:
>
> int main(int argc, char* argv[])
> {
> printf("PID = %i\n", getpid());
> }
>
> When I boot and linuxrc is executed, PID equals 7.
>
> Any ideas as to why this is and how I can run at PID
> 1?
Yes, I've noticed this too.
I concluded that to the kernel there is something magic about
"init=/bin/someprogram": The program doesn't get PID 1 anymore.
I used to have a script there fire up X and then exec init inside an
Xterm. I gave up on this after that junk started happening.
Oh, and Init refuses to be useful if it doesn't end up with PID 1.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 19:23 Linuxrc runs with PID 7 Paul Powell
2001-01-31 19:29 ` bert hubert
2001-02-01 9:01 ` Rogier Wolff [this message]
2001-02-01 10:24 ` Russell King
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=200102010901.KAA05572@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=moloch16@yahoo.com \
/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