1*6a54128fSAndroid Build Coastguard WorkerE2fsprogs 1.25 (September 20, 2001) 2*6a54128fSAndroid Build Coastguard Worker=================================== 3*6a54128fSAndroid Build Coastguard Worker 4*6a54128fSAndroid Build Coastguard WorkerThis is primarily a bug-fix release; no new features were added, but 5*6a54128fSAndroid Build Coastguard Workerthere are a number of embarrassing bug fixes and cleanups applied. 6*6a54128fSAndroid Build Coastguard Worker 7*6a54128fSAndroid Build Coastguard WorkerFix a bug mke2fs which causes stack garbage to be written to disk when 8*6a54128fSAndroid Build Coastguard Workerzapping disk sectors. (This bug could cause mke2fs to core dump for 9*6a54128fSAndroid Build Coastguard Workersome kernels, I suspect with security enhancement patches.) 10*6a54128fSAndroid Build Coastguard Worker 11*6a54128fSAndroid Build Coastguard WorkerRemove unneeded #include of <linux/config.h> which was breaking 12*6a54128fSAndroid Build Coastguard Workerbuilding e2fsprogs on the Hurd. (Addresses Debian bug #112414.) 13*6a54128fSAndroid Build Coastguard Worker 14*6a54128fSAndroid Build Coastguard WorkerUpdated tune2fs man page to reflect the fact that adding or removing a 15*6a54128fSAndroid Build Coastguard Workerjournal doesn't require running e2fsck. 16*6a54128fSAndroid Build Coastguard Worker 17*6a54128fSAndroid Build Coastguard WorkerRemove use of AC_REQUIRE from autoconf which had been used to prevent 18*6a54128fSAndroid Build Coastguard WorkerAC_CANONICAL_HOST from being called twice; unfortunately this causes 19*6a54128fSAndroid Build Coastguard Workerrecent autoconf to bomb out since they don't allow AC_REQUIRE to be 20*6a54128fSAndroid Build Coastguard Workerused outside of autoconf macros. Fortunately, it doesn't seem to be 21*6a54128fSAndroid Build Coastguard Workernecessary any more, anyway. 22*6a54128fSAndroid Build Coastguard Worker 23*6a54128fSAndroid Build Coastguard WorkerE2fsck will now not fall back to an alternate superblock if the user 24*6a54128fSAndroid Build Coastguard Workerspecifies the superblock location explicitly on the command-line. 25*6a54128fSAndroid Build Coastguard WorkerThis allows easier recovery from a situation where the primary 26*6a54128fSAndroid Build Coastguard Workersuperblock and block groups are slightly corrupted, but the backup 27*6a54128fSAndroid Build Coastguard Workersuperblocks are completely broken. 28*6a54128fSAndroid Build Coastguard Worker 29*6a54128fSAndroid Build Coastguard WorkerFix problem which caused compile_et and mk_cmds to blow up if 30*6a54128fSAndroid Build Coastguard Workere2fsprogs was in a directory with a pathname that contained spaces. 31*6a54128fSAndroid Build Coastguard Worker 32*6a54128fSAndroid Build Coastguard WorkerWe are now more paranoid about checking the entry in /etc/mtab to make 33*6a54128fSAndroid Build Coastguard Workersure the filesystem is really mounted, since some broken distributions 34*6a54128fSAndroid Build Coastguard Worker(read: Slackware) don't initialize /etc/mtab before checking non-root 35*6a54128fSAndroid Build Coastguard Workerfilesystems. (Slackware also doesn't check the root filesystem 36*6a54128fSAndroid Build Coastguard Workerseparately, and reboot if the root filesystem had changes applied to 37*6a54128fSAndroid Build Coastguard Workerit, which is dangerous and broken, but there's nothing I can do about 38*6a54128fSAndroid Build Coastguard Workerthat.) 39*6a54128fSAndroid Build Coastguard Worker 40*6a54128fSAndroid Build Coastguard WorkerMake UUID library C++ friendly by adding appropriate extern "C" 41*6a54128fSAndroid Build Coastguard Workerdeclarations and using const in the function declarations. 42*6a54128fSAndroid Build Coastguard Worker 43*6a54128fSAndroid Build Coastguard WorkerFix up the com_err texinfo file so that it can product a valid info 44*6a54128fSAndroid Build Coastguard Workerfile (previously, it could only be used to generate paper 45*6a54128fSAndroid Build Coastguard Workerdocumentation using texinfo.tex). 46*6a54128fSAndroid Build Coastguard Worker 47