Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Curl <jcurlnews@arcor.de>
To: buildroot@busybox.net
Subject: [Buildroot] init not PID 1
Date: Sat, 09 Apr 2011 20:54:22 +0200	[thread overview]
Message-ID: <4DA0AB5E.7090005@arcor.de> (raw)
In-Reply-To: <4DA08A90.2020708@michaelburghart.de>

On 09/04/2011 18:34, Michael Burghart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> once again. I just found out that I cannot shutdown with init. It complains:
>
> init: must be run as PID 1
>
> (which is correct).
> But why is it not 1?
Did you not start it from the kernel, but perhaps from a shell script? 
The first process the kernel starts is PID 1.
> - -- 
> - --
> cheers
> - -micha-
> - --
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.16 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJNoIqQAAoJEEMkp/gkis19YmcIAKYCwJENHCCiqBeg9vtKLnAY
> GerMajKzrx6+LjsW8++YZKbNJUfxDUE+8gdGOUaWIB7e+tk1P1zLVSoXFeLe4lIa
> sP1A972DRDqSPBiy0ksuRTD4N5a5prmQtbmT3HV34xHTDHxR3bjy6dql9wvZ6wTj
> JmlupMbJ4f9VFMqrqyRn1abMw8EGyJFTe4vukU2FXpkUj6HZ3JpxIKY2QLG0i0rI
> 6fx+s/3399uGvL0ch7MZFGQGCpZZvFr/w0PJ79/28pip127RguO1/IBiVwsdW86v
> MMD2n6Y2wGmDVGBeY3zxj5e8G7waoqCdJ/0sItOO2RKifx6DmoYz2rT8kpNwv9E=
> =TbaH
> -----END PGP SIGNATURE-----
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110409/8986d5a1/attachment.p7s>

  reply	other threads:[~2011-04-09 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 16:34 [Buildroot] init not PID 1 Michael Burghart
2011-04-09 18:54 ` Jason Curl [this message]
2011-04-09 22:48   ` Michael Burghart
2011-04-10  9:54 ` Gerhard Heift

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=4DA0AB5E.7090005@arcor.de \
    --to=jcurlnews@arcor.de \
    --cc=buildroot@busybox.net \
    /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