From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] initramfs: update help text
Date: Sun, 27 Jun 2010 13:42:34 +0000 (UTC) [thread overview]
Message-ID: <i07kg9$jsp$1@dough.gmane.org> (raw)
In-Reply-To: 87hbkp3sfz.fsf@macbook.be.48ers.dk
On 2010-06-27, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:
>
> >> How about just using the tarball output instead?
>
> Grant> When building an initramfs into a kernel, a tarball isn't one of the
> Grant> options that's accepted by the kernel build system.
>
> No, but you could extract the tarball (as root or using fakeroot) and
> point CONFIG_INITRAMFS_SOURCE to it.
An extracted tarball isn't one of the options either.
CONFIG_INITRAMFS_SOURCE can be pointed at either a cpio archive or the
source file list.
> But yes, providing a way to generate the cpio archive without building a
> kernel would be nicer.
It works fine the way it is. What's the reason for disabling the
buildign of a cpio file source list?
--
Grant
next prev parent reply other threads:[~2010-06-27 13:42 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
2010-06-28 15:21 ` Thomas Petazzoni
2010-06-27 13:42 ` Grant Edwards [this message]
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='i07kg9$jsp$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