buildroot/fs/ext2, branch 2016.08

fs/ext2: add options for extra space and extra inodes

2015-10-31T14:56:56+00:00

Add two options to the ext2 filesystem, one to add extra free space, one to add extra free inodes. Signed-off-by: "Yann E. MORIN" Cc: Gustavo Zacarias Tested-by: Gustavo Zacarias Acked-by: Gustavo Zacarias Cc: Martin Bark Signed-off-by: Thomas Petazzoni

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"

fs/ext2: add option to specify a filesystem label

2014-12-07T21:07:22+00:00

Filesystems of the ext familly can carry a filesystem label. Add an option for the user to specify such a label. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Károly Kasza Tested-by: Karoly Kasza Reviewed-by: Karoly Kasza Reviewed-by: Thomas Petazzoni Tested-by: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

fs/ext2: use the new mke2img host package

2014-12-07T21:06:55+00:00

And get rid of the old genext2fs.sh wrapper. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Tested-by: Karoly Kasza Reviewed-by: Karoly Kasza Reviewed-by: Thomas Petazzoni Tested-by: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

package/mke2img: new package

2014-12-07T21:06:44+00:00

Currently, we are using a shell script called genext2fs, that impersonates the real genext2fs. But that script does much more than just call genextfs: it also calls tune2fs and e2fsck. Because it impersonates genext2fs, we can not easily add new options, and are constrained by the genext2fs options. But it turns out that, of all the options supported by the real genext2fs, we only really care for a subset, namely: - number of blocks - number of inodes - percentage of blocks reeserved to root - the root directory which to generate the image from So, we introduce a new host package, mke2img, that is intended to eventually replace genext2fs.sh. This new script is highly modeled from the existing genext2fs.sh, but was slightly refreshed, and a new, supposedly sane set of options has been choosen for the features we need (see above), and some new options were added, too, rather than relying on the arguments order or environment variables: -b number of blocks in the filesystem -i number of inodes in the filesystem -r percentage of reserved blocks * -d directory containing the root of the filesystem * -o output image file -G extfs generation: 2, 3, or 4 (default: 2) -R ext2 revision: 0 or 1 (default 1) -l filesystem label -u filesystem UUID; if not specified, a random one is used * Mandatory options Since the upstream e2fsprogs are expected to release a new mke2fs that will be able to generate a filesystem image from a directory, we then will be able to replace all the logic in mke2img, to use mke2fs instead of the (relatively fragile) combination of the three tools we currently use. An entry is added for it in the "Host utilities" menu, so it can be selected for use by post-{build,image} scripts. The ext2 filesystem selection is changed to select that now. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Tested-by: Karoly Kasza Reviewed-by: Karoly Kasza Tested-by: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

.mk files: bulk aligment and whitespace cleanup of assignments

2014-10-07T13:00:28+00:00

The Buildroot coding style defines one space around make assignments and does not align the assignment symbols. This patch does a bulk fix of offending packages. The package infrastructures (or more in general assignments to calculated variable names, like $(2)_FOO) are not touched. Alignment of line continuation characters (\) is kept as-is. The sed command used to do this replacement is: find * -name "*.mk" | xargs sed -i \ -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$#\1 \2#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$[^\\]\+$$#\1 \2 \3#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$[^\\ \t]\+\s*\\$\s*$#\1 \2 \3#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$$\s*\\$#\1 \2\3#' Brief explanation of this command: ^$[A-Z0-9a-z_]\+$ a regular variable at the beginning of the line $[?:+]\?=$ any assignment character =, :=, ?=, += $[^\\]\+$ any string not containing a line continuation $[^\\ \t]\+\s*\\$ string, optional whitespace, followed by a line continuation character $\s*\\$ optional whitespace, followed by a line continuation character Hence, the first subexpression handles empty assignments, the second handles regular assignments, the third handles regular assignments with line continuation, and the fourth empty assignments with line continuation. This expression was tested on following test text: (initial tab not included) FOO = spaces before FOO = spaces before and after FOO = tab before FOO = tab and spaces before FOO = tab after FOO = tab and spaces after FOO = spaces and tab after FOO = \ FOO = bar \ FOO = bar space \ FOO = \ GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse FOO += spaces before FOO ?= spaces before and after FOO := FOO = FOO = FOO = FOO = $(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C AT91BOOTSTRAP3_DEFCONFIG = \ AXEL_DISABLE_I18N=--i18n=0 After this bulk change, following manual fixups were done: - fix line continuation alignment in cegui06 and spice (the sed expression leaves the number of whitespace between the value and line continuation character intact, but the whitespace before that could have changed, causing misalignment. - qt5base was reverted, as this package uses extensive alignment which actually makes the code more readable. Finally, the end result was manually reviewed. Signed-off-by: Thomas De Schampheleire Cc: Yann E. Morin Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard

*.mk: replace (TARGET|HOST)_PATH by BR_PATH

2014-04-16T17:28:56+00:00

Thanks to the 2 previous patches of the series, BR_PATH contains all locations in which host-packages may install programs. This patch replaces the occurrences TARGET_PATH and HOST_PATH with BR_PATH, everywhere these variables are used in the *.mk files. Signed-off-by: Samuel Martin Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

fs/ext2: fix generation of ext4 filesystems

2014-01-05T23:07:25+00:00

cset 7a58a4e (e2fsprogs: bump to version 1.42.9) broke the generation of ext4 filesystems. This is because, in ext4, some metadata are dependent on the UUID. If changing the UUID of an ext4 filesystem, tune2fs now exits with exit-code 1, and prints a message to run fsck, to avoid trashing the filesystem. This condition is of utmost importance on a mounted filesysten (which is not our case) to avoid corruption (yes, it is possible to change the UUID of a mounted filesystem). But the error is not valid for us, since we are working on an unmonted filesystem image in the first place. Since we change the UUID after we convert the filesystem (to ext4), tune2fs just bails out. We can not just ignore the exit code of tune2fs, since we still want to catch any other failure. It turns out that, changing the UUID before converting the filesystem is just the way to go. Fixes #6752. Reported-by: Daniel Mentz Signed-off-by: "Yann E. MORIN" Cc: Daniel Mentz Signed-off-by: Peter Korsgaard

Config.in files: fix incorrect indentation

2013-12-25T11:29:52+00:00

Tab instead of spaces Signed-off-by: Thomas De Schampheleire Signed-off-by: Thomas Petazzoni

rootfs-ext2: symlink with the compressed rootfs

2013-11-10T23:34:14+00:00

Previously, a symlink was created to the uncompressed filesystem, which made it a bit useless in case compression was chosen. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard