From: Goetz Bock <bock@blacknet.de>
To: buildroot@busybox.net
Subject: [Buildroot] Multiple cpio archives
Date: Mon, 20 Nov 2006 16:38:44 +0100 [thread overview]
Message-ID: <20061120153844.GF3065@priv.blacknet.de> (raw)
Dear list,
I fear this might be somewhat oftoppic, but I'll ask anyway.
Some comments on the kernelml (from quite some time ago) and the
changelogs of e.g. syslinux suggest that it might be possible to append
multiple cpio files as initrd to a linux kernel.
I would like to use this for my initramfs to seperate the modules from
the rest of my system.
But it simply does not work. I'm using linux 2.6.17-2-486 (from debian)
and a buidlroot based root.i586.cpio.gz. As bootloader I'm using
pxelinux. The two images are loaded, but only the root image is
extracted.
Any ideas?
BTW: I think there was some mini distribution that did exatly what i try
to do, but I can't find it anymore (should have bookmarked it :-( )
--
/"\ Goetz Bock at blacknet dot de -- secure mobile Linux everNETting
\ / (c) 2006 Creative Commons, Attribution-ShareAlike 2.0 de
X [ 1. Use descriptive subjects - 2. Edit a reply for brevity - ]
/ \ [ 3. Reply to the list - 4. Read the archive *before* you post ]
reply other threads:[~2006-11-20 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061120153844.GF3065@priv.blacknet.de \
--to=bock@blacknet.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