summaryrefslogtreecommitdiffstats
path: root/package/bash
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2013-05-28 12:11:37 +0000
committerPeter Korsgaard <jacmet@sunsite.dk>2013-05-29 00:18:37 +0200
commit60474dcec67922782a244ca3fe30fe9c35a5c963 (patch)
treefa17d28fb8b16a67b93e3704dffa18bebfef2bf6 /package/bash
parent5b591b4052de5c650dcaa9033d77b739b82c132a (diff)
downloadbuildroot-novena-60474dcec67922782a244ca3fe30fe9c35a5c963.tar.gz
buildroot-novena-60474dcec67922782a244ca3fe30fe9c35a5c963.zip
fs/ext2: further fix to the UUID
Turned out that setting a nil-UUID is no better than clearing it. What currently happens is as follows: - first, genext2fs does not generate a UUID - then we tune2fs to upgrade the filesystem - then we run fsck, which generates a random UUID - then we re-run tune2fs to set a nil-UUID So, on the target, if the file system is improperly unmounted (eg. with a power failure), on next boot, fsck may be run, and a new random UUID will be generated. *However*, fsck improperly updates the filesystem when it adds the UUID, and there are a few group descriptor checksum errors. Those errors will go undetected until the next fsck, which will then block for user input (bad on embedded systems, bad). Fix that by systematically generating a random UUID _before_ we call to fsck. A random UUID is not so bad, after all, since there are already so many sources of unpredictability in the filesystem: files date and ordering, files content (date, paths...) which renders a fixed UUID unneeded. And it is still possible to set the UUID in a post-image script if needed, anyway. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Diffstat (limited to 'package/bash')
0 files changed, 0 insertions, 0 deletions