Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] initramfs: update help text
Date: Sun, 27 Jun 2010 22:10:34 +0200	[thread overview]
Message-ID: <871vbs44p1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <87aaqg452f.fsf@macbook.be.48ers.dk> (Peter Korsgaard's message of "Sun, 27 Jun 2010 22:02:32 +0200")

>>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:

Hi,

 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.

Nevertheless, is there any advantage to use that instead of just
creating a cpio archive (besides it not working for you somehow)?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-06-27 20:10 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 [this message]
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=871vbs44p1.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --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