All of lore.kernel.org
 help / color / mirror / Atom feed
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:46:48 +0000 (UTC)	[thread overview]
Message-ID: <i07ko7$jsp$2@dough.gmane.org> (raw)
In-Reply-To: 20100627093056.5635ce90@surf

On 2010-06-27, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> On Sun, 27 Jun 2010 08:22:56 +0200
> Peter Korsgaard <jacmet@uclibc.org> wrote:
>
>> No, but you could extract the tarball (as root or using fakeroot) and
>> point CONFIG_INITRAMFS_SOURCE to it.
>> 
>> But yes, providing a way to generate the cpio archive without building a
>> kernel would be nicer.
>
> Well, a cpio archive can be generated by Buildroot without having to
> build a kernel, see fs/cpio/Config.in. What Grant was complaining about
> originally was the fs/initramfs case. However, last time I tried
> pointing CONFIG_INITRAMFS_SOURCE to a cpio archive, it didn't work.

I tried it, and it appeared to build OK -- but I haven't had a chance
to test the resulting image.

> Instead of my original solution, another solution would be to *not*
> make initramfs depend on BR2_LINUX_KERNEL, and to remove the
> dependency initramfs->kernel so that the kernel doesn't try to be
> built as soon as initramfs is selected. If kernel is selected, it
> will anyway be built *before* going through the initramfs code.
>
> Would this be ok ?

That would be fine for me, but if somebody is building both rootfs and
kernel, the initramfs source list (or the cpio archive) needs to be
built before the kernel.

-- 
Grant

  reply	other threads:[~2010-06-27 13:46 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 [this message]
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
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='i07ko7$jsp$2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.