NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3286a4d6aa
kumquat-buildroot/fs/ext2/Config.in

114 lines
2.7 KiB
Plaintext
Raw Normal View History

menuconfig -> config
2005-02-10 01:59:22 +01:00
config BR2_TARGET_ROOTFS_EXT2
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
bool "ext2/3/4 root filesystem"
package/mke2img: new package 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 <nb-blocks> number of blocks in the filesystem -i <nb-inodes> number of inodes in the filesystem -r <pc-reserved> percentage of reserved blocks * -d <root-dir> directory containing the root of the filesystem * -o <img-file> output image file -G <ext-gen> extfs generation: 2, 3, or 4 (default: 2) -R <ext-rev> ext2 revision: 0 or 1 (default 1) -l <label> filesystem label -u <uid> 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" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: Karoly Kasza <kaszak@gmail.com> Reviewed-by: Karoly Kasza <kaszak@gmail.com> Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-12-06 23:40:04 +01:00
select BR2_PACKAGE_HOST_MKE2IMG
Fix it so we once again build the target root_fs
2004-10-09 06:34:21 +02:00
help
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
Build an ext2/3/4 root filesystem
Fix it so we once again build the target root_fs
2004-10-09 06:34:21 +02:00
fs/ext2: enclose the ext2 options in if...endif Use a 'if...endif' construct instead of repeating the 'depends on' for each symbols. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Arnout Vandecappelle <arnout@mind.be> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:50 +02:00
if BR2_TARGET_ROOTFS_EXT2
fs/ext2: add support for ext2 rev0 and rev1 Some bootloaders have a buggy ext2 support, and require ext2 rev1 instead of the traditional ext2 rev0 that genext2fs produces. tune2fs accepts only one '-O list' at a time, so we need to construct a list of -O options. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:53 +02:00
config BR2_TARGET_ROOTFS_EXT2_2
bool
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
choice
bool "ext2/3/4 variant"
fs/ext2: default to ext2 rev1 Rev0 is very old (E.G. from before Linux was maintained in git), the kernel prints a scary warning when used: EXT4-fs warning (device sda): ext4_update_dynamic_rev:746: updating to rev 1 because of new feature flag, running e2fsck is recommended And rev0 support is broken in u-boot 2016.11: http://lists.denx.de/pipermail/u-boot/2016-December/275916.html So default to rev1 instead. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-13 09:18:27 +01:00
default BR2_TARGET_ROOTFS_EXT2_2r1
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
fs/ext2: add support for ext2 rev0 and rev1 Some bootloaders have a buggy ext2 support, and require ext2 rev1 instead of the traditional ext2 rev0 that genext2fs produces. tune2fs accepts only one '-O list' at a time, so we need to construct a list of -O options. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:53 +02:00
config BR2_TARGET_ROOTFS_EXT2_2r0
bool "ext2 (rev0)"
select BR2_TARGET_ROOTFS_EXT2_2
config BR2_TARGET_ROOTFS_EXT2_2r1
bool "ext2 (rev1)"
select BR2_TARGET_ROOTFS_EXT2_2
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
config BR2_TARGET_ROOTFS_EXT2_3
bool "ext3"
config BR2_TARGET_ROOTFS_EXT2_4
bool "ext4"
endchoice
config BR2_TARGET_ROOTFS_EXT2_GEN
int
default 2 if BR2_TARGET_ROOTFS_EXT2_2
default 3 if BR2_TARGET_ROOTFS_EXT2_3
default 4 if BR2_TARGET_ROOTFS_EXT2_4
fs/ext2: add support for ext2 rev0 and rev1 Some bootloaders have a buggy ext2 support, and require ext2 rev1 instead of the traditional ext2 rev0 that genext2fs produces. tune2fs accepts only one '-O list' at a time, so we need to construct a list of -O options. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:53 +02:00
# All ext generations are revision 1, except ext2r0, which is revision 0
config BR2_TARGET_ROOTFS_EXT2_REV
Config.in files: fix incorrect indentation Tab instead of spaces Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-25 12:09:31 +01:00
int
default 0 if BR2_TARGET_ROOTFS_EXT2_2r0
default 1 if !BR2_TARGET_ROOTFS_EXT2_2r0
fs/ext2: add support for ext2 rev0 and rev1 Some bootloaders have a buggy ext2 support, and require ext2 rev1 instead of the traditional ext2 rev0 that genext2fs produces. tune2fs accepts only one '-O list' at a time, so we need to construct a list of -O options. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:53 +02:00
fs/ext2: add option to specify a filesystem label 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" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Károly Kasza <kaszak@gmail.com> Tested-by: Karoly Kasza <kaszak@gmail.com> Reviewed-by: Karoly Kasza <kaszak@gmail.com> Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-12-06 23:40:06 +01:00
config BR2_TARGET_ROOTFS_EXT2_LABEL
string "filesystem label"
fs/ext2: Remove support for auto-calculation of rootfs size Auto-calculation of the rootfs size cannot be done in a reliable way as it depends on the host filesystem and is broken on non ext4 host (see bugs [1] [2]). So let the user specify the size he wants for his rootfs. [1] https://bugs.busybox.net/show_bug.cgi?id=8831 [2] https://bugs.busybox.net/show_bug.cgi?id=9496 Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Thomas: as suggested by Arnout, use 60 MB as the default size instead of 64 MB.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-24 17:20:29 +01:00
# 61440 = 60MB, i.e usually small enough to fit on a 64MB media
Patch from gtj -- http://bugs.uclibc.org/view.php?id=39 0000039: Adds options to ext2 filesystem creation Adds ability to specify block and inode counts, reserved blocks, permissions squash and device table in the configuration. Also adds capability to gzip output and to copy the resulting image to a secondary location like a tftp server's root directory.
2005-01-23 11:53:06 +01:00
config BR2_TARGET_ROOTFS_EXT2_BLOCKS
fs/ext2: Remove support for auto-calculation of rootfs size Auto-calculation of the rootfs size cannot be done in a reliable way as it depends on the host filesystem and is broken on non ext4 host (see bugs [1] [2]). So let the user specify the size he wants for his rootfs. [1] https://bugs.busybox.net/show_bug.cgi?id=8831 [2] https://bugs.busybox.net/show_bug.cgi?id=9496 Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Thomas: as suggested by Arnout, use 60 MB as the default size instead of 64 MB.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-24 17:20:29 +01:00
int "exact size in blocks"
default 61440
ext2: add help text for BR2_TARGET_ROOTFS_EXT2_BLOCKS Signed-off-by: J Evans <g4@novadsp.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-05-01 17:58:36 +02:00
help
Specify the file system size as a number of 1024-byte blocks.
cleanup whitespace
2005-02-16 20:48:43 +01:00
Patch from gtj -- http://bugs.uclibc.org/view.php?id=39 0000039: Adds options to ext2 filesystem creation Adds ability to specify block and inode counts, reserved blocks, permissions squash and device table in the configuration. Also adds capability to gzip output and to copy the resulting image to a secondary location like a tftp server's root directory.
2005-01-23 11:53:06 +01:00
config BR2_TARGET_ROOTFS_EXT2_INODES
fs/ext2: add options for extra space and extra inodes 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" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-29 21:10:36 +01:00
int "exact number of inodes (leave at 0 for auto calculation)"
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
default 0
cleanup whitespace
2005-02-16 20:48:43 +01:00
fs/ext2: add options for extra space and extra inodes 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" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-29 21:10:36 +01:00
config BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES
int "extra inodes" if BR2_TARGET_ROOTFS_EXT2_INODES = 0
default 0
help
Enter here the number of extra free inodes you want on
your filesystem. By default, Buildroot will not leave
many free inodes.
Patch from gtj -- http://bugs.uclibc.org/view.php?id=39 0000039: Adds options to ext2 filesystem creation Adds ability to specify block and inode counts, reserved blocks, permissions squash and device table in the configuration. Also adds capability to gzip output and to copy the resulting image to a secondary location like a tftp server's root directory.
2005-01-23 11:53:06 +01:00
config BR2_TARGET_ROOTFS_EXT2_RESBLKS
- use numeric values for the superuser to be more portable. Closes #1250
2007-03-20 17:52:44 +01:00
int "reserved blocks percentage"
fs/ext2: allow reserving zero block for root The previous default, zero, just meant "use the default value of the filesystem generator", which happened to be 5% (the traditional value for all ext-creating tools we've ever seen). So, change the new default accordingly to 5%. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-04 00:50:59 +02:00
default 5
help
The number of blocks on the filesystem (as a percentage of the
total number of blocksi), that are reserved for use by root.
Traditionally, this has been 5%, and all ext-related tools still
default to reserving 5% when creating a new ext filesystem.
cleanup whitespace
2005-02-16 20:48:43 +01:00
- update the ext2 rootfs compression mechanism to allow for gzip, bzip2, lzma or none
2006-12-14 16:47:50 +01:00
choice
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
prompt "Compression method"
default BR2_TARGET_ROOTFS_EXT2_NONE
help
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
Select compressor for ext2/3/4 filesystem of the root filesystem
- update the ext2 rootfs compression mechanism to allow for gzip, bzip2, lzma or none
2006-12-14 16:47:50 +01:00
config BR2_TARGET_ROOTFS_EXT2_NONE
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
bool "no compression"
help
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
Do not compress the ext2/3/4 filesystem.
- update the ext2 rootfs compression mechanism to allow for gzip, bzip2, lzma or none
2006-12-14 16:47:50 +01:00
config BR2_TARGET_ROOTFS_EXT2_GZIP
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
bool "gzip"
help
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
Do compress the ext2/3/4 filesystem with gzip.
- update the ext2 rootfs compression mechanism to allow for gzip, bzip2, lzma or none
2006-12-14 16:47:50 +01:00
config BR2_TARGET_ROOTFS_EXT2_BZIP2
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
bool "bzip2"
help
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
Do compress the ext2/3/4 filesystem with bzip2.
Patch from gtj -- http://bugs.uclibc.org/view.php?id=39 0000039: Adds options to ext2 filesystem creation Adds ability to specify block and inode counts, reserved blocks, permissions squash and device table in the configuration. Also adds capability to gzip output and to copy the resulting image to a secondary location like a tftp server's root directory.
2005-01-23 11:53:06 +01:00
- Patch from Thomas Lundquist to support lzma compressed ext2 rootfs.
2006-11-04 20:15:56 +01:00
config BR2_TARGET_ROOTFS_EXT2_LZMA
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
bool "lzma"
help
fs/ext2: add ability to build ext3/4 too Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image, and upgrade it to either one of ext2, ext3 or ext4. Since calling tune2fs may require running e2fsck (tune2fs will warn to do so when certain FS options are changed), we systematically call e2fsck. This makes the code path simpler, and as a side-effect checks that genext2fs did not generate garbage. In turn, e2fsck will unconditionally add a UUID to the filesystem, which is bad for reproducibility, so we call tune2fs again to remove the UUID. This does not require checking the filesystem. To ensure compatibility of Buildroot's .config, leave ext2 as the default. Boards' .config can override this at will. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:51 +02:00
Do compress the ext2/3/4 filesystem with lzma.
- Patch from Thomas Lundquist to support lzma compressed ext2 rootfs.
2006-11-04 20:15:56 +01:00
fs/common: add support for LZO and XZ compression methods Add support for LZO and XZ compression methods to cpio, ext2, tar and ubifs filesystem targets. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-22 02:03:43 +01:00
config BR2_TARGET_ROOTFS_EXT2_LZO
bool "lzo"
help
Do compress the ext2 filesystem with lzop.
config BR2_TARGET_ROOTFS_EXT2_XZ
bool "xz"
help
Do compress the ext2 filesystem with xz.
- update the ext2 rootfs compression mechanism to allow for gzip, bzip2, lzma or none
2006-12-14 16:47:50 +01:00
endchoice
- Patch from Thomas Lundquist to support lzma compressed ext2 rootfs.
2006-11-04 20:15:56 +01:00
fs/ext2: enclose the ext2 options in if...endif Use a 'if...endif' construct instead of repeating the 'depends on' for each symbols. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Arnout Vandecappelle <arnout@mind.be> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-11 14:17:50 +02:00
endif # BR2_TARGET_ROOTFS_EXT2
Reference in New Issue Copy Permalink