1E2fsprogs 1.18 (November 10, 1999) 2================================== 3 4Fix a core dumping bug in e2fsck if an imagic inode is present or 5(more rarely) if the filesystem is badly corrupted enough that e2fsck 6has to restart pass 1 processing. E2fsck now closes the filesystem 7before freeing a large number of its data structures, so in the case 8of future memory faults, at least the fixed filesystem will be fully 9written out. 10 11If a filesystem doesn't support imagic inodes, and e2fsck discovers an 12imagic inode, it will offer to clear the imagic flag. 13 14E2fsck will now offer to clear the immutable flag on special files 15(device/socket/fifos) when running it in non-preen mode. 16 17E2fsck will now set the filetype when creating /lost+found, and when 18connected orphaned inodes to /lost+found. 19 20Debugfs's ncheck and icheck commands now handles the case where there 21are bad blocks in the inode table without bombing out. 22 23The badblocks list processing code has been made more efficiently for 24appending a large number of (ordered) badblocks to the badblocks list. 25 26Some minor man page updates. 27 28Fsck now allows interactive e2fsck's when using fsck -As (not a common 29mode, but some people like to do this in boot scripts for silly reasons). 30 31Programmer's notes: 32------------------- 33 34The internal e2fsck problem code for PR_2_SPLIT_DOT was fixed to meet 35with the problem code convention. 36 37The badblocks list regression test program has been updated to work 38with previously made API name changes. 39 40The ext2fs_free() command now uses the new badblocks API to avoid 41using the compatibility layer. 42 43Added new regression test cases; the run_e2fsck test script now 44supports the ability for a test case to run a preparatory command 45before running e2fsck. 46 47