From: "Paul Smith" <psmith@nortel.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] How is initrd built?
Date: 07 Jul 2005 15:14:06 -0400 [thread overview]
Message-ID: <vpdrekaazawx.fsf@lemming.engeast.baynetworks.com> (raw)
In-Reply-To: <20050707151154.GB6259@toucan.gentoo.org>
%% Eric Edgar <rocket@gentoo.org> writes:
ee> You technically cannot extract the cpio archive as far as I can tell
ee> because it really is multiple cpio archives concatenated together.
Ah! OK.
ee> cd ${INITRAMFS_OVERLAY}
ee> find . -print | cpio --quiet -o -H newc | gzip -9 > ${CACHE_DIR}/cpio/initramfs-overlay.cpio.gz
ee> cat old-oldinitramfs.cpio.gz initramfs-overlay.cpio.gz > new-initramfs.cpio.gz
Wait, that's not right is it?
Is the initramfs really a concatenation of compressed cpio files? I
don't think it is... gzip can't handle that.
It must be a compression of a concatenation of cpio files, right? In
that case the above command line is not correct... I'd need to create
the cpio file, concatenate it to an uncompressed copy of the existing
initramfs, then compress the whole thing again.
Yes?
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@nortel.com> HASMAT--HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
gentoo-catalyst@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-07 19:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 13:45 [gentoo-catalyst] How is initrd built? Paul Smith
2005-07-06 13:52 ` Chris Gianelloni
2005-07-06 15:31 ` Paul Smith
2005-07-06 15:55 ` Chris Gianelloni
2005-07-06 16:36 ` Paul Smith
2005-07-06 16:47 ` Chris Gianelloni
2005-07-06 21:47 ` Paul Smith
2005-07-06 22:17 ` Chris Gianelloni
2005-07-07 15:14 ` Eric Edgar
2005-07-07 15:36 ` Paul Smith
2005-07-07 15:40 ` Eric Edgar
2005-07-07 16:02 ` Chris Gianelloni
2005-07-07 16:19 ` Paul Smith
2005-07-07 18:42 ` Paul Smith
2005-07-07 19:16 ` Chris Gianelloni
2005-07-07 20:01 ` Paul Smith
2005-07-07 20:44 ` Eric Edgar
2005-07-07 22:39 ` Paul Smith
2005-07-08 1:44 ` Paul Smith
2005-07-08 13:34 ` Chris Gianelloni
2005-07-08 13:31 ` Chris Gianelloni
2005-07-08 2:19 ` Paul Smith
2005-07-08 13:37 ` Chris Gianelloni
2005-07-06 22:08 ` Paul Smith
2005-07-06 22:36 ` Chris Gianelloni
2005-07-06 22:41 ` Paul Smith
2005-07-06 22:58 ` Chris Gianelloni
2005-07-07 13:50 ` Paul Smith
2005-07-07 14:05 ` Chris Gianelloni
2005-07-07 14:35 ` Paul Smith
2005-07-07 15:11 ` Eric Edgar
2005-07-07 19:14 ` Paul Smith [this message]
2005-07-07 19:34 ` Eric Edgar
2005-07-07 20:03 ` Paul Smith
2005-07-07 19:41 ` Chris Gianelloni
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=vpdrekaazawx.fsf@lemming.engeast.baynetworks.com \
--to=psmith@nortel.com \
--cc=gentoo-catalyst@lists.gentoo.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