From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8)
Date: Sun, 19 Oct 2003 00:46:04 +0200 [thread overview]
Message-ID: <200310190046.04897.arekm@pld-linux.org> (raw)
In-Reply-To: <20031018221143.GI7665@parcelfarce.linux.theplanet.co.uk>
On Sunday 19 of October 2003 00:11, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> > I've tried to create initramfs image with unpacking initrd image,
[...]
> > It doesn't work that way unfortunately (test8 with your patch).
>
> Yes and no - it *is* unpacked, but currently we have no code that would
> try to run something from initramfs. If you want to play with that -
> add something like run_init_process("/init"); right before the call of
> prepare_namespace() in init/main.c (and be ready to have /init on
> initramfs do the rest, obvoiusly).
I see. So right now external initramfs image seems to be unusable (probably
the same when compiling it in the kernel) right now. The quesion arrives -
what was the reason to not put run_init_process("/linuxrc") by default there
(like it is for initrd) ?
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PLD/Linux
next prev parent reply other threads:[~2003-10-18 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 16:27 initrd and 2.6.0-test8 Walt H
2003-10-18 17:52 ` viro
2003-10-18 18:22 ` viro
2003-10-18 18:33 ` Christophe Saout
2003-10-18 19:41 ` [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8) viro
2003-10-18 21:56 ` Arkadiusz Miskiewicz
2003-10-18 22:11 ` viro
2003-10-18 22:46 ` Arkadiusz Miskiewicz [this message]
2003-10-18 23:07 ` Valdis.Kletnieks
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=200310190046.04897.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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