Home | History | Annotate | Download | only in RelNotes
      1 E2fsprogs 1.04 (May 16, 1996)
      2 =============================
      3 
      4 First "official" (1.03 was a limited release only) to support building
      5 e2fsprogs under Linux 2.0 kernels (as well as late model 1.3 and 1.99
      6 kernels).
      7 
      8 This package includes a RPM specs file, that it can be built using the
      9 RedHat Package Manager.
     10 
     11 E2fsck now prints a hint that if there are lots of incorrectly located
     12 inode bitmaps, block bitmaps, and inode table blocks, the user might
     13 want to try using e2fsck -b 8193 first, to see if that fares any
     14 better.
     15 
     16 For ext2 filesystem written with the hurd, debugfs will now print out
     17 the translator field when printing an inode structure.
     18 
     19 Lots of miscellaneous linking/installation cleanups:
     20 
     21   Libraries are now linked using a relative pathname, instead of
     22   relying on -L working correct.  It doesn't, in many cases, including
     23   current versions of GNU ld.  This guarantees that the build tree is
     24   linking with the right libraries, instead of the ones installed in
     25   /usr/lib.
     26 
     27   Header files, man pages, and the et/ss shell scripts are now
     28   generated using a custom substitution script, instead of relying on
     29   the configure script.  This prevents needless recompilation of
     30   files; in addition, the custom substitution script is much faster.
     31 
     32   e2fsck may now be linked dynamically, by using the
     33   --enable-dynamic-e2fsck flag to configure.  This is not recommended,
     34   since it increases e2fsck's dependence on other files, but some
     35   people need to save disk space, and other critical programs on their
     36   systems were being linked dynamically anyway.
     37 
     38   Programs such as fsck which didn't need to be linked against
     39   libext2fs (or mke2fs which didn't need to be linked against libe2p)
     40   only link against libraries they actually need.  Otherwise, those
     41   programs would require the presence of libraries that otherwise
     42   could be removed from a rescue diskette.
     43 
     44   The ss include files are now installed correctly so they can
     45   actually be used by another package.
     46 
     47   If the profiling libraries are built, they are now installed on a
     48   "make install-libs".
     49 
     50