All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] initramfs: update help text
Date: Sun, 27 Jun 2010 22:08:19 +0200	[thread overview]
Message-ID: <87631444ss.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <i07kg9$jsp$1@dough.gmane.org> (Grant Edwards's message of "Sun,  27 Jun 2010 13:42:34 +0000 (UTC)")

>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:

 >> No, but you could extract the tarball (as root or using fakeroot) and
 >> point CONFIG_INITRAMFS_SOURCE to it.

 Grant> An extracted tarball isn't one of the options either.
 Grant> CONFIG_INITRAMFS_SOURCE can be pointed at either a cpio archive or the
 Grant> source file list.

No? I haven't used initramfs in years, but I'm pretty sure you can
simply point CONFIG_INITRAMFS_SOURCE at a directory to make it use that.

The help text and documentation seems to agree with me:

config INITRAMFS_SOURCE
        string "Initramfs source file(s)"
        default ""
        help
          This can be either a single cpio archive with a .cpio suffix or a
          space-separated list of directories and files for building the
          initramfs image.  A cpio archive should contain a filesystem archive
          to be used as an initramfs image.  Directories should contain a
          filesystem layout to be included in the initramfs image.  Files
          should contain entries according to the format described by the
          "usr/gen_init_cpio" program in the kernel tree.

          When multiple directories and files are specified then the
          initramfs image will be the aggregate of all of them.

 Grant> It works fine the way it is.  What's the reason for disabling the
 Grant> buildign of a cpio file source list?

Is there any advantage to using a source file for gen_init_cpio instead
of just building a cpio archive?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-06-27 20:08 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
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 [this message]
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=87631444ss.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.