buildroot/fs/initramfs, branch 2016.08

fs: declare phony targets as such

2015-04-14T08:12:32+00:00

This commit improves the filesystem handling code to declare its various targets as PHONY when appropriate. Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN"

linux: remove support of linux26-* targets

2014-07-29T21:47:03+00:00

The linux-* mirror targets of linux26-* have been added a very long time ago (2010) and linux 2.6 is now considered 'old' anyway. It no longer makes sense to support these linux26-* targets, so this patch removes them. This is a simplification introduced in preparation of the kconfig-package infrastructure. Signed-off-by: Thomas De Schampheleire Signed-off-by: Thomas Petazzoni

fs/initramfs: fix initramfs support

2014-03-06T22:01:33+00:00

On commit a24877586a566e052897e50e6a0c2f53cfb029f TARGETS_ROOTFS was introduced, however fs/initramfs/initramfs.mk was never updated, hence a show-targets would be rootfs-initramfs with rootfs-cpio afterwards hence never rebuilding the kernel with a proper cpio archive since TARGETS is always before rootfs-* as stated in the commit description. Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

Config.in files: unification of comments about dependency on Linux kernel

2013-12-15T15:24:36+00:00

This patch lines up the comments of packages that need a Linux kernel to be built by buildroot, to the format: foo needs a Linux kernel to be built Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard

package: remove the empty trailing lines

2013-09-13T09:10:23+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Peter Korsgaard

linux: Do not force GZIP initramfs compression

2013-07-08T12:50:31+00:00

Initramfs compression does not make much sense for the architectures that support compressed kernel images because in this case the data would be compressed twice. This will eventually result in a bigger kernel image and time overhead when uncompressing it. The only reason to use compressed initramfs is to reduce memory usage when the kernel prepares rootfs, and both the unpacked filesystem and initramfs.cpio are present in the memory. Buildroot attempts to force GZIP compression for initramfs, however it doesn't always work because initramfs compression mode depends on RAM disk compression supported by the kernel. Thus, CONFIG_INITRAMFS_COMPRESSION_GZIP depends on CONFIG_RD_GZIP. If CONFIG_RD_GZIP is not set, setting GZIP initramfs compression will have no effect. Besides, the kernel also supports other compression methods, like BZIP2, LZMA, XZ and LZO. Forcing the good old GZIP does not really make much sense any more. This removes initramfs compression settings from Buildroot, so that the default value preset in the kernel config is used, which is CONFIG_INITRAMFS_COMPRESSION_NONE. If initramfs compression is still needed, it can be set in the kernel config (using make linux-menuconfig) Signed-off-by: Valentine Barshak Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Normalize separator size to 80

2013-06-07T08:54:54+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Peter Korsgaard

cpio/initramfs: clarify their use in the help text

2012-11-07T10:48:13+00:00

Recent mails on the list show that it is not very clear how to create an initial RAM fs with buildroot. So make this more explicit in the cpio and initramfs help texts. Hopefully this will reduce the /init debugging we have to do. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

fs/initramfs: refactor with fs/cpio

2011-09-27T20:46:00+00:00

An initramfs is in fact the same as a cpio archive, but embedded in the kernel. So instead of duplicating the cpio infrastructure, we can simply build images/rootfs.cpio and link that into the kernel. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

initramfs/init: make sure that 0, 1, 2 fds are available

2011-08-04T19:52:21+00:00

As the kernel doesn't automatically mount devtmpfs when an initramfs is used, commit 424888e47431db738f5f9b3c6392435bfce7a842 has introduced a small wrapper script that mounts devtmpfs before starting the real init. Unfortunately, the problem is that in this case, the init process runs without any 0, 1 and 2 file descriptors, so none of the messages/errors printed by the various initialization scripts can be seen. This is due to the fact the init process relies on 0, 1 and 2 being opened by the kernel before init is started. However, as /dev/console isn't present on the filesystem at the time the kernel tries to open the console to create the 0, 1 and 2 file descriptors, the kernel fails on this and prints the famous "Warning: unable to open an initial console". The proposed workaround is to actually open 0, 1 and 2 to /dev/console in the wrapper script, right after mounting the devtmpfs filesystem, and before starting the real init. The "Warning" from the kernel is still shown, but at least the messages from the init scripts are visible. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard