From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] How is initrd built?
Date: Thu, 07 Jul 2005 10:05:57 -0400 [thread overview]
Message-ID: <1120745158.11567.37.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <vpdru0j6endy.fsf@lemming.engeast.baynetworks.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Thu, 2005-07-07 at 09:50 -0400, Paul Smith wrote:
> In the new version, the initrd doesn't appear to be an ext2 filesystem
> anymore... it's some kind of compressed cpio file?!?! Anyway, that's
> what "file" tells me.
It is an initramfs image. You can work with it just like any other cpio
archive.
> Is there any way I can work with this new format in a similar manner
> (mount it, modify it, etc.)?
There's no need to mount it, as it isn't a filesystem image, but a cpio
archive. It's about the same as a tarball, except different. :P
We switched to initramfs because it allowed us to work around the
absolute *hack* that I had included in genkernel for gensplash support
and allows us to use something sane. It also keeps us from having to
statically install the splash theme into the kernel bzImage itself,
saving a ton of space on the CD images created.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-07 14:06 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 [this message]
2005-07-07 14:35 ` Paul Smith
2005-07-07 15:11 ` Eric Edgar
2005-07-07 19:14 ` Paul Smith
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=1120745158.11567.37.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--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