From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: initrd in 2.4.19
Date: Fri, 3 May 2002 10:14:13 +1000 [thread overview]
Message-ID: <20020503001413.GT9043@zax> (raw)
In-Reply-To: <D769D33A5A2FBD4381E1F6030D28DBFA01029C92@hq-ex-6>
On Thu, May 02, 2002 at 10:13:30AM -0700, Brian Kuschak wrote:
>
> > I want to use pivot_root, so I don't use the special /linuxrc running
> > code. Instead I use "init=/linuxrc" as part of the command line. If
> > you do this your first script should work fine (pivot follwed by
> > chroot). But to be honest, I don't chroot. I don't think it's
> > necessary.
>
> Using init=/linuxrc allows my first script to work.
>
> However, it's a bit restrictive: if I want to override the usual boot
> sequence and get the kernel to mount the real root and drop into a shell I
> can't use this method. With the 'old-style' script, I can set
> "init=/bin/bash". These get applied AFTER /linuxrc terminates. If I use
> your method, I can't do that.
Remember that any kernel command line options that the kernel doesn't
recognize get passed to init - as environment variables if they
contain a "=" and as command line arguments otherwise. So it's fairly
easy to invent a new parameter to control the "real" init and have
your linuxrc interpret it and act accordingly.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-03 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 17:13 initrd in 2.4.19 Brian Kuschak
2002-05-03 0:14 ` David Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-01 17:08 Brian Kuschak
2002-05-02 11:27 ` Brad Parker
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=20020503001413.GT9043@zax \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.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).