From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards Date: Sun, 27 Jun 2010 13:46:48 +0000 (UTC) Subject: [Buildroot] [git commit master 1/1] initramfs: update help text References: <20100626054529.9E7CE81E0B@busybox.osuosl.org> <87aaqh38vi.fsf@macbook.be.48ers.dk> <87hbkp3sfz.fsf@macbook.be.48ers.dk> <20100627093056.5635ce90@surf> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 2010-06-27, Thomas Petazzoni wrote: > On Sun, 27 Jun 2010 08:22:56 +0200 > Peter Korsgaard 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