From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] initramfs: update help text
Date: Mon, 28 Jun 2010 15:13:04 +0000 (UTC) [thread overview]
Message-ID: <i0ae60$t0c$1@dough.gmane.org> (raw)
In-Reply-To: i08rds$vue$2@dough.gmane.org
On 2010-06-28, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2010-06-27, Peter Korsgaard <jacmet@sunsite.dk> wrote:
>> Thomas> Well, a cpio archive can be generated by Buildroot without having to
>> Thomas> build a kernel, see fs/cpio/Config.in. What Grant was complaining about
>> Thomas> originally was the fs/initramfs case. However, last time I tried
>> Thomas> pointing CONFIG_INITRAMFS_SOURCE to a cpio archive, it didn't work.
>>
>> Peter> So what is the difference between initramfs and cpio? Just the
>> Peter> integration with the kernel build for the first? Maybe the initramfs
>> Peter> stuff should simply be a 'embed in kernel' question on the cpio package
>> Peter> if the internal kernel build is enabled?
>>
>> Ok, looked a bit closer and noticed that the initramfs target doesn't
>> actually create a cpio, but a command file for gen_init_cpio.
>
> Right. But why does that require building a kernel? It's just a list
> of files/nodes that goes into the cpio archive. If you're allowed to
> build a cpio archive or a tar archive, surely you should be allowed to
> build the list of files that goes into the archive?
>
>> Nevertheless, is there any advantage to use that instead of just
>> creating a cpio archive (besides it not working for you somehow)?
>
> If the cpio archive works, then I'm happy. For no particular reason
> I've always used the file-list method in the past. I tried building
> the kernel with the cpio archive instead, and the build worked fine.
> But, my target HW seems to have gone walkabout for a few days, so I
> haven't been able to test the impage built with the cpio archive
> instead of the source file list.
I've got target HW again, and building the kernel using a cpio archive
instead of the cpio-file-list seems to work fine, so that's what I'll
plan on doing.
I still don't understand why one can build a cpio archive without
building a kernel, but in order to create a list of what's in the cpio
archive a kernel must be built.
--
Grant Edwards grant.b.edwards Yow! I'm sitting on my
at SPEED QUEEN ... To me,
gmail.com it's ENJOYABLE ... I'm WARM
... I'm VIBRATORY ...
next prev parent reply other threads:[~2010-06-28 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 5:44 [Buildroot] [git commit master 1/1] initramfs: update help text Peter Korsgaard
2010-06-26 14:21 ` Grant Edwards
2010-06-26 16:48 ` Thomas Petazzoni
2010-06-27 3:46 ` Grant Edwards
2010-06-26 19:13 ` Peter Korsgaard
2010-06-27 3:46 ` Grant Edwards
2010-06-27 6:22 ` Peter Korsgaard
2010-06-27 7:30 ` Thomas Petazzoni
2010-06-27 13:46 ` Grant Edwards
2010-06-27 20:02 ` Peter Korsgaard
2010-06-27 20:10 ` Peter Korsgaard
2010-06-28 0:46 ` Grant Edwards
2010-06-28 15:13 ` Grant Edwards [this message]
2010-06-28 15:21 ` Thomas Petazzoni
2010-06-27 13:42 ` Grant Edwards
2010-06-27 18:57 ` Thomas Petazzoni
2010-06-28 0:39 ` Grant Edwards
2010-06-28 7:22 ` Peter Korsgaard
2010-06-27 20:08 ` Peter Korsgaard
2010-06-28 1:03 ` Grant Edwards
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='i0ae60$t0c$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--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