From: Joe Schulz <joe@spamfilter.de>
To: linux-kernel@vger.kernel.org
Subject: Problem spawning init from script
Date: Fri, 30 Apr 2004 09:21:39 +0200 [thread overview]
Message-ID: <c6suq3$ko7$1@sea.gmane.org> (raw)
Hello world,
for internal reasons I designed a custom boot procedure with two root
partitions. One is booted by default and a script is executed via the
"init=/sbin/initscript" kernel option.
The script restrieves some information and depending on that information
it decides whether the current boot should continue or some other
partition is being mounted and boot continues on that.
As the script involves the usage of USB storage, gpg, openssl, device
mapper and various other bits, it would make some pretty big and hard
to handle initrd so I decided to try it directly as described.
Infortunately when the script tries to exec'ute either one init proces or
the other at its end, the kernel always panics:
Kernel panic: Attempted to kill init!
Does that mean I MUST use initrd to be able to use such a script or is
there a way to get around this?
Hints appreciated,
Joe
next reply other threads:[~2004-04-30 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 7:21 Joe Schulz [this message]
2004-04-30 21:14 ` Problem spawning init from script Denis Vlasenko
2004-05-01 15:24 ` Joe Schulz
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='c6suq3$ko7$1@sea.gmane.org' \
--to=joe@spamfilter.de \
--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