Initial copy of the e2fsprogs sourceforge web pages.

git-svn-id: https://e2fsprogs.svn.sourceforge.net/svnroot/e2fsprogs/web@2 46e75558-b442-0410-83ab-e6570fdeb8bf
author: tytso <tytso@46e75558-b442-0410-83ab-e6570fdeb8bf> 2008-01-03 21:09:58 +0000
committer: tytso <tytso@46e75558-b442-0410-83ab-e6570fdeb8bf> 2008-01-03 21:09:58 +0000
commit: 43aac7f52c5b538133bfa16fc282a32fe159cc81 (patch)
tree: 94628450b9218a05da8b327520bb5f35089d2de7
parent: ad24aa9152ef6cd3742279754125af936a5daa12 (diff)
download: e2fsprogs-43aac7f52c5b538133bfa16fc282a32fe159cc81.tar.gz
19 files changed, 7008 insertions, 0 deletions
diff --git a/htdocs/config.inc b/htdocs/config.inc
new file mode 100644
index 000000000..91b3ab201
--- /dev/null
+++ b/htdocs/config.inc
@@ -0,0 +1,5 @@
+<?php
+$content_file = "e2fsprogs.inc";
+$group_id = 2406;
+$title = "E2fsprogs: Ext2 Filesystem Utilities";
+?>
diff --git a/htdocs/e2fsprogs-hacking.html b/htdocs/e2fsprogs-hacking.html
new file mode 100644
index 000000000..1cf2cfb33
--- /dev/null
+++ b/htdocs/e2fsprogs-hacking.html
@@ -0,0 +1,97 @@
+<html>
+<head>
+<title>Quickstart on hacking e2fsprogs using Mercurial</title>
+</head>
+
+<body bgcolor="#ffffff">
+
+<BODY bgcolor=#FFFFFF topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth="0">
+
+<!-- top strip -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=2 bgcolor="737b9c">
+  <TR>
+    <TD><SPAN class=maintitlebar>&nbsp;&nbsp;
+      <A class=maintitlebar href="http://sourceforge.net/"><B>Home</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/about.php"><B>About</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/partners.php"><B>Partners</B></a> |
+      <A class=maintitlebar href="http://sourceforge.net/contact.php"><B>Contact Us</B></A> |
+      <A class=maintitlebar href="http://sourceforge.net/account/logout.php"><B>Logout</B></A></SPAN></TD>
+    </TD>
+  </TR>
+</TABLE>
+<!-- end top strip -->
+
+<!-- top title table -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=0 bgcolor="" valign="center">
+  <TR valign="center" bgcolor="#eeeef8">
+    <TD>
+      <A href="http://sourceforge.net"> 
+	<IMG src="http://sourceforge.net/images/sflogo2-steel.png" width="143" height="70" border="0"></A>
+    </TD>
+    <TD width="99%"><!-- right of logo -->
+      <a href="http://www.valinux.com"><IMG src="http://sourceforge.net/images/valogo3.png" align="right" alt="VA Linux Systems" hspace="5" vspace="7" border=0 width="117" height="70"></A>
+    </TD><!-- right of logo -->
+  </TR>
+  <TR><TD bgcolor="#543a48" colspan=2><IMG src="http://sourceforge.net/images/blank.gif" height=2 vspace=0></TD></TR>
+</TABLE>
+<!-- end top title table -->
+
+<!-- center table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="10" bgcolor="#FFFFFF" align="center">
+  <TR>
+    <TD>
+
+<!-- Begin actual content -->
+
+<center>
+<H1>Quickstart on hacking e2fsprogs using Mercurial</H1>
+</center>
+
+<P> Due to licensing issues with BitKeeper (BK), e2fsprogs development
+has been moved to a new distributed Source Code Management system called
+<A HREF="http://www.selenic.com/mercurial">Mercurial</A>.</P>
+
+<H2>Obtaining Mercurial</H2>
+
+<P>The best place to get Mercurial is from the <A
+HREF="http://www.selenic.com/mercurial">Mercurial web site</A>.
+Instructions on installing and using Mercurial can be found at the 
+<A HREF="http://www.serpentine.com/mercurial/">Mercurial Wiki</A>.
+
+<H2>Getting the latest e2fsprogs development sources using Mercurial</H2>
+
+<P>The Mercurial repository can be found at <A
+HREF="http://thunk.org/hg/e2fsprogs">http://thunk.org/hg/e2fsprogs</A>.
+You can either browse the e2fsprogs repository via a web browser, or
+once you've installed Mercurial you can download a copy of the
+repository via the command:
+
+<blockquote><tt>
+	hg clone http://thunk.org/hg/e2fsprogs e2fsprogs-upstream
+</tt></blockquote>
+
+<ADDRESS>
+<A HREF="http://thunk.org:/tytso">Theodore Ts'o</A>
+</ADDRESS> 
+
+<!-- end actual content -->
+
+    </TD>
+  </TR>
+</TABLE>
+<!-- end center table -->
+
+<!-- footer table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="2" bgcolor="737b9c">
+  <TR>
+    <TD align="center"><FONT color="#ffffff"><SPAN class="titlebar">
+      All trademarks and copyrights on this page are properties of their respective owners.</SPAN></FONT>
+    </TD>
+  </TR>
+</TABLE>
+
+<!-- end footer table -->
+</BODY>
+</HTML>
+
+
diff --git a/htdocs/e2fsprogs-release.html b/htdocs/e2fsprogs-release.html
new file mode 100644
index 000000000..77343f819
--- /dev/null
+++ b/htdocs/e2fsprogs-release.html
@@ -0,0 +1,4233 @@
+<HTML>
+<HEAD>
+<TITLE>E2fsprogs Release Notes</TITLE>
+</HEAD>
+
+<BODY bgcolor=#FFFFFF topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth="0">
+
+<!-- top strip -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=2 bgcolor="737b9c">
+  <TR>
+    <TD><SPAN class=maintitlebar>&nbsp;&nbsp;
+      <A class=maintitlebar href="http://sourceforge.net/"><B>Home</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/about.php"><B>About</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/partners.php"><B>Partners</B></a> |
+      <A class=maintitlebar href="http://sourceforge.net/contact.php"><B>Contact Us</B></A> |
+      <A class=maintitlebar href="http://sourceforge.net/account/logout.php"><B>Logout</B></A></SPAN></TD>
+    </TD>
+  </TR>
+</TABLE>
+<!-- end top strip -->
+
+<!-- top title table -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=0 bgcolor="" valign="center">
+  <TR valign="center" bgcolor="#eeeef8">
+    <TD>
+      <A href="http://sourceforge.net"> 
+	<IMG src="http://sourceforge.net/images/sflogo2-steel.png" width="143" height="70" border="0"></A>
+    </TD>
+    <TD width="99%"><!-- right of logo -->
+      <a href="http://www.valinux.com"><IMG src="http://sourceforge.net/images/valogo3.png" align="right" alt="VA Linux Systems" hspace="5" vspace="7" border=0 width="117" height="70"></A>
+    </TD><!-- right of logo -->
+  </TR>
+  <TR><TD bgcolor="#543a48" colspan=2><IMG src="http://sourceforge.net/images/blank.gif" height=2 vspace=0></TD></TR>
+</TABLE>
+<!-- end top title table -->
+
+<!-- center table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="10" bgcolor="#FFFFFF" align="center">
+  <TR>
+    <TD>
+
+<!-- Begin actual content -->
+
+<CENTER><H1>E2fsprogs Release Notes</H1></CENTER>
+
+<H2>Release notes for the e2fsprogs package</H2>
+<UL>
+<LI><A HREF="#1.40.4">E2fsprogs 1.40.4 (December 31, 2007)</A>
+<LI><A HREF="#1.40.3">E2fsprogs 1.40.3 (December 5, 2007)</A>
+<LI><A HREF="#1.40.2">E2fsprogs 1.40.2 (July 12, 2007)</A>
+<LI><A HREF="#1.40.1">E2fsprogs 1.40.1 (July 7, 2007)</A>
+<LI><A HREF="#1.40">E2fsprogs 1.40 (June 29, 2007)</A>
+<LI><A HREF="#1.39">E2fsprogs 1.39 (May 29, 2006)</A>
+<LI><A HREF="#1.38">E2fsprogs 1.38 (June 30, 2005)</A>
+<LI><A HREF="#1.37">E2fsprogs 1.37 (March 21, 2005)</A>
+<LI><A HREF="#1.36">E2fsprogs 1.36 (February 5, 2005)</A>
+<LI><A HREF="#1.35">E2fsprogs 1.35 (February 28, 2004)</A>
+<LI><A HREF="#1.34">E2fsprogs 1.34 (July 25, 2003)</A>
+<LI><A HREF="#1.33">E2fsprogs 1.33 (April 21, 2003)</A>
+<LI><A HREF="#1.32">E2fsprogs 1.32 (November 9, 2002)</A>
+<LI><A HREF="#1.31">E2fsprogs 1.31 (November 8, 2002)</A>
+<LI><A HREF="#1.30">E2fsprogs 1.30 (October 31, 2002)</A>
+<LI><A HREF="#1.29">E2fsprogs 1.29 (September 24, 2002)</A>
+<LI><A HREF="#1.28">E2fsprogs 1.28 (August 31, 2002)</A>
+<LI><A HREF="#1.27">E2fsprogs 1.27 (March 8, 2002)</A>
+<LI><A HREF="#1.26">E2fsprogs 1.26 (February 3, 2002)</A>
+<LI><A HREF="#1.25">E2fsprogs 1.25 (September 20, 2001)</A>
+<LI><A HREF="#1.24a">E2fsprogs 1.24a (September 2, 2001)</A>
+<LI><A HREF="#1.24">E2fsprogs 1.24 (August 30, 2001)</A>
+<LI><A HREF="#1.23">E2fsprogs 1.23 (August 15, 2001)</A>
+<LI><A HREF="#1.22">E2fsprogs 1.22 (June 22, 2001)</A>
+<LI><A HREF="#1.21">E2fsprogs 1.21 (June 15, 2001)</A>
+<LI><A HREF="#1.20">E2fsprogs 1.20 (May 20, 2001)</A>
+<LI><A HREF="#1.19">E2fsprogs 1.19 (July 13, 2000)</A>
+<LI><A HREF="#1.18">E2fsprogs 1.18 (November 10, 1999)</A>
+<LI><A HREF="#1.17">E2fsprogs 1.17 (October 26, 1999)</A>
+<LI><A HREF="#1.16">E2fsprogs 1.16 (October 22, 1999)</A>
+<LI><A HREF="#1.15">E2fsprogs 1.15 (July 18, 1999)</A>
+<LI><A HREF="#1.14">E2fsprogs 1.14 (January 9, 1999)</A>
+<LI><A HREF="#1.13">E2fsprogs 1.13 (December 15, 1998)</A>
+<LI><A HREF="#1.12">E2fsprogs 1.12 (July 4, 1998)</A>
+<LI><A HREF="#1.10">E2fsprogs 1.10 (April 24, 1997)</A>
+<LI><A HREF="#1.09">E2fsprogs 1.09 (April 14, 1997)</A>
+<LI><A HREF="#1.08">E2fsprogs 1.08 (April 10, 1997)</A>
+<LI><A HREF="#1.07">E2fsprogs 1.07 (March 14, 1997)</A>
+<LI><A HREF="#1.06">E2fsprogs 1.06 (October 7, 1996)</A>
+<LI><A HREF="#1.05">E2fsprogs 1.05 (September 7, 1996)</A>
+<LI><A HREF="#1.04">E2fsprogs 1.04 (May 16, 1996)</A>
+<LI><A HREF="#1.03">E2fsprogs 1.03 (March 27, 1996)</A>
+<LI><A HREF="#1.02">E2fsprogs 1.02 (January 16, 1996)</A>
+</UL>
+
+<H2><A NAME="1.40.4">E2fsprogs 1.40.4 (December 31, 2007)</A></H2>
+
+<P>Improve time-based UUID generation.  A new daemon uuidd, is started
+automatically by libuuid if necessary.  This daemon is setuid to allow
+updates to /var/lib/libuuid, so the clock sequence number can be
+stored and so if the clock is set backwards, it can be detected.
+(Addresses Sourceforge Bug: #1529672, Addresses Red Hat Bugzilla:
+#233471)</P>
+
+<P>Filter out the NEEDS_RECOVERY feature flag when writing out the backup
+superblocks.  This avoids e2fsck from concluding that a full
+filesystem check is required before backing up the superblock due to
+changes in the feature flags.  (Addresses Debian Bug: #454926)</P>
+
+<P>Fix fsck to only treat the '#' character as a comment at the beginning
+of the line in /etc/fstab.  Otherwise fstabs for the fuse filesystem
+will cause fsck to issue an bogus warning message.
+(Addresses Gentoo bug: #195405, Addresses Sourceforge bug: #1826147)</P>
+
+<P>Format control characters and characters with the high eighth bit set
+when printing the contents of the blkid cache, to prevent filesystems
+with garbage labels from sending escape sequences to the user's screen
+that might, for example place it in graphics mode.  (Addresses Ubuntu
+Bug: #78087)</P>
+
+<P>Fix sign-extension problem on 64-bit systems in in the com_err
+library.  (Addresses Sourceforge Bug: #1809658)</P>
+
+<P>Avoid division by zero error when probing an invalid FAT filesystem in
+the blkid library.  (Addresses Sourceforge Bug: #1831627)</P>
+
+<P>Update Dutch, Polish, and Vietnamese translations from the Translation
+Project.  Remove the Rwandan translation upon advice of the
+Translation Project.</P>
+
+<H3>Programmer's Notes</H3>
+
+<P>Fix the libss "make check" regression test so that it works if the
+current directory is not in the user's path or if the libss shared
+library is not installed.  (Addresses Sourceforge Bug: #1848974)</P>
+
+<P>Fixed spelling mistakes, typos, and otherwise clarified man pages.
+(Addresses Debian Bugs: #444883, #441872)</P>
+
+<P>Fixed various Debian packaging issues --- see debian/changelog for
+details.  (Addresses Debian Bugs: #437720, #451172, #458017)</P>
+
+<P>Fix build failure on non-Linux/non-Hurd/non-Masix systems.
+(Addresses Sourceforge Bug: #1859778)</P>
+
+<P>Fix Hurd portability issues.  (Addresses Debian Bug: #437720)</P>
+
+
+<H2><A NAME="1.40.3">E2fsprogs 1.40.3 (December 5, 2007)</A></H2>
+
+<P>Fix a potential security vulnerability where an untrusted filesystem
+can be corrupted in such a way that a program using libext2fs will
+allocate a buffer which is far too small.  This can lead to either a
+crash or potentially a heap-based buffer overflow crash.  No known
+exploits exist, but main concern is where an untrusted user who
+possesses privileged access in a guest Xen environment could corrupt a
+filesystem which is then accessed by the pygrub program, running as
+root in the dom0 host environment, thus allowing the untrusted user to
+gain privileged access in the host OS.  Thanks to the McAfee AVERT
+Research group for reporting this issue.  (Addresses CVE-2007-5497.)</P>
+
+<P>Fix hueristics in blkid which could cause a disk without partitions to
+be incorrectly skipped when a loopback device is present.  (Addresses
+Red Hat Bugzilla #400321.)</P>
+
+<P>Fix e2image so that in raw mode it does not create an image file which
+is one byte too large.</P>
+
+<P>Change mke2fs's usage message so it recommends the preferred -E option
+instead of the deprecated -R option.</P>
+
+<P>Enhance the blkid library so it will recognize squashfs filesystems.
+(Addresses Red Hat Bugzilla #305151.)</P>
+
+<P>Enhance e2fsck so it will force the backup superblocks to be backed up
+if the filesystem is consistent and key constants have been changed
+(i.e., by an on-line resize) or by e2fsck in the course of its
+operations.</P>
+
+<P>Enhance blkid's detection of FAT filesystems; so that USB disks with
+only a single bootable partition will not get missed.</P>
+
+<P>E2fsck will no longer mark a filesystem as invalid if it has time
+errors (i.e., if superblock mount time or last write time is in the
+future) and the user refuses to fix the problem.</P>
+
+<P>The Ubuntu init scripts don't properly set the system time correctly
+from hardware clock if the hardware clock is configured to tick local
+time instead of GMT time.  Work around this as best as we can by
+providing an option, buggy_init_scripts, in /etc/e2fsck.conf which can
+be set on Ubuntu systems.  (Addresses Debian Bug #441093, and Ubuntu
+Bug #131201.)</P>
+
+<P>Fix fsck to ignore /etc/fstab entries for bind mounts.  (Addresses Red
+Hat Bugzilla #151533.)</P>
+
+<P>Fix e2fsck so that if the superblock is corrupt, but still looks
+vaguely like an ext2/3/4 superblock, that it automatically tries to
+fall back to the backup superblock, instead of failing with a hard
+error.</P>
+
+<P>Make the e2fsprogs program more robust so that they will not crash
+when opening a corrupt filesystem where s_inode_size is zero.</P>
+
+<P>Change e2fsck so it uses sscanf() instead of atoi() so it non-numeric
+arguments are detected as such and the parse error is reported to the
+user.   (Addresses Debian Bug #435381.)</P>
+
+<P>Change e2fsck so it will not complain if a file has blocks reallocated
+up to the next multiple of a system's page size.</P>
+
+<P>Fix bug in ext2fs_check_desc() which will cause e2fsck to complain
+about (valid) filesystems where the inode table extends to the last
+block of the block group.  (Addresses Red Hat Bugzilla #214765.)</P>
+
+<P>Fix a bug in ext2fs_initialize() which causes mke2fs to fail while
+allocating inode tables for some relatively rare odd disk sizes.
+(Addresses Red Hat Bugzilla #241767.)</P>
+
+<P>Add Catalan translation and update Dutch and Swedish translations
+from the Translation Project.</P>
+
+<P>Fix big-endian byte-swapping bug in ext2fs_swap_inode_full().  We
+still had an issue when trying to figure out whether we need to
+byte-swap fast symlinks that contained extended attributes.</P>
+
+<P>Fixed spelling mistakes, typos, and otherwise clarified man pages.
+(Addresses SourceForge Bug #1821333.)</P>
+
+
+<H3>Programmer's Notes</H3>
+
+<P>Fix mke2fs tests to avoid needing any significant ^M (CR) characters</P>
+
+<P>Add "make check" to the RPM spec file</P>
+
+<P>Fix "make install" and 'make unstall" in misc/Makefile.in so that it
+works correctly when the prefix is not the root directory.</P>
+
+<P>Fix the resize2fs tests, r_move_itable and r_resize_inode, so they
+clena up after themselves by deleting the test.img temporary file
+after completing the test.</P>
+
+<P>Fixed a corner case bug ext2fs_unlink() when trying to delete the
+first directory entry in a directory block and the last directory
+entry in the previous directory block is not in use.  Fortunately
+ext2fs_unlink() is only used by debugfs and e2fsck, and in e2fsck in
+places where it is extremely unlikely to run into this corner case.</P>
+
+<P>Fix missing dependency which would cuase parallel builds to fail.
+(Addresses Sourceforge Bug #1842331.)</P>
+
+<P>Fix a build error on newer gcc caused by lib/ext2fs/ismounted.c
+calling open(O_CREATE) with a missing mode parameter.</P>
+
+<P>Fix the test_ss.c in lib/ss so it can be used as an example
+application program for the library as well as a regression test
+suite.</P>
+
+<P>Fix ext2fs_dblist_dir_iterate() so that error codes and abort codes
+are properly passed back up through the call stack.</P>
+
+<H2><A NAME="1.40.2">E2fsprogs 1.40.2 (July 12, 2007)</A></H2>
+
+<P>A recent change to e2fsck_add_dir_info() to use tdb files to check
+filesystems with a very large number of filesystems had a typo which
+caused us to resize the wrong data structure.  This would cause a
+array overrun leading to malloc pointer corruptions and segfaults.
+Since we normally can very accurately predict how big the the dirinfo
+array needs to be, this bug only got triggered on very badly corrupted
+filesystems.</P>
+
+<P>Fix a bug in e2fsck which caused it to incorrectly salvange
+directories when the last entry's rec_len is bogusly too big.  This
+resulted in a nonsense filesystem corruption to be reported, and
+required a second run of e2fsck to fully fix up the directory.</P>
+
+<P>Update tune2fs man page to include more discussion of reserved blocks
+(Addresses Launchpad bug #47817)</P>
+
+<P>Update Turkish, Polish, Dutch, and Vietnamese PO files from the
+Translation Project</P>
+    
+<H2><A NAME="1.40.1">E2fsprogs 1.40.1 (July 7, 2007)</A></H2>
+
+<P>Fix bug which could cause libblkid to loop forever.  When revalidating
+a partition where there is obsolete information in /etc/blkid.tab, we
+end up freeing a the type tag without clearing dev->bid_type, causing
+blkid_verify() to loop forever.  (Addresses Debian Bug: #432052)</P>
+    
+<P>The Turkish translation has a bug in it where it has the translation
+of "E@e '%Dn' in %p (%i)" to "E@E".  This causes @E to be expanded at
+@E, recursively, forever, until the stack fills up and e2fsck core
+dumps.  We fix this by making e2fsck stop @-expansions after a
+recursive depth of 10, which is far more than we need.
+(Addresses Sourceforge Bug: #1646081)</P>
+    
+<P>Compile the default mke2fs.conf into mke2fs program.  People are
+getting surprised by mke2fs creating filesystems with different
+defaults than earlier versions of mke2fs if mke2fs.conf is not
+present.  So we now create a built in version of mke2fs.conf file
+which is used by mke2fs if the /etc/mke2fs.conf is not present.
+(Addresses SourceforgeBug: #1745818)</P>
+
+<P>Improve the config/parse_types.sh helper script.  Fix a potential
+security problem if e2fsprogs is built as root (as Gentoo does!).  In
+addition fix the script and how it is called from the configure script
+so that it does the right thing when cross-compiling.  (Fixes Gentoo
+bug: #146903)</P>
+    
+<P>Update Vietnamese, French, and Dutch PO files from the Translation
+Project.  Also created a new e2fsprogs.pot file for translator.</P>
+    
+<P>Fix bogus strip permission errors when building under Debian.  When
+building the e2fsprogs dpkg's, the dh_strip command emits a large
+number of error messages caused by the permissions not being right.
+So run dh_fixperms before running dh_strip.</P>
+
+<H3>Programmer's Notes:</H3>
+
+<P>Add new function: profile_set_default().  This function sets the value
+of the pseudo file "<default>".  If the file "<default>" had
+previously been passed to profile_init(), then def_string parameter
+will be parsed and used as the profile information for the "<default>"
+file.</P>
+    
+<P>Fix mk_cmds's error reporting so that it is unambiguous that it is the
+mk_cmds script which is generating the error.  (Obviates Gentoo patch:
+e2fsprogs-1.32-mk_cmds-cosmetic.patch)</P>
+    
+<P>Fix the test suite to use LC_ALL instead of LANG.  LC_ALL is the "high
+priority" environment variable that overrides all others, where as
+LANG is the lowest priorty environment variable.  If LC_ALL is set, it
+doesn't matter whether LANG, LANGUAGE, LC_COLLATE, LC_MESSAGES, and
+the all the rest are set.  This will assure that the locale when
+running the test suites is the "C" locale.  (Obviates Gentoo patch:
+e2fsprogs-1.38-tests-locale.patch)</P>
+
+<H2><A NAME="1.40">E2fsprogs 1.40 (June 29, 2007)</A></H2>
+
+<P>Fix divide by zero error in blkid's NTFS probing logic.</P>
+
+<P>Add new blkid -g option which causes the blkid cache to be garbage
+collected.</P>
+
+<P>Fix a bug in libblkid which could cause the internal field bid_type to
+become corrupted.  Fortunately bid_type isn't used much, and bid_label
+and bid_uuid is only used by debugging code, so the impact of this bug
+was very minor.</P>
+
+<P>Mke2fs will now store the RAID stride value when a filesystem is
+created with a requested RAID stride, and then use it automatically in
+resize2fs.</P>
+
+<P>Mke2fs has a sanity check added to make sure (inode_size * num_inodes)
+isn't too big.  In some cases Lustre users have tried specifying an
+inode size of 4096 bytes, while keeping an inode ratio of one inode
+per 4096 bytes.  </P>
+
+<P>Improve sanity check in e2fsck's algorithm for finding a backup
+superblock, so that it won't accidentally find a superblock that was
+located in the journal, and then later reject it as being not a valid
+backup superblock.</P>
+
+<P>Fix e2fsck get_size logic so that it will work with the Linux floppy
+driver.  The Linux floppy driver is a bit different from the other
+block device drivers, in that if the device has been opened with
+O_EXCL, it disallows another open(), even if the second open() does
+not have the O_EXCL flag.  (Addresses Debian Bug: #410569)</P>
+
+<P>Fix error checking of badblock's last-block and start-block arguments.
+(Addresses Debian Bug: #416477)</P>
+
+<P>Fix e2fsck so that it doesn't overwrite the backup superblocks when
+recovering a journal until the master superblock has been confirmed as
+being sane.</P>
+
+<P>Change the blkid library to be much more paranoid about concluding
+that a partition contains an NTFS filesystem, and fetch the UUID and
+LABEL information from NTFS filesystems.  (Addresses Launchpad Bug:
+#110138)</P>
+
+<P>Factor out the code which sets the default journal size and move it
+into libext2fs.</P>
+
+<P>Enhance e2fsck so it will recreate the ext3 journal if the original
+journal inode was cleared to due it being corrupt after finishing the
+filesystem check.</P>
+
+<P>Fix e2fsck so that it updates the journal inode if it is corrupted and
+the backup journal information from the superblock was successfully
+used to recover the filesystem.</P>
+
+<P>Fix e2fsck so that it checks all of the blocks in the journal inode
+for validity.  The original code only checked the direct blocks to
+make sure the journal inode was sane.  Unfortunately, if some or all
+of the indirect or doubly indirect blocks were corrupted, this would
+not be caught.</P>
+
+<P>Add support in blkid to detect LUKS encrypted partitions.</P>
+
+<P>Add extra sanity checks for extended attributes in the case where the
+size is zero but the offset is very large.</P>
+
+<P>Fix byte-swapping issues for large inodes in ext2fs_read_inode_full()
+and ext2fs_get_next_inode_full().</P>
+
+<P>Clarify the copyright licenses used by the various libraries in
+the top-level COPYING  file (Red Hat Bugzilla: 166058)</P>
+
+<P>Make mke2fs's defaults when /etc/mke2fs.conf doesn't exist more sane.</P>
+
+<P>Fix mke2fs and debugfs to support large (> 16 bit) uid's and gid's.</P>
+
+<P>Remove check in e2fsck which requires EA's in inodes to be sorted;
+they don't need to be sorted, and e2fsck was previously wrongly
+clearing unsorted EA's stored in the inode structure.</P>
+
+<P>Allow mke2fs or tune2fs to create a substantially larger journal (up
+to 10,240,000 blocks).</P>
+
+<P>Fix MD superblock detection, and make sure the correct UUID is
+reported from the MD superblock.</P>
+
+<P>Fix a signed vs. unsigned bug in debugfs.</P>
+
+<P>Enhance debugfs's date parser so that it accepts integer values.</P>
+
+<P>Fix e2fsck's pass1c accounting so it doesn't terminate too early if a
+file with multiply claimed blocks is hard linked. or not at all if the
+root directory contains shared blocks</P>
+
+<P>Enhance debugfs so it can modify the block group descriptors using the
+command set_block_group_descriptor.</P>
+
+<P>Improve e2fsck's reporting of I/O errors so it's clearer what it was
+trying to do when an error happens</P>
+
+<P>Fix a bug in in how e2fsprogs byte swaps inodes containing fast
+symlinks that have extended attributes.  (Addresses Red Hat Bugzilla:
+#232663 and LTC Bugzilla: #27634)</P>
+
+<P>Fix potential file descriptor leak in ext2fs_get_device_size() in an
+error case.</P>
+
+<P>Add libreadline.so.5 support to libss.</P>
+
+<P>Impove badblocks -n/-w exclusive usage message.</P>
+
+<P>Fix dump_unused segfault in debugfs when a filesystem is not open</P>
+
+<P>Fix memory leak in blkid library.  (Addresses Debian Bug: #413661)</P>
+
+<P>Allow the debugfs lcd command to work w/o a filesystem being open.
+(Addresses LTC Bugzilla #27513)</P>
+
+<P>Fix e2fsck to clear i_size for special devices with a bogus i_blocks
+field on the first pass.</P>
+
+<P>Fix e2fsck to set the file type of the '..' entry when connecting
+a directory to lost+found.  (Addresses Lustre Bug: #11645)</P>
+
+<P>Enhance e2fsck to recover directories whose modes field were corrupted
+to look like special files.  This is probably only useful in
+artificial test cases, but it will be useful if we ever do the "inodes
+in directory" idea for ext4.</P>
+
+<P>Allow debugfs to dump (and rdump) > 2GB files.  (Addresses Debian Bug:
+#412614)</P>
+
+<P>Fix resize2fs parsing of size parameter (in sector units).  This was
+actually a bug in libe2p's parse_num_blocks() function.  When handling
+the 's' suffix, it was ignoring the blocksize information passed in
+from the caller and always interpreting the number in terms of a 1k
+blocksize.  (Addresses Debian Bug: #408298)</P>
+
+<P>There was a floating point precision error which could cause e2fsck to
+loop forever on really big filesystems with a large inode count.
+(Addresses Debian Bug: #411838)</P>
+
+<P>Fix memory leak in ext2fs_write_new_inode()</P>
+
+<P>Add support for using a scratch files directory to reduce e2fsck's
+emory utilization on really big filesystems.  This uses the TDB
+library.  See the [scratch_files] section of the e2fsck.conf man page
+for more details.</P>
+
+<P>Fixed type-punning bug which caused dumpe2fs to crash on the Arm
+platform (Addresses Debian Bug: #397044)</P>
+
+<P>Add explanatory message to badblocks that -n and -w are mutually exclusive
+(Addresses Debian Bug: #371869)</P>
+
+<P>Allow debugfs and dumpe2fs to support fs features under development.</P>
+
+<P>Add support for the new flag EXT2_FLAG_SOFTSUPP_FEATURES flag to
+ext2fs_open() , which allows application to open filesystes with features
+which are currently only partially supported by e2fsprogs.</P>
+
+<P>Allow unix_io to support offsets greater than 2G (Addresses
+SourceForge Bug: #1547922)</P>
+
+<P>Fixed overflow and signed/unsigned problems caused by the number of
+blocks or inodes exceeding 2**31 or being close to 2**32-1.</P>
+
+<P>Add support for unsigned directory hash calculations with hints in the
+superblock to fix cross-architectural portability for htree
+directories with filenames where the high 8th bit is set.  (Addresses
+Debian: #389772)</P>
+
+<P>Fix resize2fs so that it gives user-intelligible error messages if the
+filesystem or the kernel does not support on-line resizing.
+(Addresses Debian Bug: #380548)</P>
+
+<P>Require mke2fs -F -F for really dangerous operations, since -F is
+needed for less dangerous operations such as creating filesystems
+images in regular files, or creating filesystems on whole block
+devices.  These relatively innocuous usages should NOT be confused
+with running mke2fs on an apparently-mounted or in-use filesystem.</P>
+
+<P>Allow the default inode size to be specified into the mke2fs.conf
+file.</P>
+
+<P>Make the smallest default journal size is big enough so that on-line
+resizing should always work.</P>
+
+<P>Fix silly spelling error in e2fsck.  (Addresses SourceForge bug:
+#1531372)</P>
+
+<P>Fix debugfs coredump when lsdel is run without an open filesystem
+(Addresses Debian Bug: #378335)</P>
+
+<P>Fix debugfs display bug us that bytes that have the high bit set are
+displayed as "ec" instead of "ffffffec".</P>
+
+<P>Add support in lsattr so it will display the EXT4_EXTENTS_FL flag.</P>
+
+<P>Device mapper scanning wasn't working in the blkid library because the
+pathnames had an extra "/dev" when they were being probed.</P>
+
+<P>Add GFS/GFS2 support to the blkid library.</P>
+
+<P>Fix blkid support of empty FAT filesystem labels.</P>
+
+<P>Avoid recursing forever (or for a long time) when the blkid library
+searches for a device and there are symlinks to directories in /dev.</P>
+
+<P>Avoid unaligned halfword access in blkid when accessing FAT
+superblocks, as this will cause Sparc/Solaris systems to throw a
+SIGBUS error.</P>
+
+<P>The latest devmapper libraries requires pthreads, add -lpthreads to
+the static link libraries for e2fsck.static if devmapper is enabled.
+(Addresses Debian bug: #388718)</P>
+
+<P>Improve the (non-installed, for experts only) findsuper program by
+printing the uuid and label from the superblocks, as well as the
+starting and ending offsets of the filesystem given the information in
+the superblock.  Omit by default printing superblocks that are likely
+found in located in an ext3 journal unless an explicit -j option is
+given.</P>
+
+<P>Updated French and Dutch translations and added Vietnamese translation.</P>
+
+<P>Use FreeBSD's DIOCGMEDIASIZE and DIOCGDINFO ioctls if available when
+determining a partition's size, since binary searching to determine
+the device doesn't work on FreeBSD.</P>
+
+<P>Documentation about UUID's is available in enough places, and it's
+awkward to deal with debian-legal's insanities.  So I'm caving in the
+"more-lunatic-than-RMS" wing of Debian by removing RFC-4122 so we
+don't have do the dfsg tarball.  Also remove the rule that only tried
+to install RFC-4122 on Ubuntu, since Ubuntu seems to want to fetch
+e2fsprogs exclusively from Debian.  (Addresses Debian Bug: #407107)</P>
+
+<P>Fix the info-dir line so that the menu name does not contain a .info
+prefix.  First of all, it's ugly, secondly, it causes the install-info
+command to fail to remove the com_err info file from the
+/usr/share/info/dir file when the comerr-dev package is removed and
+purged.  (Addresses Debian Bug: #401711)</P>
+
+<P>Fixed spelling mistakes, typos, and otherwise clarified man pages.
+(Addresses Debian Bug: #369761, #373004, #379695)</P>
+
+<P>Fixed various Debian packaging issues --- see debian/changelog for
+details.  (Addresses Debian Bugs #389554, #390664, #413208, #419605,
+#408352, #415560, #399155)</P>
+
+
+<H3>Programmer's notes:</H3>
+
+<P>E2fsck now supports the %It expansion when printing a problem report.
+It will print the type of the inode in the problem context.</P>
+
+<P>Fix misc/Makefile.in so that it builds even if e2fsck hasn't been built yet
+(Addresses Sourceforge Bug: #1565561)</P>
+
+<P>Remove unused variables and other lint/gcc -Wall cleanups</P>
+
+<P>Add check to ext2fs_get_device_size() so it will return EFBIG for for
+filesystems contained in regular files where the filesystem image size
+is returned by stat64().</P>
+
+<P>Set local environment variables to C so mk_cmds and compile_et always
+work.  (Addresses SourceForge Bug: #1532177)</P>
+
+<P>Added the 64-bit byte swapping function ext2fs_swab64().</P>
+
+<P>Added two new helper functions to prevent 2**31/2**32-1 overflow
+problems: ext2fs_div_ceil() and e2p_percent().</P>
+
+<P>Create new ext2fs library inline functions ext2fs_group_first_block()
+and ext2fs_group_last_block() in order to calculate the starting and
+ending blocks in a block group.</P>
+
+<P>Create the generated files read-only to remind developers not to edit them.</P>
+
+<P>Add support for autoconf 2.60 (with backwards compatibility for older
+versions of autoconf).</P>
+
+<P>Added an "make rpm" target to top-level Makefile</P>
+
+<P>Added various FreeBSD portability fixes.</P>
+
+<P>Exclude mercurial files from the RPM build tree to speed up copy/build.</P>
+
+<P>Use root_sysconfdir to define the locations of mke2fs.conf and
+e2fsck.conf instead of using a hard-coded /etc pathname.</P>
+
+<P>Prevent e2fsck.h and ext2_ext_attr.h from getting included multiple times.</P>
+
+<P>Fixed "make clean" in blkid's Makefile.in file from removing tst_*.c files.</P>
+
+<P>If diff -u is supported, use it to report test failures.</P>
+
+<P>Updates/improvements to RPM spec file</P>
+
+<P>Add on-disk format definitions for the following new features:
+EXT4_FEATURE_RO_COMPAT_HUGE_FILE, EXT4_FEATURE_RO_COMPAT_GDT_CSUM,
+EXT4_FEATURE_RO_COMPAT_DIR_NLINK, EXT4_FEATURE_INCOMPAT_64BIT,
+EXT4_FEATURE_RO_COMPAT_EXTRA_ISIZE</P>
+
+<P>Add a new make target "checked-failed" in the tests directory which
+reruns any failed tests</P>
+
+<P>Update draft-leach-uuids-guids-01.txt with rfc4122.txt</P>
+
+<P>Fix miscellaneous bugs reported by Coverity: Dead code, potential nul
+pointer dereferences, memory leaks, etc.  None were security-criticial
+problems.</P>
+
+<P>Fix up usage and decrement error messages in the test_icount program</P>
+
+<P>Add debugging code to the com_err library; if the environment variable
+COMERR_DEBUG is set to 1, print out debugging messages as error tables
+are added and removed from the com_err library.  If the
+COMERR_DEBUG_FILE environment variable is set (and the process is not
+setuid) the debugging messages may be redirected to a file.</P>
+
+<P>Change all of the e2fsprogs programs to use the newer add_error_table()
+and remove_error_table() interfaces instead of the much older
+initialize_*_error_table() function.</P>
+
+<P>Add TDB support into the ext2fs library.  This allows us to have a
+guaranteed library we can count on always being present so we can
+store data in an on-disk database.</P>
+
+<P>Add support for using TDB to store the icount data, so we don't run out
+of memory when checking really large filesystems.</P>
+
+<P>Change the regression test suite so that it skips empty test directories.</P>
+
+<P>Define the l_i_iversion field in ext2_inode.  The l_i_version field is
+now defined from the old l_i_reserved1 field in the ext2 inode.  This
+field will be used to store high 32 bits of the 64-bit inode version
+number.</P>
+
+<P>Add Makefile production rule for e2fsprogs.spec in case it gets
+deleted.</P>
+
+<P>Add new function profile_get_uint() to allow for a clean way to fetch
+unsigned integers from the context.</P>
+
+<P>Add test to make sure the ext2 superblock structure is 1024 bytes.</P>
+
+<P>Fix typo in name of f_dup4 regression test</P>
+
+<P>Add new function blkid_gc_cache() which performs a garbage collection
+pass on the /etc/blkid.tab file.</P>
+
+<P>The ext2fs_open() function now sets EXT2_FLAG_MASTER_SB_ONLY.  In
+general, only e2fsck (after the filesystem is clean), tune2fs, and
+resize2fs should change the backup superblocks by default.  Most
+callers of ext2fs_open() should not be touching any superblock fields
+which require the backups to be touched.</P>
+
+<P>Add new function to libext2fs, ext2fs_default_journal_size(), which
+returns the default journal size.</P>
+
+
+<H2><A NAME="1.39">E2fsprogs 1.39 (May 29, 2006)</A></H2>
+
+<P>Fix 32-bit cleanliness in e2fsprogs so that we can support filesystems
+between 2**31 and 2**32 blocks.</P>
+
+<P>Change mke2fs to use /etc/mke2fs.conf as a configuration file to
+configure the filesystem features, blocksize, and inode_ratio for
+different filesystem types.</P>
+
+<P>Mke2fs will now create filesystems hash trees and on-line resizing
+enabled by default, based on the new /etc/mke2fs.conf file.</P>
+
+<P>The e2fsprogs tools (resize2fs, e2fsck, mke2fs) will open the
+filesystem device node in exclusive mode to prevent accidents by
+system administrators.  In the case of resize2fs and mke2fs, it will
+only use exclusive mode if the filesystem is not mounted.</P>
+
+<P>Fixed a bug in mke2fs which caused it to to fail when creating the
+resize inode for large filesystems.  (Addresses Debian Bug #346580)</P>
+
+<P>When allocating space for the RAID filesystems with the stride
+parameter, mke2fs will now place each portion of the group's inode
+table right up after the superblock (if present) in order to minimize
+fragmentation of the freespace.</P>
+
+<P>Speed up mke2fs and e2fsck by writing inode and block bitmaps more
+efficiently by writing the inode and block bitmaps in one pass, thus
+reducing the number of disk seeks required.</P>
+
+<P>Add support for on-line resizing to resize2fs.</P>
+
+<P>Fix blkid library so that logic to determine whether or not a device's
+cached information in /etc/blkid.tab needs to be verified or not
+doesn't get confused by a system clock which is insane (for example,
+if the battery is dead on a Macintosh running PPC Linux.  (Addresses
+Red Hat Bug: #182188)</P>
+
+<P>The blkid library will now store the UUID of the external journal used
+by ext3 filesystems, so that in the future, the userspace mount binary
+can use this to find the location of the external journal and pass
+this information to the kernel.</P>
+
+<P>E2fsck will now consult a configuration file, /etc/e2fsck.conf to
+control how various options should be handled.  See the e2fsck.conf
+man page for more details.   (Addresses Debian Bug: #150295)</P>
+
+<P>E2fsck now prints an explanatory message when delaying a filesystem
+check when the system is running on battery.  (Addresses Debian Bug:
+#350306)</P>
+
+<P>E2fsck will detect if the superblock's last mount field or last write
+field is in the future, and offer to fix if so.  (Addresses Debian Bug
+#327580) These problems will be fixed automatically in preen mode
+since Debian's boot sequence bogusly doesn't set the time correctly
+until potentially very late in the bootup process, and this can cause
+false positives which will cause users' systems to fail to boot.
+(Addresses Debian Bugs #343662 and #343645)</P>
+
+<P>E2fsck now checks to see if the superblock hint for the location of
+the external journal is incorrect, and if so, offer to update it.
+(Addresses Debian Bug: #355644)</P>
+
+<P>Fix e2fsck from segfaulting on disconnected inodes that contain one or
+more extended attributes.  (Addresses Debian Bug: #316736, #318463)</P>
+
+<P>E2fsck will stop and print a warning if the user tries running a
+read/write badblocks test on a read-only mounted root filesystem.</P>
+
+<P>Fix a memory leak in e2fsck's error paths.  (Thanks to Michael
+C. Thompson for pointing these out; they were originally found using
+Coverity.)</P>
+
+<P>When resizing a file containing a filesystem, resize2fs will expand or
+truncate a file as necessary.  (Addresses Debian Bug: #271607)</P>
+
+<P>Resize2fs will now automatically determine the RAID stride parameter that
+had been used to create the filesystem, and use that for newly created
+block groups.   The RAID stride parameter may also be manually specified
+on the command line using the new -S option to resize2fs.</P>
+
+<P>Fix mke2fs so that it correctly creates external journals on
+big-endian machines (such as a S/390).  </P>
+
+<P>Fix a bug in the e2p library which could cause dumpe2fs to (rarely)
+fail to print out the journal or hash seed UUID.  (Thanks to Guillaume
+Chambraud for pointing this out.)</P>
+
+<P>Dumpe2fs will now print the size of the journal (if present).</P>
+
+<P>Fix debugfs's set_inode_field command so it can properly set the frag,
+fsize, uid_high, gid_high, and author fields in the inode instead of
+silently failing, and so that setting the i_size actually sets i_size
+correctly.</P>
+
+<P>Add a new debugfs command, set_current_time, which sets fs->now so
+that regression test suites can repeatedly modify the filesystem's
+last_write fields.</P>
+
+<P>Fix a bug in debugfs's icheck which would incorrectly report the owner
+of an extended attribute block.</P>
+
+<P>Fix the debugfs commands htree_dump, dx_hash, and list_dir so they print a
+print a usage message when an illegal option character is given.</P>
+
+<P>Fix debugfs's dump_unsued command on filesystems with a 64k blocksize
+so it won't core dump.  (Addresses SourceForge bug #1424311)</P>
+
+<P>Fix mklost+found so that it creates a full-sized directory on
+filesystems with larger block sizes.</P>
+
+<P>Fix a file descriptor leak in blkid library.</P>
+
+<P>Fix a display bug in "badblocks -sv" so that the done message properly
+clears the block number at the end of the test.  (Addresses Debian Bug
+#322231)</P>
+
+<P>Allow fractional percentages to the -m option in mke2fs and tune2fs
+(Addresses Debian Bug: #80205)</P>
+
+<P>Use fstat/fstat64 in getsize.c if the the target is a regular file,
+instead of attempting to do a binary search.  Fix some fd leaks in
+error cases.</P>
+
+<P>Add support for device mapper library to the blkid library to ensure
+that the "best" (i.e., leaf) device is probed by the blkid library.</P>
+
+<P>Fix the blkid library so that it notices when an ext2 filesystem is
+upgraded to ext3.</P>
+
+<P>Improve the blkid's library VFAT/FAT detection; it now understands
+labels stored in the root directory, and is more paranoid about
+checking the FAT superblock values.</P>
+
+<P>Fixed a fd leak in the uuid library which was causing problems for the
+LVM tools.  (Addresses Debian Bug: #345832)</P>
+
+<P>Add support for the reiser4 and software suspend partitions to the
+blkid library.  Also add support for extract the label from iso9660
+filesystems.</P>
+
+<P>Fix a compile_et bug which miscount the number of error messages if
+continuations are used in the .et file.</P>
+
+<P>Add extra sanity checks to protect users from unusual cirucmstances
+where /etc/mtab may not be sane, by checking to see if the device is
+reported busy (works on Linux 2.6) kernels.  (Addresses Debian Bug
+#319002)</P>
+
+<P>Updated French, Dutch, Polish, and Swedish translations.  (Addresses Debian
+Bug: #343149, #341911, #300871, #316604, #316782, #330789)</P>
+
+<P>Fix use-after-free bug in e2fsck when finishing up the use of the
+e2fsck context structure.</P>
+
+<P>Fixed spelling mistakes, typos, and otherwise clarified man pages and
+documentation.  (Addresses Debian Bugs: #329859, #322188, #316811,
+#312515, #351268, #357951, #347295, #316040, #368392, #368393, #368394,
+#368179)</P>
+
+<P>Fixed various Debian packaging issues --- see debian/changelog for
+details.  (Addresses Debian Bugs #317862, #320389, #290429, #310950,
+#310428, #330737, #330736, #329074, #356293, #360046, #366017, #364516,
+#362544, #362970)</P>
+
+
+<h3>Programmer's notes:</h3>
+
+<P>Update config.guess and config.sub to latest version (2006-02-23) from
+FSF.</P>
+
+<P>Fix asm_types.h type conflicts on AMD 64 platforms.  (Addresses Debian
+Bugs: #360661, #360317)</P>
+
+<P>Fixed the Makefile so that they work correctly on newer versions of
+GNU make (i.e., 3.81).</P>
+
+<P>Add valgrind support to the regression test suites, and eliminate
+false positives from valgrind.</P>
+
+<P>Add a regression test suite for the blkid library.</P>
+
+<P>Fix a fencepost error in resize2fs caught by valgrind.  </P>
+
+<P>Fix compiler warnings about missing memcpy prototypes.</P>
+
+<P>We no longer have the sparc assembly code in the header file any more,
+so we shouldn't set _EXT2_HAVE_HAS_BITOPS_ for the sparc.  This would
+break compiles on the sparc architectures when using gcc.</P>
+
+<P>In the libext2fs library, add the new field fs->now which if non-zero
+is used instead of the system time when setting various filesystem
+fields (last modified time, last write time, etc.)</P>
+
+<P>Fix gcc 4.01 complaints by adding a missing #include <string.h> to
+ext2fs.h which is needed since the inline functions use memcpy().
+(Addresses Sourceforge Bug #1251062)</P>
+
+<P>Use BUILD_CFLAGS and BUILD_LDFLAGS instead of CFLAGS and LDFLAGS in
+the build system when building files in the util directory which are
+needed during the build process.  This avoids potential problems when
+cross-compiling and some of the options specified in CFLAGS or LDFLAGS
+are not recognized as valid by the host compiler.  (Addresses
+Sourceforge Bug #1261547)</P>
+
+<P>Clean up the blkid library by making the superblock and generic i/o
+functions to be more generic.  Clean up interface to the probe
+function, and fix memory leak.  Finallly, remove an unneeded reference
+to probe.h in the lib/blkid/resolve.c</P>
+
+<P>Add an ext2fs_read_bb_FILE regression test to confirm proper detection
+of invalid block #'s.</P>
+
+<P>The x86 asm constraints for ext2fs_{set/clear}_bit have been fixed to
+indicate that the the function read/writes the memory location.</P>
+
+<P>Fix various gcc -Wall complaints.</P>
+
+<P>Add a dependency to make sure that the subdirectories are created
+before creating all of the object files, in order to address parallel
+build problem in the library Makefiles.  (Addresses Sourceforge Bug:
+#1261553)</P>
+
+<P>Add $(LDFLAGS) to the command line argument when generating an ELF or
+Solaris shared library, to allow cross-compile and other builds that
+might need to specify -L paths to needed libraries.  (Addresses
+Sourceforge Bug #1261549)</P>
+
+<P>Add a new feature, EXT2_FEATURE_COMPAT_LAZY_BG, which is initially
+intended for testing purposes.  It allows an ext2/ext3 developer to
+create very large filesystems using sparse files where most of the
+block groups are not initialized and so do not require much disk
+space.  Eventually it could be used as a way of speeding up mke2fs and
+e2fsck for large filesystem, but that would be best done by adding an
+RO_COMPAT extension to the filesystem to allow the inode table to be
+lazily initialized on a per-block basis, instead of being entirely
+initialized or entirely unused on a per-blockgroup basis.</P>
+
+<P>Fix backwards compatibility so e2fsprogs will better compile on Linux
+2.0.35 systems.</P>
+
+<P>Make test scripts more robust against locale-related environment variables</P>
+
+<P>Fix type warning problem with sizeof() in ext2fs_open2().</P>
+
+<P>Fix type warning problem with time_t in debugfs.</P>
+
+<H2><A NAME="1.38">E2fsprogs 1.38 (June 30, 2005)</A></H2>
+
+<P>Fix blkid's test programs (built with "make check") compile correctly
+even without "configure --enable-blkid-debug".</P>
+
+<P>Fix ia64 core dump bug caused by e2fsprogs running afoul of C99 strict
+type aliasing rules on newer gcc compilers.  (Addresses Red Hat
+Bugzilla ##161183.)</P>
+
+<P>Fix com_err library to make it more compatible with recent changes
+made to the com_err library in MIT Kerberos V5 version 1.4.
+(Addresses Sourcefroge Bug #1150146)</P>
+
+<P>General cleanup of messages printed by e2fsprogs programs for grammar,
+consistency, and to make life easier for translators.  Fixed a few
+strings containing English that had not been marked as needing
+translations.  Removed strings that do not need to be translated, to
+make life easier for translators.</P>
+
+<P>Mke2fs and badblocks will take advantage of a feature in Linux 2.6 to
+test to see if a device appears to be in use instead of just relying
+on /proc/mounts and /etc/mtab.  (Addresses Debian Bug #308594).</P>
+
+<P>Fix portability problem in the filefrag program affecting platforms
+where the size of an integer is smaller than the size of a long.
+(Addresses Debian Bug #309655)</P>
+
+<P>Mke2fs will now use a larger journal by default for filesystems
+greater than 4GB.  (128 MB instead of 32MB).</P>
+
+<P>Mke2fs will refuse to create filesystems greater than 2**31-1 blocks,
+unless forced.  This is to avoid signed vs. unsigned kernel bugs in
+block numbers that still need to be fixed.</P>
+
+<P>The blkid program has a new option which will more efficiently search
+for device when it is known (or expected) that only one matching
+device will be found in the system, such as when doing a lookup by
+UUID.</P>
+
+<P>Debian's e2fsprogs-specific initrd fragment will avoid including
+unnecessary libraries into the initrd ramdisk by unsetting LD_PRELOAD
+and LD_LIBRARY_PATH, and filtering out libraries found in
+/etc/ld.so.preload.  (Addresses Debian Bug: #304003)</P>
+
+<P>Fixed a potential portability issue in the blkid programs for
+architectures where the char type is unsigned.  (Addresses Sourceforge
+Bug: #1180585)</P>
+
+<P>Fix a bug in filefrag so that it doesn't falsely count an extra
+discontinuity when the first block found is an indirect block.
+(Addresses Debian Bug #307607).</P>
+
+<P>Fix blkid's recognition of cramfs filesystems, and enhance it to be
+able to handle cramfs labels.</P>
+
+<P>Fix debugfs's stat command to not core dump when a filesystem is not
+open.</P>
+
+<P>Fix e2fsck's handling of error conditions caused by the resize inode
+claiming blocks that are also used by other inodes, a filesystem
+corruption which was commonly caused by a bug in Fedora Core 3's
+resize2fs program.</P>
+
+<P>Fixed bug in filefrag which caused it to fail on non-ext2/3
+filesystems.  (Addresses Debian Bug: #303509)</P>
+
+<P>If the superblock last mount time indicates that the system clock may
+not be accurate, then e2fsck will omit checking inodes' deletion time
+field for indications of a potential corrupted orphaned inode list.
+(Previously e2fsck only ommited these LOW_DTIME checks when the
+superblock's last write time looked insane.)</P>
+
+<P>Fixed a IA64 core dump bug in the e2p library which affected dumpe2fs.
+(Addresses Debian bug #302200)</P>
+
+<P>Make the blkid library more paranoid about being run from setgid
+programs, and to use __secure_getenv() from libc if it is available.</P>
+
+<P>Fixed spelling mistakes, typos, and otherwise clarified man pages.
+(Addresses Debian Bugs: #304591, #304592, #304594, #304597, #304593
+and Sourceforge Bug: #1189803)</P>
+
+<P>Updated and fixed translations.</P>
+
+<P>Fixed various Debian packaging issues --- see debian/changelog for
+details.</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Ext2fs_set_bit(), ext2fs_clear_bit(), and ext2fs_test_bit( have been
+changed to take an unsigned int for the bit number.  Negative bit
+numbers were never allowed (and didn't make any sense), so this should
+be a safe change.  This is needed to allow safe use of block numbers
+greater than or equal to 2**31.</P>
+
+<P>The compile_et program will avoid recreating generated foo_err.c and
+foo_err.h files if no changes are necessary.  The compile_et program
+will also atomically replace these files to avoid a potential parallel
+build race problem on SMP systems.  (Addresses Sourceforge Bug:
+#1157933)</P>
+
+<P>Added a new function to the blkid library, blkid_probe_all_new(),
+which only probes newly added disk devices, and change
+blkid_find_dev_with_tag() to use this function so that when a
+requested tag is not found, devices that were previously not checked
+are searched before searching all devices in the system.</P>
+
+<P>Added new functions to the blkid library, blkid_dev_set_search() and
+blkid_dev_has_tag().</P>
+
+<P>E2fsck's problem strings can now use @m and @n as abbrevations for
+"multiply-claimed" and "invalid", respectively.</P>
+
+<P>The e2fsprog.pot file now has an explanation of how the @-expansion
+and %-expansion works, and strings in e2fsck/problem.c which contain @
+characters now have comments in e2fsprogs.pot with the @-expansion to
+make life easier for translators.</P>
+
+<P>Fixed missing return values in the ext2fs library which could cause it
+to return random garbage in certain error conditions.</P>
+
+<P>Allow the current time to be overriden via the E2FSCK_TIME environment
+variable for use in regression tests.</P>
+
+<P>The test scrpit driver program now exits with a non-zero status if
+there any of its test that it ran failed.</P>
+
+<P>Fixed problems with parabuilds on SMP systems.  (Addresses Sourceforge
+Bug: #1157933)</P>
+
+<P>Fixed "make check" so that it compiles correctly even when e2fsprogs'
+header files have not be installed in the system include directories.
+(Addresses Sourceforge Bug: #1180572)</P>
+
+<P>Fixed gcc -Wall nits.</P>
+
+
+<H2><A NAME="1.37">E2fsprogs 1.37 (March 21, 2005)</A></H2>
+
+<P>Add support for checking the validity of Extended Attributes stored in
+inodes to e2fsck.</P>
+
+<P>Add support for dumping the contents of large inodes to debugfs,
+including the extended attributes stored in inodes.</P>
+
+<P>Fix mke2fs, e2fsck, debugfs, and the ext2fs_mkdir function so that
+when we create a new inode we make sure that the extra information in
+the inode (any extra fields in a large inode and any ea-in-inode
+information) is initialized correctly.  This can take place when
+mke2fs creates the root and lost+found directory, when e2fsck creates
+a new root inode or a new lost+found directory, and when the user uses
+the debugfs write, mknod, or mkdir commands.  Otherwise, the newly
+create inode could inherit garbage (or old EA information) from a
+previously deleted inode.</P>
+
+<P>Fixed a bug in e2fsck so it would notice if a file with an extended
+attribute block was exactly 2**32 blocks, such that i_blocks wrapped
+to zero.</P>
+
+<P>Added support to filefrag to detect files which are using the new
+experimental file extents format, and use the non-ext2 algorithm in
+that case.  Fixed a bug to avoid reporting a false discontinuity if
+there is one or more unallocated blocks at the beginning of a file.</P>
+
+<P>Duplicated a check for noticing whether or not the number of blocks
+(given a certain blocksize) is greater than 2**32 when the
+BLKGETSIZE64 ioctl is not available to ext2fs_get_device_size().  This
+allows mke2fs to automatically use a larger blocksize when creating a
+filesystem on a very large device when run on systems that do not
+support BLKGETSIZE64.</P>
+
+<P>Fix the I18N build which was broken in e2fsprogs 1.36 because the
+build system had been switched to treat the .gmo files as shipped
+files (for backwards compatibility with systems that have older GNU
+I18N tools installed), but the gen_tarball.in script was still
+removing the .gmo files from the official source distribution.</P>
+
+<P>Fixed various Debian packaging issues --- see debian/changelog for
+details.  (Addresses Debian Bugs ##296769, #299341)</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Added new functions to the e2p library which convert between a string
+and os_type: e2p_os2string() and e2p_string2os(), and used them to
+make the generated binaries more compact.</P>
+
+<P>Fixed a compile-time error on Darwin systems.</P>
+
+<P>Cleaned up the lib/ext2fs Makefile slightly.</P>
+
+<H2><A NAME="1.36">E2fsprogs 1.36 (February 5, 2005)</A></H2>
+
+<p>All of the patches that were applied to Fedore Core 3's
+e2fsprogs-1.35-11.2 have been integrated, although sometimes with a
+lot of bug fixes first.  Users of Fedora Core 3 are strongly
+encouraged to upgrade to e2fsprogs 1.36 as soon as possible.</p>
+
+<p>Add support for filesystem with the online resizing via resize inode
+feature.  Fixed numerous bugs from the Fedora patches.  The Fedora
+patches also didn't bother to do any consistency checking on the
+resize inode, or add any tests to the regression test suite.  The "-R
+resize=4g" option to mke2fs was a no-op in the Fedora patches, despite
+being listed in mke2fs's usage message.  All of these shortcomings
+have been corrected.</p>
+
+<p>E2fsck can also also fix filesystems trashed by Fedora's resize2fs
+program.  In order to do this, the user must run the commands:
+<blockquote>
+	debugfs -w /dev/hdXXX -R "features ^resize_inode</br>
+        e2fsck -f /dev/hdXXX
+</blockquote>
+Optionally, the ext2prepare command can be used to re-enable online
+resizing after the filesystem has been fixed.</p>
+
+<p>The fsck program will now accept an optional filedescriptor argument
+to the -C option.  (The Fedora version of this patch would sometimes
+cause fsck to ignore a parameter on fsck's command line in some rare
+cases, sigh.)</p>
+
+<p>Make sure e2fsprogs doesn't write garbage into the reserved portion of
+large inodes.</p>
+
+<p>Make sure resize2fs releases the blocks belonging to the old inode
+table blocks when moving the inode table.  (Addresses Debian Bug:
+#290894)</p>
+
+<p>Skip the r_resize_inode test if resize2fs is not compiled (due to
+configure --disable-resizer)</p>
+
+<p>E2fsck now checks the summary filesystem accounting information, and
+if any of the information is obviously wrong, it will force a full
+filesystem check.  (Addresses Debian Bug #291571)</p>
+
+<p>Fix e2fsck to not complain when the resize_inode feature is enabled,
+s_reserved_gdt_blocks is zero, and there is no DIND block allocated in
+the resize inode.</p>
+
+<p>Fix e2fsck to note delete symlinks that contain an extended attribute
+after the ext_attr feature flag has been cleared.  (Addresses Red Hat
+Bugzilla #146284).</p>
+
+<p>Add new utility program, copy_sparse.c, which is very useful
+for dealing with large sparse files (such as e2image files).</p>
+
+<p>Add support for jnl_blocks[] for debugfs's set_super_value.</p>
+
+<p>Fix filefrag so that it works correctly with sparse files.</p>
+
+<p>Filefrag -v will print first and last blocks.</p>
+
+<p>Add interpretation of OS Creator values for FreeBSD and Lites in mke2fs
+and dumpe2fs.</p>
+
+<p>Add mke2fs support so that it can support filesystems larger than 4TB
+automatically, by retrying with a 4k blocksize if the device size is
+too big to be expressed using a 1k blocksize.  (Addresses Sourceforge
+bug #1106631)</p>
+
+<p>Change blkid to test for NTFS first because Windows sometimes doesn't
+clear enough of the parition to confuse the probing routines into
+thinking the old filesystem type is still valid.  (Addresses Debian
+Bug #291990)</p>
+
+<p>Add support for swap partition label and uuid's in the blkid library.</p>
+
+<p>Add support to the blkid library to recognize Oracle ASM volumes.</p>
+
+<p>Make blkid -t display all devices that match the specified criteria,
+not just the first one, and work more consistently when the blkid
+cache file is not available or set to /dev/null.  (Addresses Debian
+Bug #290530 and #292425)</p>
+
+<p>Badblocks will now correctly display block numbers greater than
+999,999,999 in its progress display.</p>
+
+<p>The tune2fs program will not allow the user from setting a ridiculous
+number of reserved blocks which would cause e2fsck to assume the
+superblock was corrupt.  E2fsck's standards for what is a ridiculous
+number of reserved block has also been relaxed to 50% of the blocks in
+the filesystem.</p>
+
+<p>The blkid library will return vfat in preference to msdos, and ext3 in
+preference to ext2 (if the journalling flag is set) so that mount will
+do the right thing.  (Addresses Debian bug #287455)</p>
+ <p> 
+Mke2fs will now use the -E option for extended options; the old -R
+(raid options) option is still accepted for backwards compatibility.
+Fix a double-free problem in resize2fs.  (Red Hat Bugzilla #132707)</p>
+
+<p>Mke2fs will now accept a size in megabytes, gigabytes, and other units
+(via "32m" or "4g" on the command line) if the user finds this more
+convenient than specifying a block count.</p>
+
+<p>Fix an obscure, hard-to find bug in "e2fsck -S" caused by an inode
+cache conherency problem.</p>
+
+<p>Debugfs now supports a new command, set_inode_field, which allows a
+user to manually set a specific inode field more conveniently, as well
+as set entries in the indirect block map.</p>
+
+<p>Debugfs's set_super_value command has been enhanced so that the user
+can set most superblock fields, including the date/time fields and
+some of the more newsly added superblock fields.</p>
+
+<p>E2fsprogs programs now accept an offset to be passed to the file
+specifiers, via the syntax: "/tmp/test.img?offset=1024".</p>
+
+<p>E2fsprogs programs will now accept blocksizes up to 65536; kernel
+support on the x86 doesn't exist for now, but it can be useful on
+other architectures with page sizes greater than 4k.  There are 2.6
+kernel patches out there which enable this, but they are of this
+writing still experimental.</p>
+
+<p>The e2image command now takes the -s option which will scramble
+directory entries for raw image files.</p>
+
+<p>Fix a file descriptor leak in the filefrag program.</p>
+
+<p>Make sure e2fsck doesn't crash when /proc/acpi/ac_adapter is not
+present.</p>
+
+<p>Fix bug in debugfs where kill_file would lead to errors when deleting
+devices and symlinks.  (Sourceforge Bugs #954741 and #957244)</p>
+
+<p>Fix bug in the blkid library when detecting the ocfs1 filesystem </p>
+
+<p>Remove obsolete EVMS 1.x and a.out DLL support.</p>
+
+<p>E2fsck will attempt to recover from a journal containing illegal blocks.</p>
+
+<p>Fixed two potential ordering constraint problems in e2fsck which might
+cause the filesystem to be corrupted if e2fsck is interrupted during a
+(extremely narrow) race window.  Thanks to Junfeng Yang from the
+Stanford Metacompilation group for pointing this out.</p>
+
+<p>Fixed bug in e2fsck where it would not accurately detect whether or
+not the system is running on adaptor if the ACPI device representing
+the AC adapter didn't correspond to the what was used on IBM
+Thinkpads.</p>
+
+<p>Change e2fsck to accept directories greater than 32MB.</p>
+
+<p>Fix e2fsck so that a checkinterval of zero disables a time-based check
+of the filesystem.</p>
+
+<p>Debugfs will check the DEBUGFS_PAGER enviroment variable in preference
+to the PAGER environment variable.  (Addresses Debian Bug #239547)</p>
+
+<p>Tune2fs will not mark rewrite the superblock if the feature bitmasks 
+are not modified.</p>
+
+<p>The debugfs program will set the filetype information when creating a
+link.</p>
+
+<p>Add debugfs -d option to use a separate source of data blocks when
+reading from an e2image file.</p>
+
+<p>Add e2image -I option which allows the e2image metadata to be
+installed into a filesystem.</p>
+
+<p>Fixed bug in the badblocks program which caused "done" to always
+appear in english even when a translation was available.  (Addresses
+Debian Bug #252836)</p>
+
+<p>The blkid program has a new option -o which controls the output format
+of the blkid program; this is makes blkid more convenient to use in
+shell scripts.</p>
+
+<p>Fix a minor bug in uuid library, which was not using the full 14 bits
+of clock sequence when generating UUID's.</p>
+
+<p>Fix a Y8.8888K problem in the uuid library.</p>
+
+<p>Logsave now creates a new session id for itself to avoid getting
+killed by init whan transitioning between init levels.</p>
+
+<p>Change the licensing of the UUID library to be the 3-clause BSD-style
+license; this allows Apple to use the uuid library in Darwin.</p>
+
+<p>Add ocfs and ocfs2 probe support into the blkid library.</p>
+
+<p>Fix a memory and file descriptor leak in the blkid library.</p>
+
+<p>The blkid library will revalidate the device if the system time is
+earlier than last verification time of the device, since that
+indicates that the system time is probably nottrustworthy.</p>
+
+<p>The blkid library will override the default location of the blkid.tab
+file by the BLKID_FILE environment variable, if it is available.</p>
+
+<p>Change the getsize functions to use the BLKGETSIZE64 ioctl on Linux 2.6.</p>
+
+<p>Add various portability fixes for lame new versions of glibc, Darwin
+and GNU/KFreeBSD, as well as removing XSI:ism's.  (Addresses Debian
+Bugs #239934, #264630, #269044, #255589, #289133)</p>
+
+<p>Add support for Windows 9x/NT under Cygwin.</p>
+
+<p>Updated and clarified various man pages.  (Addresses Debian Bugs #236383,
+	#241940, #238741, #242995, #256669, #268148, #256760, #273679)</p>
+
+<p>Updated and fixed translations.   (Addresses Debian bugs #244105, #262836)</p>
+
+<p>Update the rpm spec files so that it works better with Fedora core 2
+and RH9.</p>
+
+<p>Fixed various Debian packaging issues (see debian/changelog).  In
+particular, fixed the Debian initrd scripts.  (Addresses Debian bugs
+#241183, #248050, #253595, #247775)</p>
+
+
+<h3>Programmer's notes: </h3>
+
+<p>Fixed various gcc -Wall warnings.</p>
+
+<p>The uuid library now has new functions uuid_unparse_upper() and
+uuid_unparse_lower() which forces the case of the hex digits to be
+upper case, or lower case.</p>
+
+<p>The build process has been speeded up by enhancing the subst program
+to update the modtime on the generated files even when the generated
+file hasn't changed.</p>
+
+<p>The uuid library now uses C99 stdint.h types instead of custom types.</p>
+
+<p>Updated config.guess and config.sub with newer versions from the FSF.</p>
+
+<p>Removed out of date .cvsignore files from the source distribution.</p>
+
+<p>The ext2fs_unlink() function will return an error if both the name and
+inode number are unspecified, to avoid doing something surprising
+(such as unconditionally deleting the first directory entry).
+Directory entries are now deleted by coalescing them with the previous
+directory entry if possible, to avoid directory fragmentation.  This
+is not an issue with the e2fsprogs suite, but may be a problem for
+some of the users of libext2fs, such as e2tools.</p>
+
+<p>Add support for version numbers of the form "1.36-rc1".</p>
+
+<p>Fix build of mke2fs.static.</p>
+
+<p>Add basic ext2fs library support for large (EA in inode) inodes.</p>
+
+<p>The test_io mechanism can now abort after n reads or writes to a
+particular block.  The block is specified by TEST_IO_BLOCK environment
+variable, and the read/write count by the TEST_IO_READ_ABORT and
+TEST_IO_WRITE_ABORT environment variables.  The block data is now only
+dumped if the 0x10 bit is set in TEST_IO_FLAGS.</p>
+
+<p>UUID_DEFINE() in the uuid library now creates a static variable, with
+__attribute__ ((unused)) if we are using GCC, so that UUID_DEFINE can
+be used in header files.</p>
+
+<p>Add support for the install-strip and install-shlibs-strip targets, as
+suggested by the GNU coding guielines.  "make install" no longer
+strips the binaries which are installed.</p>
+
+<p>Remove support for the --enable-old-bitops configure option which was
+only for very old sparc systems.</p>
+
+<p>Remove support for --enable-clear-htree; this was only needed during
+the early development of the htree patch.</p>
+
+<p>Use Linux-kernel-style makefile output so it is easier to see compiler
+warnings.</p>
+
+<p>Update gettext files to version 0.14.1.</p>
+
+<p>Update to use autoconf 2.5x.</p>
+
+<p>Improved support for compiling e2fsprogs under dietlibc.</p>
+
+<p>Make e2fsprogs portable to Solaris and FreeBSD systems.</p>
+
+<p>Add blkid_verify(), blkid_get_library_version(), and
+blkid_parse_version_string() functions to the blkid library.</p>
+
+<p>Add pkg-config files for e2fsprogs's libraries.</p>
+
+<p>Fix "make uninstall" to so that it removes everything that is installed.</p>
+
+<p>Add a configure --enable-maintainer-mode option which enables the
+makefile rules to rebuild the configure script from configure.in, and
+to reubuild the .gmo files in po directory.</p>
+
+<p>Drop the sparc assembly bitwise operations; it's less efficient
+than the GCC 3.4 compile code and triggers compiler warnings on
+sparc64.  Thanks to Matthias Andree for his analysis and suggestions.
+(Addresses Debian Bug #232326)</p>
+
+
+<H2><A NAME="1.35">E2fsprogs 1.35 (February 28, 2004)</A></H2>
+
+<P>E2fsck has a new -k option, which in conjunction with the -c options,
+preserves the existing badblocks list.</P>
+
+<P>Cleaned up e2fsck's preen-mode messages during the passes 1b, 1c, and 1d.</P>
+
+<P>E2fsprogs will now deal correctly with symlinks that contain
+extended attribute information, which can be created using SE Linux.
+(Addresses Debian Bug #232328)</P>
+                                                                               
+<P>Remove a double longjump into an invalid stack frame bug in e2fsck.
+(This was during an abort sequence, which normally worked on Linux and
+caused a core dump on other operating systems.)</P>
+
+<P>Fix NLS bug in e2fsck, by avoiding trying to expand an empty string
+(the NLS library will replace "" with the .po header information).</P>
+ 
+<P>Fix a bug in mke2fs which caused -T largefile or -T largefile4 to core
+dump due to a division by zero error.  (Addresses Debian bug #207082)</P>
+
+<P>Fixed a bug in e2fsck which caused it to incorrectly fix a filesystem
+when reconnecting a directory requires creating a lost+found
+directory.  (Addresses Debian bug #219640).</P>
+
+<P>Fixed a bug where e2fsck would bomb out if a journal needed to be
+replayed when using an alternate superblock.</P>
+ 
+<P>E2fsck will give an extra grace period before actually forcing a check
+if the laptop is running on battery.  The next time fsck runs while
+the system is on the AC mains, or after the grace period is exceeded,
+the filesystem will be checked.  (Addresses Debian bug #205177)</P>
+
+<P>E2fsck will inform the user when there are 5 or fewer mounts before a
+filesystem check will be forced.  (Addresses Debian bug #157194)</P>
+
+<P>Fix e2fsck's handling of corrupted indirect blocks in the bad block.
+We now correctly handle the case where there is an overlap between a
+block group descriptor or a superblock and a bad block indirect block.
+In the case where the indirect block is corrupted, we now suggest
+"e2fsck -c".</P>
+
+<P>Fix byte swap bugs in e2fsck that caused the journal backup location 
+in the superblock and symlinks created by SE Linux to be cleared
+by e2fsck on big-endian machines.  (Addresses Debian bug #228723)</P>
+
+<P>E2fsck -c now replaces the current list of bad blocks with the ones
+found by badblocks.</P>
+
+<P>Fix bugs in e2fsck and tune2fs which could cause a core dump if a
+non-existent LABEL or UUID specifier is to e2fsck or tune2fs.</P>
+
+<P>Fix a potential bug in e2fsck which could cause it to core dump when
+trying to print the location of the backup superblock.</P>
+
+<P>Protect against a potential core dump in e2fsck when printing a
+message about backup superblocks.</P>
+
+<P>Add support for backing up the journal inode location in the
+superblock.  E2fsck will automatically save the journal information in
+the superblock if it is not there already, and will use it if the
+journal inode appears to be corrupted.  ext2fs_add_journal_inode()
+will also save the backup information, so that new filesystems created
+by mke2fs and filesystems that have journals added via tune2fs will
+also have journal location written to the superblock as well.
+Debugfs's logdump command has been enhanced so that it can use the
+journal information in the superblock.</P>
+
+<P>E2fsck will now update all superblocks when moving the journal inode.</P>
+  
+<P>Shrink the size of the e2fsck executable by moving some initialized
+variables to the BSS segment.</P>
+
+<P>E2fsck will avoid printing the ^A and ^B characters which bracket the
+progress bar when stdout and stdin are a tty device instead of a pipe
+to another program.  (Addresses Debian bug #204137)</P>
+
+<P>Debugfs's mkdir command will automatically expand the directory if
+necessary.  (Addresses Debian Bug: #217892)</P>
+ 
+<P>Fixed a bug in debugfs so that copying a file from /dev/null uses the
+correct mode bits.  (Addresses Debian Bug: #217456)</P>
+ 
+<P>If the environment variables DEBUFS_PAGER and PAGER are not set,
+debugfs now searches for the appropriate pager to use, beginning with
+/usr/bin/pager, and then falling back to 'more' and 'less'.
+(Addresses Debian bug #221977)</P>
+
+<P>Debugfs will now support 2.6 device numbers where the major or minor
+number may be larger than 255.  (Addresses Sourceforge bug #865289)</P>
+ 
+<P>Chattr now stops processing options when it sees '--'.  (Addresses
+Debian bug #225188)</P>
+
+<P>Fix regression tests so they work correctly when e2fsprogs is compiled
+with configure --disable-htree.</P>
+
+<P>Fix bug in uuid library when there is no network card and the library
+is generating a time-based uuid.  The random MAC address was not
+correctly generated to be a multicast address.</P>
+ 
+<P>Add compile_et extensions from Heimdall that were missed the first time
+around.</P>
+
+<P>Fix bug in badblocks when using O_DIRECT; we need to make sure that
+we're reading from an offset which is page aligned.  For read-only and
+read-write tests, we try to recover after an error so that we can
+continue reading on page-aligned boundaries.  (Addresses Debian Bug
+#203713)</P>
+  
+<P>Badblocks now checks 64 blocks at a time instead of 16.  (Addresses
+Debian bug #232240)</P>
+ 
+<P>Updated and clarified various man pages.  (Addresses Debian Bug
+#206845, #222606, #214920, #232406)</P>
+
+<P>Updated and fixed translations.   (Addresses Debian bugs #200086, #214633)</P>
+
+<P>Fixed various Debian packaging issues (see debian/changelog).</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fixed a build problem so that e2fsprogs would compile with the
+--enable-profile option to configure selected.  (Addresses Sourceforge
+bug #811408)</P>
+ 
+<P>Fixed C++ problems with the ext2fs.h header.  (Addresses Red Hat
+Bugzilla Bug #112448)</P>
+                                                                               
+<P>Centralize code which calculates the location of the superblock
+and block group descriptors so that it is in a single library routine.</P>
+
+<P>Added two new functions, ext2fs_file_open2() and
+ext2fs_inode_io_intern2() which take a pointer to an inode structure.</P>
+
+<P>Fix compile_et to output the correct prototype for
+initialize_xxx_err_table_r() in the header file.  (Addresses Debian
+bug #204332)</P>
+
+<P>In the lib/et makefile, make sure com_err.info is deleted on "make clean".</P>
+  
+<P>Fix 64-bit warnings in e2fsprogs pass1b by using inttypes.h if
+present.  This is for when we try stuffing an int into void * pointer.</P>
+
+<P>Fix type-punning which can cause gcc 3.x to miscompile code by getting
+confused about pointer aliasing.  ext2fs_getmem(), ext2fs_free_mem(),
+and ext2fs_resize_mem() all now take a 'void *' instead of a 'void
+**'.  The EVMS code uses an ugly union approach since we don't want to
+modify the EVMS interfaces. </P>
+
+<P>Make sure all Makefiles use $(MAKE) rather than hardcoded "make", to
+aid build process on systems can use invoke GNU make as "gmake".</P>
+
+<P>Added regression testing for mke2fs.</P>
+
+<P>Fixed gcc -Wall nitpicks.</P>
+
+<P>Fixed various compiler warnings.</P>
+
+<P>Add portability fixes for FreeBSD and for using fsctl under Darwin to
+support ext2 ioctl's.</P>
+
+
+<H2><A NAME="1.34">E2fsprogs 1.34 (July 25, 2003)</A></H2>
+
+<P>Fixed a bug introduced in E2fsprogs 1.30 which caused fsck to spin in
+a tight loop while waiting for a child fsck to exit in some cases.
+This burns CPU times which slows down the low-level filesystem check.</P>
+
+<P>Added code to mke2fs to assure that the default block size for a
+filesystem is at least as big as the sector size of the device, if it
+can be determined.</P>
+
+<P>Changed mke2fs and resize2fs to round the default size of a filesystem
+to be an even multiple of the VM pagesize in order to avoid a Linux
+kernel bug introduced when the storage of the buffer cache was moved
+into the page cache.</P>
+
+<P>Mke2fs will warn the user when creating a filesystem with journaling
+and a blocksize greater than 4096.  (Addresses Debian bug #193773)</P>
+
+<P>Fixed a bug in resize2fs which caused it to fail on filesystems with a
+non-empty bad block list.  Resize2fs now discards any blocks on the
+badblock list which are no longer part of the filesystem as the result
+of a filesystem shrink.  (Note: this means that shrinking and then
+enlarging a filesystem is no longer a reversible operation;
+information about bad blocks in the part of the filesystem which is to
+be chopped off will be lost.)</P>
+
+<P>Changed resize2fs so the user can use prefixes to specify the units of
+the new filesystem size (sectors, kilobytes, megabytes, or gigabytes),
+and to make the error and informational messages explicitly display
+the blocksize used by the filesystem, in order to avoid confusion.
+(Addresses Debian bug: #189814)</P>
+
+<P>Added a new debugfs command, dump_unused, which dumps the contents of
+all unused blocks to stdout.  (Useful as an emergency try-to-find
+deleted data command.)</P>
+
+<P>Added a new debugfs command, imap, which prints the location of a
+specified inode in the inode table.</P>
+
+<P>Fixed a bug in the badblocks program which caused it to use one bit of
+randomness in its non-destructive read/write test, instead of using a
+full 8 bits of randomness.</P>
+
+<P>Added a new option (-t) to badblocks, which allows the user to control
+the test pattern(s) used when checking a disk.</P>
+
+<P>The blkid probe function now more correctly detects UDF filesystems.</P>
+
+<P>Fixed a bug in the blkid library which caused it to not update its
+cache if a filesystem changes from having a label to not having a
+label.</P>
+
+<P>Fixed a bug in the blkid library which could avoid an infinite loop
+in blkid_find_dev_with_tag() if /proc is not mounted and there the
+/etc/blkid.tab file has not yet been created.</P>
+
+<P>Fixed the badblocks program so that the destructive read/write test
+honors the -c option, and to use O_DIRECT when possible to avoid
+thrashing the system block buffer cache.</P>
+
+<P>Fixed various NLS issues.
+<UL>
+<LI> Added Czech and Sweedish translations
+<LI> Removed testing NYC translation
+<LI> Fixed NLS support for message abbrevations in e2fsck
+<LI> Remove de-utf.po, since we shouldn't have two versions using different
+	charset encodings.
+<LI> Used ngettext() (abbreivated with the macro P_(str1, str2, n)) to 
+	simplify the statistics reporting in e2fsck.
+</UL></P>
+
+<P>Changed configure.in so that its defaults for *BSD systems no longer
+build an fsck wrapper, and not to install in /usr/local by default.</P>
+
+<P>Fixed some minor spelling errors/typo's in e2fsck and the configure
+script.</P>
+
+<P>Fixed various Debian packaging issues (see debian/changelog). </P>
+
+<P>Updated and clarified man pages.  (Addresses Debian Bug #195616)</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fix gcc -Wall nitpicks.</P>
+
+<P>Updated gettext implementation used by e2fsprogs to 0.11.5, and enable
+NLS support by default.  (Added partial workaround for gettext/Darwin
+incompatibility problems.)</P>
+
+<P>Added full MIT KRB5 and Himdall compaibility support to the com_err
+library and the compile_et program.  (Addresses Debian bug #191900)</P>
+
+<P>Added the blkid_known_fstype() function to the blkid library, which
+returns true if it is passed a filesystem type which is recognized by
+the blkid probing functions.</P>
+
+<P>Improved the documentation for the blkid library.</P>
+
+<P>Added the ext2fs_get_device_sectsize() function the the ext2fs library, which
+returns the hardware sector size of a device, if it is available.</P>
+
+<P>Added a dependency in the blkid library's .so file to the uuid
+library, since the former uses the latter.  (Addresses Debian bug
+#194094)</P>
+
+<P>Added --with-diet-libc and --disable-evms to the configure script.</P>
+
+<P>Fixed a minor memory leak in the badblocks program.</P>
+
+<P>Fixed a portability problem in tune2fs --- not all systems have strptime().</P>
+
+<P>Fixed a portability problem in debugfs with the use of getopt() more
+than once.  Old-style BSD, new-style BSD, and Linux C libraries all do
+things differently.</P>
+
+<P>Add support Windows support to ext2fs_get_device_size().</P>
+
+<P>Added (normally disabled) debugging code to the Unix I/O manager which
+causes it to disable all userspace caching if the NO_IO_CACHE is
+defined.</P>
+
+<P>Changed the test I/O manager so it can always be linked into e2fsck,
+mke2fs, and tune2fs if enabled via --enable-test-io-debug to the
+configure script.  The test I/O manager will only print any debugging
+information if the TEST_IO_FLAGS or TEST_IO_BLOCK environment
+variables are set, which specifies which I/O operations are logged and
+a block number to watch, respectively.  The log messages are sent to
+stderr by default, unless a filename is specified via the
+TEST_IO_LOGFILE environment variable.</P>
+
+
+<H2><A NAME="1.33">E2fsprogs 1.33 (April 21, 2003)</A></H2>
+
+<P>Added a new utility program, logsave, which captures the output of a
+command in a log file, even if the containing directory hasn't been
+mounted yet (in which case the it saves the output in memory until it
+can write out the logfile).  This is useful for capturing the
+output of fsck during the boot sequence.</P>
+
+<P>Fixed some portability problems that were causing problems under
+the Cygwin32 environment.</P>
+
+<P>Mke2fs now interprets a negative number to the -b option as a minimum
+block size.</P>
+
+<P>Fixed a bug in mke2fs which was incorrectly checking the argument to
+the -g option if the default block size was used.  (Addresses Debian
+bug #188319)</P>
+
+<P>Fsck now explicitly ignores tmpfs and devpts, and it will complain if
+it can not find filesystem checkers for jfs, reseirfs, and xfs.</P>
+
+<P>E2fsck now updates the global free block and inode counters from the
+block group specific counters quietly.  This is needed for an
+experimental patch which eliminates locking the entire filesystem when
+allocating blocks or inodes; if the filesystem is not unmounted
+cleanly, the global counts may not be accurate.</P>
+
+<P>Imported bug fixes to the EVMS plugin from the EVMS 2.0 tree.  (EVMS
+2.0 is not yet supported; this only pulled in the bug fixes: fixed
+possible hangs caused by bugs in calling waitpid, and not setting the
+pipe to non-blocking mode; also fixed a file descriptor leak; made
+sure all functions call log entry/exit functions.)</P>
+
+<P>Badblocks now flushes its output file as bad blocks are discovered.</P>
+
+<P>The uuid library is now more paranoid about assuming the correctness
+of the /dev/random device; it mixes in a stream of bytes from
+random/srandom, just in case.</P>
+
+<P>Update Debian files to reflect the fact that I am now the Debian
+maintainer of e2fsprogs.  Other various Debian-specific packaging
+cleanups.</P>
+
+<P>Move the source tarball generation functions from the top-level
+makefile to the util/gen-tarball script.  </P>
+
+<P>Updated the Turkish .po translation file.</P>
+
+<P>Added heimdall and MIT krb5 extensions to the com_err library to make
+it more compatible with com_err libraries from those distributions.</P>
+
+<P>Changed dumpe2fs to always display the superblock fields relating to
+the journalling and/or directory indexing feature even if those
+features are not enabled.</P>
+
+<P>Updated and clarify copyright statement vis-a-vis alpha releases of
+e2fsprogs.</P>
+
+<P>The ss library will now try to dynamically link to the readline
+library and use it if it is present in the system.  This means that
+the debugfs program now has line editing and history features.  The
+SS_READLINE_PATH environment variable is used to find a readline or
+readline-compatible library.</P>
+
+<P>E2fsck now finds most duplicate filenames (all when rebuilding all
+directories via the -D option) and offers to delete or rename
+duplicate filenames/directory entries.  (Addresses Debian Bug #176814).</P>
+
+<P>Fix bug in e2image.  When writing out a raw image file, include data
+blocks from symlinks that do not store the symlink within the inode.</P>
+
+<P>Fix bug in resize2fs which incorrectly moved the block and inode
+bitmaps for sparse superblock filesystems and incorrectly marked
+blocks as in use.  (Addresses Debian bug #174766)</P>
+ 
+<P>Added a new shared library, the blkid library, which efficiently
+allows fsck, mke2fs, e2fsck, and tune2fs to be able to look up LABEL
+and UUID filesystem specifiers without needing to search all of the
+devices in the system.  Instead, the device is looked up in a cache
+file, and then verified to make sure the blkid cache is correct.</P>
+
+<P>Tune2fs and e2label will accept LABEL=xxx and UID=yyy specifiers for
+the device name, using the blkid library.  (Addresses Debian bugs
+#166048, #179671)</P>
+
+<P>Fsck now supports backslash escapes in /etc/fstab so that \040 can be
+used for spaces in device labels.</P>
+
+<P>Removed 32-bit limitations for debugfs's dump command.</P>
+
+<P>If the user specifies a large number of inodes, Mke2fs will
+automatically adjust the number of blocks per group to find a valid
+set of filesystem parameters.</P>
+
+<P>Add workaround to detect broken MD devices where when some of the
+underlying devices are marked read-only, writes to the MD device are
+silently dropped.  E2fsck will detect if there is an attempt to run
+the journal twice, and abort with an error if this is the case.
+(Addresses IBM Bugzilla bug #1226)</P>
+
+<P>E2fsck will print an error if more than one of the -p/-a, -n or -y
+options are specified.</P>
+
+<P>E2fsck will fix HTREE corruptions in preen mode, without stopping the
+boot process.  This is needed because the 2.4 ext2 filesystem
+accidentally had the INDEX_FL backwards compatibility code removed.</P>
+
+<P>Mke2fs no longer creates filesystems with the dir_index flag set by
+default; the user has to specifically request it.</P>
+
+<P>Update and clarified various man pages. (Addresses Debian bugs
+#173612, #175233, #175113, and #170497, #185945, #188318)</P>
+
+<P>Created man page for the mk_cmds program (from the libss library).</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fix various gcc -Wall nits.</P>
+
+<P>Fixed a lot of portability problems that caused e2fsprogs not to build
+successfully under Solaris and Apple/Darwin.</P>
+
+<P>Fixed a Makefile dependency to allow building e2fsprogs using parallel
+make jobs.</P>
+
+<P>Changes to create a subset distribution which consists only of the
+et, ss, uuid, and blkid libraries.  The configure script and top-level
+makefile were changed to support working with a subset distribution.</P>
+
+<P>Removed EXT2_FEATURE_RO_COMPAT_BTREE_DIR mention of since it's not
+actually used, and might people who are looking for
+EXT2_FEATURE_COMPAT_DIR_INDEX, which is in use.</P>
+
+<P>Updated debian files to fix a number of Lintian warnings.</P>
+
+<P>Updated config.guess and config.sub with newer versions from the FSF.</P>
+
+<P>Removed unnecessary libraries from being linked into the fsck, lsattr, 
+chattr, and blkid executables.</P>
+
+
+<H2><A NAME="1.32">E2fsprogs 1.32 (November 9, 2002)</A></H2>
+
+<P>Fixed a bug in the Unix I/O routines which caused needless writebacks
+of clean blocks from the unix_io cache (they were erroneously marked
+as being dirty, so they were getting written back to disk before
+getting evicted from the disk cache).  This was harmless, but it
+significantly slowed down e2fsck.</P>
+
+<P>Made some other minor optimizations to the Unix I/O routines to save a
+small amount of CPU time.</P>
+
+<P>Updated internationalization files.</P>
+
+<H2><A NAME="1.31">E2fsprogs 1.31 (November 8, 2002)</A></H2>
+
+<P>Update EVMS ext2fsim plugin with EVMS 1.2.  (We still support
+compiling the fsim plugin with EVMS 1.0 and 1.1.)  Add better error
+handling for child process that die unexpectly.  Add a hack to force
+mkfs to create filesystems that won't cause problems with hardware
+that has 2k or 4k minimum blocksize requirements.  Read from child
+processes in non-blocking mode, so that the GUI continues to update.</P>
+
+<P>Fix e2fsck so that it returns the appropriate exit code when the root
+filesystem has been changed, so that system's rc scripts will be told that 
+the system needs to be rebooted.</P>
+
+<P>Fix a bug in ext2fs_flush/ext2fs_close; when the MASTER_SB_ONLY flag
+was set, some of the descriptor blocks that should have been written
+out were getting skipped.</P>
+
+<P>Changed e2fsck to force out changes to the backup copies of the
+superblock and block group descriptors when important changes are made
+to those data structures.</P>
+
+<P>Fix a bug where e2fsck could erroneously mark a filesystem as being
+clean if a check of dirty filesystem is interrupted with a ^C.  (Bug
+introduced in e2fsprogs 1.28.)</P>
+
+<P>If journal debuging is enabled using --enable-jbd-debug, the debugging
+level is now set via the E2FSCK_JBD_DEBUG environment variable.</P>
+
+<P>If byteswapping support is disabled using configure --disable-swapfs,
+skip the tests which depend on byte-swapping, so that "make check"
+won't bomb out.</P>
+
+<P>Lshattr will now display the indexed directory flag.  Also, some of
+the more esoteric compression flags are supressed unless compression
+support has been enabled.</P>
+
+<P>Update man pages.</P>
+
+
+<H2><A NAME="1.30">E2fsprogs 1.30 (October 31, 2002)</A></H2>
+
+<P>When resizing a filesystem, and inodes need to moved, resize2fs will
+update the inode's ctime field, and the mtime field of the containing
+directories, so that incremental backups using dump/restore will work
+correctly.</P>
+
+<P>In order to avoid spurious errors, e2fsck wil check the last
+superblock write time to determine whether or not it can safely use
+the LOW_DTIME checks to determine if there are inodes on the orphan
+inode linked list that had somehow gotten disconnected.  (Addresses
+Sourceforge bug #620980)</P>
+
+<P>Partition in /proc/partitions that being with the string "lvm" are
+considered real partitions even if they do not end with a number.</P>
+
+<P>Fixed a bug in the the uuid generation function, where if /dev/urandom
+is not present, but /dev/random is, and there isn't sufficient
+entropy, the get_random_byte function could spin a loop forever.</P>
+
+<P>E2fsck, mke2fs, etc. will now reliably notice when image files are
+mounted using the loopback interface.  (Addresses Sourceforge bug
+#619119)</P>
+
+<P>When flushing buffers (as is done by badblocks, for example) check to
+see if the BLKFLSBUF ioctl succeeds, and if so, avoid using the
+FDFLUSH ioctl which causes the MD device driver which causes confusing
+syslog messages about obselete ioctl messages.  (Addresses Sourceforge
+bug #545832).</P>
+
+<P>Debugfs's write command now checks to see if the destination filename
+exists before creating it.  (Addresses Sourceforge bug #478195.)</P>
+
+<P>When installing man pages, search for compressed man pages using all
+commonly used compression extensions (i.e., .Z, .gz, .bz2, etc.)</P>
+
+<P>Fixed a bug in fsck where multiple filesystems specified on the
+command were not being checked in parallel due to a logic bug
+introduced to support the FSCK_MAX_INST environment variable.</P>
+
+<P>We have added a new superblock field, s_mkfs_time, which indicates
+when a filesystem was created.  It is set via mke2fs, and printed out
+by dumpe2fs, but is not actually touched by the kernel.</P>
+
+<P>Dumpe2fs has been made more robust by not aborting if there is an
+error reading the block/inode bitmaps; instead it will still print out
+the location of the block/inode bitmaps and inode table.</P>
+
+<P>Add support for the an alternative block group descriptor layout which
+allows for on-line resizing without needing to prepare the filesystem
+in advance.  (This is the incomat feature flag meta_bg.)</P>
+
+<P>Add support for storing default mount options in the superblock, so
+that the filesystem can be mounted with specific mount options without
+needing to specify them on the mount command line or in the /etc/fstab
+file.</P>
+
+<P>Add support for a new inode flag, which is to be used for indicating
+the top of directory hierarchies for the Orlov block allocator.</P>
+
+<P>Fix e2fsck so that if it creates the lost+found directory, it does so
+with the more apporpriate permissions of 0700.  Also change
+mklost+found so that it also creates the directory 0700.</P>
+
+<P>Fixed format bug in e2fsck if NLS is in use.</P>
+  
+<P>Add a German translation for e2fsprogs's NLS support.</P>
+
+<P>Fixed e2fsck so that it more handles BAD_BLOCK_IN_INODE_TABLE even at
+the beginning of the inode table.  This won't matter much, since if
+there is a bad block at the beginning of the inode table, the root
+directory won't be available.  But at least e2fsck won't crash in this
+case.</P>
+
+<P>Fixed endian problems in the htree code for e2fsck and debugfs.</P>
+  
+<P>When byte-swapping a filesystem on a PPC architecture, byte-swap the
+bitmaps since the historical big-endian ext2 variant had byte-swapped
+bitmaps, and the ext2fs library assumes this.  This fixes the
+regression test suite on PPC machines.</P>
+
+<P>Fix e2image so that it handles a bad block in the inode table
+appropriately.</P>
+
+<P>E2fsck now uses a more sophisticated algorithm to salvage corrupted
+directories that recovers more information in the corrupted directory
+block.</P>
+
+<P>E2fsck now performs additional consistency checks on indexed (HTREE)
+directories.</P>
+
+<P>Fix bug where efsck might get confused about whether a completely
+empty directory block is an empty leaf block or an interior htree
+node.  This could cause e2fsck to get confused into think that a valid
+indexed directory was corrupted.</P>
+
+<P>E2fsck no longer creates an empty directory entry at the end of a
+directory block when optimizing a directory.  This would cause some
+earlier versions of the dxdir kernel code to corrupt the directory
+when attempting to split a node containing an empty directory entry.</P>
+
+<P>E2fsck could sometimes in rare circumstances leave the indexed flag
+set after a small directory was optimized by compressing it instead of
+indexing it.  (This should never happen in real life, since
+directories that small wouldn't have been indexed, but better safe
+than sorry.)</P>
+
+<P>E2fsck now only updates the master superblock in all cases.  This
+slightly shortens its run time.</P>
+
+<P>Ext2ed can deal with directory entries of length 0; previously it
+would get stuck in an infinite loop.</P>
+
+<P>Fsck now has support for reiserfs volumes when parsing LABEL= and UUID=
+specifiers.  (Sourceforge patch #613447)</P>
+
+<P>Badblocks will now work correctly on read-only devices such as
+CD-ROM's.  (Sourceforge patch #600451)</P>
+
+<P>Updated and clarified man pages.  (Addresses Debian bug #167108)</P>
+
+<H2><A NAME="1.29">E2fsprogs 1.29 (September 24, 2002)</A></H2>
+
+<P>Fixed a bug in e2fsck which could corrupt a directory when optimizing
+it (via the -D option) or rebuiliding the hash tree index with a 1 in
+512 probability, due to a fence post error.</P>
+
+<P>Fixed a bug in the LVM support code which caused LABEL='xxx' not to
+work correctly.</P>
+
+<P>Mke2fs now enables the directory indexing flag by default.  (Since
+this is a compatible feature flag, it's safe to do so.)</P>
+
+<P>Tune2fs will support setting the directory indexing feature flag.  It
+will automatically set up the default hash algorithm and hash seed
+fields in the superblock.</P>
+
+<P>If the bone-headed user enters the root filesystem twice in
+/etc/fstab, the -R option which skips the root filesystem will skip
+all of them.  (Addresses Debian bug #159423).  Note!  This is not a
+precedent for dealing intelligently with any other kind of doubled
+entry in /etc/fstab!</P>
+
+
+<H3>Programmer's notes:</H3>
+
+<P>Removed perror declaration in lib/et/internal.h.  All modern systems
+can be expected to define perror() these days.  Besides, the lib/et
+code wasn't using perror at all anyway.  :-)</P>
+
+<H2><A NAME="1.28">E2fsprogs 1.28 (August 31, 2002)</A></H2>
+
+<P>Add support for the Hashed-Tree Directory Indexing to e2fsck.  Support
+for setting the htree flag is not included yet, although it can be
+manually turned on via the debugfs program.</P>
+
+<P>Clarified e2fsck error message which is printed when it cannot find
+sufficient contiguous block when relcating filesystem metadata.</P>
+
+<P>Added support for building an EVMS plugin module for ext2/3.  This
+module is substantially the same as the EVMS module shipping with EVMS
+1.1, with one or two bugfixes.  E2fsprogs can also build this plugin
+for use with EVMS 1.0 (which did not include the ext2 plugin module),
+if the configure --enable-old-evms flag is given.</P>
+
+<P>Fsck will search through EVMS volumes when trying to resolve
+filesystem specifications such as LABEL=xxx or UUID=xxx.</P>
+  
+<P>Added a new utility program, /sbin/findfs, which will return
+filesystem specifications such as LABEL=xxx or UUID=xxx, and prints
+the device name.</P>
+
+<P>Update and clarified various man pages. (addresses Debian Bug #145044,
+#146437, #131350, #151990, #144621, #141938)</P>
+
+<P>If there are no filesystems specified on fsck's command line, fsck now
+treat that as if the -As options were given.  Previously it would
+simply do nothing.  (Addresses Debian Bug #153102)</P>
+
+<P>Mke2fs no longer treats a failure to be able to clear the MD signature
+at the end of the filesystem as a fatal error.  (Addresses Debian Bug
+#155007)</P>
+
+<P>The e2p library functions (which are used by lsattr and chattr) now
+double check to make sure the file is a regular file or directory
+before attempting to use the ext2 ioctls.  Some device drivers
+unfortunately respond to the ext2 ioctl's with unknown behaviour.
+(Addresses Debian Bug #152029).</P>
+
+<P>The extended attribute handling has been updated to correspond with
+the latest V2 bestbits ACL code.</P>
+
+<P>Fixed bug in e2fsck which caused it to not clear the dtime field when
+processing truncated inodes on the orphan list.  This could cause data
+loss(!) if a filesystem is rebooted before a truncate has been
+committed.</P>
+
+<P>E2fsck now uses red/black trees in pass1b, which removes some O(n**2)
+algorithms.  This makes e2fsck much faster in the case of severely
+corrupted filesystems where a large number of blocks are claimed by a
+large number of inodes.  (Thanks to the 2.5 IDE device driver for
+inspiring this work.)</P>
+
+<P>Resize2fs has been significantly sped up when shrinking and expanding
+a filesystem by a very small number of blocks (for example, when EVMS
+is converting a partition to be an EVMS legacy volume).</P>
+
+<P>Added a new option to e2fsck, -D, which will optimize or compress all
+of the directories in the filesystem.</P>
+
+<P>E2fsck now catches SIGINT and SIGTERM to make sure it will can
+properly clean up and only exit at safe points.  Fsck will pass
+SIGINT/SIGTERM to its child processes, and wait until they have all
+exited before it exits.</P>
+
+<P>The uuid parsing code in the uuid library now properly complains when
+an illegally formated uuid is presented to it.  (Addresses Debian bug
+#152891)</P>
+
+<P>Restrict use of the 2.4 setrlimit ABI f*ckup to kernels between 2.4.10
+and 2.4.17, since the workaround can cause problems when using a 2.4
+kernel with an old version of glibc built with the 2.2 headers.</P>
+
+<P>Fixed a bug in mke2fs where it wasn't properly clearing the initial
+superblock used by other filesystems.  (Addresses Debian bug #147256.)</P>
+
+<P>Added support for the synchronous directory feature written by Andrew
+Morton.</P>
+
+<P>The debugfs program can delete directories using the rmdir command.</P>
+
+<P>Add support for 8k and 16k filesystems (for systems with page sizes
+that are greater or equal to 8k or 16k, respectively).  Note that
+these filesystems can not be mounted on x86 systems, or other systems
+with only 4k page sizes, due to limitations in the current Linux VM
+code.</P>
+
+<P>Resize2fs requires that the filesystem state be valid and have no
+errors; otherwise, e2fsck -f must be run first.  (Previously it simply
+required that the last fsck time be greater than the last mount time.)</P>
+
+<P>Configure now defaults the man pages directory to /usr/share/man on
+Linux systems.</P>
+
+<P>E2fsck now offers to truncate inodes which contain too many blocks (so
+that i_blocks would overflow.  Also fixed handling of large sparse
+files.</P>
+
+<P>E2fsck now more completely checks for symlink validity, including
+requiring NULL termination and length checks.</P>
+
+<P>E2fsck will offer to try forcing a disk write to remap a bad block
+after finding a read error when reading a filesystem metadata block.</P>
+
+<P>Fixed a bug in debugfs which caused the -b and -s options to crash
+debugfs, as well as breaking the testb, setb, and clearb functions.</P>
+
+<P>Added a bmap command to debugfs which calculates the logical to
+physical block mapping for a particular inode.</P>
+
+<P>Fixed a bug in code which checked to see if a device was mounted which
+sometimes (rarely) failed in the case of a plain file.</P>
+
+<P>Fixed a bug in resize2fs where when it reported an error, it would
+print a message erroneously indicating that the filesystem had been
+resized before it aborted.</P>
+
+<P>When resizing a plain file which is smaller than the requested size,
+resize2fs will attempt to extended the file so that programs like
+e2fsck will not complain that the file is too small.</P>
+
+<P>Resize2fs will print the actual new size of the filesystem when it is
+finished resizing.</P>
+
+<P>Fixed a bug in debugfs where "ls -l" would report incorrectl file type
+information on big-endian systems.</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fixed collisions with C++ reserved words.</P>
+
+<P>Added portability fixes for building e2fsprogs on the HURD and AIX.</P>
+
+<P>Added the ext2ed program for creation of test cases.  (ext2ed has many
+limitations and bugs which make it unsuitable for production use.)</P>
+
+<P>The ext2fs_read_dir_block2 and ext2fs_write_dir_block now take a new
+flag, EXT2_DIRBLOCK_V2_STRUCT, which will will reverse when the
+name_len field is byte swampped on big-endian machines, since in the
+V2 structure, name_len is a char field which is doesn't need to be
+byte swapped --- except if an old-style kernel had byte-swapped the
+name_len field as part of the V1 structure.</P>
+  
+<H2><A NAME="1.27">E2fsprogs 1.27 (March 8, 2002)</A></H2> 
+
+<P>The warning messages for mke2fs now go to standard error.</P>
+
+<P>Fixed to make sure "make check" runs all of the test programs with
+LD_LIBRARY_PATH set, so that we test the libraries in the build tree.</P>
+
+<P>The mke2fs program checks the boot sector for the BSD disk label, and
+avoids erasing it if it is there.</P>
+
+<P>Fixed a bug in e2fsck which caused it to core dump if the journal
+inode was missing when it was supposed to be there.</P>
+
+<P>E2fsck now prints ranges in pass 5 when printing deltas for the block
+and inode bitmaps.</P>
+
+<P>Debugfs's "ls -l" command now will print out the file type information
+in the directory entry.</P>
+
+<P>Create man pages and hard links for fsck.ext3 and mkfs.ext3.  If
+mke2fs is invoked as mkfs.ext3, create the filesystem with a journal.</P>
+
+<P>Debugfs can now examine the experimental directory indexing
+information.</P>
+
+<P>Fixed bug in debugfs which caused it to core dump if modify_inode is
+called without an open filesystem.</P>
+
+<P>The debugfs lsdel command now runs its output through a pager first.</P>
+
+<P>When installing manual pages, remove the compressed manual pages first.</P>
+
+<P>Synchronized with Debian's packaging information for e2fsprogs-1.26-1.</P>
+
+<P>Fix the 2.4 resource limitation workaround introduced in 1.26 which
+actually broke things on mips32, sparc32, and Alpha platforms.</P>
+
+<P>Updated the I18N code so that calls to setlocate(LC_CTYPE, 0) are made
+(which is required by the newer libintl libraries).</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fixed various gcc -Wall complaints.</P>
+
+<P>Fixed a few memory leaks in the e2fsck journaling code, and in the
+ismounted code checking for a swap device.</P>
+
+<P>Add new inode I/O abstraction interface which exports an inode as
+an I/O object.</P>
+  
+<P>Exported ext2_file_flush as a public interface.</P>
+  
+<P>In ext2_file_write, we now mark the buffer void * argument as a const,
+since ext2_file_write doesn't modify the buffer.</P>
+
+<P>Lots of small random portability fixes to make e2fsprogs build under
+AIX --- even without the 5L compatibility toolkit, and even using the
+uber-crippled AIX native C compiler.</P>
+
+
+<H2><A NAME="1.26">E2fsprogs 1.26 (February 3, 2002)</A></H2>
+
+<P>Dumpe2fs will keep going now if the bad block inode can't be read.
+(Previously it stopped with a fatal error.)</P>
+
+<P>E2fsck will now give an opportunity to run the journal even if the
+recovery flag is not set.  This is the default behaviour if e2fsck is
+using a backup superblock, since the needs_recovery flag will never be
+set in the backup superblock copies.</P>
+
+<P>E2fsck now automatically finds the backup superblock/group descriptors
+even when the primary superblock is completely destroyed for 2k and 4k
+filesystems.  (Previously it just guessed/assumed that we were dealing
+with a 1k filesystem in that case, and users had to manually specify
+the backup superblock number.)</P>
+
+<P>Fixed a bug in e2fsck where it dereferences a null pointer when there
+is a problem opening a filesystem in preen mode.</P>
+
+<P>E2fsck now handles external journals correctly; previously it trashed
+the external journal device if the journal needed to be replayed.</P>
+
+<P>Work around ulimit incompatibility problem caused by recent 2.4
+kernels; the unix IO module will automatically try to set any resource
+limits to be infinite on startup.</P>
+
+<P>Fixed a bug in e2fsck where it wasn't allocating a new block or inode
+bitmap if it wasn't present and the blocksize was 2k or 4k.
+(Addresses Debian Bug #116975)</P>
+
+<P>E2fsck will check and fix botched ext3 V1 to V2 superblock updates by
+clearing the new V2 fields if they do not make sense or if the ext3
+superblock is version 1 superblock.</P>
+
+<P>E2fsck will automatically relocate the ext3 journal from a visible
+file (i.e., /.journal) to an hidden inode if the filesystem has been
+opened read/write.  This allows the users to add a journal while the
+filesystem is mounted, but the next time the system is rebooted, the
+journal file will disappear.  This avoids problems with backups,
+stupid operators with superuser bits, etc.</P>
+
+<P>Fix a bug in fsck where it would not support a filesystem type of
+"auto" if the device was specified in terms of LABEL=xxx or UUID=xxx.</P>
+
+<P>Fsck now supports fstab entries of the form "ext3,ext2".  It will also
+automatically identify reiserfs filesystems.</P>
+
+<P>The number of processes spawned by fsck can now be limited using the
+FSCK_MAX_INST environment variable.</P>
+
+<P>Fsck now searchs the LVM proc hierarchy to find logical volumes which
+should be searched for  UUID and label information.</P>
+
+<P>Work around a bug in 2.4.10+ kernels by trying to unset the filesize
+limit if at all possible, when opening a block device.  (The filesize
+limit shouldn't be applied against writes to a block device.)</P>
+
+<P>In mke2fs and e2fsck, specifying the -c option twice will now do
+a read/write test on the disk.  Update the man pages to encourage
+using the -c option, and to discouraging running badblocks separately,
+since users tend to forget to set the blocksize when running 
+badblocks.</P>
+
+<P>Mke2fs now automatically clears the immutable attribute on a
+pre-existing .journal file left over from a previous failed attempt to
+add a journal to an alreadyy-mounted filesystem.</P>
+
+<P>Fixed mke2fs's exit codes to consistently indicate when the mke2fs
+operation failed.</P>
+
+<P>Mke2fs now creates the lost+found directory with permissions of 0700,
+so that files that had previously lived in protected directory are
+safe if they get dropped in lost+found and the system administrator
+doesn't deal with immediately.  (Addresses Debian #bug 118443)</P>
+
+<P>Mke2fs and e2fsck (and all programs that use the
+ext2fs_check_if_mounted function) will now properly identify that a
+device is mounted, even in cases where devfs has confused things with
+multiple devices names with the same identity, or if a dim-witted
+system administrator has done something stupid like creating device
+file aliases in their home directory.  Also now checks for swap devices
+by using /proc/swaps.  (Addresses Debian bug #106622)</P>
+
+<P>Added a new option (-T) to tune2fs which sets the time a filesystem
+was last checked.</P>
+
+<P>Speed up e2image when creating sparse raw image files by optimizing
+away excess lseek() system calls.</P>
+
+<P>Fix support of large (> 2GB) files when used as a filesystem in
+mke2fs, tune2fs, debugfs, and findsuper.</P>
+
+<P>Debugfs's stat and icheck commands now properly deals with large (>
+2GB) files.</P>
+
+<P>Debugfs's set_super_value command now prints out the list of valid
+superblock fields which can be set using the command.</P>
+
+<P>Debugfs's rm and kill_file command now updates the superblock free block
+and inode counts, thus keeping the filesystem consistent.</P>
+
+<P>Debugfs's lsdel command now takes an optional argument which allows
+the user to only see the most recently deleted files.</P>
+
+<P>A new command (undel) was added to debugfs which automates
+undeleting a deleted inode and linking it back to a directory.</P>
+
+<P>Debugfs's ls command now takes a new option, -d, which lists 
+deleted directory entries.</P>
+
+<P>Debugfs's testb, freeb, setb, and find_free_block commands now take an
+optional count argument.</P>
+
+<P>Add support for a new ext2 file attribute, EXT2_NOTAIL_FL, which will
+be used to signal that a particular inode should not be eligible for
+tail-merging --- this is needed for programs like LILO.</P>
+
+<P>The findsuper (an unreleased, uninstalled utility program) has been
+improved to add extra validity checks and to add a progress meter.
+(It is still an unsupported program; the officially supported way to
+recover from a trashed partition table is to use gpart; findsuper is
+for wizards only.  :-)</P>
+
+<P>Debugfs was fixed to compile with "configure --disable-swapfs".</P>
+
+<P>Cleaned up various manual pages.   (Addresses Debian bug #119624, #120171)</P>
+
+<P>Added new translation file for Turkish.</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fix general gcc -Wall complaints.</P>
+
+<P>E2fsprogs (mostly) works with the dietlibc.</P>
+
+<P>The programming texinfo file has been expanded to include description
+of additional libext2fs functions.  (Still not compeltely done, but a
+lot of the more important functions have been documented.)</P>
+
+<P>Added a umask structure to struct_ext2_filsys, which currently only
+modifies the behaviour of ext2fs_mkdir(), but if we add any file
+creation functions to libext2fs, we should also make sure they respect
+the umask setting.</P>
+
+<P>The build-rpm script was fixed to be a bit more safe.</P>
+
+<P>The tests' Makefile now has a way of automating test case creation 
+for e2fsck, using "make testnew".</P>
+
+<P>Created a new function, ext2fs_dir_iterate2 which passes more
+information to the callback function (identical to the one used by
+ext2fs_dblist_dir_iterate).  The directory iterator functions take a
+new flag, DIRENT_FLAG_INCLUDE_REMOVED, which will return deleted
+directory entries.  If the directory entry is deleted, the callback
+function will be called with the entry paraemter set to
+DIRENT_DELETED_FILE.</P>
+  
+<P>Added new functions, ext2fs_inode_alloc_stats and
+ext2fs_block_alloc_stats, which takes updates block/inode allocation
+statistics in the bitmaps, block group descriptors, and superblock
+when inodes or blocks are allocated or deallocated.</P>
+
+
+<H2><A NAME="1.25">E2fsprogs 1.25 (September 20, 2001)</A></H2>
+
+<P>This is primarily a bug-fix release; no new features were added, but
+there are a number of embarassing bug fixes and cleanups applied.</P>
+
+<P>Fix a bug mke2fs which causes stack garbage to be written to disk when
+zapping disk sectors.  (This bug could cause mke2fs to core dump for
+some kernels, I suspect with security enhancement patches.)</P>
+
+<P>Remove unneeded #include of &lt;linux/config.h&gt; which was breaking
+building e2fsprogs on the Hurd.  (Addresses Debian bug #112414.)</P>
+
+<P>Updated tune2fs man page to reflect the fact that adding or removing a
+journal doesn't require running e2fsck.</P>
+
+<P>Remove use of AC_REQUIRE from autoconf which had been used to prevent
+AC_CANONICAL_HOST from being called twice; unfortunately this causes
+recent autoconf to bomb out since they don't allow AC_REQUIRE to be
+used outside of autoconf macros.  Fortunately, it doesn't seem to be
+necessary any more, anyway.</P>
+
+<P>E2fsck will now not fall back to an alternate superblock if the user
+specifies the superblock location explicitly on the command-line.
+This allows easier recovery from a situation where the primary
+superblock and block groups are slightly corrupted, but the backup
+superblocks are completely broken.  </P>
+
+<P>Fix problem which caused compile_et and mk_cmds to blow up if
+e2fsprogs was in a directory with a pathname that contained spaces.</P>
+
+<P>We are now more paranoid about checking the entry in /etc/mtab to make
+sure the filesystem is really mounted, since some broken distributions
+(read: Slackware) don't initialize /etc/mtab before checking non-root
+filesystems.  (Slackware also doesn't check the root filesystem
+separately, and reboot if the root filesystem had changes applied to
+it, which is dangerous and broken, but there's nothing I can do about
+that.)</P>
+
+<P>Make UUID library C++ friendly by adding appropriate extern "C"
+declarations and using const in the function declarations.</P>
+
+<P>Fix up the com_err texinfo file so that it can product a valid info
+file (previously, it could only be used to generate paper
+documentation using texinfo.tex).</P>
+
+
+<H2><A NAME="1.24a">E2fsprogs 1.24a (September 2, 2001)</A></H2>
+
+<P>Fix brown-paper bug in mke2fs which caused it to segfault when
+printing the version string.</P>
+
+
+<H2><A NAME="1.24">E2fsprogs 1.24 (August 30, 2001)</A></H2>
+
+<P>Revert the BLKGETSIZE64 support, since for some distributions, this
+ioctl has been used by an unofficial kernel patch to update the last
+sector on the disk, and this was causing disk corruption problems as a
+result.
+</P>
+
+<P>Mke2fs is now more careful about zapping swap space signatures and
+other filesystem/raid superblock magic values so that programs like
+mount who try to use hueristics to determine the filesystem type of a
+partition are less likely to be confused.
+</P>
+
+<P>E2fsck will no longer complain if the the mode of EXT2_RESIZE_INO is a
+regular file (since Andreas Dilger's on-line resizing tools will set
+its mode bits).
+</P>
+
+<P>Fixed some minor texinfo, man pages nits for spelling errors,
+texinfo warnings, etc.  (Addresses Debian bug #110621.)
+</P>
+
+<P>E2fsprogs program no longer print the filesystem version number
+(i.e. 0.5b), since it only confuses people and doesn't serve any real
+purpose.
+</P>
+
+<P>E2fsck will once again compile under libc5, since it will supply its
+own version of strnlen if necesssary.
+</P>
+
+<P>Mke2fs and tune2fs will allow the use of UUID= or LABEL= specifiers
+when specifying the external journal device.  tune2fs will also search
+devices looking for the externla journal debice when removing.  
+</P>
+
+<H2><A NAME="1.23">E2fsprogs 1.23 (August 15, 2001)</A></H2>
+
+<P>Add initial support for extended attributes (EA); e2fsck will
+correctly handle a filesystem with EA's and check the EA blocks for
+corruptions.
+</P>
+
+<P>E2fsck's symlink sanity checking has been cleaned up.  It now checks
+the i_size value of fast symlinks, and checks for immutable flags
+being set of symlinks, etc.
+</P>
+
+<P>E2fsck now offers to clear inodes which are special files that have a
+non-zero i_blocks or i_size field.  (The i_size field check was in the
+previous version of the code, but due to a bug it didn't offer to
+clear the inode unless i_size and i_size_high were both non-zero.)
+</P>
+
+<P>E2image can now create "raw" image files, which only contain the
+filesystem metadata placed in a spare file so that e2fsck, dumpe2fs,
+debugfs, etc., can be run directly on the raw image file.
+</P>
+
+<P>Add support for the 64-bit block device patches.
+</P>
+
+<P>Fixed bugs in creating external journals with a 1k blocksize.
+</P>
+
+<P>Add initial support for external journals (so long as the external
+journal only supports a single filesystem) in e2fsck.
+</P>
+
+<P>Remove requirement for needing to run fsck on a filesystem after
+removing a journal (either internal or external).
+</P>
+
+<P>The man pages now document how to create and manage external journals.
+</P>
+
+<P>Speed up the check of an ext3 filesystems by avoiding a needless flush
+of all of the superblock and block group descriptors.
+</P>
+
+<P>Speed up creating an internal journal using tune2fs in the case where
+the filesystem has a lot blocks already allocated.
+</P>
+
+<P>Tune2fs has been fixed to make sure that only error messages go to
+stderr, and normal message go to stdout. (Addresses Debian bug #108555)
+</P>
+
+<P>Fixed a minor bug in mke2fs; if -O none is passed to mke2fs, it will
+now not set the sparse_super feature.  (Addresses Debian bug #108165)
+</P>
+
+<P>Add support in fsck for the filesystem type "auto".
+</P>
+
+<P>Fsck -A will not try to interpret device names for filesystems which
+have a pass number is 0.  (Addresses Debian bug #106696).
+</P>
+
+<P>Fsck prints a warning message if now valid filesystems are passed to
+it.  (Addresses Debian Bug #107458.)
+</P>
+
+<P>E2fsck now gives an explicit warning if there filesystem still has
+errors at the end of the run. (Addresses Debian bug #104502)
+</P>
+
+<P>E2fsck will set the EXT2_ERROR_FS flag if the journal superblock
+reflects an error.  E2fsck will also not run the orphan list if the
+filesystem contains errors, since the orphan list might be corrupted.
+</P>
+
+<P>E2fsck now prints the number of large files when given the -v option.
+</P>
+
+<P>Fixed minor memory leaks in e2fsck.
+</P>
+
+<P>Some minor man pages updates. (Addresses Debian bug #30833, #108174)
+</P>
+
+<H2><A NAME="1.22">E2fsprogs 1.22 (June 22, 2001)</A></H2>
+
+<P>Fixed a bug in e2fsck's handling of orphan inodes which are special
+files (i.e., block/character device files, named FIFO's, etc.).
+</P>
+
+<P>Fixed a bug accidentally introduced in e2fsprogs 1.21 which caused
+tune2fs to fail at adding a journal to a mounted filesystem.
+</P>
+
+<P>Fixed a few big-endian bugs in e2fsprogs:
+</P>
+<UL>
+<LI> The directory block functions were accidentally reporting
+		some directories as corrupted when they weren't.
+<LI> If e2fsprogs is compiled --disable-swapfs, the C language 
+		  equivalents weren't being included for big-endian platforms.
+		  (Fixes Debian bug #101686).
+</UL>
+
+<P>Fixed a Hurd compilation problem.  (Addresses Debian bug #101361)
+</P>
+
+<H3>Programmer's notes:</H3>
+
+
+<P>Use platform independent method of defining the BLKFLSBUF and FDFLUSH
+ioctls, and allow them to be defined for non-i386 platforms.
+</P>
+
+<P>The uuid.h header file is now protected against multiple inclusions.
+</P>
+
+<P>E2fsprogs is now being developed using BitKeeper.  Changed the test
+scripts to deal with BK's stripping CR characgters from text files,
+and changed the top-level Makefile.in to avoid including BitKeeper
+files when generating the source tarball.
+</P>
+
+<H2><A NAME="1.21">E2fsprogs 1.21 (June 15, 2001)</A></H2>
+
+<P>Added new configure flags which allow a subset e2fsprogs to be built;
+this is most useful for boot floopies, since the resulting shared
+libraries and programs are slimmed down by removing features that
+aren't necessary for a boot floppy.  The new flags that were added
+are: --disable-swapfs, which removes support for byte swapping old
+legacy PPC/68k filesystems, --disable-debugfs, which removes support
+for debugfs from the libext2fs library, --disable-imager, which
+removes support for the e2image program, and --disable-resizer, which
+removes support for resize2fs.</P>
+
+<P>E2fsck now prints the number of mounts or days elapsed since the last
+check when e2fsck is forced to check an otherwise clean filesystem.</P>
+
+<P>Tune2fs now prints an informative message about how often a filesystem
+will be checked when adding a journal to the filesystem, to remind the
+user that he/she may want to adjust those parameters using tune2fs
+-c/-i.</P>
+
+<P>Worked around hurd brain-damage which causes e2fsck to sometimes
+believe a filesystem is the root filesystem based on device numbers
+(since Hurd doesn't have dev_t's, which is arguably a POSIX.1
+violation).</P>
+
+<P>Fixed a bug introduced in 1.20 which caused e2fsck to abort with an
+erroneous error with the -F option was specified.</P>
+
+<P>Fixed a ext3 recovery bug in the revoke handling; synchronized with
+ext3 0.7a.</P>
+
+<P>Fixed two bugs in e2fsck's handling of dup block handling, dealing
+with relatively uncommon edge cases: a directory with an indirect
+block which is claimed by another file, and when the last inode in the
+filesystem has blocks claimed by another file.</P>
+
+<P>E2fsck now checks to see if the i_size field of a fast symlink is too
+big, and offers to clear the symlink if so.</P>
+
+<P>E2fsck now checks to see if i_size_high of special files is non-zero,
+and offers to clear i_size_high.</P>
+
+<P>Fix e2fsck's handling of incompatible journal flags so that the user
+has chance to abort, and then has the option to clear out the journal
+entirely.  (Addresses Debian bug #98527.)</P>
+
+<P>Fixed a bug in fsck which could cause it to core dump if a mix of
+standard and non-standard device names are used in /etc/fstab.
+(Debian bug #100559)</P>
+
+<P>Fixed a bug in debugfs which caused read errors when copying a file to
+not be noticed.</P>
+
+<P>The debugfs set_super_value command can now modify the s_lastcheck field.</P>
+
+<P>Fixed a bug in lsattr and chattr which was accidentally introduced in
+1.20 to support > 2GB files; both lsattr and chattr wasn't reading
+directories correctly because the change modified the layout of struct
+dirent to be incompatible with the libe2p shared library.</P>
+
+<P>Cleaned up the mke2fs manual page and included a discussion about why
+it's good to periodically check the filesystem even when journaling is
+enabled.</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Fix general gcc -Wall complaints.</P>
+
+<P>The types needed by the ext2 header files are now provided by
+lib/ext2fs/ext2_types.h, instead of include/asm/types.h.</P>
+
+<P>Integers are now preferred to longs when trying to find a 32-bit type
+in ext2_types.h.  Also, if linux/types.h has already been defined,
+don't try to redefine the types.</P>
+
+<P>Fixed make depend script so that it automatically corrects the
+pathname cleanups performed by make -M, so I don't have to fix them up
+by hand.</P>
+
+<P>Fixed the d_loaddump test case to be more robust, and not depend on
+bash'isms.</P>
+
+<P>Removed debugfs's dependence on pread(), which was accidentally
+intrudced in e2fsprogs 1.20</P>
+
+<P>Fixed a performance bug in the libext2fs's icount routine; the size
+estimate of the icount array was incorrectly being calculated.</P>
+
+<P>Removed use of the badblocks compatibility functions in the e2fsprogs
+programs.</P>
+
+<P>Added paranoia code which protects against strange cases where /etc
+isn't on the root filesystem, or if /etc/mtab doesn't exist.</P>
+
+<P>The header file ext2_types.h is now installed.</P>
+
+<P>Autoconf is used to determine when we are on big-endian machines,
+instead of doing run-time tests, to save a few bytes of code.</P>
+
+<P>The ext2fs_mark_generic_bitmap and ext2fs_unmark_generic_bitmap
+functions are no longer inline functions, which saves space and
+doesn't really cost any real performance.</P>
+
+<P>The ext2fs library no longer depends on the e2p library.  (What need
+there was of it --- namely, fsetflags, was coded in-line).</P>
+
+<P>Fixed the makefile so that lib/ext2fs/ext2_types.h is generated even
+when the user is stupid and tries compiling the package using "make
+install" as root.</P>
+
+<P>Miscellaneous code cleanups:
+<UL>
+<LI> Added missing files from Makefile.in's SRCS file, so that 
+		their dependencies would be properly calculated.
+<LI> Removed redundant code
+<LI> Fixed comments in code
+<LI> Removed no-longer unneeded argsused #pragma.
+</UL></p>
+
+
+<H2><A NAME="1.20">E2fsprogs 1.20 (May 20, 2001)</A></H2>
+
+<P>Add support for replaying the ext3 journal purely in user mode,
+including handling the orphaned inode list.  Used code contributed by
+Andreas Dilger, with bug fixes and the orphaned inode handling done
+by Theodore Ts'o.</P>
+
+<P>The mke2fs and tune2fs programs can create or modify a filesystem to
+include an ext3 journal.  Tune2fs also can be used to remove an ext3
+journal from a filesystem.</P>
+
+<P>E2fsck will now check for the existence of a linked list of orphan
+inodes in the superblock, and clear those inodes before starting the
+rest of the filesystem check (but after the journal playback).</P>
+
+<P>E2fsck now validates the file descriptor passed to the -C option,
+which saves against the completion bar getting written to an
+unexpected location, such as the disk being checked.  (Debian
+bug/wishlist #55220)</P>
+
+<P>E2fsck will now bump the filesystem revision number from zero to one
+if any of the compatibility bits are set.</P>
+
+<P>Fixed a bug where a badly corrupted directory on a big endian system
+could cause e2fsck to die with a bus error.  The
+ext2fs_read_dir_block() and ext2fs_process_dir_block() functions in
+the ext2 library now does alignment sanity checks on the rec_len field
+of the directory entry before using it.</P>
+
+<P>The ext2 library has been enhanced to make tune2fs safe to run on
+mounted filesystems.  (Users could usually get away with using tune2fs
+on mounted filesystems before, but with the advent of ext3 and
+journaling, it became important to make tune2fs was *really* safe for
+use even when the filesystem being modified is mounted.)  E2label is
+now implemented by tune2fs using an argv[0] dispatch, so that e2label
+is also now safe for use on mounted filesystems.</P>
+
+<P>Added a new program, e2image, which creates a backup of critical ext2
+filesystem data structures.  The generated image file can be examined
+using dumpe2fs and debugfs.  In the future, e2fsck will be able to use
+the image file to help recover very badly damaged filesystems.</P>
+
+<P>Fixed a number of LFS bugs in e2fsck; very, very large (> 2**42) files
+no longer cause e2fsck to bomb out.  Also treat files > 2GB as being
+large file when deciding whether or not the filesystem has large files.</P>
+
+<P>Fixed lsattr and chattr so that they work correctly on large files.
+(Fixes Debian bug #72690.)</P>
+
+<P>Removed limitation in get_device_size() which imposed a one terrabyte
+filesystem limitation.  (Most 2.2 kernels still have a signed int
+problem which cause 1 TB block device limitation.  Fortunately, the
+kernel patches to fix this are much easier than fixing the 2TB
+limitation in the kernel.  :-)</P>
+
+<P>A max_mount_count of zero is now treated as if no mount count were
+set.  (Previously, no mount count was indicated by using -1, and a
+mount count of zero caused e2fsck to always be run.)</P>
+
+<P>Mke2fs supports two new filesystem types largefile and largefile4.</P>
+
+<P>Mke2fs now adds some randomness in s_max_mount_count so that multiple
+filesystems won't be all checked at the same time under normal
+operations.</P>
+
+<P>Fixed bug in the progress bar printing code which could cause e2fsck
+to core dump on an illegal filesystem.</P>
+
+<P>Fixed bug in fsck which could allow more than one instance of e2fsck
+to be printing a progress bar.  (Debian bug #65267)</P>
+
+<P>Fsck using a UUID or a LABEL specifier will work even if devfs is
+compiled into the kernel and not mounted.  If the pathnames in
+/proc/partitions are incorrect, fsck will search /dev for the correct
+device (using the new ext2fs_find_block_device library function).
+Fsck now also checks the RAID devices first so that they are properly
+found when they are in use.  Support has also been added to support
+additional IDE disks and the DAC 960 device names.  (Debian bug #94159)</P>
+
+<P>Fixed a bug in fsck which caused it not deal properly with 16
+byte long filesystem labels.</P>
+
+<P>Fsck's -t option has been made a lot more flexible.  The semantics for
+what happens if a comma-separated list to fsck has been regularized,
+and it is now possible to filter what filesystems will get checked
+based what is in the filesystem's fstab entry's option field.  (Debian
+bug #89483.)</P>
+
+<P>The dumpe2fs program can now print out the group description
+information in hex, and also prints the location of the superblock and
+block group descriptor for those block groups that have them.</P>
+
+<P>Mke2fs now clears the ext2 superblock before it starts creating a
+filesystem, so that the superblock magic number is only written if the
+filesystem creation process successfully completes.</P>
+
+<P>The debugfs program's stat command now pretty-prints the blocks used
+by an inode so that it's more compact and informative.</P>
+
+<P>The debugfs stats command now uses the same libe2p code (which is used
+by dumpe2fs) to print the superblock header information.  This is more
+complete, and it avoids a bit of code duplication.</P>
+
+<P>Added a new debugfs command, set_super_value (ssv) which allows the
+user to set arbitrary superblock fields.</P>
+
+<P>Debugfs was extended to support inode numbers in hex (by prefixing
+them with 0x), and so that modify_inode can set the inode generation
+number.  Also, there is now a new function command called logdump
+which will dump an ext3 journal.</P>
+
+<P>Fixed a bug in debugfs so that quitting out of the pager doesn't kill
+debugfs.</P>
+
+<P>Debugfs's dump command now stops immediately upon reporting a disk
+read error.  (Fixed a bug in ext2fs_file_read library routine which
+caused debugfs not to stop.)  (Debian bug #79163)</P>
+
+<P>On systems with /proc/mounts (mainly Linux systems), /proc/mounts is
+checked before /etc/mtab is used, since /proc/mounts is more likely to
+be accurate.</P>
+
+<P>Added portability fixes for Solaris and Linux/ia64.</P>
+
+<P>Various manual pages were clarified and cleaned up.  (Fixed debian
+bugs #63442, #67446, and #87216)</P>
+
+
+<H3>Programmer's notes:</H3>
+
+<P>The e2fsck message printer now supports %Iu and %Ig, which will print
+out the inode's user and group owners, respectively.</P>
+
+<P>E2fsprogs now includes its own version of include/linux/ext2_fs.h, so
+that no longer dependent on the system having the correct version of
+the kernel header files.</P>
+
+<P>Added a new function to libext2, ext2fs_find_block_device(), which
+searches the system (i.e., /dev, /devfs, /devices) for a pathname to a
+device given its device number.</P>
+
+<P>Added a new function to libext2, ext2fs_sync_device, which centralizes
+all of the places which might try to use the BLKFLSBUF or FDFLUSH
+ioctls (and usually failing to define them since the system header
+files don't usually do this for us, and we're trying to avoid usage of
+kernel include files now).</P>
+
+<P>Added new utility programs in tests/progs: random_exercise and
+hold_inode.  They aren't built by default; they're useful for
+exercising ext3 filesystem code.</P>
+
+<P>Added a new ext2 filesystem flag, EXT2_FLAG_SUPER_ONLY, which causes
+the filesystem close functions to only update the superblock, and to
+not touch the block group descriptors.  Needed by tune2fs when
+modifying a mounted filesystem.</P>
+
+<P>Got rid of struct ext2fs_sb and replaced it with the standard struct
+ext2_super_block from include/linux/ext2_fs.h.  Note: this may break
+source (but not binary) compatibility of some users of the ext2
+library.  Those applications should just simply do a global search and
+replace of struct ext2fs_sb with struct ext2_super_block, and include
+the new header file <ext2fs/ext2_fs.h> which defines it.</P>
+
+<P>The ino_t type has been renamed ext2_ino_t to protect applications
+that attempt to compile -D_FILE_OFFSET_BITS=64, since this
+inexplicably changes ino_t(!?).  So we use ext2_ino_t to avoid an
+unexpected ABI change.</P>
+
+<P>The Makefiles have been reworked so that "make check" can be run from
+the top-level Makefile.</P>
+
+<P>Fix general gcc -Wall complaints and removed dead code.</P>
+
+<P>Remove use of NOARGS, because we assume everyone does ANSI C these
+days.</P>
+
+<P>Added build-rpm script from sct.</P>
+
+<P>New functions ext2fs_image_{inode,super,bitmap}_{read,write} added 
+to support e2image.</P>
+
+<P>New function ext2fs_flush_icache which must be called if the
+application program modifies the inode table blocks without going
+through ext2fs_write_inode() interface.</P>
+
+<P>New ext2fs_check_mount_point() function, which will return the mount
+point of a device if mounted.</P>
+
+<P>The io_channel abstraction now has an optional interface,
+io_channel_write_range, which allows specific byte ranges to be
+written.  </P>
+
+<P>The unix_io IO channel now supports write-through caching, so that
+journal creation is more efficient.</P>
+
+<P>Added x86 assembly language routines to support byte swapping, to
+reduce executable size.</P>
+
+<P>Fixed bug in the utility program subst so that it's possible to
+replace a substitution variable with a zero-length string.</P>
+
+<P>Fixed numbering e2fsck pass1 problem numbers; an extra zero had
+slipped into some of the problem number.</P>
+<H2><A NAME="1.19">E2fsprogs 1.19 (July 13, 2000)</A></H2>
+
+<P>Release the resize2fs program since the timeout before it could
+be published it under the GPL has finally expired.</P>
+
+<P>Add experimental support needed for the ext2 compression patches.
+This requires compiling e2fsprogs with the --enable-compression flag
+to the configure script.</P>
+
+<P>Added ext3 journalling support.  E2fsck will run the journal (if
+necessary) by temporarily mounting the filesystem.  /sbin/fsck.ext3 is
+installed as a symlink to e2fsck.  Fsck has been taught about ext3,
+and treats it the same as ext2 in terms of the progress bar logic.
+Dumpe2fs will display the superblock journaling information if the
+filesystem has a journal.  The ext2 library will now permit opening an
+ext3 filesystem with the recovery flag set.  This is necessary for
+on-line dump's to work correctly, but there may be issues with this
+working well since ext3 is much less agressive about syncing blocks to
+the filesystem, since they're safe on the journal.</P>
+
+<P>Tune2fs and e2fsck have been changed to allow the mount_count check to
+be disabled by setting max_mount_count to -1.  (This was already
+supported by the kernel.)</P>
+
+<P>Create a symbolic link for fsck.ext3, since the e2fsprogs utilities
+are used for ext3 as well.</P>
+
+<P>Added internationalization support for e2fsprogs; must be enabled
+by passing --enable-nls to configure.</P>
+
+<P>Always use the provided ext2fs header files to insulate ourselves from
+kernel version changes.  Which include files are used by e2fsprogs
+have also been cleaned up to improve portability.</P>
+
+<P>Limit the number of times that e2fsck updates the progress bar so that
+people who are booting using a 9600 baud console don't get swampped by
+too many updates.</P>
+
+<P>Improved the loop detection algorithm in e2sck's pass #3 so that it is
+much, much faster for large filesystems with a large number of
+directories.</P>
+
+<P>The memory footprint for e2fsck is now slightly smaller than before.</P>
+
+<P>E2fsck now checks if special devices have a non-zero size, and offers
+to clear the size field if it finds such an inode.  </P>
+
+<P>E2fsck now checks if special devices have the append-only flag set,
+and offers to clear the inode.</P>
+
+<P>E2fsck now properly handles some "should never fail" cases during a
+bitmap copy in pass5.</P>
+
+<P>E2fsck now properly prints control characters in filenames as ^A .. ^Z.</P>
+
+<P>Added non-destructive write testing to the badblocks program,
+courtesy of David Beattie.  The badblocks also now has an option to
+input the current set of bad blocks, so that known bad blocks are
+skipped to speed up the badblocks test.  There is also a persistent
+rescan feature which causes badblocks to run until it has completed
+some number of passes without discovering any new bad blocks.</P>
+
+<P>Badblocks now checks to see if the device is mounted and refuses to
+do the tests involving writing to the device if it is mounted.  Also,
+badblocks now allows the number of blocks to be checked to be
+defaulted to the size of the partition.</P>
+
+<P>Fixed a bug in fsck which didn't allow non-root users to be able to
+check filesystems if there were any LABEL= or UUID= entries in
+/etc/fstab.</P>
+
+<P>The Hurd doesn't support the filetype filesystem feature.  The mke2fs
+program now makes sure that for the Hurd, the filestype feature is
+turned off.  E2fsck will check to see if the filetype feature is
+turned on for Hurd filesystems, and offer to turn off the feature.</P>
+
+<P>Mke2fs now has a safety check to make sure the number of blocks do not
+exceed 32 bits even on a 64 bit platform.</P>
+
+<P>Really fixed a bug in fsck to allow "fsck -As" to run interactive
+fsck's.  (For those people who like to do interactive fsck's in the
+/etc/rc scripts!?!)</P>
+
+<P>Debugfs has a few new features: the rdump command, which will do a
+recursive dump of a directory and all of its contents, and the lcd
+command which does a local chdir (much like the ftp command of the
+same name).  In addition, the debugfs program and the open_filesystem
+command now takes three new options: -b and -s, which allows the
+blocksize and superblock location to be specified, and the -c option
+which is used in catastrophic situations where the block group
+descriptors are corrupt.  If the -c option is specified, debugfs will
+skip trying to read in the block and inode bitmaps.</P>
+
+<P>Debufs's lsdel command was fixed to handle bad blocks in the inode
+table.</P>
+
+<P>A Y2K bug in debugfs's "ls -l" handling was fixed by switching to use
+4 digit years.</P>
+
+<P>General improvements in error messages</P>
+
+<UL>
+<LI> Mke2fs prints a sane error message if the partition size is zero
+	(usually because the partition table wasn't reread by the
+	kernel due to the partition being busy), instead of "invalid
+	argument passed to ext2 library while initializing superblock".
+
+<LI> Fsck now prints more self-explanatory message if an invalid UUID=
+	or LABEL= specification is passed to it.
+</UL>
+
+<P>UUID library changed to use the LGPL.</P>
+
+<P>Fixed a bug in the UUID library where very rapid calls to the
+time-based UUID generator could cause duplicate UUID's to be returned.
+This was not a problem for e2fsprogs, but it could be a problem for
+other users of the library.</P>
+
+<P>Make the UUID library more robust in the face of missing or an
+improper /dev/urandom or /dev/random files.</P>
+
+<P>Added some random portability fixes for Solaris.</P>
+
+<P>Some minor man page updates.</P>
+
+<P>Fixed a memory leak in the ss library.</P>
+
+
+<H3>Programmer's notes</H3>
+
+
+<P>We now try to use lseek64 and open64 from the LFS if possible.</P>
+
+<P>The 3rd parameter in e2p's print_flags is now a flags word, instead of
+a boolean option.</P>
+
+<P>The mark and unmark bitmap functions now return the previous state of
+the bit that was being changed, which is useful for some speed
+optimizations.</P>
+
+<P>The following functions have been added to enhance the badblocks list
+handling in libext2fs: ext2fs_write_bb_FILE, ext2fs_read_bb_FILE2, and
+ext2fs_badblocks_equal.</P>
+
+<P>The ext2 header files now have the latest journalling fields to the
+superblock.</P>
+
+<P>The ext2fs_mkdir function in libext2fs now properly backs out of error
+conditions robustly.</P>
+
+<P>Cleaned up makefiles:</P>
+<UL>
+<LI> to cleanly  compile with the -j flag.
+<LI> so distclean removes all generated files.
+<LI> so in case of an error while installing header files, the make aborts.
+</UL>
+
+<P>Fix test_script so that it works correctly when compiling in the
+source directory.</P>
+
+<P>Update libraries to build under a.out shared libraries (again).</P>
+
+<P>Clean up the build process so it's more friendly in case of missing
+directories.</P>
+
+<P>The ext2fs header file can now be #include'd into C++ programs.</P>
+
+<P>The e2p.h header file is now installed.</P>
+
+<P>Added workaround to a gawk 3.0.5 bug in lib/ss/mk_cmds.</P>
+
+
+<H2><A NAME="1.18">E2fsprogs 1.18 (November 10, 1999)</A></H2>
+
+<P>Fix a core dumping bug in e2fsck if an imagic inode is present or
+(more rarely) if the filesystem is badly corrupted enough that e2fsck
+has to restart pass 1 processing.  E2fsck now closes the filesystem
+before freeing a large number of its data structures, so in the case
+of future memory faults, at least the fixed filesystem will be fully
+written out.</P>
+
+<P>If a filesystem doesn't support imagic inodes, and e2fsck discovers an
+imagic inode, it will offer to clear the imagic flag.</P>
+
+<P>E2fsck will now offer to clear the immutable flag on special files
+(device/socket/fifos) when running it in non-preen mode.</P>
+
+<P>E2fsck will now set the filetype when creating /lost+found, and when
+connected orphaned inodes to /lost+found.</P>
+
+<P>Debugfs's ncheck and icheck commands now handles the case where there
+are bad blocks in the inode table without bombing out.</P>
+
+<P>The badblocks list processing code has been made more efficiently for
+appending a large number of (ordered) badblocks to the badblocks list.</P>
+
+<P>Some minor man page updates.</P>
+
+<P>Fsck now allows interactive e2fsck's when using fsck -As (not a common
+mode, but some people like to do this in boot scripts for silly reasons).</P>
+
+<H3>Programmer's notes</H3>
+
+<P>The internal e2fsck problem code for PR_2_SPLIT_DOT was fixed to meet
+with the problem code convention.</P>
+
+<P>The badblocks list regression test program has been updated to work
+with previously made API name changes.</P>
+
+<P>The ext2fs_free() command now uses the new badblocks API to avoid
+using the compatibility layer.</P>
+
+<P>Added new regression test cases; the run_e2fsck test script now
+supports the ability for a test case to run a prepratory command
+before running e2fsck.</P>
+
+<H2><A NAME="1.17">E2fsprogs 1.17 (October 26, 1999)</A></H2>
+
+<P>Fixed nasty typo in fsck which caused parallelized fsck's to go into an
+infinite loop.</P>
+
+<P>Fixed a bug in fsck where it used strncmp to compare a binary UUID,
+thus potentially causing problems if a binary UUID contained a NULL
+character.</P>
+
+<P>E2fsck now uses stricter checks for directory entries in pass 2:
+zero-length filenames are not allowed; neither are 8 byte long
+directory entries.</P>
+
+<P>The debugfs "dirty" command now clears the filesystem valid bit.
+(Previously this just set the dirty-as-in-needs-writing-out-to-disk
+bit in the in-core superblock image.  The new functionality is more
+what the user expects, and is more useful.)</P>
+
+<P>Added a debugging hook to test parallel fsck; if the environment
+variable FSCK_FORCE_ALL_PARALLEL, then filesystems on the same drive
+will be checked in parallel when they normally would not be.</P>
+
+<H3>Programmer's notes</H3>
+
+<P>Fixed some #ifdef's for compilation under the Hurd OS.</P>
+
+<P>Fixed minor W2K compatibility problems.</P>
+
+<P>Fixed some miscellaneous GCC warnings.</P>
+
+<H2><A NAME="1.16">E2fsprogs 1.16 (October 22, 1999)</A></H2>
+
+<P>Fixed a race condition bug in fsck; when printing a progress bar, if
+checking multiple filesystems in parallel, it was possible for fsck to
+send e2fsck a SIGUSR1 signal before e2fsck had installed its signal
+handler, which would cause it to terminate with a signal 10.</P>
+
+<P>E2fsck now properly handles filesystems that have the
+INCOMPAT_FILETYPE feature turned on.  It can be used to convert a
+filesystem into using or not using FILETYPE feature.</P>
+
+<P>E2fsck now properly handles filesystems that have the IMAGIC feature
+turned on (this is used on Linux AFS servers).</P>
+
+<P>The mke2fs program now creates filesystems that have the filetype and
+sparse_superblock features enabled by default, unless it is run on a
+pre-2.2 kernel.  These features are not supported by a pre-2.2 kernel,
+so there is now a new flag -O which allows the user to specify with
+which features she would like to create the filesystem; "mke2fs -O
+none" will create a filesystsem compatible with 2.0 kernels.</P>
+
+<P>The tune2fs program now has a -O option which allows the user to set
+and reset "safe" filesystem features.  Currently, the only ones which
+allows to be modified are the filetype and sparse_superblock features.
+Note setting or clearing either feature will require running e2fsck on
+the filesystem afterwards.  (n.b. Clearing the sparse_superblock feature
+requires that there is enough free space on the filesystem for the
+extra superblocks which will be created by e2fsck.)</P>
+
+<P>Debugfs can now set and print filesystem features in the superblock
+using the "features" command.  Dumpe2fs will print out the complete
+set of features when listing the superblock.</P>
+
+<P>Dumpe2fs has new options -f (force) and -h (header-only).</P>
+
+<P>Fixed a bug in e2fsck which could cause the PROGRAMMING ERROR/bonehead
+message to come up.  This could happen when decrementing or
+incrementing a link count could result in an overflow.</P>
+
+<P>Fixed a bug in e2fsck where the block count on the lost+found
+directory would not be properly incremented when the directory was
+expanded to the point where an indirect block needed to be allocated.</P>
+
+<P>E2fsck now makes some additional sanity checks on the superblock to
+avoid crashing or giving a memory allocation error if some of the
+values in the superblock are unresonable (but the superblock otherwise
+looks valid).</P>
+
+<P>Fixed a bug in e2fsck where a very badly corrupted filesystem might
+require two passes to completely fix the filesystem.  This happened if
+an inode claimed blocks that was part of the filesystem metadata
+(typically, when garbage was written into an inode table or indirect
+block, since this kind of filesystem corruption normally doesn't
+happen otherwise).</P>
+
+<P>On the Alpha, glibc declares st_flags although it isn't actually used;
+the configure script was improved to detect this case so that
+e2fsprogs can avoid using the non-functional stat field.</P>
+
+<P>The manual pages were updated to use a more consistent formatting
+style consistent with standard Unix man pages.  Mke2fs's man page
+added documentation for a few previously undocumented options.</P>
+
+<P>Fixed minor display bugs in tune2fs and mke2fs.</P>
+
+<H3>Programmer's notes</H3>
+
+<P>Improved portability of e2fsprogs to non-Unix systems (in particular, NT).</P>
+
+<P>Added features to parse and print feature strings into the e2p library.  
+(e2p_feature2string, e2p_string2feature, e2p_edit_feature).</P>
+
+<P>ext2fs_mkdir() and ext2fs_new_dir_block() now creates directories
+whose directory entries contain proper filetype information if the
+filesystem supports it.</P>
+
+<P>ext2fs_link() now uses the low 3 bits of its flags parameter to pass
+the directory entry filetype information.  This is used to set the
+directory entry filetype information if the filesystem supports it.</P>
+
+<P>Fixed a bug in ext2fs_expand_dir() where the block count in a
+directory's inode would not be properly incremented when the directory
+was expanded to the point where an indirect block needed to be
+allocated.</P>
+
+<H2><A NAME="1.15">E2fsprogs 1.15 (July 18, 1999)</A></H2>
+
+<P>Add configuration checks so that e2fsprogs will compile cleanly on
+Linux 2.3 kernels that have renamed i_version to i_generation.</P>
+
+<P>E2fsck now prints a progress/completion bar (and not just a simple
+spinner) if the -C0 option is requested or if it receives a SIGUSR1
+signal.  Fsck will automatically manage the (potentially muliple)
+e2fsck processes to print completion bars if it is given a -C option,
+with the right thing happening if multiple filesystems are being
+checked in parallel.</P>
+
+<P>Mke2fs now has better automatic hueristics to determine the filesystem
+parameters to be used for a particular filesystem.  Added a new option
+-T which allows the user to specify how the filesystem is to be used,
+which helps mke2fs do a better job selecting the filesystem parameters.</P>
+
+<P>Mke2fs now creates revision 1 filesystems by default, and with the
+sparse superblock feature enabled.  The sparse superblock feature is
+not understood by Linux 2.0 kernels, so they will report errors when
+mounting the filesystem.  This can be worked around by using the mount
+options "check=none".</P>
+
+<P>Fix bug where if /dev/null couldn't be opened (should never happen),
+e2fsck would hang in a tight loop.</P>
+
+<P>Make e2fsck handle the case where /lost+found isn't a directory.</P>
+
+<P>E2fsck now uses mallinfo if it exists to get accurate statistics about
+its memory usage.</P>
+
+<P>Fix bug in e2fsck where it wouldn't check to see if a disconnected
+inode had any problems before connecting it to /lost+found.</P>
+
+<P>Add check to e2fsck so it makes sure that total number of inodes in
+the filesystem is a sane number.</P>
+
+<P>Fix fencepost error when clearing an the end of the block bitmap which
+caused the last block in the bitmap not to get cleared.</P>
+
+<P>Cleaned up a number of messages in e2fsck:</P>
+<UL>
+<LI> The message "Group's #'s copy of the group descriptor..."
+		was fixed so that the correct number would be displayed.
+<LI>  Added missing space in the "disk write-protected" error messsage
+<LI>  Cleaned up the error message printed when a non-interactive
+		e2fsck needs to abort a check because the filesystem
+		appears to be mounted.
+</UL>
+
+<P>Added a new command-line utility, uuidgen, which will create and print
+a UUID.</P>
+
+<P>Make debugfs's icheck command more robust by checking to make sure an
+inode has valid blocks before interarting over the inode's blocks.</P>
+
+<P>UUID generation now uses a random-based scheme whenever possible to
+prevent potential privacy problems.</P>
+
+<P>Man pages for all of the UUID functions in the lirbary were added.</P>
+
+<P>Fixed bug in fsck so it won't coredump if a filesystem not in
+/etc/fstab is given to it.</P>
+
+<P>Fsck now understands the UUID=xxxx and LABEL=yyyy forms in /etc/fstab
+that most of the other mount utilities understands.</P>
+
+<P>Mke2fs will make a filesystem even if it appears mounted if the force
+option is given.</P>
+
+<P>Dumpe2fs has new command-line options which allow a filesystem expert
+to specify the superblock and blocksize when opening a filesystem.
+This is mainly useful when examining the remains of a toasted
+filesystem.</P>
+
+<P>The badblocks program has been updated to display correctly on disks
+with large block numbers.</P>
+
+<P>The badblocks program no longer gives spurious errors when errors
+occur on non-block boundaries, which is common if the blocksize is
+larger than 1k.</P>
+
+<P>Mke2fs will sync the disk device every MKE2FS_SYNC block groups if the
+MKE2FS_SYNC environment variable is set.  This is to work around a VM
+bug in the 2.0 kernel.  I've heard a report that a RAID user was able
+to trigger it even using a 2.2 kernel, but hopefully it will not be
+needed for most Linux 2.2 users.</P>
+
+<P>Fixed miscellaneous documentation and man pages.</P>
+
+<H3>Programmer's notes</H3>
+
+<P>Cleaned up functions such as pass1_get_blocks, pass1_read_inode which
+in e2fsck's pass1.c really should have been static.</P>
+
+<P>The return value of the uuid_compare() function was changed to make it
+match with the convetions used by strcmp, memcmp, and Paul Leach's
+UUID sample document.</P>
+
+<P>The "make depend" process has now been made more automated; it now
+automatically word-wraps the dependencies, and only replaces source
+Makefile.in if there has been a change in the dependencies.  Also, a
+top-level "make depend" now recurses through all the subdirectories
+automatically.</P>
+
+<P>The Makefile in .../util has been changed so that subst is built using
+the native C compiler during a cross-compilation, since the subst
+program is only used during the build process.  Also add an explicit
+rule to build util/subst by cd'ing to the correct directory and
+running Makefile.</P>
+
+<P>The man directories are defined in terms mandir, so that the configure
+script can override the location of the manual pages.</P>
+
+<P>The config files have been updated to recognize new machine types for
+both the i386 and alpha families.</P>
+
+<P>Fsck has been modified so that it will accurately create an
+fsck_instance even when the noexecute flag is set.  This allows for
+accurate debugging of the fsck pass structure.  Also, when the verbose
+flag is given twice, fsck will print debugging information about when
+fsck is waiting for jobs to finish.</P>
+
+
+
+<H2><A NAME="1.14">E2fsprogs 1.14 (January 9, 1999)</A></H2>
+
+<P>Fix the fstab parsing code so that it can handle blank lines and
+comment characters.  Also, missing pass numbers need to be treated as
+zero.</P>
+
+<P>Fixed a bug in e2fsck where under some circumstances (when e2fsck
+needs to restart processing after fixing an egregious inconsistency)
+it would try to access already freed memory.</P>
+
+<P>E2fsck now prints non-printable characters in directory entries and
+pathnames using '^' and 'M-' notation.</P>
+
+<P>Fixed chattr so that it will ignore symbolic links when doing
+recursive descent traversals.  For both chattr and lsattr, no longer
+print the version string unless the -V option is given.</P>
+
+<P>Allow the system administrator to directly specify the number of
+inodes desired in the filesystem, for some special cases where this is
+necessary.</P>
+
+<P>Fix portability problems so that e2fsprogs can be compiled under Linux
+1.2 systems and Solaris systems.</P>
+
+<P>Update the config.guess file with a more recent version that will
+identify newer Linux platforms.</P>
+
+<H3>Programmer's notes</H3>
+
+<P>Ext2fs_read_inode and ext2fs_write_inode will now return an error if
+an inode number of zero is passed to them.</P>
+
+<H2><A NAME="1.13">E2fsprogs 1.13 (December 15, 1998)</A></H2>
+
+<P>Fixed a bug in debugfs where an error messages weren't getting printed
+when the ext2 library routines to read inodes returned errors in the
+stat, cmri and rm commands.</P>
+
+<P>Fixed a bug in mke2fs so that if a ridiculous inode ratio parameter is
+provided, it won't create an inode table smaller than the minimum
+number of inodes required for a proper ext2 filesystem.</P>
+
+<P>Fsck now parses the /etc/fstab file directly (instead of using
+getmntent()), so that it can distinguish between a missing pass number
+field and pass number field of zero.  This caused problems for
+diskless workstations where all of the filesystems in /etc/fstab have
+an explicit pass number of zero, and fsck could not distinguish this
+from a /etc/fstab file with missing pass numbers.</P>
+
+<P>E2fsck will create a /lost+found directory if there isn't one in the
+filesystem, since it's safer to create the lost+found directory before
+it's needed.</P>
+
+<P>Fixed e2fsck so that it would detect bogus immutable inodes which
+happen to be sockets and FIFO files, and offer to clear them.</P>
+
+<P>If a filesystem has multiple reasons why it needs to be checked, and
+one of the reasons is that it is uncleanly mounted, e2fsck will print
+that as the reason why the filesystem is being checked.</P>
+
+<P>Cleaned up the output routines of mke2fs so that it doesn't overflow
+an 80 column display when formating really big filesystems.</P>
+
+<P>Added a sanity check to e2fsck to make sure that file descriptors 0,
+1, 2 are open before opening the hard disk.  This avoids a problem
+where a broken program might exec e2fsck with those file descriptors
+closed, which would cause disastrous results if the kernel returns a
+file descriptor for the block device which is also used by FILE *
+stdout.</P>
+
+<P>Fixed up the e2fsck progress reporting functions so that the values
+reliably reach 100% at the completion of all of the e2fsck passes.</P>
+
+<P>Fixed minor documentation bugs in man pages and usage messages.</P>
+
+<H3>Programmer's notes</H3>
+
+<P>Fixed a number of lint warnings in the ext2fs library and potential
+portability problems from other OS's header files that might define
+CPP macros for names like "max" and "min".</P>
+
+<P>ext2fs_badblocks_list_add() has been made more efficient when it needs
+to grow the bad blocks list.</P>
+
+<P>Fixed a bug in e2fsck which caused it to dereference a freed pointer
+just before exiting.</P>
+
+<P>Fixed the substition process for generating the mk_cmds and compile_et
+scripts so that they will work outside of the build tree.</P>
+
+<P>Add sanity check to e2fsck so that if an internal routine
+(ext2fs_get_dir_info) returns NULL, avoid dereferencing the pointer
+and causing a core dump.  This should never happen, but...</P>
+
+<H2><A NAME="1.12">E2fsprogs 1.12 (July 4, 1998)</A></H2>
+
+<P>E2fsprogs now works with glibc (at least with the version shipped wtih
+RedHat 5.0).  The ext2fs_llseek() function should now work even with
+i386 ELF shared libraries and if llseek() is not present.  We also
+explicitly do a configure test to see if (a) llseek is in libc, and
+(b) if llseek is declared in the system header files.  (See standard
+complaints about libc developers don't understand the concept of
+compatibility with previous versions of libc.)</P>
+
+<P>The ext2fs library now writes out the block group number in each of
+the superblock copies.  This makes it easier to automatically
+determine the starting block group of the filesystem when the block
+group information is trashed.</P>
+
+<P>Added support for the EXT2_FEATURE_INCOMPAT_FILETYPE feature,
+which means that e2fsprogs will ignore the high 8 bits of the
+directory entry's name_len field, so that it can be used for other
+purposes.</P>
+
+<P>Added support for the EXT2_FEATURE_RO_COMPAT_LARGE_FILE feature.
+E2fsprogs will now support filesystems with 64-bit sized files.</P>
+
+<P>Added support for the EXT2_FEATURE_COMPAT_DIR_PREALLOC feature.</P>
+
+<P>Added new program "e2label", contributed by Andries Brouwer.  E2label
+provides an easy-to-use interface to modify the filesystem label.</P>
+
+<P>Fixed bug so that lsattr -v works instead of producing a core dump.</P>
+
+<P>Fixed a minor bug in mke2fs so that all groups with bad superblock
+backup blocks are printed (not just the first one).</P>
+
+<P>Mke2fs will check the size of the device, and if the user specifies a
+filesystem size larger than the apparent size of the device it will
+print a warning message and ask if the user wants to proceed.</P>
+
+<P>E2fsck has a new option -C, which sends completion information to the
+specified file descriptor.  For the most part, this is intended for
+programs to use, although -C 0 will print a spinning character to the
+stdout device, which may be useful for users who want to see something
+happening while e2fsck goes about its business.</P>
+
+<P>Fixed a bug in e2fsck which could cause a core dump when it needs to
+expand the /lost+found directory, and sometimes the bitmaps haven't
+been merged in.  Also fixed a related bug where ext2fs_write_dir_block
+was used to write out a non-directory block.  (Which would be bad on a
+non-Intel platform with byte swapping going on.)</P>
+
+<P>Fixed bug in e2fsck where it would print a "programming error" message
+instead of correctly identifying where a bad block was in used when
+the bad block was in a non-primary superblock or block group
+descriptor.  Also fixed a related bug when sparse superblocks are in
+use and there is a bad block where a superblock or block group
+descriptor would have been in a group that doesn't include a
+superblock.</P>
+
+<P>Fixed a bug in e2fsck (really in libext2fs's dblist function) where if
+the block group descriptor table is corrupt, it was possible to try to
+allocate a huge array, fail, and then abort e2fsck.
+ext2fs_get_num_dirs() now sanity checks the block group descriptor,
+and subsitutes reasonable values if the descriptors are obviously bogus.</P>
+
+<P>If e2fsck finds a device file which has the immutable flag set and the
+i_blocks beyond the normal device number are non-zero, e2fsck will
+offer to remove it, since it's probably caused by garbage in the inode
+table.</P>
+
+<P>When opening a filesystem, e2fsck specially checks for the EROFS error
+code, and prints a specific error message to the user which is more
+user friendly.</P>
+
+<P>If the filesystem revision is too high, change the e2fsck to print
+that this is either because e2fsck is out of date, or because the
+superblock is corrupt.  </P>
+
+<P>E2fsck now checks for directories that have duplicate '.' and '..'
+entries, and fixes this corruption.</P>
+
+<P>E2fsck no longer forces a sync of the filesystem (with attendant sleep
+calls) at all times.  The ext2fs_flush() function now performs a sync
+only if it needed to write data blocks to disk.</P>
+
+<P>Fixed a minor bug in e2fsck's pass1b's file cloning function, where
+certain errors would not be properly reported.</P>
+
+<P>Updated and expanded a few points in the man pages which users
+complained wheren't explicit enough.</P>
+
+<P>Added special case byte-swapping code if compiling on the PowerPC, to
+accomodate the strange big-endian variant of the ext2 filesystem that
+was previously used on the PowerPC port.</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Removed C++ keywords from the ext2fs libraries so that it could be
+compiled with C++.</P>
+
+<P>E2fsck's internal organization has now been massively reorganized so
+that pass*.c don't have any printf statements.  Instead, all problems
+are reported through the fix_problem() abstraction interface.  E2fsck
+has also been revamped so that it can be called as a library from a
+application.</P>
+
+<P>Added new fileio primitives in libext2fs for reading and writing
+files on an unmounted ext2 filesystem.  This interface is now used by
+debugfs.</P>
+
+<P>Added a new libext2fs function for mapping logical block numbers of
+a file to a physical block number.</P>
+
+<P>Added a new libext2fs function, ext2fs_alloc_block(), which allocates
+a block, zeros it, and updates the filesystem accounting records
+appropriately.</P>
+
+<P>Added a new libext2fs function, ext2fs_set_bitmap_padding(), which
+sets the padding of the bitmap to be all one's.  Used by e2fsck pass 5.</P>
+
+<P>The libext2fs functions now use a set of memory allocation wrapper
+functions: ext2fs_get_mem, ext2fs_free_mem, and ext2fs_resize_mem,
+instead of malloc, free, and resize.  This makes it easier for us to
+be ported to strange environments where malloc, et. al. aren't
+necessarily available.</P>
+
+<P>Change the libext2fs fucntion to return ext2-specific error codes
+(EXT2_DIR_EXISTS and EXT2_DB_NOT_FOUND, for example) instead of using
+and depending on the existence of system error codes (such as EEXIST
+and ENOENT).</P>
+
+<P>Renamed io.h to ext2_io.h to avoid collision with other OS's header
+files.</P>
+
+<P>Add protection against ext2_io.h and ext2fs.h being included multiple
+times.</P>
+
+<P>The types used for memory lengths, etc. have been made more portable.
+In generla, the code has been made 16-bit safe.  Added Mark
+Habersack's contributed DOS disk i/o routines.</P>
+
+<P>Miscellaneous portability fixes, including not depending on char's
+being signed.</P>
+
+<P>The io_channel structure has a new element, app_data, which is
+initialized by the ext2fs routines to contain a copy of the filesystem
+handle.</P>
+
+<P>ext2fs_check_directory()'s callback function may now return the error
+EXT2_ET_CALLBACK_NOTHANDLED if it wishes ext2fs_check_directory() to
+really do the checking, despite the presence of the callback function.</P>
+
+
+<H2><A NAME="1.10">E2fsprogs 1.10 (April 24, 1997)</A></H2>
+
+<P>Mke2fs once again defaults to creating revision #0 filesystems, since
+people were complaining about breaking compatibility with 1.2 kernels.
+Warning messages were added to the mke2fs and tune2fs man pages that
+the sparse superblock option isn't supported by most kernels yet (1.2
+and 2.0 both don't support parse superblocks.)</P>
+
+<P>Added new flag to mke2fs -R <raid options>, which allows the user to
+tell mke2fs about the RAID configuration of the filesystem.  Currently
+the only supported raid option is "stride" which specifies the width
+of the RAID stripe.</P>
+
+<P>Fixed bug in e2fsck where pass1b would bomb out if there were any
+blocks marked bad in the inode table.</P>
+
+<P>Fixed rare bug in mke2fs where if the user had a very unlucky number
+of blocks in a filesystem (probability less than .002) the resulting
+filesystem would be corrupt in the last block group.</P>
+
+<P>Fixed bug where if e2fsck tried to allocate a block to fix a
+filesystem corruption problem and the filesystem had no free blocks,
+ext2fs_new_block() would loop forever.</P>
+
+<P>The configure script now checks explicitly to see if "-static" works,
+since that can't be assumed to be true --- RedHat doesn't install
+libc-static by default.</P>
+
+<P>Fixed bug in libext2's block iterator functions where under some
+cirmcustances, file with holes would cause the bcount parameter to the
+callback function to be incorrect.  This bug didn't affect any of
+e2fsprogs programs, but it was discovered by Paul Mackerras, the
+author of the PPC boot loader.</P>
+
+<P>Removed use of static variables to store the inode cache in libext2fs.
+This caused problems if more than one filesystem was accessed via
+libext2fs (static variables in libraries are generally a bad idea).
+Again, this didn't affect e2fsprogs programs, but it was discovered by
+Paul Mackerras.</P>
+
+<P>Fixed minor bugs and version code drift to assure that e2fsprogs 1.10
+will compile cleanly with 1.2.13 kernels (even with a.out shared
+libraries!)</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Added new functions to duplicate an ext2 filesystem handle, and its
+associated substructure.  New functions: ext2fs_dup_handle(),
+ext2fs_copy_dblist(), ext2fs_badblocks_copy(), ext2fs_copy_bitmap().
+Other structures, such as the io_channel and the inode_cache, now have
+a ref count so that they only get freed when they are no longer used
+by any filesystem handle.  (These functions were added as part of the
+development effort for an ext2 resizer).</P>
+
+
+
+<H2><A NAME="1.09">E2fsprogs 1.09 (April 14, 1997)</A></H2>
+
+<P>Fixed bug in mke2fs (really in lib/ext2fs/initialize.c) which was
+accidentally introduced in the 1.08 release.  The overhead calculation
+was accidentally removed, which caused ext2fs_initialize() to not
+notice when the filesystem size needed to be adjusted down because
+there wasn't enough space in the last block group.</P>
+
+<P>Fixed bug in version parsing library routine; it was always parsing
+the library version string, instead of using the passed-in string.</P>
+
+<P>Clarified chattr man page.</P>
+
+
+<H2><A NAME="1.08">E2fsprogs 1.08 (April 10, 1997)</A></H2>
+
+<P>E2fsck 1.07 was very slow when checking very large filesystems with a
+lot of files that had hard links (i.e., news spools).  This was fixed
+by seriously revamping the icount abstraction.  Added a formal test
+suite for the icount abstraction.</P>
+
+<P>Debugfs now has a "-l" option to the "ls" command, which lists the
+inode number, permissions, owner, group, size, and name of the files
+in the directory.</P>
+
+<P>Fix a bug in e2fsck where when a directory had its blocks moved to
+another location during the pass 1b processing, the directory block
+list wasn't updated, so pass 2 wouldn't check (and correct) the
+correct directory block.</P>
+
+<P>E2fsck will now treat inodes which contain blocks which are claimed by
+the filesystem metadata by treating them as multiply claimed blocks.
+This way, the data in those blocks can be copied to a new block during
+the pass 1b--1d processing.</P>
+
+<P>E2fsck will attempt to determine the correct superblock number and
+display it in the diagnostic and warning messages if possible.</P>
+
+<P>Add support for a new (incompatible) feature, "sparse_super".  This
+feature reduces the number of blocks which contain copies of backup
+superblocks and block group descriptors.  (It is only an incompatible
+feature because of a bug in ext2_free_blocks.)  mke2fs and tune2fs now
+support a new -s option; e2fsck will recognize filesystems built with
+this feature turned on.</P>
+
+<P>E2fsck now checks the library to make sure is the correct version,
+using new library functions.  (This helps to diagnose incorrectly
+installed e2fsprogs distributions.)</P>
+
+<P>Dumpe2fs now prints more information; its now prints the the
+filesystem revision number, the filesystem sparse_super feature (if
+present), the block ranges for each block group, and the offset from
+the beginning of the block group.</P>
+
+<P>Mke2fs now distributes the inode and block bitmap blok so that the
+won't be concentrated in one or two disks in RAID/striping setups.
+Also, if the user chooses a 2k or 4k block group, mke2fs will try to
+choose the largest blocks per group that be chosen.  (For 2k blocks,
+you can have up to 16384 blocks/group; for 4k blocks, you can have up
+to 32768 blocks/group.)  Previously mke2fs would not allow
+specification of more than 8192 blocks per group, even if you were
+using a 2k or 4k block group.</P>
+
+<H3>Programmer's notes</H3>
+
+<P>Added a new function ext2fs_create_icount2() which takes a "hint"
+argument.  This hint argument presets the icount array with the list
+of inodes which actually need to be in the icount array.  This really
+helps to speed up e2fsck.</P>
+
+<P>Added a new function ext2fs_icount_validate() which checks the rep
+invariant for the icount structure.  This is used mostly for testing.</P>
+
+<P>The error mesasage given when a bad inode number is passed to
+test_generic_bitmap to reflect EXT2FS_TEST_ERROR (instead of
+EXT2FS_UNMARK_ERROR).</P>
+
+<P>Added a new function ext2fs_set_dir_block which sets the block of a
+dblist entry, given the directory inode and blockcnt.</P>
+
+<P>Added a new function ext2fs_get_library_version() which returns the
+current library version, and ext2fs_parse_version_string() which
+returns a version number based on a e2fsprogs version string.</P>
+
+<P>The icount functions will return EINVAL if the passed in inode number
+is out of bounds.</P>
+
+
+<H2><A NAME="1.07">E2fsprogs 1.07 (March 14, 1997)</A></H2>
+
+<P>E2fsck is now uses much less memory when checking really large
+filesystems (or rather, filesystems with a large number of inodes).
+Previously a filesystem with 1 million inodes required 4 megabytes of
+memory to store inode count statistics; that storage requirement has
+now been reduced to roughly half a megabyte.</P>
+
+<P>E2fsck can now properly deal with bad blocks appearing inside the
+inode table.  Instead of trying to relocate the inode table (which
+often failed because there wasn't enough space), the inodes in the bad
+block are marked as in use.</P>
+
+<P>E2fsck will automatically try to use the backup superblocks if the
+primary superblocks have a bad magic number or have missing meta-data
+blocks (or meta-data blocks which are out of range).</P>
+
+<P>E2fsck's pass 3 has been made more efficient; most noticeable on
+filesystems with a very large number of directories.</P>
+
+<P>Completely revamped e2fsck's system of printing problem reports.  It
+is now table driven, to make them more easily customizeable and
+extendable.  Error messages which can be printed out during preen mode
+are now one line long.</P>
+
+<P>Fixed e2fsck's filesystem swapping code so that it won't try to swap
+fast symbolic links or deleted files.</P>
+
+<P>Fixed e2fsck core dumping when fixing a filesystem which has no
+directories (not even a root directory).</P>
+
+<P>Added a check to e2fsck to make sure that the length of every
+directory entry is a multiple of 4 (since the kernel complains if it
+isn't).</P>
+
+<P>Added a check to e2fsck to make sure that a directory entry isn't a
+link to the root directory, since that isn't allowed.</P>
+
+<P>Added a check to e2fsk to now make sure the '.' and '..' directory
+entries are null terminated, since the 2.0 kernel requires it.</P>
+
+<P>Added check to write_bitmaps() to make sure the superblock doesn't get
+trashed if the inode or block bitmap is marked as being block zero.</P>
+
+<P>Added checking of the new feature set fields in the superblock, to
+avoid dealing with new filesystem features that this package wasn't
+set up to handle.</P>
+
+<P>Fixed a fencepost error in ext2fs_new_block() which would occasionally
+try to allocate a block beyond the end of a filesystem.</P>
+
+<P>When the UUID library picks a random IEEE 802 address (because it
+can't find one from a network card), it sets the multicast bit, to
+avoid conflicting with a legitimate IEEE 802 address.</P>
+
+<P>Mke2fs now sets the root directory's owner to be the real uid of the
+user running mke2fs.  If the real uid is non-zero, it also sets
+the group ownership of the root directory to be the real group-id of
+the user running mke2fs.</P>
+
+<P>Mke2fs now has more intelligent error checking when it is given a
+non-existent device.</P>
+
+<P>When badblocks is given the -vv option, it now updates the block that
+it is currently testing on every block.</P>
+
+<P>Fixed a bug in fsck where it wouldn't modify the PATH envirnoment
+currently correctly if PATH wasn't already set.</P>
+
+<P>Shared libraries now built with dependencies.  This allows the shared
+library files to be used with dlopen(); it also makes the transition
+to libc 6 easier, since ld.so can tell which libc a particular shared
+library expects to use.</P>
+
+<H3>Programmer's notes:</H3>
+
+<P>Added new abstraction (defined in dblist.c) for maintaining a list of
+blocks which belongs to directories.  This is used in e2fsck and other
+programs which need to iterate over all directories.</P>
+
+<P>Added new functions which test to see if a contiguous range of blocks
+(or inodes) are available.  (ext2fs_*_bitmap_range).</P>
+
+<P>Added new function (ext2_inode_has_valid_blocks) which returns true if
+an inode has valid blocks.  (moved from e2fsck code).</P>
+
+<P>Added new function (ext2fs_allocate_tables) which allocates the
+meta-data blocks as part of initializing a filesystem.  (moved from
+mke2fs code).</P>
+
+<P>Added a new I/O manager for testing purposes.  It will either allow a
+program to intercept I/O requests, or print debugging messages to
+trace the activity of a program using the I/O manager.</P>
+
+<P>The badblocks_list functions now store the bad blocks in a sorted
+order, and use a binary search to speed up badblocks_list_test.</P>
+
+<P>The inode scan function ext2fs_get_next_inode() may now return a soft
+error returns: MISSING_INODE_TABLE and BAD_BLOCK_IN_INODE_TABLE in
+those cases where part of an inode table is missing or there is a bad
+block in the inode table.  </P>
+
+<P>Added a new function (ext2fs_block_iterate2) which adds new arguments to
+the callback function to return a pointer (block and offset) to the
+reference of the block.</P>
+
+<P>Added new function (ext2fs_inode_scan_goto_blockgroup) which allows an
+application to jump to a particular block group while doing an inode
+scan.</P>
+
+<P>The badblocks list functions were renamed from badblocks_* to
+ext2fs_badblocks_*.  Backwards compatibility functions are available
+for now, but programs should be modified to use the new interface.</P>
+
+<P>Some of the library functions were reorganized into separate files to
+reduce the size of some programs which statically link against the
+ext2 library.</P>
+
+<P>Put in some miscellaneous fixes for the Alpha platform.</P>
+
+
+<H2><A NAME="1.06">E2fsprogs 1.06 (October 7, 1996)</A></H2>
+
+<P>Fixed serious bug in e2fsck: if the block descriptors are bad, don't
+smash the backup copies in ext2fs_close().  (The problem was that when
+e2fsck -p discovered the problem, while it was closing the filesystem
+and exiting, it was also blowing away the backup superblocks on the
+disk, which was less than friendly.)  We now make it the case that we
+only write out the backup superblock and the back block descriptors if
+the filesystem is completely free from problems.</P>
+
+<P>Fixed a bug in block_interate in the lib/ext2fs library which caused
+e2fsck to fail on GNU Hurd-created filesystems.</P>
+
+<P>Add support for Linux/FT's bootloader, which actually uses
+EXT2_BOOT_LOADER, and sets its mode bits which caused e2fsck to want
+to clear the inode.</P>
+
+<P>Add support for the "A" (no atime update) attribute.  (Note: this
+attribute is not yet in production kernels.)</P>
+
+<P>The test suite is not automatically run when doing a "make all" from
+the top level directory.  Users should manually run "make check" if
+they wish to run the test suite.</P>
+
+<P>Upon a preenhalt(), make the printed message more explicit that
+running e2fsck "MANAULLY" means without the -p or -a options.</P>
+
+<P>In e2fsck, if a disconnected inode is zero-length, offer to clear it
+instead of offering to connect it to lost+found.</P>
+
+<P>In e2fsck, if a filesystem was just unmounted uncleanly, and needs
+e2fsck to be run over it, change e2fsck to explicitly display this
+fact.</P>
+
+<P>For dumpe2fs and e2fsck, cause the -V option to print out which
+version of the ext2fs library is actually getting used.  (This will
+help detect mismatches of using a 1.06 utility with a 1.05 library,
+etc.)</P>
+
+<H3>Programmers' notes:</H3>
+
+<P>EXT2_SWAP_BYTES was changed to EXT2_FLAG_SWAP_BYTES, which better fits
+the naming convention.</P>
+
+<P>In ext2fs_initialize(), make sure the description for the inode bitmap
+is correctly initialize.</P>
+
+<P>Fixed minor type typo in ext2fs_allocate_generic_bitmap()</P>
+
+<H2><A NAME="1.05">E2fsprogs 1.05 (September 7, 1996)</A></H2>
+
+<P>Add support for new fields in the ext2 superblock --- volume name,
+volume UUID, and last mounted field.  Dumpe2fs displays these fields,
+tune2fs and mke2fs allows you to set them.  E2fsck will automatically
+generate a UUID for those volumes that don't have them.</P>
+
+<P>Put in support for e2fsck to recognize HURD specific ext2 features ---
+most notably, the translator block.  The e2fsprogs tools will now use
+the creator_os field in the superblock to correctly handle different
+OS-specific variants of the ext2 filesystem.</P>
+
+<P>E2fsck now fixes inodes which have a the deletion time set, but which
+have a non-zero i_link_count field by offering to clear the deletion
+time.  Previously e2fsck assumed that the inode was deleted (per 0.3c
+ext2 kernel behavior) and offered to unlink the file.</P>
+
+<P>If e2fsck sets the clean bit, but nothing else, set the exit code
+FSCK_NONDESTRUCT.  After all, e2fsck did fix a filesystem error --- it
+set the filesystem valid bit when it was previously cleared.  :-) This
+was needed to make the HURD fsck driver happy.</P>
+
+<P>If the  user  refuses to attach an  unattached  inode, e2fsck  will no
+longer set the inode's link count.  Otherwise, the  inode would end up
+getting marked as unused, which might cause loss of data later.</P>
+
+<P>Make the message issued by e2fsck when the superblock is corrupt less
+confusing for users.  It now mentions that another reason for the
+"corrupt superblock" message might be that the partition might not be
+an ext2 filesystem at all (it might swap, msdos filesystem, ufs, etc.)</P>
+
+<P>Make the libext2 library more robuest so that e2fsck won't coredump on
+an illegal superblock where the blocksize is zero.  (f_crashdisk is
+the test case).</P>
+
+<P>By default, create filesystems where the default checkinterval is 6
+months (180 days).  Linux servers can be robust enough that 20 reboots
+can be a long, long time.</P>
+
+<P>Added configure flag --enable-old-bitops, which forces the bitops to
+use the old (native) bitmask operations.  By default on the sparc
+platform, the standard ext2 bit ordering is now used.</P>
+
+<P>Added a new feature to e2fsck to byte-swap filesystems; this can be
+used to convert old m68k filesystems to use the standard byte-order
+storage for the superblock, inodes, and directory blocks.  This
+function is invoked by using the '-s' option to e2fsck.</P>
+
+<P>Debugfs's "dump" command has been enhanced so that it writes out the
+exact size of the file so that the nulls at the end of the file are
+eliminated.  The command also accept a new "-p" option which will
+attempt preserve to preserve the ownernship, permissions, and
+file modification/access times.</P>
+
+<P>Debugfs has two new options, -f and -R.  The -R option allows the user
+to execute a single debugfs command from the command line.  The -f
+option allows the user to specify a "command file" containing debugfs
+commands which will get executed.</P>
+
+<P>Dumpe2fs now pretty prints the check interval, instead of just
+printing the check interval as a number of seconds.</P>
+
+<P>Fix bugs in debugfs: the params command when no filesystem is opened
+no longer causes a core dump.  It is now possible to unlink a file
+when a pathame containing a '/' is specified.</P>
+
+<P>Tune2fs has a new -C option which sets the number of times the
+filesystem has been mounted.</P>
+
+<P>Fix the chattr '-v' option so that it actually works.  Chattr was
+being buggy about the -v option parsing.</P>
+
+<H3>Programmers' notes:</H3>
+
+<P>The directory lib/uuid contains a set of library routines to generate
+DCE compatible UUIDs.  </P>
+
+<P>Extended ext2fs_namei() to handle symbolic links.  Added new function
+ext2fs_nami_follow() which will follow last symbolic link in the case
+where the pathname points to a sym link.</P>
+
+<P>The ext2fs_block_iterate function will now return the HURD translator
+block, if present.  The new flag BLOCK_FLAG_DATA_ONLY will cause the
+iterator to return data blocks only.  The ext2fs.h file now defines
+constants BLOCK_COUNT_IND, BLOCK_COUNT_DIND, BLOCK_COUNT_TIND, and
+BLOCK_COUNT_TRANSLATOR, which are the magic values passed in the block
+count field of the iterator callback function.</P>
+
+<P>The test script driver now takes an optional second argument, which is
+the test case to be run.  This allows you to run a test case without
+needing to run the entire test suite.</P>
+
+<P>On Linux ELF systems, install the .so files in the correct places
+(/usr/lib).  The .so files must be stored in the same directory as the
+.a files.</P>
+
+<P>Fixed miscellaneous HURD compilation issues with header file being
+included in the right order.</P>
+
+<P>Fixed debugfs so that it resets optind to zero, not one, since setting
+optind to zero is more correct.</P>
+
+<H2><A NAME="1.04">E2fsprogs 1.04 (May 16, 1996)</A></H2>
+
+<P>First "official" (1.03 was a limited release only) to support building
+e2fsprogs under Linux 2.0 kernels (as well as late model 1.3 and 1.99
+kernels).</P>
+
+<P>This package includes a RPM specs file, that it can be built using the
+RedHat Package Manager.</P>
+
+<P>E2fsck now prints a hint that if there are lots of incorrectly located
+inode bitmaps, block bitmaps, and inode table blocks, the user might
+want to try using e2fsck -b 8193 first, to see if that fares any
+better.</P>
+
+<P>For ext2 filesystem written with the hurd, debugfs will now print out
+the translator field when printing an inode structure.</P>
+
+<H3>Lots of miscellaneous linking/installation cleanups:</H3>
+
+<P>Libraries are now linked using a relative pathname, instead of
+relying on -L working correct.  It doesn't, in many cases, including
+current versions of GNU ld.  This guarantees that the build tree is
+linking with the right libraries, instead of the ones installed in
+/usr/lib.</P>
+
+<P>Header files, man pages, and the et/ss shell scripts are now
+  generated using a custom substitution script, instead of relying on
+  the configure script.  This prevents needless recompilation of
+  files; in addition, the custom substitution script is much faster.</P>
+
+<P>e2fsck may now be linked dynamically, by using the
+  --enable-dynamic-e2fsck flag to configure.  This is not recommended,
+  since it increases e2fsck's dependence on other files, but some
+  people need to save disk space, and other critical programs on their
+  systems were being linked dynamically anyway.</P>
+
+<P>Programs such as fsck which didn't need to be linked against
+  libext2fs (or mke2fs which didn't need to be linked against libe2p)
+  only link against libraries they actually need.  Otherwise, those
+  programs would require the presense of libraries that otherwise
+  could be removed from a rescue diskette.</P>
+
+<P>  The ss include files are now installed correctly so they can
+  actually be used by another package.</P>
+
+<P>  If the profiling libraries are built, they are now installed on a
+  "make install-libs".</P>
+
+
+<H2><A NAME="1.03">E2fsprogs 1.03 (March 27, 1996)</A></H2>
+
+<P>Change the m68k bit numbering for bitmasks to match the bit numbering
+used by all other ext2 implementations.  (This change was requested by
+the m68k kernel development team.)</P>
+
+<P>Support (in-development) filesystem format revision which supports
+(among other things) dynamically sized inodes.</P>
+
+<P>Fixed a bug in the ext2 library so that an intelligent error is
+returned if mke2fs is run with a ridiculously small number of blocks
+for a partition.</P>
+
+<P>Fixed a bug in the ext2 library which required that the device be
+openable in read/write mode in order to determine its size.  This
+caused e2fsck -n to require read/write access when it was not
+previously necessary.</P>
+
+<P>Fixed a bug in e2fsck which casued it to occasionally fail the test
+suite depending on which version of the floating point library it was
+using.</P>
+
+<P>Fixed a bug in e2fsck so that it now halts with a fatal error when
+certain superblock consistency checks fail.  Previously it continued
+running e2fsck, with some potential confusing/damaging consequences.</P>
+
+<P>Added new flag to fsck which allows the root to be checked in parallel
+with other filesytems.  This is not the safest thing in the world to
+do, but some system administrators really wanted it.</P>
+
+<P>Fixed -Wall flames in lib/ss.</P>
+
+
+<H2><A NAME="1.02">E2fsprogs 1.02 (January 16, 1996)</A></H2>
+
+<P>Fix to allow e2fsprogs to be compiled on recent 1.3 (pl45+) kernels.</P>
+
+<P>Change e2fsck to print statistics of how many non-contiguous files are
+on the system.  Note that a file which is larger than 8k blocks, it is
+guaranteed to be non-contiguous.</P>
+
+<P>In mke2fs, print a warning message if a user tries to format a whole
+disk (/dev/hda versus /dev/hda1).  If a user really wants to format a
+whole disk, the -F (force) option forces mke2fs to format a whole disk
+as a filesytem.</P>
+
+<P>Fix a bug in fsck where in some cases it might start checking
+partitions in the next pass before it finishes checking partitions in
+the current pass.  This still won't cause two partitions on the same
+disk will be checked, so it's rarely a problem in real life.</P>
+
+<P>Patch lsattr so that it won't hang when checking a named pipe.</P>
+
+<P>Minor compilation fixes:</P>
+<UL>
+<LI> Fix the order of libraries that were linked in debugfs.
+<LI> Allow the sources to be compiled with -ansi turned on.
+</UL>
+
+<HR>
+
+<P><A HREF="http://e2fsprogs.sourceforge.net">Back to e2fsprogs page</A></P>
+
+<P><A HREF="ext2.html">Back to ext2fs home page</A></P>
+
+<ADDRESS>
+<A HREF="http://thunk.org/tytso">Theodore Ts'o</A>
+</ADDRESS> 
+
+<!-- end actual content -->
+
+    </TD>
+  </TR>
+</TABLE>
+<!-- end center table -->
+
+<center>
+<a href="http://www2.valinux.com/adbouncer.phtml?f_s=468x60&f_p=625">
+<img src="http://www2.valinux.com/adserver.phtml?f_s=468x60&f_p=625" width="468" height="60" border="0"
+alt="Member of the VA Affiliate Underground" ></a>
+</center>
+
+<!-- footer table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="2" bgcolor="737b9c">
+  <TR>
+    <TD align="center"><FONT color="#ffffff"><SPAN class="titlebar">
+      All trademarks and copyrights on this page are properties of their respective owners.</SPAN></FONT>
+    </TD>
+  </TR>
+</TABLE>
+
+<!-- end footer table -->
+</BODY>
+</HTML>
diff --git a/htdocs/e2fsprogs.inc b/htdocs/e2fsprogs.inc
new file mode 100644
index 000000000..954f60119
--- /dev/null
+++ b/htdocs/e2fsprogs.inc
@@ -0,0 +1,40 @@
+<Center>
+<H1> Welcome to the E2fsprogs Sourceforge Page</H1>
+</CENTER>
+
+<P>This is the home page for the e2fsprogs package.  It provides the
+filesystem utilities for use with the <A HREF="ext2.html">ext2
+filesystem.</A> It also supports the ext3 filesystem with journaling
+support.</P>
+
+<P>The e2fsprogs <A HREF="http://sourceforge.net/projects/e2fsprogs">
+Sourceforge summary page</A> can be found here.  For more information
+about the ext2 filesystem, <A HREF="ext2.html">click here</A>.</P>
+
+<P>The latest development sources for e2fsprogs is maintained in a <A
+HREF="http://www.kernel.org/pub/software/scm/git/docs">Git</A>
+repository at <a
+HREF="http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=summary">git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git</a>.
+A quick tutorial about how to start using git can be found 
+<A HREF="http://www.kernel.org/pub/software/scm/git/docs/tutorial.html">here</A>.</P>
+
+
+<IMG SRC="images/new.gif" ALIGN=LEFT><H2>Release 1.40.4 of e2fsprogs is
+available!</H2>
+
+<P>I am happy to announce a new release of the e2fsprogs distribution.
+All users of e2fsprogs are urged to upgrade to the 1.40.4 version as
+soon as possible, which can be found <A HREF="http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.40.4.tar.gz">here</A>.</P>
+
+<P>This release contains a number of bug fixes and enhancements over
+the previous releases.  In particular if you wish to experiment with
+the on-line resizing feature in the 2.6 kernels you should upgrade to
+this version of e2fsprogs.  For more details, see the 
+<A HREF="e2fsprogs-release.html">release notes.</A></P>
+
+
+<ADDRESS>
+<A HREF="http://thunk.org/tytso">Theodore Ts'o</A>
+</ADDRESS> 
+
+
diff --git a/htdocs/ext2-dir.gif b/htdocs/ext2-dir.gif
new file mode 100644
index 000000000..1eb7384c9
--- /dev/null
+++ b/htdocs/ext2-dir.gif
diff --git a/htdocs/ext2-inode.gif b/htdocs/ext2-inode.gif
new file mode 100644
index 000000000..40d834960
--- /dev/null
+++ b/htdocs/ext2-inode.gif
diff --git a/htdocs/ext2-vfs.gif b/htdocs/ext2-vfs.gif
new file mode 100644
index 000000000..ea44bdd06
--- /dev/null
+++ b/htdocs/ext2-vfs.gif
diff --git a/htdocs/ext2.html b/htdocs/ext2.html
new file mode 100644
index 000000000..aa762e96c
--- /dev/null
+++ b/htdocs/ext2.html
@@ -0,0 +1,155 @@
+<HTML>
+<HEAD>
+<TITLE>Ext2fs Home Page</TITLE>
+</HEAD>
+
+<BODY bgcolor=#FFFFFF topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth="0">
+
+<!-- top strip -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=2 bgcolor="737b9c">
+  <TR>
+    <TD><SPAN class=maintitlebar>&nbsp;&nbsp;
+      <A class=maintitlebar href="http://sourceforge.net/"><B>Home</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/about.php"><B>About</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/partners.php"><B>Partners</B></a> |
+      <A class=maintitlebar href="http://sourceforge.net/contact.php"><B>Contact Us</B></A> |
+      <A class=maintitlebar href="http://sourceforge.net/account/logout.php"><B>Logout</B></A></SPAN></TD>
+    </TD>
+  </TR>
+</TABLE>
+<!-- end top strip -->
+
+<!-- top title table -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=0 bgcolor="" valign="center">
+  <TR valign="center" bgcolor="#eeeef8">
+    <TD>
+      <A href="http://sourceforge.net"> 
+	<IMG src="http://sourceforge.net/images/sflogo2-steel.png" width="143" height="70" border="0"></A>
+    </TD>
+    <TD width="99%"><!-- right of logo -->
+      <a href="http://www.valinux.com"><IMG src="http://sourceforge.net/images/valogo3.png" align="right" alt="VA Linux Systems" hspace="5" vspace="7" border=0 width="117" height="70"></A>
+    </TD><!-- right of logo -->
+  </TR>
+  <TR><TD bgcolor="#543a48" colspan=2><IMG src="http://sourceforge.net/images/blank.gif" height=2 vspace=0></TD></TR>
+</TABLE>
+<!-- end top title table -->
+
+<!-- center table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="10" bgcolor="#FFFFFF" align="center">
+  <TR>
+    <TD>
+
+<!-- Begin actual content -->
+
+<CENTER><H1>Ext2fs Home Page</H1></CENTER>
+
+<IMG SRC="../images/new.gif" ALIGN=LEFT>
+<H2>Release 1.40.4 of e2fsprogs is available!</H2>
+
+<P>On December 31, 2007, version 1.40.4 of e2fsprogs was <A
+HREF="http://e2fsprogs.sourceforge.net">announced</A>.</P>
+
+<H2>Ext2fs Utilities</H2>
+
+The following Ext2fs Utilities are available:
+
+<UL>
+  <LI><A HREF="http://e2fsprogs.sourceforge.net">e2fsprogs</A>, which consists of
+		e2fsck, mke2fs, debugfs, dumpe2fs, tune2fs, and most
+		of the other core ext2fs filesystem utilities.
+  <LI><A HREF="http://dump.sourceforge.net/">dump</A>, which will
+	allow you to make backups of your ext2
+	filesystems.  It uses a format which is compatible with the
+	BSD dump and restore programs.
+
+  <LI>defrag, which will defragment your ext2 filesystem
+  <LI>ext2ed, which is a text/windows (curses) interface for examining and
+		editing an ext2 filesystem.  
+		It unfortunately is limited to filesystems smaller than 2GB,
+		and is heavily Intel byte order dependent, and has apparently
+		been abandoned by its original author.  (So for those
+		people who were used to seeing ext2ed in older Linux 
+		distributions, and wondered where it went to, that's 
+		the explanation.)
+		<P>It has been integrated
+		into e2fsprogs version 1.28, but its limitations mean that
+		it should only be used by developers who need to generate
+		test cases. </P>
+
+   <LI><A HREF="http://www.yipton.demon.co.uk/">FSDEXT2</A> --- A (read-only) 
+	ext2 filesystem driver for Windows 95, implemented as Windows 95 
+	File System Driver (FSD).  This driver is maintained by 
+	Peter van Sebille (pese@nlnwgfsc.origin.nl).
+   <LI><A HREF="http://www.sourceforge.net/projects/ext2fsd">Ext2fsd</A>,
+	An ext2
+	filesystem driver for Windows NT/2K/XP.  The most recent
+	version has read-write support.  
+</UL>
+
+<H2>Papers and Documentation of the Ext2 Filesystem</H2>
+
+<UL>
+ <LI> <A HREF="ext2intro.html">Design and Implementation of the Second Extended Filesystem</A>
+</UL>
+
+<H2>Other useful links related to the ext2 filesystem</H2>
+
+<UL>
+<LI>Ext3dev/ext4 --- Future enhancements to ext3
+<UL>
+<LI>
+<LI><A HREF="http://fedoraproject.org/wiki/ext3-devel">Ext3dev/Ext4
+development wiki
+<LI><A HREF="http://ext2.sourceforge.net">Ext2/3 development home page
+</UL>
+</UL>
+
+<UL>
+<LI>Ext3 --- Journaling for ext2fs
+<UL>
+<LI><A HREF="ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/">Ext3 for the 2.2 
+	kernel</A>
+</UL>
+<LI><A HREF="http://thunk.org/tytso/linux/extfs-2.4-update/">Backports</A> of 
+	recent enhancements of the ext2/3 filesystems from 2.5 to the 2.4
+	kernel.
+<LI><A HREF="http://www.sas.com/standards/large.file/">Large File Support</A> API
+</UL>
+
+<H2>Other Linux filesystem development efforts</H2>
+<UL>
+<LI><A HREF="http://www.globalfilesystem.org">The Global File System (GFS)</A>
+<LI>SGI's <A HREF="http://oss.sgi.com/projects/xfs/">XFS port to Linux</A>
+<LI>IBM's <A HREF="http://oss.software.ibm.com/developer/opensource/jfs/">JFS port to Linux</A>
+<LI><A HREF="http://www.idiom.com/~beverly/reiserfs.html">Reiserfs</A>
+<LI><A HREF="http://www.coda.cs.cmu.edu/">CODA</A>, a distributed filesystem like AFS
+<LI><A HREF="http://www.complang.tuwien.ac.at/czezatke/lfs.html">
+dtfs</A>, a log-structed filesystem under development
+<LI><A HREF="http://collective.cpoint.net/lfs/">Another LFS filesystem</A> 
+under development.
+</UL>
+
+<ADDRESS>
+<A HREF="http://thunk.org:/tytso">Theodore Ts'o</A>
+</ADDRESS> 
+
+<!-- end actual content -->
+
+    </TD>
+  </TR>
+</TABLE>
+<!-- end center table -->
+
+
+<!-- footer table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="2" bgcolor="737b9c">
+  <TR>
+    <TD align="center"><FONT color="#ffffff"><SPAN class="titlebar">
+      All trademarks and copyrights on this page are properties of their respective owners.</SPAN></FONT>
+    </TD>
+  </TR>
+</TABLE>
+
+<!-- end footer table -->
+</BODY>
+</HTML>
diff --git a/htdocs/ext2intro.html b/htdocs/ext2intro.html
new file mode 100644
index 000000000..a695beac6
--- /dev/null
+++ b/htdocs/ext2intro.html
@@ -0,0 +1,899 @@
+<HTML>
+<HEAD>
+<TITLE>Design and Implementation of the Second Extended Filesystem</TITLE>
+</HEAD>
+<BODY>
+
+<P>This paper was first published in the Proceedings of the First Dutch
+International Symposium on Linux, ISBN 90-367-0385-9.</P>
+
+<HR>
+
+<H2>Design and Implementation of the Second Extended Filesystem</H2>
+
+<H4>R�my Card, Laboratoire MASI--Institut Blaise Pascal,
+E-Mail: card@masi.ibp.fr, and<BR>
+Theodore Ts'o, Massachussets Institute of Technology,
+E-Mail: tytso@mit.edu, and<BR>
+Stephen Tweedie, University of Edinburgh,
+E-Mail: sct@dcs.ed.ac.uk</H4>
+
+<H3>Introduction</H3>
+
+<P>Linux is a Unix-like operating system, which runs on PC-386
+computers. It was implemented first as extension to the Minix
+operating system <A href="#minix">[Tanenbaum 1987]</A> and its
+first versions included support for the Minix filesystem only.
+The Minix filesystem contains two serious limitations: block
+addresses are stored in 16 bit integers, thus the maximal
+filesystem size is restricted to 64 mega bytes, and directories
+contain fixed-size entries and the maximal file name is 14
+characters.
+
+<P>We have designed and implemented two new filesystems that are
+included in the standard Linux kernel. These filesystems,
+called ``Extended File System'' (Ext fs) and ``Second Extended
+File System'' (Ext2 fs) raise the limitations and add new
+features.
+
+<P>In this paper, we describe the history of Linux filesystems. We
+briefly introduce the fundamental concepts implemented in Unix
+filesystems. We present the implementation of the Virtual File
+System layer in Linux and we detail the Second Extended File
+System kernel code and user mode tools. Last, we present
+performance measurements made on Linux and BSD filesystems and
+we conclude with the current status of Ext2fs and the future
+directions.
+
+<H3>History of Linux filesystems</H3>
+
+<P>In its very early days, Linux was cross-developed under the
+Minix operating system. It was easier to share disks between
+the two systems than to design a new filesystem, so Linus
+Torvalds decided to implement support for the Minix filesystem
+in Linux. The Minix filesystem was an efficient and relatively
+bug-free piece of software.
+
+<P>However, the restrictions in the design of the Minix
+filesystem were too limiting, so people started thinking and
+working on the implementation of new filesystems in Linux.
+
+<P>In order to ease the addition of new filesystems into the
+Linux kernel, a Virtual File System (VFS) layer was developed.
+The VFS layer was initially written by Chris Provenzano, and
+later rewritten by Linus Torvalds before it was integrated into
+the Linux kernel.  It is described in <A href="#section:vfs">The Virtual File System</A>.
+
+<P>After the integration of the VFS in the kernel, a new
+filesystem, called the ``Extended File System'' was implemented
+in April 1992 and added to Linux 0.96c. This new filesystem
+removed the two big Minix limitations: its maximal size was 2
+giga bytes and the maximal file name size was 255 characters.
+It was an improvement over the Minix filesystem but some
+problems were still present in it. There was no support for the
+separate access, inode modification, and data modification
+timestamps. The filesystem used linked lists to keep track of
+free blocks and inodes and this produced bad performances: as
+the filesystem was used, the lists became unsorted and the
+filesystem became fragmented.
+
+<P>As a response to these problems, two new filesytems were
+released in Alpha version in January 1993: the Xia filesystem
+and the Second Extended File System. The Xia filesystem was
+heavily based on the Minix filesystem kernel code and only
+added a few improvements over this filesystem. Basically, it
+provided long file names, support for bigger partitions and
+support for the three timestamps. On the other hand, Ext2fs was
+based on the Extfs code with many reorganizations and many
+improvements. It had been designed with evolution in mind and
+contained space for future improvements. It will be described
+with more details in <A href="#section:ext2fs">The Second
+Extended File System</A>
+
+<P>When the two new filesystems were first released, they
+provided essentially the same features. Due to its minimal
+design, Xia fs was more stable than Ext2fs. As the filesystems
+were used more widely, bugs were fixed in Ext2fs and lots of
+improvements and new features were integrated. Ext2fs is now
+very stable and has become the de-facto standard Linux
+filesystem.
+
+<P>This table contains a summary of the features
+provided by the different filesystems:
+
+<TABLE border>
+<TR><TH></TH><TH>Minix FS</TH><TH>Ext FS</TH><TH>Ext2 FS</TH><TH>Xia FS</TD></TR>
+<TR><TH>Max FS size</TH><TD>64 MB</TD><TD>2 GB</TD><TD>4 TB</TD><TD>2 GB</TD></TR>
+<TR><TH>Max file size</TH><TD>64 MB</TD><TD>2 GB</TD><TD>2 GB</TD><TD>64 MB</TD></TR>
+<TR><TH>Max file name</TH><TD>16/30 c</TD><TD>255 c</TD><TD>255 c</TD><TD>248 c</TD></TR>
+<TR><TH>3 times support</TH><TD>No</TD><TD>No</TD><TD>Yes</TD><TD>Yes</TD></TR>
+<TR><TH>Extensible</TH><TD>No</TD><TD>No</TD><TD>Yes</TD><TD>No</TD></TR>
+<TR><TH>Var. block size</TH><TD>No</TD><TD>No</TD><TD>Yes</TD><TD>No</TD></TR>
+<TR><TH>Maintained</TH><TD>Yes</TD><TD>No</TD><TD>Yes</TD><TD>?</TD></TR>
+</TABLE>
+
+<H3>Basic File System Concepts</H3>
+
+<P>Every Linux filesystem implements a basic set of common
+concepts derivated from the Unix operating system
+<A href="#bach">[Bach 1986]</A> files are represented by inodes,
+directories are simply files containing a list of entries and
+devices can be accessed by requesting I/O on special files.
+
+<H4>Inodes</H4>
+
+<P>Each file is represented by a structure, called an inode.
+Each inode contains the description of the file: file type,
+access rights, owners, timestamps, size, pointers to data
+blocks. The addresses of data blocks allocated to a file are
+stored in its inode. When a user requests an I/O operation on
+the file, the kernel code converts the current offset to a
+block number, uses this number as an index in the block
+addresses table and reads or writes the physical block. This
+figure represents the structure of an inode:
+
+<IMG SRC="ext2-inode.gif">
+
+<H4>Directories</H4>
+
+<P>Directories are structured in a hierarchical tree. Each
+directory can contain files and subdirectories.
+
+<P>Directories are implemented as a special type of files.
+Actually, a directory is a file containing a list of entries.
+Each entry contains an inode number and a file name. When a
+process uses a pathname, the kernel code searchs in the
+directories to find the corresponding inode number. After the
+name has been converted to an inode number, the inode is loaded
+into memory and is used by subsequent requests.
+
+<P>This figure represents a directory:
+
+<IMG SRC="ext2-dir.gif">
+
+<H4>Links</H4>
+
+<P>Unix filesystems implement the concept of link. Several
+names can be associated with a inode. The inode contains a
+field containing the number associated with the file. Adding a
+link simply consists in creating a directory entry, where the
+inode number points to the inode, and in incrementing the links
+count in the inode. When a link is deleted, i.e. when one uses
+the <TT>rm</TT> command to remove a filename, the kernel
+decrements the links count and deallocates the inode if this
+count becomes zero.
+
+<P>This type of link is called a hard link and can only be used
+within a single filesystem: it is impossible to create
+cross-filesystem hard links. Moreover, hard links can only
+point on files: a directory hard link cannot be created to
+prevent the apparition of a cycle in the directory tree.
+
+<P>Another kind of links exists in most Unix filesystems.
+Symbolic links are simply files which contain a filename. When
+the kernel encounters a symbolic link during a pathname to
+inode conversion, it replaces the name of the link by its
+contents, i.e. the name of the target file, and restarts the
+pathname interpretation. Since a symbolic link does not point
+to an inode, it is possible to create cross-filesystems
+symbolic links. Symbolic links can point to any type of file,
+even on nonexistent files. Symbolic links are very useful
+because they don't have the limitations associated to hard
+links. However, they use some disk space, allocated for their
+inode and their data blocks, and cause an overhead in the
+pathname to inode conversion because the kernel has to restart
+the name interpretation when it encounters a symbolic link.
+
+<H4>Device special files</H4>
+
+<P>In Unix-like operating systems, devices can be accessed via
+special files. A device special file does not use any space on
+the filesystem. It is only an access point to the device
+driver.
+
+<P>Two types of special files exist: character and block
+special files. The former allows I/O operations in character
+mode while the later requires data to be written in block mode
+via the buffer cache functions. When an I/O request is made on
+a special file, it is forwarded to a (pseudo) device driver. A
+special file is referenced by a major number, which identifies
+the device type, and a minor number, which identifies the unit.
+
+<A name="section:vfs">
+<H3>The Virtual File System</H3>
+</A>
+
+<H4>Principle</H4>
+
+<P>The Linux kernel contains a Virtual File System layer which
+is used during system calls acting on files. The VFS is an
+indirection layer which handles the file oriented system calls
+and calls the necessary functions in the physical filesystem
+code to do the I/O.
+
+<P>This indirection mechanism is frequently used in Unix-like
+operating systems to ease the integration and the use of
+several filesystem types <A href="#vnodes">[Kleiman 1986,</A> 
+<A href="#lfs:unix">Seltzer <I>et al.</I> 1993]</A>.
+
+<P>When a process issues a file oriented system call, the
+kernel calls a function contained in the VFS. This function
+handles the structure independent manipulations and redirects
+the call to a function contained in the physical filesystem
+code, which is responsible for handling the structure dependent
+operations. Filesystem code uses the buffer cache functions to
+request I/O on devices. This scheme is illustrated in this
+figure:
+
+<IMG SRC="ext2-vfs.gif">
+
+<H4>The VFS structure</H4>
+
+<P>The VFS defines a set of functions that every filesystem has
+to implement. This interface is made up of a set of operations
+associated to three kinds of objects: filesystems, inodes, and
+open files.
+
+<P>The VFS knows about filesystem types supported in the
+kernel. It uses a table defined during the kernel
+configuration. Each entry in this table describes a filesystem
+type: it contains the name of the filesystem type and a pointer
+on a function called during the mount operation. When a
+filesystem is to be mounted, the appropriate mount function is
+called. This function is responsible for reading the superblock
+from the disk, initializing its internal variables, and
+returning a mounted filesystem descriptor to the VFS. After the
+filesystem is mounted, the VFS functions can use this
+descriptor to access the physical filesystem routines.
+
+<P>A mounted filesystem descriptor contains several kinds of
+data: informations that are common to every filesystem types,
+pointers to functions provided by the physical filesystem
+kernel code, and private data maintained by the physical
+filesystem code. The function pointers contained in the
+filesystem descriptors allow the VFS to access the filesystem
+internal routines.
+
+<P>Two other types of descriptors are used by the VFS: an inode descriptor
+and an open file descriptor. Each descriptor contains informations related to
+files in use and a set of operations provided by the physical filesystem code.
+While the inode descriptor contains pointers to functions that can be used to
+act on any file (e.g. <TT>create</TT>, <TT>unlink</TT>), the file descriptors
+contains pointer to functions which can only act on open files (e.g.
+<TT>read</TT>, <TT>write</TT>).
+
+<A name="section:ext2fs">
+<H3>The Second Extended File System</H3>
+</A>
+
+<H4>Motivations</H4>
+
+<P>The Second Extended File System has been designed and
+implemented to fix some problems present in the first Extended
+File System. Our goal was to provide a powerful filesystem,
+which implements Unix file semantics and offers advanced
+features.
+
+<P>Of course, we wanted to Ext2fs to have excellent
+performance.  We also wanted to provide a very robust
+filesystem in order to reduce the risk of data loss in
+intensive use. Last, but not least, Ext2fs had to include
+provision for extensions to allow users to benefit from new
+features without reformatting their filesystem.
+
+<H4>``Standard'' Ext2fs features</H4>
+
+<P>The Ext2fs supports standard Unix file types: regular files,
+directories, device special files and symbolic links.
+
+<P>Ext2fs is able to manage filesystems created on really big
+partitions. While the original kernel code restricted the
+maximal filesystem size to 2 GB, recent work in the VFS layer
+have raised this limit to 4 TB. Thus, it is now possible to use
+big disks without the need of creating many partitions.
+
+<P>Ext2fs provides long file names. It uses variable length
+directory entries. The maximal file name size is 255
+characters. This limit could be extended to 1012 if needed.
+
+<P>Ext2fs reserves some blocks for the super user
+(<TT>root</TT>). Normally, 5% of the blocks are reserved. This
+allows the administrator to recover easily from situations
+where user processes fill up filesystems.
+
+<A name="subsection:ext2fs:adv-feat">
+<H4>``Advanced'' Ext2fs features</H4>
+</A>
+
+<P>In addition to the standard Unix features, Ext2fs supports
+some extensions which are not usually present in Unix
+filesystems.
+
+<P>File attributes allow the users to modify the kernel
+behavior when acting on a set of files. One can set attributes
+on a file or on a directory. In the later case, new files
+created in the directory inherit these attributes.
+
+<P>BSD or System V Release 4 semantics can be selected at mount
+time. A mount option allows the administrator to choose the
+file creation semantics. On a filesystem mounted with BSD
+semantics, files are created with the same group id as their
+parent directory. System V semantics are a bit more complex: if
+a directory has the setgid bit set, new files inherit the group
+id of the directory and subdirectories inherit the group id and
+the setgid bit; in the other case, files and subdirectories are
+created with the primary group id of the calling process.
+
+<P>BSD-like synchronous updates can be used in Ext2fs. A mount
+option allows the administrator to request that metadata
+(inodes, bitmap blocks, indirect blocks and directory blocks)
+be written synchronously on the disk when they are modified.
+This can be useful to maintain a strict metadata consistency
+but this leads to poor performances. Actually, this feature is
+not normally used, since in addition to the performance loss
+associated with using synchronous updates of the metadata, it
+can cause corruption in the user data which will not be flagged
+by the filesystem checker.
+
+<P>Ext2fs allows the administrator to choose the logical block
+size when creating the filesystem. Block sizes can typically be
+1024, 2048 and 4096 bytes. Using big block sizes can speed up
+I/O since fewer I/O requests, and thus fewer disk head seeks,
+need to be done to access a file. On the other hand, big blocks
+waste more disk space: on the average, the last block allocated
+to a file is only half full, so as blocks get bigger, more
+space is wasted in the last block of each file. In addition,
+most of the advantages of larger block sizes are obtained by
+Ext2 filesystem's preallocation techniques (see section
+<A href="#subsection:ext2fs:allocation">Performance optimizations</A>).
+
+<P>Ext2fs implements fast symbolic links. A fast symbolic link
+does not use any data block on the filesystem. The target name
+is not stored in a data block but in the inode itself. This
+policy can save some disk space (no data block needs to be
+allocated) and speeds up link operations (there is no need to
+read a data block when accessing such a link). Of course, the
+space available in the inode is limited so not every link can
+be implemented as a fast symbolic link. The maximal size of the
+target name in a fast symbolic link is 60 characters. We plan
+to extend this scheme to small files in the near future.
+
+<P>Ext2fs keeps track of the filesystem state. A special field
+in the superblock is used by the kernel code to indicate the
+status of the file system. When a filesystem is mounted in
+read/write mode, its state is set to ``Not Clean''. When it is
+unmounted or remounted in read-only mode, its state is reset to
+``Clean''. At boot time, the filesystem checker uses this
+information to decide if a filesystem must be checked. The
+kernel code also records errors in this field. When an
+inconsistency is detected by the kernel code, the filesystem is
+marked as ``Erroneous''. The filesystem checker tests this to
+force the check of the filesystem regardless of its apparently
+clean state.
+
+<P>Always skipping filesystem checks may sometimes be
+dangerous, so Ext2fs provides two ways to force checks at
+regular intervals. A mount counter is maintained in the
+superblock. Each time the filesystem is mounted in read/write
+mode, this counter is incremented. When it reaches a maximal
+value (also recorded in the superblock), the filesystem checker
+forces the check even if the filesystem is ``Clean''. A last
+check time and a maximal check interval are also maintained in
+the superblock. These two fields allow the administrator to
+request periodical checks. When the maximal check interval has
+been reached, the checker ignores the filesystem state and
+forces a filesystem check.
+
+Ext2fs offers tools to tune the filesystem behavior.
+The <TT>tune2fs</TT> program can be used to modify:
+<UL>
+<LI>the error behavior. When an inconsistency is detected by
+the kernel code, the filesystem is marked as ``Erroneous'' and
+one of the three following actions can be done: continue normal
+execution, remount the filesystem in read-only mode to avoid
+corrupting the filesystem, make the kernel panic and reboot to
+run the filesystem checker.
+<LI>the maximal mount count.
+<LI>the maximal check interval.
+<LI>the number of logical blocks reserved for the super user.
+</UL>
+
+<P>Mount options can also be used to change the kernel error behavior.
+
+<P>An attribute allows the users to request secure deletion on
+files. When such a file is deleted, random data is written in
+the disk blocks previously allocated to the file. This prevents
+malicious people from gaining access to the previous content of
+the file by using a disk editor.
+
+<P>Last, new types of files inspired from the 4.4 BSD
+filesystem have recently been added to Ext2fs. Immutable files
+can only be read: nobody can write or delete them. This can be
+used to protect sensitive configuration files. Append-only
+files can be opened in write mode but data is always appended
+at the end of the file. Like immutable files, they cannot be
+deleted or renamed. This is especially useful for log files
+which can only grow.
+
+<H4>Physical Structure</H4>
+
+<P>The physical structure of Ext2 filesystems has been strongly
+influenced by the layout of the BSD filesystem
+<A href="#mckusick:ffs">[McKusick <I>et al.</I> 1984]</A>. A
+filesystem is made up of block groups. Block groups are
+analogous to BSD FFS's cylinder groups. However, block groups
+are not tied to the physical layout of the blocks on the disk,
+since modern drives tend to be optimized for sequential access
+and hide their physical geometry to the operating system.
+
+<P>The physical structure of a filesystem is represented in this
+table:
+<TABLE border>
+<TR>
+<TD>Boot<BR>Sector</TD>
+<TD>Block<BR>Group 1</TD>
+<TD>Block<BR>Group 2</TD>
+<TD>...<BR>...</TD>
+<TD>Block<BR>Group N</TD>
+</TR>
+</TABLE>
+
+<P>Each block group contains a redundant copy of crucial filesystem
+control informations (superblock and the filesystem descriptors) and
+also contains a part of the filesystem (a block bitmap, an inode
+bitmap, a piece of the inode table, and data blocks). The structure of
+a block group is represented in this table:
+<TABLE border>
+<TR>
+<TD>Super<BR>Block</TD>
+<TD>FS<BR>descriptors</TD>
+<TD>Block<BR>Bitmap</TD>
+<TD>Inode<BR>Bitmap</TD>
+<TD>Inode<BR>Table</TD>
+<TD>Data<BR>Blocks</TD>
+</TR>
+</TABLE>
+
+<P>Using block groups is a big win in terms of reliability:
+since the control structures are replicated in each block
+group, it is easy to recover from a filesystem where the
+superblock has been corrupted. This structure also helps to get
+good performances: by reducing the distance between the inode
+table and the data blocks, it is possible to reduce the disk
+head seeks during I/O on files.
+
+<P>In Ext2fs, directories are managed as linked lists of
+variable length entries. Each entry contains the inode number,
+the entry length, the file name and its length. By using
+variable length entries, it is possible to implement long file
+names without wasting disk space in directories. The structure
+of a directory entry is shown in this table:
+<TABLE border>
+<TR>
+<TD>inode number</TD><TD>entry length</TD>
+<TD>name length</TD><TD>filename</TD>
+</TR>
+</TABLE>
+
+<P>As an example, The next table represents the structure of a
+directory containing three files: <TT>file1</TT>,
+<TT>long_file_name</TT>, and <TT>f2</TT>:
+<TABLE border>
+<TR><TD>i1</TD><TD>16</TD><TD>05</TD><TD><TT>file1 </TT></TD></TR>
+</TABLE>
+<TABLE border>
+<TR><TD>i2</TD><TD>40</TD><TD>14</TD><TD><TT>long_file_name </TT></TD></TR>
+</TABLE>
+<TABLE border>
+<TR><TD>i3</TD><TD>12</TD><TD>02</TD><TD><TT>f2 </TT></TD></TR>
+</TABLE>
+
+<A name="subsection:ext2fs:allocation">
+<H4>Performance optimizations</H4>
+</A>
+
+<P>The Ext2fs kernel code contains many performance
+optimizations, which tend to improve I/O speed when reading and
+writing files.
+
+<P>Ext2fs takes advantage of the buffer cache management by
+performing readaheads: when a block has to be read, the kernel
+code requests the I/O on several contiguous blocks. This way,
+it tries to ensure that the next block to read will already be
+loaded into the buffer cache. Readaheads are normally performed
+during sequential reads on files and Ext2fs extends them to
+directory reads, either explicit reads (<TT>readdir(2)</TT>
+calls) or implicit ones (<TT>namei</TT> kernel directory
+lookup).
+
+<P>Ext2fs also contains many allocation optimizations. Block
+groups are used to cluster together related inodes and data:
+the kernel code always tries to allocate data blocks for a file
+in the same group as its inode. This is intended to reduce the
+disk head seeks made when the kernel reads an inode and its
+data blocks.
+
+<P>When writing data to a file, Ext2fs preallocates up to 8
+adjacent blocks when allocating a new block. Preallocation hit
+rates are around 75% even on very full filesystems. This
+preallocation achieves good write performances under heavy
+load. It also allows contiguous blocks to be allocated to
+files, thus it speeds up the future sequential reads.
+
+<P>These two allocation optimizations produce a very good locality of:
+<UL>
+<LI>related files through block groups
+<LI>related blocks through the 8 bits clustering of block allocations.
+</UL>
+
+<H3>The Ext2fs library</H3>
+
+<P>To allow user mode programs to manipulate the control
+structures of an Ext2 filesystem, the libext2fs library was
+developed.  This library provides routines which can be used to
+examine and modify the data of an Ext2 filesystem, by accessing
+the filesystem directly through the physical device.
+
+<P>The Ext2fs library was designed to allow maximal code reuse
+through the use of software abstraction techniques.  For
+example, several different iterators are provided.  A program
+can simply pass in a function to
+<TT>ext2fs_block_interate()</TT>, which will be called for each
+block in an inode.  Another iterator function allows an
+user-provided function to be called for each file in a
+directory.
+
+<P>Many of the Ext2fs utilities (<TT>mke2fs</TT>,
+<TT>e2fsck</TT>, <TT>tune2fs</TT>, <TT>dumpe2fs</TT>, and
+<TT>debugfs</TT>) use the Ext2fs library.  This greatly
+simplifies the maintainance of these utilities, since any
+changes to reflect new features in the Ext2 filesystem format
+need only be made in one place--in the Ext2fs library.  This
+code reuse also results in smaller binaries, since the Ext2fs
+library can be built as a shared library image.
+
+<P>Because the interfaces of the Ext2fs library are so abstract
+and general, new programs which require direct access to the
+Ext2fs filesystem can very easily be written. For example, the
+Ext2fs library was used during the port of the 4.4BSD dump and
+restore backup utilities. Very few changes were needed to adapt
+these tools to Linux: only a few filesystem dependent functions
+had to be replaced by calls to the Ext2fs library.
+
+<P>The Ext2fs library provides access to several classes of
+operations.  The first class are the filesystem-oriented
+operations.  A program can open and close a filesystem, read
+and write the bitmaps, and create a new filesystem on the disk.
+Functions are also available to manipulate the filesystem's bad
+blocks list.
+
+<P>The second class of operations affect directories.  A caller
+of the Ext2fs library can create and expand directories, as
+well as add and remove directory entries.  Functions are also
+provided to both resolve a pathname to an inode number, and to
+determine a pathname of an inode given its inode number.
+
+<P>The final class of operations are oriented around inodes.
+It is possible to scan the inode table, read and write inodes,
+and scan through all of the blocks in an inode.  Allocation and
+deallocation routines are also available and allow user mode
+programs to allocate and free blocks and inodes.
+
+<H3>The Ext2fs tools</H3>
+
+<P>Powerful management tools have been developed for Ext2fs.
+These utilities are used to create, modify, and correct any
+inconsistencies in Ext2 filesystems.  The <TT>mke2fs</TT>
+program is used to initialize a partition to contain an empty
+Ext2 filesystem.
+
+<P>The <TT>tune2fs</TT> program can be used to modify the filesystem
+parameters. As explained in section <A href="#subsection:ext2fs:adv-feat">
+``Advanced'' Ext2fs features</A>, it can change the error
+behavior, the maximal mount count, the maximal check interval,
+and the number of logical blocks reserved for the super user.
+
+<P>The most interesting tool is probably the filesystem
+checker.  <TT>E2fsck</TT> is intended to repair filesystem
+inconsistencies after an unclean shutdown of the system.  The
+original version of <TT>e2fsck</TT> was based on Linus
+Torvald's fsck program for the Minix filesystem.  However, the
+current version of <TT>e2fsck</TT> was rewritten from scratch,
+using the Ext2fs library, and is much faster and can correct
+more filesystem inconsistencies than the original version.
+
+<P>The <TT>e2fsck</TT> program is designed to run as quickly as
+possible.  Since filesystem checkers tend to be disk bound,
+this was done by optimizing the algorithms used by
+<TT>e2fsck</TT> so that filesystem structures are not
+repeatedly accessed from the disk.  In addition, the order in
+which inodes and directories are checked are sorted by block
+number to reduce the amount of time in disk seeks.  Many of
+these ideas were originally explored by
+<A href="#bsd:fsck">[Bina and Emrath 1989]</A> although they have
+since been further refined by the authors.
+
+<P>In pass 1, <TT>e2fsck</TT> iterates over all of the inodes
+in the filesystem and performs checks over each inode as an
+unconnected object in the filesystem.  That is, these checks do
+not require any cross-checks to other filesystem objects.
+Examples of such checks include making sure the file mode is
+legal, and that all of the blocks in the inode are valid block
+numbers.  During pass 1, bitmaps indicating which blocks and
+inodes are in use are compiled.
+
+<P>If <TT>e2fsck</TT> notices data blocks which are claimed by
+more than one inode, it invokes passes 1B through 1D to resolve
+these conflicts, either by cloning the shared blocks so that
+each inode has its own copy of the shared block, or by
+deallocating one or more of the inodes.
+
+<P>Pass 1 takes the longest time to execute, since all of the
+inodes have to be read into memory and checked.  To reduce the
+I/O time necessary in future passes, critical filesystem
+information is cached in memory.  The most important example of
+this technique is the location on disk of all of the directory
+blocks on the filesystem.  This obviates the need to re-read
+the directory inodes structures during pass 2 to obtain this
+information.
+
+<P>Pass 2 checks directories as unconnected objects.  Since
+directory entries do not span disk blocks, each directory block
+can be checked individually without reference to other
+directory blocks.  This allows <TT>e2fsck</TT> to sort all of
+the directory blocks by block number, and check directory
+blocks in ascending order, thus decreasing disk seek time. The
+directory blocks are checked to make sure that the directory
+entries are valid, and contain references to inode numbers
+which are in use (as determined by pass 1).
+
+<P>For the first directory block in each directory inode, the
+`.' and `..' entries are checked to make sure they exist, and
+that the inode number for the `.' entry matches the current
+directory.  (The inode number for the `..' entry is not checked
+until pass 3.)
+
+<P>Pass 2 also caches information concerning the parent
+directory in which each directory is linked.  (If a directory
+is referenced by more than one directory, the second reference
+of the directory is treated as an illegal hard link, and it is
+removed).
+
+<P>It is noteworthy to note that at the end of pass 2, nearly
+all of the disk I/O which <TT>e2fsck</TT> needs to perform is
+complete.  Information required by passes 3, 4 and 5 are cached
+in memory; hence, the remaining passes of <TT>e2fsck</TT> are
+largely CPU bound, and take less than 5-10% of the total
+running time of <TT>e2fsck</TT>.
+
+<P>In pass 3, the directory connectivity is checked.
+<TT>E2fsck</TT> traces the path of each directory back to the
+root, using information that was cached during pass 2.  At this
+time, the `..' entry for each directory is also checked to make
+sure it is valid.  Any directories which can not be traced back
+to the root are linked to the <TT>/lost+found</TT> directory.
+
+<P>In pass 4, <TT>e2fsck</TT> checks the reference counts for
+all inodes, by iterating over all the inodes and comparing the
+link counts (which were cached in pass 1) against internal
+counters computed during passes 2 and 3.  Any undeleted files
+with a zero link count is also linked to the
+<TT>/lost+found</TT> directory during this pass.
+
+<P>Finally, in pass 5, <TT>e2fsck</TT> checks the validity of
+the filesystem summary information.  It compares the block and
+inode bitmaps which were constructed during the previous passes
+against the actual bitmaps on the filesystem, and corrects the
+on-disk copies if necessary.
+
+<P>The filesystem debugger is another useful tool.
+<TT>Debugfs</TT> is a powerful program which can be used to
+examine and change the state of a filesystem. Basically, it
+provides an interactive interface to the Ext2fs library:
+commands typed by the user are translated into calls to the
+library routines.
+
+<P><TT>Debugfs</TT> can be used to examine the internal
+structures of a filesystem, manually repair a corrupted
+filesystem, or create test cases for <TT>e2fsck</TT>.
+Unfortunately, this program can be dangerous if it is used by
+people who do not know what they are doing; it is very easy to
+destroy a filesystem with this tool.  For this reason,
+<TT>debugfs</TT> opens filesytems for read-only access by
+default.  The user must explicitly specify the <TT>-w</TT> flag
+in order to use <TT>debugfs</TT> to open a filesystem for
+read/wite access.
+
+<H3>Performance Measurements</H3>
+
+<H4>Description of the benchmarks</H4>
+
+<P>We have run benchmarks to measure filesystem performances.
+Benchmarks have been made on a middle-end PC, based on a
+i486DX2 processor, using 16 MB of memory and two 420 MB IDE
+disks. The tests were run on Ext2 fs and Xia fs (Linux 1.1.62)
+and on the BSD Fast filesystem in asynchronous and synchronous
+mode (FreeBSD 2.0 Alpha--based on the 4.4BSD Lite
+distribution).
+
+<P>We have run two different benchmarks. The Bonnie benchmark
+tests I/O speed on a big file--the file size was set to 60 MB
+during the tests. It writes data to the file using character
+based I/O, rewrites the contents of the whole file, writes data
+using block based I/O, reads the file using character I/O and
+block I/O, and seeks into the file. The Andrew Benchmark was
+developed at Carneggie Mellon University and has been used at
+the University of Berkeley to benchmark BSD FFS and LFS. It
+runs in five phases: it creates a directory hierarchy, makes a
+copy of the data, recursively examine the status of every file,
+examine every byte of every file, and compile several of the
+files.
+
+<H4>Results of the Bonnie benchmark</H4>
+
+<P>The results of the Bonnie benchmark are presented in this
+table:
+<TABLE border>
+<TR><TH></TH><TH>Char Write<BR>(KB/s)</TH>
+<TH>Block Write<BR>(KB/s)</TH>
+<TH>Rewrite<BR>(KB/s)</TH>
+<TH>Char Read<BR>(KB/s)</TH>
+<TH>Block Read<BR>(KB/s)</TH></TR>
+<TR><TD>BSD Async</TD><TD align="right">710</TD><TD align="right">684</TD><TD align="right">401</TD><TD align="right">721</TD><TD align="right">888</TD></TR>
+<TR><TD>BSD Sync</TD><TD align="right">699</TD><TD align="right">677</TD><TD align="right">400</TD><TD align="right">710</TD><TD align="right">878</TD></TR>
+<TR><TD>Ext2 fs</TD><TD align="right">452</TD><TD align="right">1237</TD><TD align="right">536</TD><TD align="right">397</TD><TD align="right">1033</TD></TR>
+<TR><TD>Xia fs</TD><TD align="right">440</TD><TD align="right">704</TD><TD align="right">380</TD><TD align="right">366</TD><TD align="right">895</TD></TR>
+</TABLE>
+
+<P>The results are very good in block oriented I/O: Ext2 fs
+outperforms other filesystems. This is clearly a benefit of the
+optimizations included in the allocation routines. Writes are
+fast because data is written in cluster mode. Reads are fast
+because contiguous blocks have been allocated to the file. Thus
+there is no head seek between two reads and the readahead
+optimizations can be fully used.
+
+<P>On the other hand, performance is better in the FreeBSD
+operating system in character oriented I/O. This is probably
+due to the fact that FreeBSD and Linux do not use the same
+stdio routines in their respective C libraries. It seems that
+FreeBSD has a more optimized character I/O library and its
+performance is better.
+
+<H4>Results of the Andrew benchmark</H4>
+
+The results of the Andrew benchmark are presented in
+this table:
+<TABLE border>
+<TR>
+<TH></TH>
+<TH>P1 Create<BR>(ms)</TH>
+<TH>P2 Copy<BR>(ms)</TH>
+<TH>P3 Stat<BR>(ms)</TH>
+<TH>P4 Grep<BR>(ms)</TH>
+<TH>P5 Compile<BR>(ms)</TH>
+</TR>
+<TR><TD>BSD Async</TD><TD align="right">2203</TD><TD align="right">7391</TD><TD align="right">6319</TD><TD align="right">17466</TD><TD align="right">75314</TD></TR>
+<TR><TD>BSD Sync</TD><TD align="right">2330</TD><TD align="right">7732</TD><TD align="right">6317</TD><TD align="right">17499</TD><TD align="right">75681</TD></TR>
+<TR><TD>Ext2 fs</TD><TD align="right">790</TD><TD align="right">4791</TD><TD align="right">7235</TD><TD align="right">11685</TD><TD align="right">63210</TD></TR>
+<TR><TD>Xia fs</TD><TD align="right">934</TD><TD align="right">5402</TD><TD align="right">8400</TD><TD align="right">12912</TD><TD align="right">66997</TD></TR>
+</TABLE>
+
+<P>The results of the two first passes show that Linux benefits
+from its asynchronous metadata I/O. In passes 1 and 2,
+directories and files are created and BSD synchronously writes
+inodes and directory entries. There is an anomaly, though: even
+in asynchronous mode, the performance under BSD is poor. We
+suspect that the asynchronous support under FreeBSD is not
+fully implemented.
+
+<P>In pass 3, the Linux and BSD times are very similar. This is
+a big progress against the same benchmark run six months ago.
+While BSD used to outperform Linux by a factor of 3 in this
+test, the addition of a file name cache in the VFS has fixed
+this performance problem.
+
+<P>In passes 4 and 5, Linux is faster than FreeBSD mainly
+because it uses an unified buffer cache management. The buffer
+cache space can grow when needed and use more memory than the
+one in FreeBSD, which uses a fixed size buffer cache.
+Comparison of the Ext2fs and Xiafs results shows that the
+optimizations included in Ext2fs are really useful: the
+performance gain between Ext2fs and Xiafs is around 5-10%.
+
+<H3>Conclusion</H3>
+
+<P>The Second Extended File System is probably the most widely
+used filesystem in the Linux community. It provides standard
+Unix file semantics and advanced features. Moreover, thanks to
+the optimizations included in the kernel code, it is robust and
+offers excellent performance.
+
+<P>Since Ext2fs has been designed with evolution in mind, it
+contains hooks that can be used to add new features. Some
+people are working on extensions to the current filesystem:
+access control lists conforming to the Posix semantics
+<A href="#posix6">[IEEE 1992]</A>, undelete, and on-the-fly
+file compression.
+
+<P>Ext2fs was first developed and integrated in the Linux
+kernel and is now actively being ported to other operating
+systems. An Ext2fs server running on top of the GNU Hurd has
+been implemented. People are also working on an Ext2fs port in
+the LITES server, running on top of the Mach microkernel
+<A href="#mach:foundation">[Accetta <I>et al.</I> 1986]</A>, and
+in the VSTa operating system. Last, but not least, Ext2fs is an
+important part of the Masix operating system
+<A href="#masix:osf">[Card <I>et al.</I> 1993]</A>,
+currently under development by one of the authors.
+
+<H3>Acknowledgments</H3>
+
+<P>The Ext2fs kernel code and tools have been written mostly by
+the authors of this paper. Some other people have also
+contributed to the development of Ext2fs either by suggesting
+new features or by sending patches. We want to thank these
+contributors for their help.
+
+<H3>References</H3>
+
+<P><A name="mach:foundation">[Accetta <I>et al.</I> 1986]</A>
+M. Accetta, R. Baron, W. Bolosky, D. Golub, R. Rashid, A. Tevanian, and
+M. Young.
+Mach: A New Kernel Foundation For UNIX Development.
+In <I>Proceedings of the USENIX 1986 Summer Conference</I>, June 1986.
+
+<P><A name="bach">[Bach 1986]</A>
+M. Bach.
+<I>The Design of the UNIX Operating System</I>.
+Prentice Hall, 1986.
+
+<P><A name="bsd:fsck">[Bina and Emrath 1989]</A>
+E. Bina and P. Emrath.
+A Faster fsck for BSD Unix.
+In <I>Proceedings of the USENIX Winter Conference</I>, January 1989.
+
+<P><A name="masix:osf">[Card <I>et al.</I> 1993]</A>
+R. Card, E. Commelin, S. Dayras, and F. M�vel.
+The MASIX Multi-Server Operating System.
+In <I>OSF Workshop on Microkernel Technology for Distributed Systems</I>,
+June 1993.
+
+<P><A name="posix6">[IEEE 1992]</A>
+<I>SECURITY INTERFACE for the Portable Operating System Interface for
+Computer Environments - Draft 13</I>.
+Institute of Electrical and Electronics Engineers, Inc, 1992.
+
+<P><A name="vnodes">[Kleiman 1986]</A>
+S. Kleiman.
+Vnodes: An Architecture for Multiple File System Types
+in Sun UNIX.
+In <I>Proceedings of the Summer USENIX Conference</I>, pages 260--269,
+June 1986.
+
+<P><A name="mckusick:ffs">[McKusick <I>et al.</I> 1984]</A>
+M. McKusick, W. Joy, S. Leffler, and R. Fabry.
+A Fast File System for UNIX.
+<I>ACM Transactions on Computer Systems</I>, 2(3):181--197, August
+1984.
+
+<P><A name="lfs:unix">[Seltzer <I>et al.</I> 1993]</A>
+M. Seltzer, K. Bostic, M. McKusick, and C. Staelin.
+An Implementation of a Log-Structured File System for
+UNIX.
+In <I>Proceedings of the USENIX Winter Conference</I>, January 1993.
+
+<P><A name="minix">[Tanenbaum 1987]</A>
+A. Tanenbaum.
+<I>Operating Systems: Design and Implementation</I>.
+Prentice Hall, 1987.
+<P>
+
+<HR>
+
+<P>Thanks to Michael Johnson for HTMLizing it (originally for use in
+the <A HREF="http://khg.redhat.com/HyperNews/get/fs/fs.html"> Kernel
+Hacker's Guide</A>).</P>
+
+</BODY>
+</HTML>
diff --git a/htdocs/extensions-ext23/extensions-ext23.pdf b/htdocs/extensions-ext23/extensions-ext23.pdf
new file mode 100644
index 000000000..6b9effe29
--- /dev/null
+++ b/htdocs/extensions-ext23/extensions-ext23.pdf
diff --git a/htdocs/extensions-ext23/img1.png b/htdocs/extensions-ext23/img1.png
new file mode 100644
index 000000000..058f9a2f3
--- /dev/null
+++ b/htdocs/extensions-ext23/img1.png
diff --git a/htdocs/extensions-ext23/img2.png b/htdocs/extensions-ext23/img2.png
new file mode 100644
index 000000000..df68b4d7c
--- /dev/null
+++ b/htdocs/extensions-ext23/img2.png
diff --git a/htdocs/extensions-ext23/index.html b/htdocs/extensions-ext23/index.html
new file mode 100644
index 000000000..988d5dd20
--- /dev/null
+++ b/htdocs/extensions-ext23/index.html
@@ -0,0 +1,1051 @@
+<HTML>
+<HEAD>
+<TITLE>FREENIX Track: USENIX 2002 Annual Technical Conference - Paper</TITLE>
+<META NAME="description" CONTENT="Porting NetBSD to the AMD x86-641: a case study in OS portability">
+<META NAME="keywords" CONTENT="x86-64">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META NAME="Generator" CONTENT="LaTeX2HTML v99.2beta8">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<!-- <LINK REL="STYLESHEET" HREF="x86-64.css"> -->
+
+</HEAD>
+<!-- IE understands topmargin, leftmargin, rightmargin, NS understands marginheight -->
+<BODY BGCOLOR="#ffffff" TEXT="#000000"  link="#990000" alink="#666666" vlink="#666666" TOPMARGIN="0" LEFTMARGIN="0" RIGHTMARGIN="0" MARGINHEIGHT="0">
+
+
+<table width=100% border=0 cellspacing=0 cellpadding=8><tr><td>
+
+
+<FONT SIZE="+1" COLOR="#990000" FACE="verdana, arial, helvetica, sans-serif"><B>USENIX 2002 Annual Technical Conference, Freenix Track -  Paper</B></FONT>&nbsp&nbsp&nbsp
+<FONT SIZE="-1" FACE="verdana, arial, helvetica, sans-serif">[<a href="http://www.usenix.org/publications/library/proceedings/usenix02/tech/freenix.html">USENIX 2002 Technical Program Index</a>]</FONT>
+<P>
+
+<table>
+<tr><td><b>Pp. 235&#150;244 of the <i>Proceedings</i></b></td></tr>
+<TR><TD><A HREF="extensions-ext23.pdf"><B>PDF Version</B></A></td></tr>
+</table>
+<!-- START OF PAGE CONTENTS -->
+
+
+<H1 ALIGN="CENTER"><FONT SIZE="+2"><B>Planned Extensions to the Linux Ext2/Ext3 Filesystem</B></FONT></H1>
+<P ALIGN="CENTER"><STRONG>Theodore Y. Ts'o 
+<BR><EM>International Business Machines Corporation</EM> 
+<BR> tytso@mit.edu, http://www.thunk.org/tytso 
+<BR>
+<P></P>
+Stephen Tweedie 
+<BR><EM>Red Hat </EM>
+<BR> sct@redhat.com
+</STRONG></P>
+
+<P>
+
+<P>
+
+<H2><A NAME="SECTION00001000000000000000">
+Abstract</A>
+</H2>
+
+<P>
+The ext2 filesystem was designed with the goal of expandability while
+maintaining compatibility.  This paper describes ways in which advanced
+filesystem features can be added to the ext2 filesystem while retaining
+forwards and backwards compatibility as much as possible.  Some of the
+filesystem extensions that are discussed include directory indexing,
+online resizing, an expanded inode, extended attributes and access
+control lists support, extensible inode tables, extent maps, and
+preallocation.
+
+<P>
+
+<H1><A NAME="SECTION00010000000000000000">
+Introduction</A>
+</H1>
+
+<P>
+Linux's second extended filesystem[<A
+ HREF="index.html#card:ext2">1</A>] (also known as ext2)
+was first introduced into the Linux kernel in January, 1993.  At the
+time, it was a significant improvement over the previous filesystems
+used in the 0.97 and earlier kernels, the Minix and the ``Extended'' or
+(ext) filesystem.  Fundamentally, the design of the ext2 filesystem is
+very similar to that of the BSD Fast Filesystem[<A
+ HREF="index.html#mckusick:ffs">2</A>].  
+
+<P>
+The ext2 filesystem is divided into <EM>block groups</EM> which are
+essentially identical to the FFS's cylinder group; each block group
+contains a copy of the superblock, allocation bitmaps, part of a fixed,
+statically allocated inode table, and data blocks which can be allocated
+for directories or files.  Like most classic Unix filesystems, ext2/3
+uses direct, indirect, double indirect, and triple indirection blocks to
+map logical block numbers to physical block numbers.  Ext2's directory
+format is also essentially identical to traditional Unix filesystems in
+that a simple linked list data structure is used to store directory
+entries.
+
+<P>
+Over the years, various improvements have been added to the ext2
+filesystem.  This has been facilitated by a number of superblock fields
+that were added to the ext2 filesystem just before Linux 2.0 was
+released.  The most important of these fields, the compatibility
+bitmaps, enable new features to be added to the filesystem safely.
+There are three such compatibility bitmaps: read-write, read-only, and
+incompat.  A kernel will mount a filesystem that has a bit in the
+read-write compatibility bitmask that it doesn't understand.  However,
+an unknown bit in the read-only compatibility bitmap cause the kernel to
+only be willing to mount the filesystem read-only, and the kernel will
+refuse to mount in any way a filesystem with an unknown bit in the
+incompat bitmask.  These bitmaps have allowed the ext2 filesystem to
+evolve in very clean fashion.
+
+<P>
+Today, more developers than ever have expressed interest in working on
+the ext2/3 filesystem, and have wanted to add or integrate various new
+exciting features.  Some of these features include: preallocation,
+journaling, extended attributes and access control lists, on-line
+resizing, tail-merging, and compression.  Some of these features have
+yet to be merged into the mainline ext2 code base, or are only available
+in prototype form.  In the case of the journaling support, although
+filesystems with journaling support are fully backwards compatible with
+non-journalled ext2 filesystems, the implementation required enough
+changes that the resulting filesystem has been named <EM>ext3</EM>. 
+
+<P>
+The goal of this paper is to discuss how these features might be added
+to the filesystem in a coordinated fashion.  Many of these new features
+are expected of modern filesystems; the challenge is to add them while
+maintaining ext2/3's advantages of a relatively small and simple code
+base, robustness in the face of I/O errors, and high levels of forwards
+and backwards compatibility.
+
+<P>
+
+<H1><A NAME="SECTION00020000000000000000">
+Proposed enhancements to the ext2 filesystem format</A>
+</H1>
+
+<P>
+We will discuss a number of extensions to the ext2/3 filesystem which
+will likely be implemented in the near future.  For the most part, these
+extensions are independent of each other, and can be implemented in any
+order, although some extensions have synergistic effects.  For example,
+two new features that will be described below, extent maps and
+persistent preallocation, are far more effective when used in
+combination with each other.
+
+<P>
+
+<H2><A NAME="SECTION00021000000000000000">
+Directory indexing</A>
+</H2>
+
+<P>
+Daniel Phillips has implemented a directory indexing scheme
+using a fixed-depth tree with hashed keys[<A
+ HREF="index.html#phillips:dirindex">3</A>].  This
+replaces the linear directory search algorithm currently in use with
+traditional ext2 filesystems, and significantly improves performance for
+very large directories (thousands of files in a single directory).
+
+<P>
+The interior, or index, nodes in the tree are formatted to look like
+deleted directory entries, and the leaf nodes use the same format as
+existing ext2 directory blocks.  As a result, read-only backwards
+compatibility is trivially achieved.  Furthermore, starting in the Linux
+2.2 kernel, whenever a directory is modified, the <TT>EXT2_BTREE_FL</TT>
+(since renamed <TT>EXT2_INDEX_FL</TT>) is cleared.  This allows us to
+guarantee read/write compatibility with Linux 2.2 kernels, since the
+filesystem can detect that the internal indexing nodes are probably no
+longer consistent, and thus should be ignored until they can be
+reconstructed (via the <TT>e2fsck</TT> program).
+
+<P>
+Daniel Phillip's directory indexing code is currently available as a set
+of patches versus the 2.4 ext2 code base.  As of this writing, the
+patches still need to be merged with the ext3 journaling code base.  In
+addition, there are plans to select a better hash function that has
+better distribution characteristics for filenames commonly found in
+workloads such as mail queue directories.  There are also plans to add
+hinting information in the interior nodes of the tree to indicate that a
+particular leaf node is nearly empty and that its contents could be
+merged with an adjacent leaf node.
+
+<P>
+
+<H2><A NAME="SECTION00022000000000000000">
+On-line filesystem resizing</A>
+</H2>
+
+<P>
+Andreas Dilger has implemented patches to the ext2 filesystem that
+support dynamically increasing the size of the filesystem while the
+filesystem is on-line.  Before logical volume managers (LVMs) became
+available for Linux, off-line resizing tools such as <TT>resize2fs</TT>,
+which required that the filesystem be unmounted and checked using <TT>e2fsck</TT> first, were sufficient for most users' needs.  However, with the
+advent of LVM systems that allow block devices to be dynamically grown,
+it is much more important filesystems to be able to grow and take
+advantage of new storage space which has been made available by the LVM
+subsystem without needing to unmount the filesystem first.  Indeed,
+administrators of enterprise-class systems take such capabilities for
+granted.  (Dynamically shrinking mounted filesystems is a much more
+difficult task, and most filesystems do not offer this functionality.
+For ext2/3 filesystems, filesystems can be shrunk using the off-line
+resizing tool <TT>resize2fs</TT>.)
+
+<P>
+A disadvantage of the current ext2 resizing patches is that they require
+that the filesystem be prepared before the filesystem can be resized
+on-line.  This preparation process, which must be done with the
+filesystem unmounted, finds the inodes using the blocks immediately
+following the block group descriptors, and relocates these blocks so
+they can be reserved for the resizing process.  These blocks must be
+reserved since the current layout of the ext2 superblock and block group
+descriptors require an additional block group descriptor block for each
+256MB, 2GB, or 16GB of disk space for filesystems with 1KB, 2KB, and 4KB
+blocksizes, respectively.  Although the requirement for an off-line
+preparation step is quite inconvenient, this scheme does have the
+advantage that the filesystem format remains unmodified, so it is fully
+compatible with kernels that do not support on-line resizing.  Still, if
+the system administrator knows in advance how much a filesystem may need
+to be grown, reserving blocks for use by the block group descriptors may
+be a workable solution.
+
+<P>
+Requiring advance preparation of the filesystem can be obviated if we
+are willing to let the filesystem become incompatible with older kernels
+after it has been extended.  Given that many 2.0 and 2.2 kernels do not
+support LVM devices (and so would be unable to read a filesystem stored
+on an LVM anyway), this may be acceptable.  The change in the filesystem
+format replaces the current scheme where the superblock is followed by a
+variable-length set of block group descriptors.  Instead, the
+superblock and a <EM>single</EM> block group descriptor block is placed at
+the beginning of the first, second, and last block groups in a <EM>meta-block group</EM>.  A meta-block group is a collection of block groups
+which can be described by a single block group descriptor block.  Since
+the size of the block group descriptor structure is 32 bytes, a
+meta-block group contains 32 block groups for filesystems with a 1KB
+block size, and 128 block groups for filesystems with a 4KB blocksize.
+Filesystems can either be created using this new block group descriptor
+layout, or existing filesystems can be resized on-line, and a new field
+in the superblock will indicate the first block group using this new
+layout.
+
+<P>
+This new scheme is much more efficient, while retaining enough
+redundancy in case of hardware failures.  Most importantly, it allows
+new block groups to be added to the filesystem without needing to change
+block group descriptors in the earlier parts of the disk.  Hence, it
+should be very simple to write an ext2/3 filesystem extension using this
+design that provides on-line resizing capabilities.
+
+<P>
+
+<H2><A NAME="SECTION00023000000000000000">
+An expanded inode</A>
+</H2>
+
+<P>
+The size of the on-disk inode in the ext2/3 filesystem has been 128
+bytes long during its entire lifetime.  Although we have been very
+careful about packing as much information as possible into the inode, we
+are finally getting to the point where there simply is not enough room
+for all of the extensions that people would like to add to the ext2/3
+filesystem.
+
+<P>
+Fortunately, just before the release of Linux 2.0, most of the work to
+allow for an expanded inode was added.  As part of the changes to
+version 1 of the ext2 superblock, the size of the inode in the
+filesystem was added as a parameter in the superblock.  The only
+restriction on the size of inode is that it must evenly divide the
+filesystem blocksize.  Unfortunately, some safety-checking code which
+aborted the filesystem from being mounted if the inode size was not 128
+bytes was never removed from the kernel.  Hence, in order to support
+larger inodes, a small patch will have to made to the 2.0, 2.2, and 2.4
+kernels.  Fortunately the change is simple enough that it should be
+relatively easy to get the change accepted into production kernels.
+
+<P>
+One of the most important features that requires additional space in the
+inode is the addition of sub-second resolution timestamps.  This is
+needed because given today's very fast computers, storing file
+modification times with only second granularity is not sufficient for
+programs like <TT>make</TT>.  (For example, if <TT>make</TT> can compile all
+of the object files for a library and create the library within a
+second, a subsequent <TT>make</TT> command will not be able to determine whether
+or not the library needs to be updated.)
+
+<P>
+Another limitation imposed by the current inode field sizes is the use
+of a 16&nbsp;bits for <EM>i_links_count</EM>, which limits the number of
+subdirectories that can be created in a single directory.  The actual
+limit of 32,000 is smaller than what is possible with an
+unsigned 16-bit field, but even if the kernel were changed to allow
+65,535 subdirectories, this would be too small for some
+users or applications.
+
+<P>
+In addition, extra inode space can also enable support 64-bit block numbers.
+Currently, using 4KB blocks, the largest filesystem that ext2 can support
+is 16TB.  Although this is larger than any commonly available
+individual disks, there certainly are RAID systems that export block
+devices which are larger than this size.
+
+<P>
+Yet another future application that may require additional storage
+inside the inode is support for <EM>mandatory access control</EM>
+[<A
+ HREF="index.html#tcsec">4</A>] (MAC) or audit labels.  The NSA SE (Security-Enhanced)
+Linux[<A
+ HREF="index.html#loscocco:selinux">5</A>] implementation requires a single 32-bit
+field for both purposes; other schemes may require two separate 32-bit
+fields to encode MAC and audit label.
+
+<P>
+In order to maximize backwards compatibility, the inode will be expanded
+without changing the layout of the first 128 bytes.  This allows for
+full backwards compatibility if the the new features in use are
+themselves backwards compatible -- for example, sub-second resolution
+timestamps.
+
+<P>
+Doubling the inode size from 128 bytes to 256 bytes gives us room for 32
+additional 32-bit fields, which is a lot of extra flexibility for new
+features.  However, the 32 new fields can be very quickly consumed by
+designers proposing filesystem extensions.  For example, adding support
+for 64-bit block pointers will consume almost half of the new fields.
+Hence, allocation of these new inode fields will have to be very
+carefully done.  New filesystem features which do not have general
+applicability, or which require a large amount of space, will likely
+<EM>not</EM> receive space in the inode; instead they will likely have to
+use Extend Attribute storage instead.
+
+<P>
+
+<H2><A NAME="SECTION00024000000000000000">
+Extended attributes, access control lists, and tail merging</A>
+</H2>
+
+<P>
+One of the more important new features found in modern filesystems is
+the ability to associate small amounts of custom metadata (commonly
+referred to as <EM>Extended Attributes</EM>) with files or directories.
+Some of the applications of Extended Attributes (EA) include Access
+Control Lists[<A
+ HREF="index.html#posix:secdraft">6</A>], MAC Security
+Labels[<A
+ HREF="index.html#posix:secdraft">6</A>], POSIX
+Capabilities[<A
+ HREF="index.html#posix:secdraft">6</A>], DMAPI/XDSM[<A
+ HREF="index.html#opengroup:xdsm">7</A>] (which
+is important for implementing Hierarchical Storage Management systems),
+and others.
+
+<P>
+Andreas Gruenbacher has implemented ext2 extensions which add support
+for Extended Attributes and Access Control Lists to ext2.  These
+patches, sometimes referred to as the <EM>Bestbits patches</EM>, since they
+are available at web site <TT>http://www.bestbits.at</TT>, have been
+relatively widely deployed, although they have not yet been merged into
+the main-line ext2/3 code base.
+
+<P>
+The <EM>Bestbits</EM> implementation uses a full disk block to store each
+set of extended attributes data.  If two or more inodes have an identical set
+of extended attributes, then they can share a single extended attribute
+block.  This characteristic makes the <EM>Bestbits</EM> implementation
+extremely efficient for Access Control Lists (ACLs), since very often
+a large number of inodes will use the same ACL.  For example, it is likely
+that inodes in a directory will share the same ACL.  The <EM>Bestbits</EM>
+implementation allows inodes with the same ACL to share a common data
+structure on disk.  This allows for a very efficient storage of ACLs, as
+well as providing an important performance boost, since caching shared
+ACLs is an effective way of speeding up access control checks, a 
+common filesystem operation.
+
+<P>
+Unfortunately, the Bestbits design is not very well suited for generic
+Extended Attributes, since the EA block can only be shared if all of the
+extended attributes are identical.  So if every inode has some
+inode-unique EA (for example, a digital signature), then each inode will
+need to have its own EA block, and the overhead for using EAs may be
+unacceptably high.
+
+<P>
+For this reason, it is likely that the mechanism for supporting ACLs may
+be different from the mechanisms used to support generic EAs.  The
+performance requirements and storage efficiencies of ACL sharing justify
+seriously considering this option, even if it would be more
+aesthetically pleasing, and simpler, to use a single EA storage
+mechanism for both ACLs and generic EAs.
+
+<P>
+There may be a few other filesystem extensions which require very fast
+access by the kernel; for example, mandatory access control (MAC) and
+audit labels, which need to be referenced every time an inode is
+manipulated or accessed.  In these cases, however, as mentioned in the
+previous section, the simplest solution is to reserve an extra field or
+two in the expanded ext2 inode for these applications.
+
+<P>
+One of more promising tactics for solving the EA storage problem is to
+combine it with Daniel Phillips's proposal of adding <EM>tail merging</EM>
+to the ext2 filesystem.  Tail merging is the practice of storing the
+data contained in partially filled blocks at the end of files (called
+tails) in a single shared block.  This shared block could also be used
+as a location of storing Extended Attributes.  In fact, tail-merging can
+be generalized so that a tail is simply a special Extended Attribute.
+
+<P>
+The topic of extended attributes is still a somewhat controversial area
+amongst the ext2 developers, for a number of reasons.  First, there are
+many different ways in which EAs could be stored.  Second, how EAs will
+be used is still somewhat unclear.  Realistically, they are not used
+very often today, primarily because of portability concerns; EAs are not
+specified by any of the common Unix specifications:
+POSIX.1[<A
+ HREF="index.html#posix1">8</A>], SUS[<A
+ HREF="index.html#opengroup:sus">9</A>], etc., are not supported
+by file archiving tools such as <TT>tar</TT> and <TT>zip</TT>, and they cannot
+be exported over NFS (though the new NFSv4 standard[<A
+ HREF="index.html#nfsv4">10</A>] does
+include EA support.)  Still, the best alternatives which seem to have
+been explored to date will probably keep the Bestbits approach
+exclusively for ACLs, and an approach where multiple inodes can utilize
+a single filesystem block to store tails and extended attributes.
+
+<P>
+However, progress is being made: the linux-2.5 kernel now includes a
+standard API for accessing ACLs, and the popular <I>Samba</I>
+file-serving application can already use that API, if it is present.
+
+<P>
+
+<H2><A NAME="SECTION00025000000000000000">
+Extensible inode table</A>
+</H2>
+
+<P>
+With the increase in size of the on-disk inode data structure, the
+overhead of the inode table naturally will be larger.  This is
+compounded by the general practice of significantly over-provisioning
+the number of inodes in most Unix filesystems, since in general the
+number of inodes cannot be increased after the filesystem is created.
+While experienced system administrators may change the number of inodes
+when creating filesystems, the vast majority of filesystems generally
+use the defaults provided by <TT>mke2fs</TT>.  If the filesystem can
+allocate new inodes dynamically, the overhead of the inode table can be
+reduced since there will no longer be a need to overallocate inodes.
+
+<P>
+Expanding the inode table might seem to be a simple and straightforward
+operation, but there are a number of constraints that complicate things.
+We cannot simply increase the parameter indicating the number of inodes
+per block group, since that would require renumbering all of the inodes
+in the filesystem, which in turn would require scanning and modifying
+all of the directory entries in the filesystem.
+
+<P>
+Also complicating matters is the fact that the inode number is currently
+used as part of the block and inode allocation algorithms.  An inode's
+number, when divided by the filesystem's <TT>inodes_per_block_group</TT>
+parameter, results in the block group where the inode is stored.  This
+is used as a hint when allocating blocks for that inode for better
+locality.  Simply numbering new inodes just beyond the last used inode
+number will destroy this property.  This presents problems especially if
+the filesystem may be dynamically resized, since growing the filesystem
+also grows the inode table, and the inode numbers used for the
+extensible inode table must not conflict with the inode numbers used
+when the filesystem is grown.
+
+<P>
+One potential solution would be to extend the inode number to be 64
+bits, and then encode the block group information explicitly into the
+high bits of the inode number.  This would necessarily involve an
+incompatible change to the directory entry format.  However, if we
+expand the block pointers to 64 bits to support petabyte-sized
+filesystems, we ultimately may wish to support more than <IMG
+ WIDTH="26" HEIGHT="16" ALIGN="BOTTOM" BORDER="0"
+ SRC="img1.png"
+ ALT="$2^{32}$"> inodes
+in a filesystem anyway.  Unfortunately, there are two major
+implementation problems with expanding the inode number which make
+pursuit of this approach unlikely.  First, the size of the inode number
+in <TT>struct stat</TT> is 32 bits on 32-bit platforms; hence, user space
+programs which depend on different inodes having unique inode numbers
+may have this assumption violated.  Secondly, the current ext2/3
+implementation relies on internal kernel routines which assume a 32-bit
+inode number.  In order to use a 64-bit inode number, these routines
+would have to be duplicated and modified to support 64-bit inode
+numbers.
+
+<P>
+Another potential solution to this problem is to utilize inode numbers
+starting from the end of the inode space (i.e., starting from <IMG
+ WIDTH="53" HEIGHT="33" ALIGN="MIDDLE" BORDER="0"
+ SRC="img2.png"
+ ALT="$2^{32}-1$">
+and working downwards) for dynamically-allocated inodes, and using an
+inode to allocate space for these extended inodes.  For the purposes of
+the block allocation algorithm, the extended inode's block group
+affiliation can be stored in a field in the inode.  However, the
+location of the extended inode in this scheme could no longer be
+determined by examining its inode number, so the location of the inode
+on disk would no longer be close to the data blocks of the inode.  This
+would result in a performance penalty for using extended inodes (since
+the location of the inode and the location of its data blocks would no
+longer necessarily be close together), but hopefully the penalty would
+not be too great.  Some initial experiments which grouped the inode
+tables of <EM>meta-block groups</EM> together showed a very small
+performance penalty, although some additional benchmarking is necessary.
+(A simple experiment would be to modify the block allocation algorithms
+to deliberately allocate blocks in a different block group from the
+inode, and to measure the performance degradation this change would
+cause.)
+
+<P>
+
+<H2><A NAME="SECTION00026000000000000000">
+Extent maps</A>
+</H2>
+
+<P>
+The ext2 filesystem uses direct, indirect, double indirect, and triple
+indirection blocks to map file offsets to on-disk blocks, like most
+classical Unix filesystems.  Unfortunately, the direct/indirect block
+scheme is inefficient for large files.  This can be easily demonstrated
+by deleting a very large file, and noting how long that operation can
+take.  Fortunately, ext2 block allocation algorithms tend to be very
+successful at avoiding fragmentation and in allocating contiguous data
+blocks for files.  For most Linux filesystems in production use today,
+the percentage of non-contiguous files reported by <TT>e2fsck</TT> is
+generally less than 10%.  This means that in general, over 90% of the
+files on an ext2 filesystem only require a single <EM>extent map</EM> to
+describe all of their data blocks.  The extent map would be encoded in a
+structure like this:
+
+<P>
+<PRE>
+    struct ext2_extent {
+            __u64   logical_block;
+            __u64   physical_block;
+            __u32   count;
+    };
+</PRE>
+
+<P>
+Using such a structure, it becomes possible to efficiently encode the
+information, ``Logical block 1024 (and following 3000 blocks) can be
+found starting at physical block 6536.''  The vast majority of files in
+a typical Linux system will only need a few extents to describe all of
+their logical to physical block mapping, and so most of the time, these
+extent maps could be stored in the inode's direct blocks.
+
+<P>
+However, extent maps do not work well in certain pathalogical cases,
+such as sparse files with random allocation patterns.  There are two
+ways that we can deal with these sorts of cases.  The traditional method
+is to store the extent maps in a B-tree or related data structure,
+indexed by the logical block number.  If we pursue this option, it will
+not be necessary to use the full balancing requirements of B-trees; we
+can use similar design choices to those made by the directory indexing
+design to significantly simplify a B-tree implementation: using a fixed
+depth tree, not rotating nodes during inserts, and not worrying about
+rebalancing the tree after operations (such as truncate) which remove
+objects from the tree.
+
+<P>
+There is however an even simpler way of implementing extents, which is
+to ignore the pathological case altogether.  Today, very few files are
+sparse; even most DBM/DB implementations avoid using sparse files.  In
+this simplification, files with one or two extents can store the extent
+information in the inode, using the fields that were previously reserved
+for the direct blocks in the inode.  For files with more extents than
+that, the inode will contain a pointer to a single extent-map block.
+(The single extent-map block can look like a single leaf belonging to an
+extent-map tree, so this approach could be later extended to support a
+full extent-map tree if this proves necessary.)  If the file contains
+more extent maps than can fit in the single extent-map block, then
+indirect, double-indirect, and triple-indirect blocks could be used to
+store the remainder of the block pointers.
+
+<P>
+This solution is appealing, since for the vast majority of files, a
+single extent map is more than sufficient, and there is no need to
+adding a lot of complexity for what is normally a very rare case.  The
+one potential problem with this simplified solution is that for very
+large files (over 25 gigabytes on a filesystem using a 4KB blocksize), a
+single extent map may not be enough space if filesystem metadata located
+at the beginning of each block group is separating contiguous chunks of
+disk space.  Furthermore, if the filesystem is badly fragmented, then
+the extent map may fill even more quickly, necessitating a fall back to
+the old direct/double indirect block allocation scheme.  So if this
+simplification is adopted, preallocation becomes much more important to
+ensure that these large block allocations happen contiguously, not just
+for performance reasons, but to avoid overflowing the space in a single
+extent map block.
+
+<P>
+We can solve the first problem of metadata (inode tables, block and
+inode bitmaps) located at the beginning of each block group breaking up
+contiguous allocations by solved by moving all the metadata out of the
+way.  We have tried implementing this scheme by moving the inode tables
+and allocation bitmaps to the beginning of a <EM>meta-block group</EM>.
+The performance penalty of moving the inode table slightly farther away
+from the data blocks related to it was negligible.  Indeed, for some
+workloads, performance was actually slightly improved by grouping the
+metadata together.  Making this change does not require a format change
+to the filesystem, but merely a change in the allocation algorithms used
+by the <TT>mke2fs</TT> program.  However, the kernel does have some
+sanity-checking code that needs to be removed so that the kernel would
+not reject the mount.  A very simple patch to weaken the checks in <TT>ext3_check_descriptors()</TT> was written for the 2.4 kernel.  Patches to
+disable this sanity check, as well as the inode size limitation, will be
+available for all commonly used Linux kernel branches at <TT>http://e2fsprogs.sourceforge.net/ext2.html</TT>.
+
+<P>
+
+<H2><A NAME="SECTION00027000000000000000">
+Preallocation for contiguous files</A>
+</H2>
+
+<P>
+For multimedia files, where performance is important, it is very useful
+to be able to ask the system to allocate the blocks in advance,
+preferably contiguously if possible.  When the blocks are allocated, it
+is desirable if they do not need to be zeroed in advanced, since for a
+4GB file (to hold a DVD image, for example), zeroing 4GB worth of
+pre-allocated blocks would take a long time.
+
+<P>
+Ext2 had support for a limited amount of preallocation (usually only a
+handful of blocks, and the preallocated blocks were released when the
+file was closed).  Ext3 currently has no preallocation support at all;
+the feature was removed in order to make adding journaling support
+simpler.   However, it is clear that in the future, we will need to add
+a more significant amount of preallocation support to the ext2/ext3
+filesystem.
+
+<P>
+In order to notify the filesystem that space should be preallocated,
+there are two interfaces that could be used.  The POSIX specification
+leaves explicitly undefined the behavior of <TT>ftruncate()</TT> when the
+argument passed to <TT>ftruncate</TT> is larger than the file's current
+size.  However, the X/Open System Interface developed by the Austin
+Group[<A
+ HREF="index.html#austin:xsh">11</A>] states if the size passed to <TT>ftruncate()</TT> is
+larger than the current file size, the file should be extended to the
+requested size.  The ext2/ext3 can use <TT>ftruncate</TT> as a hint that
+space should be preallocated for the requested size.
+
+<P>
+In addition to multimedia files, there are also certain types of files
+whose growth characteristics require persistent preallocation beyond the
+close of the inode.  Examples of such <EM>slow-growth</EM> files include log
+files and Unix mail files, which are appended to slowly, by different
+processes.  For these types of files, the ext2 behavior of discarding
+preallocated blocks when the last file descriptor for an inode is closed
+is not sufficient.  On the other hand, retaining preallocated blocks for
+all inodes is also not desirable, as it increases fragmentation and
+can tie up a large number of blocks that will never be used.
+
+<P>
+One proposal would be to allow certain directories and files to be
+tagged with an attribute indicating that they are slow-growth files, and
+so the filesystem should keep preallocated blocks available for these
+files.  Simply setting this flag on the <TT>/var/log</TT> and <TT>/var/mail</TT> directories (so that newly created files would also have this
+flag set, and be considered slow-growth files) would likely make a big
+difference.  It may also be possible to heuristically determine that a
+file should be treated as a slow-growth file by noting how many times it
+has been closed, and then re-opened and had data appended to it.  If
+this happens more than once or twice, we can assume that it would be
+profitable to treat the file as a slow-growth file.  Files opened with
+the <TT>O_APPEND</TT> flag (which is rarely used for regular file I/O)
+could also be assumed to be have slow-growth characteristics.
+
+<P>
+The types of preallocation described above are all non-persistent
+preallocation schemes.  That is, the pre-allocated blocks are released
+if the filesystem is unmounted or if the system is rebooted.  It is also
+possible to implement persistent preallocations (which is required for
+<TT>posix_fallocate</TT>), where the blocks are reserved on disk, and but
+not necessarily pre-zeroed.  To support this feature, a 64-bit field in
+the inode will have to be allocated out of the newly expanded ext2 inode.
+This field, called the <EM>high watermark</EM>, specifies the last address
+that has actually been written to by the user.  Attempts to read from
+the inode past this point must cause a zero-filled page to be returned,
+in order to avoid a security problem of exposing previously written and
+deleted data.  Of course, if the user seeks past the high watermark and
+writes a block, the kernel must at that point zero all of the blocks
+between the high watermark and the point where the write was attempted.
+
+<P>
+Persistent preallocation may not be very important, since few
+applications require guarantees about preallocated contiguous
+allocations (even in the face of an unexpected system shutdown).  As a
+result, persistent preallocation will likely be a very low-priority item
+to implement.  The benefits of allowing (non-persistent) preallocation
+in ext3 filesystems are far greater, since they address the allocation
+needs of both slow-growth log and mail spool files, as well as large
+multimedia files.
+
+<P>
+
+<H1><A NAME="SECTION00030000000000000000">
+Compatibility issues</A>
+</H1>
+
+<P>
+Whereas many of the new features described in this paper are fully
+backwards compatible, some of these proposed new features introduce
+various different types of incompatibility.  For example, even though an
+older kernel would be able to read a filesystem containing files with
+high watermark pointers to implement persistent preallocation, a kernel
+which did not know to check the high watermark pointer could return
+uninitialized data, which could be a security breach.  Because of this
+security issue, the persistent preallocation feature must use a bit in
+the <TT>incompat</TT> compatibility bitmask in the superblock.
+
+<P>
+Moreover, there are some changes that simply require incompatible
+filesystem feature bits due to the fundamental changes in the filesystem
+format.  A  good example of such a feature is the extent map
+changes.  Older kernels will not know how to interpret extent
+maps.  In the past, when we have made incompatible changes, <TT>e2fsprogs</TT>
+has provided conversion utilities (usually as part of the <TT>tune2fs</TT> and
+<TT>e2fsck</TT> programs) to add and remove new features to filesystems.   
+
+<P>
+Other changes, such as expanding the size of the on-disk inode
+structures, will require the use of technology already found in <TT>resize2fs</TT> to relocate data blocks belonging to inodes to other
+locations on disk to make room for growing system data areas.
+
+<P>
+Andreas Dilger has also suggested an interesting way of providing the
+largest amount of backwards compatibility as possible by adding
+compatibility flags on a per-inode basis.  So if there are only a few
+files which are using persistent-preallocation or extent maps, the
+filesystem could be mounted without causing problems for the majority of
+the files which are not using those features.
+
+<P>
+Table&nbsp;<A HREF="index.html#compat">1</A> shows which of the proposed new ext2 features are
+backwards compatible and which are not.  Each incompatible feature can
+be enabled or disabled on a per-filesystem (and perhaps per-inode
+basis); in addition, for many of these incompatible changes, it would be
+very simple to make backports of these features available to older
+kernels so that they would be able to use filesystems with some of these
+new features.
+
+<P>
+<BR><P></P>
+<DIV ALIGN="CENTER"><A NAME="109"></A>
+<TABLE>
+<CAPTION><STRONG>Table 1:</STRONG>
+Ext2/3 extensions compatibility chart</CAPTION>
+<TR><TD><DIV ALIGN="CENTER">
+<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
+<TR><TD ALIGN="LEFT">Feature</TD>
+<TD ALIGN="CENTER">Compatible?</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Directory indexing</TD>
+<TD ALIGN="CENTER">Y</TD>
+</TR>
+<TR><TD ALIGN="LEFT">On-line filesystem resizing</TD>
+<TD ALIGN="CENTER">N</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Expanded inode</TD>
+<TD ALIGN="CENTER">Y</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Subsecond timestamps</TD>
+<TD ALIGN="CENTER">Y</TD>
+</TR>
+<TR><TD ALIGN="LEFT"><EM>Bestbits</EM> ACL</TD>
+<TD ALIGN="CENTER">Y</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Tail-merging</TD>
+<TD ALIGN="CENTER">N</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Extent maps</TD>
+<TD ALIGN="CENTER">N</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Preallocation</TD>
+<TD ALIGN="CENTER">Y</TD>
+</TR>
+<TR><TD ALIGN="LEFT">Persistent preallocation</TD>
+<TD ALIGN="CENTER">N</TD>
+</TR>
+</TABLE>
+</DIV>
+
+<A NAME="compat"></A></TD></TR>
+</TABLE>
+</DIV><P></P><BR>
+
+<P>
+
+<H1><A NAME="SECTION00040000000000000000">
+Implementation issues</A>
+</H1>
+
+<P>
+Nearly all of the extensions described here can be implemented
+independently of the others.  This allows for distributed development,
+which is consonant with the general Linux development model.  The only
+real dependency that exists is that a number of the new features, such
+as subsecond timestamps, persistent preallocation, and 64-bit block
+numbers require an expanded inode.  Hence, an early priority will be
+enhancing <TT>resize2fs</TT> so that it can double the size of the inode
+structure on disk.  Another high priority task is to make available
+kernel patches for all commonly used kernel versions (at least for the
+2.2 and 2.4 kernels) that remove the safety checks that prevent current
+kernels from mounting filesystems with expanded inodes.  The sooner
+these patches are available, the sooner they can get adopted and
+installed on production systems.  This will ease the transition and
+compatibility issues immensely.
+
+<P>
+
+<H2><A NAME="SECTION00041000000000000000">
+Factorization of ext2/3 code</A>
+</H2>
+
+<P>
+One of the reasons why we have separate code bases for ext2 and ext3 is
+that journaling adds a lot of complexity to a number of code paths,
+especially in the block allocation code.  Factoring out these changes so
+that journaling and non-journaling variants of block allocation
+functions, inode modification routines, etc., could be selected via
+function pointers and an operations table data structure will clean up
+the ext2/3 implementation.  This will allow us to have a single code
+base which can support filesystems both with and without journaling.
+
+<P>
+
+<H2><A NAME="SECTION00042000000000000000">
+Source control issues</A>
+</H2>
+
+<P>
+Now that as many as six developers are experimenting with various ext2/3
+extensions, some kind of source control system is needed so that each
+developer could have their own source-controlled playground to develop
+their own changes, and also allow them to easily merge their changes
+with updates in the development tree.  Up until now we have been using
+CVS.  However, our experience with using CVS for maintaining ext3 kernel
+code has shown that CVS does not deal well with a large number of
+branches.  Keeping track of a large number of branches is very difficult
+under CVS; it does not have any native visualization tools, and merging
+changes between different branches is a manual process which is highly
+error-prone.
+
+<P>
+We have started using <TT>bitkeeper</TT> to maintain the <TT>e2fsprogs</TT>
+user space utilities, and this experiment has been very successful.  In
+addition, the master 2.4 and 2.5 Linux kernels are being maintained
+using <TT>bitkeeper</TT>, as Linus Torvalds and many other kernel
+developers have found that it best fits the highly distributed nature of
+development of the Linux kernel.  For these reasons, the authors are
+currently strongly exploring the possibility of using <TT>bitkeeper</TT> as
+the source control mechanism for the ext2/3 kernel code.  The
+open-source <TT>subversion</TT> source control system may also be viable in
+the future: it promises good support for repeated merges between
+development branches, but it is still quite immature compared to <TT>bitkeeper</TT> and CVS.
+
+<P>
+
+<H1><A NAME="SECTION00050000000000000000">
+Conclusions</A>
+</H1>
+
+<P>
+In this paper, we have reviewed some of the extensions to the ext2/3
+filesystem that are currently being planned.  Some of these designs may
+change while the extensions are being implemented.  Still, it is useful
+to work through design issues before attempting to put code to paper (or
+to emacs or vi buffers, as appropriate), since a number of these
+extensions interact with one another, and create dependencies amongst
+themselves.
+
+<P>
+In addition, there are number of other optimizations being planned for
+the Linux 2.5 kernel that are not strictly part of the ext2 filesystem,
+but which will significantly impact its performance.  Examples of such
+planned optimizations in the VM layer include write-behind optimizations
+and support for the <TT>O_DIRECT</TT> open flag.
+
+<P>
+Other topics that we will likely explore in the future include allowing
+multiple filesystems to share a journal device, better allocation
+algorithms that take into account RAID configurations, and large (32KB
+or 64KB) blocksizes.
+
+<P>
+Finally, perhaps it would be appropriate to answer at this point a 
+common question.  Given that there are many new, modern filesystems such
+as XFS with advanced features, why are we working on adding new features
+to ext2/3?  There are a number of answers to that question:
+
+<UL>
+<LI>Ext3 supports data journaling which can improve performance
+	for remote filesystems that require synchronous updates of
+	data being written.
+
+<P>
+</LI>
+<LI>Ext3 allows for a smooth upgrade facility for existing ext2
+	filesystems (of which there are many).
+
+<P>
+</LI>
+<LI>The ext3 code base is fairly small and clean, and has an existing
+	strong developer community that work at a variety
+	of different companies.  Hence, the future of ext2/3 is not tied
+	to the success or failure of a single company, and a single
+	company can not unduly influence the future of ext2/3.
+
+<P>
+</LI>
+</UL>
+
+<P>
+
+<H1><A NAME="SECTION00060000000000000000">
+Acknowledgments</A>
+</H1>
+
+<P>
+There have many people who have worked on the ext2 and ext3 filesystems,
+and their contributions both in terms of code and design discussions
+have been invaluable.  Those in particular who deserve special mention
+include Andrew Morton and Peter Braam (who both helped with the port of
+ext3 to 2.4), Daniel Phillips (who implemented the tail-merging and
+directory indexing patches), Andreas Dilger (who contributed numerous
+patches to ext3 and to e2fsprogs), and Al Viro (who has fixed up and
+significantly improved the truncate and directory page cache).  All of
+these people also contributed extensively to discussions on the <TT>ext2-devel@lists.sourceforge.net</TT> mailing list, and helped to refine the
+design plans found in this paper.  Thank you all very much indeed.
+
+<P>
+ 
+<H2><A NAME="SECTION00070000000000000000">
+Bibliography</A>
+</H2><DL COMPACT><DD>
+<P>
+<P></P><DT><A NAME="card:ext2">1</A>
+<DD>
+R.&nbsp;Card, T.&nbsp;Y. Ts'o, and S.&nbsp;Tweedie, ``Design and implementation of the second
+  extended filesystem,'' in <EM>Proceedings of the 1994 Amsterdam Linux
+  Conference</EM>, 1994.
+
+<P>
+<P></P><DT><A NAME="mckusick:ffs">2</A>
+<DD>
+M.&nbsp;McKusick, W.&nbsp;Joy, S.&nbsp;Leffler, and R.&nbsp;Fabry, ``A fast file system for
+  UNIX,'' <EM>ACM Transactions on Computer Systems</EM>, vol.&nbsp;2, pp.&nbsp;181-197,
+  August 1984.
+
+<P>
+<P></P><DT><A NAME="phillips:dirindex">3</A>
+<DD>
+D.&nbsp;Phillips, ``A Directory Index for Ext2,'' <EM>Proceedings of the
+  2001 Annual Linux Showcase and Conference</EM>, 2001.
+
+<P>
+<P></P><DT><A NAME="tcsec">4</A>
+<DD>
+Trusted Computer Security Evaluation Criteria, DOD 5200.28-STD. 
+ Department of Defense, 1985.
+
+<P>
+<P></P><DT><A NAME="loscocco:selinux">5</A>
+<DD>
+P.&nbsp;Loscocco and S. Smalley, ``Integrating Flexible Support for Security
+ Policies into the Linux Operating System'', <EM>Freenix Track: 2001
+ Usenix Annual Technical Conference</EM>, 2001.
+
+<P>
+<P></P><DT><A NAME="posix:secdraft">6</A>
+<DD>
+POSIX 1003.1e Draft Standard 17 (withdrawn), POSIX, 1997.
+
+<P>
+<P></P><DT><A NAME="opengroup:xdsm">7</A>
+<DD>
+CAE Specification Systems Management: Data Storage Management (XDSM)
+ API, The Open Group, 1997.
+
+<P>
+<P></P><DT><A NAME="posix1">8</A>
+<DD>
+Portable Operating System Interface (POSIX) - Part 1: System
+ Application Program Interface (API), IEEE, 1996.
+
+<P>
+<P></P><DT><A NAME="opengroup:sus">9</A>
+<DD>
+The Single Unix Specification, Version 2, The Open Group, 1997
+
+<P>
+<P></P><DT><A NAME="nfsv4">10</A>
+<DD>
+S. Shepler and B. Callaghan and D. Robinson and R. Thurlow
+ and C. Beame and M. Eisler and D. Noveck, ``NFS Version 4 Protocol'',
+ RFC 3010, Internet Engineering Task Force, 2000.
+
+<P>
+<P></P><DT><A NAME="austin:xsh">11</A>
+<DD>
+The Open Group Base Specifications Issue 6: Systems Interface volume
+ (XSI), The Open Group, 2001.
+
+<P>
+<P></P><DT><A NAME="bitkeeper">12</A>
+<DD>
+The Bitkeeper Distributed Source Management System, <TT>http://www.bitkeeper.com</TT>, 2002.
+
+<P>
+</DL>
+
+<P>
+
+<ADDRESS>
+Theodore Tso
+2002-04-16
+</ADDRESS>
+
+<!-- END OF PAGE CONTENTS -->
+</td></tr>
+</table>
+<HR>
+<TABLE BORDER="0" WIDTH="100%" CELLSPACING="0" CELLPADDING="0" ALIGN="LEFT">
+<TR><TD VALIGN="TOP" WIDTH="40%">
+<ADDRESS>
+<FONT SIZE="2">This paper was originally published in the Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference, June 10-15, 2002, Monterey Conference Center, Monterey, California, USA.
+</FONT><br>
+<!-- EDIT THE DATE AND YOUR LOGIN NAME BELOW -->
+<FONT SIZE="2">Last changed:  16 May 2002 ml</FONT><BR>
+</ADDRESS>
+</TD><TD VALIGN="TOP" ALIGN="RIGHT" WIDTH="60%">
+
+<!-- Upwards Navigation Table -->
+<table border=0 cellspacing=0 cellpadding=0>
+<tr><td>
+<a href="../../../../freenix.html"><font size=1>Freenix Technical Program</font></a><br>
+</td></tr>
+<tr><td>
+<a href="../../../../../index.html"><font size=1>USENIX 2002 Home</font></a><br>
+</td></tr>
+<tr><td>
+<a href="/index.html"><font size=1>USENIX home</font></a><br>
+</td></tr></table>
+<!-- End of Upwards Navigation Table -->
+</TD></TR></TABLE>
+</TD></TR></TABLE>
+</CENTER>
+</BODY>
+</HTML>
+
diff --git a/htdocs/images/new.gif b/htdocs/images/new.gif
new file mode 100644
index 000000000..b9ed17e55
--- /dev/null
+++ b/htdocs/images/new.gif
diff --git a/htdocs/index.php b/htdocs/index.php
new file mode 100644
index 000000000..96ddaea25
--- /dev/null
+++ b/htdocs/index.php
@@ -0,0 +1,100 @@
+<?php
+// Generic Source Forge Web Page Template
+// Modified from the Source Forge Default Page (v 1.2) with the 
+// following changes:
+// 
+// 1.  Use the small SourceForge icon with the project group id so that the 
+//     project gets "credit" for hits to its page.
+//
+// 2.  Change the "no content yet" message with an include of a 
+//	project-specific content file.
+//
+// 3.  Change copyright statement to remove (C) VA Linux systems (since 
+//	this is project-specific content.
+//
+//$headers = getallheaders();	// Why was this being run in the default page?
+
+// The config.inc file should define the following two variables:
+// content_file, which contains the file which should be included to get
+// the actual content for this web page, and group_id, which defines the 
+// SourceForge group id, so that web hits to the page get counted for the 
+// most active project statistics.  An example config.inc file might 
+// look like this:
+//
+// < ? php
+// $content_file = "serial.inc";
+// $group_id = 310;
+// ? >
+//
+// (Note the space between the angle brackets and the question mark was added
+// to prevent PHP from getting confused when parsing the comments in this 
+// PGP page. Remove the space when creating your config.inc file.)
+//
+include "config.inc"; 
+?>
+<HTML>
+<HEAD>
+<TITLE><?php print "$title" ?></TITLE>
+</HEAD>
+
+<BODY bgcolor=#FFFFFF topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth="0">
+
+<!-- top strip -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=2 bgcolor="737b9c">
+  <TR>
+    <TD><SPAN class=maintitlebar>&nbsp;&nbsp;
+      <A class=maintitlebar href="http://sourceforge.net/"><B>Home</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/about.php"><B>About</B></A> | 
+      <A class=maintitlebar href="http://sourceforge.net/partners.php"><B>Partners</B></a> |
+      <A class=maintitlebar href="http://sourceforge.net/contact.php"><B>Contact Us</B></A> |
+      <A class=maintitlebar href="http://sourceforge.net/account/logout.php"><B>Logout</B></A></SPAN></TD>
+    </TD>
+  </TR>
+</TABLE>
+<!-- end top strip -->
+
+<!-- top title table -->
+<TABLE width="100%" border=0 cellspacing=0 cellpadding=0 bgcolor="" valign="center">
+  <TR valign="center" bgcolor="#eeeef8">
+    <TD>
+      <A href="http://sourceforge.net"> 
+      <IMG src="http://sourceforge.net/sflogo.php?group_id=<?php print "$group_id" ?>&type=1" width="1" height="1" border="0">
+	<IMG src="http://sourceforge.net/images/sflogo2-steel.png" width="143" height="70" border="0"></A>
+    </TD>
+    <TD width="99%"><!-- right of logo -->
+      <a href="http://www.valinux.com"><IMG src="http://sourceforge.net/images/valogo3.png" align="right" alt="VA Linux Systems" hspace="5" vspace="7" border=0 width="117" height="70"></A>
+    </TD><!-- right of logo -->
+  </TR>
+  <TR><TD bgcolor="#543a48" colspan=2><IMG src="http://sourceforge.net/images/blank.gif" height=2 vspace=0></TD></TR>
+</TABLE>
+<!-- end top title table -->
+
+<!-- center table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="10" bgcolor="#FFFFFF" align="center">
+  <TR>
+    <TD>
+	<?php include($content_file) ?>
+
+    </TD>
+  </TR>
+</TABLE>
+<!-- end center table -->
+
+<?php 
+	if (file_exists("banner.inc")) {
+		include "banner.inc";
+	}
+?>
+
+<!-- footer table -->
+<TABLE width="100%" border="0" cellspacing="0" cellpadding="2" bgcolor="737b9c">
+  <TR>
+    <TD align="center"><FONT color="#ffffff"><SPAN class="titlebar">
+      All trademarks and copyrights on this page are properties of their respective owners.</SPAN></FONT>
+    </TD>
+  </TR>
+</TABLE>
+
+<!-- end footer table -->
+</BODY>
+</HTML>
diff --git a/htdocs/old-tytso-key.asc b/htdocs/old-tytso-key.asc
new file mode 100644
index 000000000..9716c12c4
--- /dev/null
+++ b/htdocs/old-tytso-key.asc
@@ -0,0 +1,332 @@
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: 2.6.1
+
+mQBtAi4vWLkAAAEDAMRopdzq20I9DR7sLb/HJiCbFjCvc/YQxHkBXOt9SryUXquP
+2RFg2/5F4Pn+0ApDTn1+va9vjBhhrWxh/2r0yqbKfHRI6GxJrKljbaCX2XmyOyia
+B/Ot4vsMeVx48aN2EQAFEbQtVGhlb2RvcmUgWS4gVHMnbyBbRU5DUllQVElPTl0g
+PHR5dHNvQG1pdC5lZHU+iQBVAwUQMMokMMKbwnFPAGm1AQE65QIAvzidSH6eXv/l
+zuZCoxbVy6dDjzEhKlz8NuRLbh3czDbcxdcatZbTS5cZ4wE5lKJy72Ak3DLOQPNM
+J2JfKl1lGIkAVQIFEDDKIXtSMVxYLwenQQEBSlgB/0vfKW34si/2iXGn6MhW/xNh
+VI5U3wE4b/mDxYe72vrXZJvwkpaL+ex5N2vPBVIwdS1B3KQyp9tYhw5VACTr+PeJ
+AJUDBRAwxpYYWXsE50XQopEBATB+A/sHY+LPjoDF/MPwtBhKiZ1MB+YdsX2SVglR
+X79sOlc0mQuAP5j+7k4raAJ8lymlvM0ErMpBsGOQwpDQrRGqYM+4U3XzDRJ1WYlw
+7K8L167ww6BM4XwjTBtSm2sFjgwB6GXAtpRlKU8c+ngF2C6fvp+zVxliEkby9EUI
+uKK5U8+NmYkAlQMFEC+EoZgmql+lvV414QEBDJ8EALi8CurKyj8AKEedqL6LnqED
+aK2cxQr1A/CkHMGdD1/Ws3kTNDKj+PWdjZcCexJkyE5CtKvWzAMNTWzeLm6HaWBs
+TUsbSjbc5hwYZYFk/aIdK8FgZW2XOqOlAuGAwfJWPHBay45ireowMhS12z3Uqd6N
+/0nNvU9mz7pIgnsxoh/ziQCVAwUQMMo41r0pBjh2h1kFAQFmyAP+MEAN0Uy5YbLt
+cCpEcA6oKiUtvAt+QRoQOs+k3a+8s/Pj9xXp1gQeitV04DAhIpVYpXlNtvsoZRYE
+LoqZaPIyqFt6ynCdPGgRZ/UwVf3e8uadFLsWcSlmyX9Lv9b8z5Jv9QMTQ1UXh/U9
+dsiMA2i1mupxYJWszgf25/bpInikHaqJAJUDBRAwxxWa34CTT575fU0BAX2bBAC7
+y8S6vhPHcSyvKusbEXqPbspXiCEUuPt5v+1qLuNEBvgIivicsvHsHulY8crnNIer
+AGSVA8K1VDic40fxw+qsO0LZ+DzjTY83bACfdncbQNDz/Xb3zhmX7qiDI8lW3SUR
+GfLdwzIa9epaYhMg8wplFj21VaPgQIhKBLaq/6RiH4kAlQIFEDDHJHm1TKsl4RJh
+uQEBms4D/0rChMD3qnF1rGYQlg3uWmIzI3IDxJz+c8fMQadWBBbyecRd3AxK73mU
+ve0/uwarHgbGtyHCmFFA81Vz3s9m++mu2u0iYNVJY5okpB3KYUGFf7I9LoOhJeOd
+fHkx6MOWhWcmHA9sSU1XATpdSgIj+gXjoitm5DY8VDrkV4EeqZwfiQCVAwUQMMcj
+/9w+goNjlgi5AQHysAQAv3ODQ0TKsN8YbyL+NcrXtmP0i6jdljxNPwVFHSVkxkpE
+9a7C57t2mU4BsAgpAD4xCemsWxp1QeKUSwB8QuzaLzaDYemeozU/WUT3p9k3rtQ1
+kPx3DYa+KQdAlbdyZew1zxMadEKVSD+8FYuZtN/YIyW2gGfRvH5G71J5QM/7RI6J
+AFUCBRAvg2M7M/BVPBdeATkBAZu1AgCVa0xnsz/Hd8XJyyZ6hg9tWU+GHidO94hk
+2AKV7CDMrQVweN/NR9b8CHKqxzGNLGgGdS+wBRNVinpcQaXUSuPGiQCVAwUQMAzF
+ge7gqjTuB8DxAQHfWQP9Ea/cYpC/gmKmljBGg9vDgW+TK8dCBWUJ6K2h4lutZuy5
+EHRWwizmW50ocCsAByZ9VtgrY0ZAviLheuux7X7oV4mzIpSCKtDaiGKR7kvzoRPc
+XKE/rfwfdognwwtVigc+arc5TwfHq7Y1E6abITfkQJlpiZ2FmVxuwf/T9OVO3syJ
+AHUDBRAwNrti2Sp74XjMxi0BATfbAv95tAKPMhJzMkZXy/FNuUBDgtlwt55Cv5Jx
+IjbIhpyHbyqeLcuvzHZ2G2/ml5dFeywmA/lnG1qziRO7EBoGnfar1gwCqqY3vn9s
+kGAuzeUt/y0O/aE7V2geFuEgcCpFnbKJAJUDBRAwKvlZa1pnjYGyp3kBAR0GBACt
+cFArev8y85kEquK5gF6YFd2aKlbjm52ASyaGlgdFCd0lpmW0Td5+Y1U0QsGkUSgP
+xv7DWEG9Er5Vcr673z9b8qJNxvbFXZWRyNkrOtTwyLhmKpvIR1W44kYTHlUqaBDg
+xXGuHwXwvqKfeFjhp4Eq59ZTT28txAZu+syAdnwixokAlQMFEDAapY/6PsTtB7Dg
+VQEBd9EEAJMickNuaSt+oI2nUDcd7JziJiLocy3WovslmJ7rgZdf/gqSxBqppsAR
+PSFT6es8nrI6x1m8fslIJjbirdT4y783yoUoT12fGDOVGagTHD7dYSF13JEB2Dt0
+ZEQKY/kKYTi5oWsirHWWf0aFy0l3uyh9SkrbTRCPBIu7L0gSJvNQiQCVAgUQMA9L
+yeLlu+H7XhUZAQHy1QQAldOiTE4B95/r+Tfi5HiJ4qQXA+4mAzxHwHK7ZcjTT2TK
+jg6gFRsjqiJORwyyr/EC+QHPahmRa50KGDwN1Nee7g/w+cySgue/Yjx/SlJBJb3d
+lSZPNKvd25HiuXPwcgptGadqVs6NM1+7SqPmaZXbePCZU5xflm5bwpHX4QkPLu+J
+AJUDBRAwDs8/sfyMh3t65eEBAYaxA/9yV39tU2woy/ctQOKR6OnrEYWwFL6X2lIk
+INKwP+MZ71Idd8XHn1JpIp99N8mi0uR7rpV9mA0KeOiAnvB7ARguLGKOZkOqEwwQ
+9DjmZSb2bWrPYxB95M74tfC6MmLKz3fNr5xA3gCKAp3zmMdM/wF23NJACAetal5E
+zoi/2VM+qokAlQMFEC+IjmpfsPMJnFe5UQEBj3oD/jZnCxg10FQNeG8+6yqsxqdQ
+8cRCTx/RspozPyBpFWAFLSCBYGvqZWJHzS92GoGgiFn4/gNEB7HBiVSmI2FQI2Yd
+XLqjVu8xJGvMMPJC6UcPabrApfN3bLQNAYbIGYVGZQkHcCjQlqr98Xy3rFk2A2YB
+lGCjQolwPCkADCT59/leiQCVAwUQMA0jOuJgpPLZnQjrAQE7UwQA6sHsO0+VOHKU
+OwU7VSCEvcVHn7r3WjA+kkJriVJiPxLR5ywPul2jZdACOoL4x/6rrfrwUOaz3dJy
+yRHGTg7i8VFg91zI0WPlj9IQxR9Z/LX6Ik7t5n5xNcYoh7Y1NJgBUyEFVuQtr/pu
+y8KQ5un+rR5R/k4odYgUQyRvBM5AcJSJAJUDBRAviAA7ZlpwpDAiyVEBATeCA/9o
+NzLLEn6mg3ZKBi7tfeaAGnR3n668zyBBmK599yUvdpczVxQ5eYbHJQ6cON7GvyEq
+ucpjffNo6mpirYUltvNcBNuLkNlb+PRD+u8LZhKsW6xULYwieCklnr+FvWv1dLYD
+LgsOYfhvCgJIECbGaMqaut9q/jyWeURcLjUN2951dokAlQMFEDANHQKBiAtp7iRC
+nQEBSS4EALvZPYBFKmnD9U0wJ9FkwiNatN1ZktY0iQqhDe6TnAjy6oEIy32Cb8y1
+nJ7DCGoGN1W7Z+AsErrTn+zBOD9f2MLEvoq5/cz1N/jlbaxBfs0GdiD/yzqUy1Xn
+VBMQ1430pOw91LyDQo7REJzOApIo9BtNf8Q1k7rAaTS1n0PWvYCdiQCVAwUQMMzS
+PtZx9wH4ZX25AQEKdAP/brNNkRjDpaetrbqU3CD+mSRm50wgmdRn12NdybUnDwDB
+J5p+jA0CnuHWrfpvoUm08lOEtlSBSvKz+AT2H20V2wCQw/eGcixmya7cXhvr3cbM
+81mKJ3fJqzRUDODOwWaR0U0Osg5lHRfQCrwZliYTQfSDIFzGduqnpNTvRa2icruJ
+AJMDBRAwFO243BB5z3iqM6kBAd9IA+4sv1Ymn5Je/PIC4YtURK4EIaIRc780ypfm
+UTVChgG0JlMIqtGrg7JiPLL/N+4fMkkdsiVDnaFkXqhJoAbdw2nzTag1oaTzp205
+z+n7Zi9z15BvX3U0Lx2uZMo+BhFD83NTHHWUHQd4c1CUOaFTbiNQe3g24HuQ9h6T
+DIn+MoaJAJUDBRAwCtsNdx2Srolyx8EBAXLQA/48P+dSdeBXc9G8oKrQwgWPNfPP
+Yoq7aVzw1UtUaY6Pre8KumadhDBt0G0U7JMuK7Ndsnirw+WmZIuc1Ei63IdB0BXu
+G69AkgcDBo5lzzHsc4kbaeTA5STfEOmvuo4hbWkWAslt79l7Vjpq9zkyg8pXjhfF
+QVc2PtK/7TYCTHvSA4kAdQMFEC/GLdkvITgfhcqGmQEBIzkC/jYDKQXR0aehrd/c
+qD0U0utvMBoX/bZV1GFgtgEjFiK8tkku+bHuxucjqKr27fk3J7VzvN+42QyScjnu
+0hlX1jk4BGw/pjlzvV9oJtVebJYLmdJXSCLJTqbreFVkKFPZVIkAlQMFEC+D4JdW
+J7UrUuwqjQEBf88EAOAVgsFHzT9fc0iiYHu5Ql4rWpHkZ6wCvC/I/Xoln7GFwGVN
+OPMgHHZNY+MmOqzOUi6cyeUKKIqp6AIAuCfYUW7wY0LEryncsG/oLNUjiZMmAMEO
+TGvqIwiSnwxEhon+x/MsQMaWVESLYdpJ6uO4Wbn3A14IDaPc406+/Vr182kXiQCV
+AwUQL4N4zOg5A8tVy2QhAQGRrAP/VOEaYK+Zzqgkq58tVzKrXwhfUAPdKr3PadKr
+/YnM+I9tBT49NFL8fNjppZIX9uJX+n6LfiFKhZbccG1M5kgDWN3Wfesc+HO0GCFv
+26pDRe1tpEjeEGqG5/O54x56t5YVsWknKmnkN3SAGxrHjSIakDgljfJUAYBhp5JK
+fDkWz2mJAJUCBRAvVFjGq0ve+FOq8lkBAS4qA/4iC8EYERuHOxCcBLHuYyCb9PfC
+zG8SMiTIsTUDvGtv9y8njNKoen6yo0cSWvbx+dywv0ioLJpDvbH7S+FZ3F4gICas
+FFspQIYi/7Eh4CRvnTeAAIyAQpmqZGUCe5gJjFJ/3o43Yof5TxvjkUCE4DOJhjRE
+wbY9n+oI7BT7Tx2ecIkAlQMFEC77TtfFLUdtDb+QbQEBVgQD/0fnZ+vh5yByJv4f
+wy/sp+EJSTqSfHdfWr34OsWyGnijurkxvv/sNqPHFNkbm7cJOHNb/eF0fm+lKXiv
+rILNED4rVxDmCNRZTsCulZmJ38KbZt23Ir2SFSkJAwjBNjPAElQxM9IEyzHSE2Jx
+m+uhxUPRwVI72FanFf+CKsnV7cgPiQCVAgUQLvioy1sjC0SkKFUJAQG4tgP/Qf8O
+dPpY9qUAI0Qvm0mC8pIkc13HCRVzqrD8trpn9Lpx1ZkxqixYbzUbC4tpMGJJtEO6
+7pzDww7w3MEtIhDuDTRzugmYRebO44iCbUBdV9kfxAr/1UypO+7wSLYpXXp4Pcmv
+X4dT2W87+stLL0VGJn2taFJ0o7oz/c319TVgZbiJAJUDBRAu5rq7hxvAWY8bGaUB
+AfnFBAC2FYr5O7+t9MtDyM0Y6f9wAiRlLY7vEBk4CU6eWmnQWlbQzhsWY7+3kdiz
+ALEmgVrJPVBTr3SNvqtxLaAN5TDWwCnQen02WUgoazdCdZ82J3asbksA6ZebF73k
+nX99wDwiVECjAd030HqCdERsZRM0EkIlO+98CGRBLhQVz1mpQokAlQMFEC77GP0X
+9dzI7xVAiQEBJP8D/RDegKVq4/5GhwkzQN5cx/OgluuC3lbc6QJD0Av6KGWhQhj6
+7gbKREg2hAsSsKROjhCjhfC6pNfsGS+qMZJeJ3IfS1u4gE1aMSL3DstH7D5tLJ2i
+DUKFFzKUhGKq07Yts8IdQKa7pIFNTsNEVYOS/NHWBEpS+HDoGF6zVRXTjPCNiQCV
+AwUQLvCrLWc1jG5vDiNxAQFWuQP6AiPb5QTSlIsD2kerszpxMB6s0YR0N4AfaD3k
+MKgMyKA9mTFpHY8NlTxVPhswoyC+8M2VMc/7oZ2NhggpECvaoOIQ2CATKRUS9u4r
+zK8RuW4pzunZH4uFvkkv31Bw+rUC/OR51TQ0wPkFD6IjKY8LlPXc+OTc/QRwe0yp
+l2nwlxGJAHUDBRAu7hzoapsJyFgmz40BAa1vAwCyxMU+OGy+TizCyReqgYrAtf+d
+L3CZA47nYPOZudUE5BKecd29cV1n95dnxnG1T/HDoUaxflw7zdrRQ4ZCwPMLYYDW
+rWjlbtwoT5Tkh4YOhQpPPdb9g5WDS+lracrO+wuJAFUDBRAu59ibqn0S2IICPJ0B
+ASZCAgCn4crLnO4Gt2ffjMPBna4G1aFl+ryv/DK8hDHXkgvrssuNIC2MUoJOZ5ac
+OvKFGoFMnT4JKMifnUu/IKF15XNOiQCVAwUQLuf2+jJyiM5s7VOJAQG5lgQA2aiK
+L12HUwxerGHVPp4ojaHavRaJ1JPmGAdvTKySc2JEO+xYkgnZwTCrLIqwFTtmiDqD
+px+yiCR8wqmIUFE2QZ4deTFVX36RBgA4ysPMmayWo2r8EZYsclYjs6f6uHSTXTuS
+0YEyHySTji12ocWUbFzjC9NKyL+JIY602shHuHGJAJUDBRAu6AKcSbe2IzT9IV0B
+AWFjA/99Ra+k2i+VCNIho+u0qySLkrvgls1m8rRJ1iEXbzeYNQFasZGRHmQPkTpo
+5LR4rrdeCeOiG+5JnJ7NeGuOUFkVYkB8g1OcqxRyatL2m22VitKm997I7gHvSIgg
+wdP0taQtN+e3ze0ZxC8Ib/Hr8ULn7Nh57CyKrHRzy1kEVtQKx4kAlQMFEC7nU0f/
+HvxIbPtLrQEBpAUEAJzsPXyvCBY1kifQVmG8WwMBG1gb8LN9HRZAKxG9V89g60q3
+8M5bYEA7Sj90Oqe6LxYh8pwvAsdKa/tKUXEihcAAAksjUI7dOdl5sLfT9rIaFn7X
+7XbPbQcbqWGNz89IvU+gTRPU3K28Y9eSQkDR5YB6NfWGwUgcq16pTxfpv7aQiQCV
+AwUQLubFuKv/B7RG8yEtAQET6QP/Q4eiMMfHBLZ4VeD0vNuSUKO0Usy/kyw28ojd
+oPdxEUyoJ2PEgcOmabtSYeWJxa3N2AMVQt7sRHL+vtCeu3cyz3IX2Mxfa7dmKTJw
+gHfAuXsYlQa1LqyJWAt/duzUkXOUy42FliSyByHdcGQt/VipISvG/NaLVQdTnCpO
+wP3QTZGJAJUDBRAu5roShN+65i1SfjEBAYuEA/9bGwd4Q81RfdCbQET4L9xhZlRu
+LckFcNJgZVNPbd16ny9nJD3ZFj71z3VkqLTtCVYmQKthiFRXokP5Z4rsdxkWDN1/
+n/9pgVFTk6uaV1DE2SCotipZgjGP1uvtdgdg0hZHqpXAi5HaHI8RbameiuA+6m9l
+G+C5JiGPKIlrnuzrSIkAlQIFEC5E2nBU3V+iPGYkZwEBLfID/1sfYORvhC2UUWwN
+9YbXYs+7hFNBc5Gor4St4ytcAy6WIiRAOEp18HitS+0IVi2+qShZhYL4OkCmXmcs
+AIWcbLhy8uSMcqEAq2AKxnErv2DaHf+lEhkbWCbtwboHZDXcNnHf7TgarP5STG4R
+7Du6NKTbfwzvmTCDgV4trp9eXKLHiQCVAgUQLj6Mp7T+rHlVUGpxAQGbagQArAxE
+tuh2Q2seboN45UFJRGmC0HpiZ7mJ0/9cg71UbduEZqum1U/jFQinhKEpCvtqwNTx
+OnJb5aMAScCwEyq3ouQguzmYnEBAtLenpUfVAoPFm6vuO90p47yezZUS8QSuXu0n
+qay+U8ROKE5pmIP9Yj8/45JkYwziCY9Y27PQD5OJAJUCBRAuPYywn+savKgvyHcB
+AXgvA/0dkcy1CYVn86SdEi19dANP0nGNILftNiNYnlP7eOTvDXXk2sq7rH0qGc4z
+O0f7rfFOMs0JQpumoeBPd5KycVi/E3WbIXl2RZHdJElPQTvNVchoObiK0ikm5xhQ
+O93BjKqHOQrpef3AubnowJk9kepMgovTXCm5rYYTQk1YNeiPCYkAlQIFEC47+adH
+xfijgSq47QEBeL4D/0pkSU0Ww5wQS1Wv3333lMEdDd0EV522BK/eOJcl+wbiom4j
+4W0FAE2CjTF+2kcP/MfZrJSSAVX+tqVbIuPV7d9YjIPOoXTxFGxgY04CnBjX0bOA
+W0P/3Eag0VTv5wJEJCe8KpzUv73qdn2Bqy8T+zLqjVe/12XBMTslgTxEYH2yiQCV
+AgUQLjXsJvoCKdi6GAHVAQEGqwP9FTzO6dp86BI+PfDZdFhtrCwSlXyz/nIgomw2
+hznWgsczenCAtj63ftwp2WKrmkGaVMQR8vyMD6u9R7s8zKPJmy8mG8mOQqY2IRg5
+nZ6Gm45vT1hxWki9PCUuTw4rpTsZau7lpMT6irY7mfXIH9n0j+I/lcqx7EqRnJM7
+JGyn9WyJAJUCBRAuNDr/X4A3GNoO3IEBAZgFA/4uZNn8VQTH9eKxFmBLbqxYmpiP
+7FnYL9u9OPqCd16koch/jW9jV3qi0jEDkjrBJDNrh46XNfRvrISyn3Y9Hpq424OZ
+Tn7Wx1qWkm0MpZzrg9rLlcs4pTD+cbg5p1HT2wiLr3qJFmoL1Pga9MN0lT/sM7iq
+tFEX1wpg9X7ViLjc8IkAlQIFEC40EeUgEb28C9kaLQEBERIEAJmO7SL84h+8nA9v
+UcmhTy/KlgV8kY2fSTL1FsBhlFUHzo/KwsNGtzp5u2Dp8HKfzyp+egKg4vYt3qRT
+6cJOJScC+1wys265JMSIYRmb1Jndc6m4RbB1TcJxrtfzzSZDRKT8fwxjNnB3xUqe
+4QoI6CXf14fp0/PT4y9zOk8o43mmiQCVAgUQLjXfKV/ggdzgPJX1AQF+1gQAgrkq
+jXQZ5mlqUqj+MxtkFqeTSNdknkeIsQbO5iM0QWOv3Yk9En6MHlM859bWVY5oXRXN
+n5IWxLExiC758Zev44/20e1BzqU8P3BFHUbgfqNue5V+fCtUApyWS+HJfqFGRbjg
+X3mEcVIvQm2w1R0xvAdVbVcFM5M9G08+FanZn0WJAJUCBRAuNd8MJ0a5O0bvstUB
+AVNyA/9qItbkEN3b6FVTE/4Mbstm1xz/Kyzb6yH6jrEonh7yurOtl0ddGftEJhiK
+wXnm99j7Y0ebAyliUJPSdNsiUZ9ehjKkbT5FUeCGSWo3zhMBRhgdxYc/XkDEa/L3
+Y0awPj7Wq0EByn5WPSeSvU9KUZt8bSQ2Vz3336uYxTR1v4SJ04kAlQIFEC40CiX7
+wj+NsTMUOQEBPMQEAI+TbXTdGvzzkb/USEr1dMCrlbf7NCUc8NDRn9oHT8LbzOvJ
+ebat0R6giiWunrfO7ooKwhj3TqjzsqJmwBuEyVTC3ZM8R6wvaI2OLN1UwP/rzQ5L
+ZBsHHFQ949KPSpHPDz9manm+xPdfA5NYynWROh4KB4UiwFOmE/UuijsXowi+iQCV
+AgUQLjQGJJDwvktRSrLVAQEnsQP/RP+IbzKT7lbr9ZiahtoZ0CcgbVpRKqBxpsav
+SP/nBPJWvSu6gWBVeGz38wo2RMoIETmLikxsI4o6bu/8wXdjnXR+y/KcQoVmGzDA
+2LL12m9yg+GatwX56+05xV3yDCKX9D841I/zE2k5RPbGTZtJXvji/BIoL6fc5TJi
+Ol9min2JAJUCBRAuMubMXL/sOWbOibcBAeoMA/4zh8nW0mv4slbK989K5+9FN//D
+e7HpWjcrm4ytyplkaDSCbUFCsTTvHb1K5d1Ak33f5U8YNXoJ22ExiyajJbpErSLo
+i1D+Tyz/GlE1A/J8xv0xwnr1V3GP0fx3Gaap+ourLjr9cuKKXOesVPSetUxOnld8
+Rbl3iOBQBhBpElq95YkAVQIFEC4y5qUHiMysn584uwEBWhsB/iw9XvXwMYQAvc0m
+dchOxj1oc/JaAthhDAXHqhAddRFzHRT9Mp1jwJKcWCuBYB/nwG3N1fTvpuPT+WFY
+bzQz5dCJAJUCBRAuMuY9bgu8vltBViEBAWacA/wLRHl1akRsmyl0SohNvmP/z63h
+c59LZQwYdhIJWxvP8P3BdD1/BYMnih2m5I7T6WSA32z4TRMNgJBB8e0y2rWS1ZDJ
++L2c5ZC1UPD51COqxT7Hffi92vgEoMiSzmKwbyglceVsvXsTxGhEkBMbNFY1H0by
+2qM8AsiyPOGb9G8TZYkAVQIFEC4whBxVBWb6TQxO4QEBdeYCAJfkro+5FYXNW8ce
+aLn+GID5HiURrDcvPkFeV+BNGstYEobNDI2XldftxTzxXta7+dCateGYtRTPpXQd
+mh7bg/qJAG4CBRAuMBa+OHQrXMGwavEBAdQ2AsQJT1agdn6GLgQy2enbNozDOOnQ
+MsFMFcJEUvhrP15v5Wjc/nZw1776agjLtMtzx2pAOPcOZginJ6UWF7YN22XN6n2E
+svMhz8RuYDBeEwFuQzQAmTge606gEokAlQIFEC4wAZtEFXDNRmtCiQEBHN4D/Rz0
+RWSroKwd7IBgQLiuJAfLNCbJFOTPy7HGzhArrD65/vRxaeK+XkqIk0XEqEvoZxP1
+20VoDYtaezC9txMebSZmSGRJX80dt6D+QpqdDR2D21LCjI4qwKXCK1ntaVJ4dltp
+cRe2/FjPDv0EKa3OOtxIL+S7qZrDiHVMyu/DdbwumQCNAi4vUOsAAAEEAMphr4f8
+Ju6tzx4s1Z9H86yIVqu7bJLjjs0434dpUNjtz/zUL+J6L2qIMbWBGBE7xFuj2BjX
+dyqRBRAFLGuua7BjYuLYEikxv2/FVAC1jQ8hYXyrG2v1UlQOVE9tlWSESOVaEaQB
+fCJ/5gNuU+6jCVZkCdqv264oVEQVcM1Ga0KJAAURtClUaGVvZG9yZSBUcydvIFtT
+SUdOQVRVUkVdIDx0eXRzb0BtaXQuZWR1PokAVQMFEDDKJHzCm8JxTwBptQEB8XAC
+ALkBbZPwpTGah5RsNUpyBcyG0MsvAOwogFpdB7jrkKS39hBh0ZdbOn7G0UppdBee
+iUvikTbV8wS4JYm+qrPS/XGJAFUCBRAwyiGpUjFcWC8Hp0EBAUyJAgCNQtvHwFZe
+mW+2yOvbOxby0xuXehS1aA6eznSMxjqyE19OojWS/nBsgnwfzgrgEBFYyYda7qng
+EDXa8z0pX+3xiQCVAwUQMMaWTll7BOdF0KKRAQFJ9wP/SQTPbVPm1wKpQVDtu5mH
+DHqn9ym4wjHTcIu3dVMDGST7jFutyVdpPnG121CA6iqw2BkboNIZcZCe64L74lpz
+6kRmGGmn/NAnwhy3bu+ArIaSZnHzT7ZvQrcCe8J0erof6radGt4QQF68rM90POrg
+QCuuUX10Dn1W8OxDNhYm01KJAJUDBRAvhKGyJqpfpb1eNeEBAXbMA/0aUly4AMnv
+wasNOwn279rgSIIqknLv4hUymEHxuBHf8wsLWHqM5lfS6sC8Lb5cl0d95fGJlr8A
+1X7ATBMALDENZtzdubIWo9HZRfEQ6BpKhaVkTsjWx9jyaukuboSu5XkxmjlTJ4Hg
+wshET2Q0jvpKGnEBciCvoKLkGCdHyHuAQ4kAlQMFEDDKOOy9KQY4dodZBQEBoC0D
+/j5SSn3pckm8+u8JYsXvVKRGTPsDt+ey/Cw6FVZoo2anW5LPFmbsLsY+2r7YUmPW
+kOCphFID26rcMX/zO13Rm0Y6h8o0+Utt+HCHvbtxZ3aKEu/FEw24geKZYXvZ2+/J
+GOVznR45J7Ji5Lqmb++k80Zgow8nLSLMROjZxMTphPYWiQB1AwUQMMjb4TCetiCf
+WxV9AQG8ggL+Kv4G2td2yZxWOZ6ZEiF06j84dJS9ZlMl7u21kwZYjPFqoVvr/zL2
+zVDQobHy9NaPs0zvoXOQlgrwpY7MrkppnVA9QPh5DG4Ni57aTseFcKph62VR7yzz
+GqMF1qt7RKpdiQCVAgUQMMcky7VMqyXhEmG5AQHzvwP/bVaVZcGeNJ2xw4gUvQp3
+9N/xgrDNz6YfiJOdUgcBBFh7/NUJW7fnhxPAeHrmBjOzd0IQIX+n21pi7c2PIubs
+c0CVBeieRL9Mou7ECkIatSGqAkGbFpneeyiudMHO1P2VQv7+xASFKegONXygHPqg
+ojEMBFyu0VOjrZQN7Ao6ge2JAJUDBRAwxyRH3D6Cg2OWCLkBARBPBADD+YQg/Q3x
+6WuRtDzp0ODqHvTGTPal1nJYo0gpE4o502YBI5qkLdExNARGDGCAhTO+5KWoee05
+MQkj3eJebeeGbANAAvIw4hS1qRn3mxWBvGeC7/ZOffb9ssymwS2t1q1Kl68UygzZ
+uIeEAtvHH+RciR1jExM2lvBIIYhF14ZeJYkAlQMFEDAMxbTu4Ko07gfA8QEBgjQD
+/3Z1FbexlIRRToow9aK4aO+2DW0e/pA/YTJtyObUqpvggMtxM3MoD31fhckHcvBB
+bsuLeOLaxgLPPHPqw7uLFx4WODKZmNUuL/pRYSsO+M9cPaomGpp2nEr5iJ9fAKYJ
+npUUv7MMCgwmyrC8UQ7Eg3wxRE3OqzVgwo+c37tvWwxSiQB1AwUQMDa7ltkqe+F4
+zMYtAQE6bwL/Xuvd5xxpXCtJPnaY9pE2qK5PkBHUAXeXmMrC8E21uLFdz2Kjvps3
+vE+G8ttDCBQZtjrd0yIKF3j/aQ75QSK+QrzkuxvAo+A5ca+EdW0bqdODfGfT2x2/
+MRZA4RGUGhRoiQCVAwUQMBql4fo+xO0HsOBVAQFegAP8DoyWXg/3i15NBwNBpqbR
+FFipKLsiMKP0nr4tcOsKK32ugpm1q/rpCAFUKrwgg0Uy7NzDfVVcjeuasC+9Xu6b
+UMLW8eT9uxtkVFb4L32yc+SJXp25RekOxrXO2bfuNFW3CNYxiygrY/YmWp9RCdfX
+3xq96+D5TgoJ0ME5iwAoTsyJAJUCBRAwD1Uo4uW74fteFRkBAYzhA/0d4GzPSLcg
+uDoc/uvQQ5qxLmfK1WmyopaXsP+qN5bi2YHIm717ssf9oeAeYX0GTuk8uzoXHG68
+mFIe9YGbs1e+s7r4FLBQBHSRDXLzsy+CIbx1mUfmqEeacd8kJYoC8chT+t8BFs5N
+B2tSpvH4+QFotrGjWWB2VU7uAR3l1LVXZYkAlQMFEDAOz1ux/IyHe3rl4QEBok0E
+ALgWg1EHJzZNllXDpA7ZTI0dlTWVHixC0Bc6stm/YowDQJkp4G47K+7adxsGyUbH
+kpp1jXCZitOLdkTKNispPxJQ3bmTerqoU9Py2aMSqLensz/gXFqeZdVTBmzDZ3rH
+ehDmmKxGrc9JZylh0+GUIA8993s1769WqVwu3SsSLWR1iQCVAwUQL4iOkV+w8wmc
+V7lRAQGTDQQAll49hTeTyl3hfnoW6/4j/Z6ca09dxhpc1FanZSSchbWcTy7/u0+O
+YSFS2xBNroSWdXbHp8KcwZynmfcgFeWsDmANnSoIJjjcd4MTfDuCYPdN8HAii1QB
+jXzxijx98HYoOmUKVo2VuYkCKsPkIqQIP+kAZSG3Q+QQeqM9zgBaVCKJAJUDBRAw
+DUex4mCk8tmdCOsBAYhcBAC1tCn2Wewk0Ac6eM9jB1MyMbLOBshQ4QOIU+CpfHxe
+A+nLhMbHo8D0EPqkiyq+nTlMrIbL9qgQlpgJCiIiqK7VT9iU52YuNaqVrpwT6zRs
+DYW25N7ifDw8n3qjyM1t2MB6PYAi8wmOy1B+VWPLEayCi5Q03gU9fNnU8ivgLGNg
+14kAlQMFEC+IAGVmWnCkMCLJUQEBw3QEAM2TwCVJ5UdHY72fK1pAqEa7oZpkMC+7
+/o5AGNnn1edkdXSZiswNwd5rwfND4FpkFsNK7f7K1p8MBUcVpLcXLLKl0jJ17lMN
+eldXyzbAYbEW5eepwAEDvx743UDBE7bsFTretzTzBzt61uUvG+NOS1N0uBkGbDsf
+pQlajGlBCPppiQCVAwUQMA0dbYGIC2nuJEKdAQHJ4AQA4c+KKCE2zyqyTw93GxFq
+zRr02qDNNS/P0RPscYmE1vMd2NXtAtmaTYmbSVcawakeJDNTZjEIKcQBSq4p5sMF
+MP2f9yQtX/3OrV+Dbd94hn975NxqYmpz0p3iLOZnkvyrr6V8+MsyJ8DDqKQ9GGC3
+zCSFPXg951byAForkVqLDX+JAJUDBRAwygzzaoquVEuNE50BAY3qBACjMvXEbbci
+SXR0Tn92fBH2HeHI3N6/Dhcp3Xf6Gmn1XlJVPBkNLcT/ukkCJ7Q1/tyIUhDvSbpa
+JaqbbACTws3JpeeU5jdGmBeROuNpD8oLtdLsw8QS3YpMMtpZp9zsSGUt64g4+iFq
+c3uw0q4Sdu+aACFXultMNPqoxU5/xhI84YkAdQMFEDANDEQADvWCVm9jxQEBVCED
+AO5bA0J1qV/OqjwNH3e+6gb1qVqvDRtzPMLeTs+Y2AC/EguQTsvVOuBZGEzNw6lP
+XbFhSJ1MxKT9qgbU6R1aR54g0p8egFkKc8bc5SRC6edKRrYL8IpUubkQMoMTR594
+kYkAlQMFEDAK2xx3HZKuiXLHwQEB2ZsEAKiraImOKC5Kb91RMjNS7pkawstPjr5x
+CyqxH+7FKWciAdIqCSwrg1NsMg8nqKO08q7LFuT8/WT9G3zloQLEC/9fb513ofMb
++n4PenQMG75TB0tpLD/4PW4EN1gLZJ9zf4/jecCF8Ni4JRjEdPCqWD0/kHln11LA
+8KeLpfsiVojSiQB1AwUQL8YuRy8hOB+FyoaZAQH65wMAjNShj8m1NFrKr5NQTe7A
+d40/GbTb7IsBW4x9gKJxJcu3m1lmZNf2gE+c+1YVviFBsGp28yh1wS1unZDuFka0
+zpWEIx0aNd7cAIEUD2C3MoCuRprJxTDcDGriylf8mq9xiQCVAwUQL4Pg51YntStS
+7CqNAQFkXQP/em3MrkqrMlfvsB5t5qrC/4y9QuccA47DhDGtZonLvaYe+cl/1iit
+lk+9f2hZoAsXHnDuOwGF8FUeqOqaU0qFFKHvyjU4JevhRnB62PpKuZwJkVZwiAFh
+FHhC7PyOtCZRNbJXT0krXwray0PtnjLpIrM3cQFZVEO8HC+YBkXpu0KJAJUDBRAv
+g3h46DkDy1XLZCEBAUiqBACsFz/fC73cWRgSUOGxLK/r8kG+3kX+pK2QlI5iYJiO
+cSyGPeU2hyqUc/Nah+EQTmqljUtBJsY5F9VyGSQbRJQ3hG3OxGoRlIpxhYX7wqL9
+W1BNeXHej91eaM6MjijZSxBxu/OdBT6znbdPGEFLACqrLXuYYB5XXAjUE3CDVGU5
+wYkAlQIFEC9UWKmrS974U6ryWQEBUWsD/0NC+DjCVzyz1Q5HtcNABPlpk/M//jeX
+J9wrcj4GvLVVmwluFv57GotMDLBnhCJNuiisQP0ZxicwVNqOw1BnCmRwhdvaWhOz
+zMahYg0zjlF51Rb5Kbnyeso9dw92PG+1t0OJAYbe5llivVf2GbtZmTPBqERdj6d1
+X3H4x5nUXkQriQCVAwUQLvtO7cUtR20Nv5BtAQEg7AP+KQveDXKKq0vR8ufjvJoM
+QMc9KWNgJiKv5/AVKIK/Hyra3SKiwcDBbutorhoQ8nZbz7Y4tBMZ+Jde3x1G25xi
+Z1ph7caZJMArZxYvfmez3JwN+W+SNriDxAn06/ciQtSp48IW+0p0/KQWhEW27AYj
+bhms4leIpvIoq5Pz88JpMROJAJUCBRAu+KiQWyMLRKQoVQkBAcOjA/4ww5ltNoO3
+l9zFhHHU5338w47ZN1r+3KIHM6ra4zf48a9c215LSeiO46B7yRckG7s00ygjEMEQ
+7libEXebiRfPHyYAu3OSdCTn1mXRC198Q1KfNX09SqQMHHLtdwWwMIcSqDblbuK0
+TalgYnaIYWOUPer3BEGC1ZHo5rl8/2InGIkAlQMFEC7muhyHG8BZjxsZpQEBjtsD
+/j20WpPJTWgjUNotDxq3dZRxnNwURhaAjxjPEDFnkzYQQyuPG1WSm6fjVYafsqO7
+xztyZ/vdUDEqiPNHwsjm6XosnDsUu8mEyJn6c8EFPQB6NBk5Ess1zmUwtoaehh9j
+jHNW8ddepwy3VGp5OY7vfFLc630guON8HzmacnFrv4J1iQCVAwUQLvsY7Rf13Mjv
+FUCJAQGlRwP+LBTBn6yM+TvKF+PloYvnpWfR5Us4GIePiO6nNKTJlIsZPgdIXxPE
+FmAC7E8mAJOgiDVidGHUvJveQgrdoExDBtMeDe7qavor2g1cswt8lgkDwwQeZlPV
+Q+Anf0LU0cDlaBr9lw2BWW5U4BfRQ4o4LwGQQEeBzipx7sbHFM0MB0uJAJUDBRAu
+8KtlZzWMbm8OI3EBAehHBACWZR4vRmFYgls1yMGcMVzrquDxkpraCy+xwkvOj/X8
+Ww+t/XfS/xRplz0f3qakDKNu6i1VXMf1LnCyOHv99rPpvy79O3YhvQWKNm5X1n5L
++fA2HiDZ2OzAWRXhXUNP6TVW+oOEzidHfMxqloV4fsWxfmkYQ2L/TwWfF63broe7
+2YkAdQMFEC7uHRJqmwnIWCbPjQEBdjADAITUsmpYPofsh6WGvB+t/cYbJ+kJHoow
+zEgfAOBpPd1WMZFQ0CRSsYnoT4K+hbu3gVq8zW6L67PpBtDY75WGxFmVFg3aQQEE
+vMZtFavwg+8jWR6gJngY7TtUN9NhQmHBOYkAVQMFEC7n2G+qfRLYggI8nQEBQfQB
+/2YM2W8+/4lryPYUDvy5Lls7ucWXAMXDDNL6kB6O8z9OvmFVJMQQyUgIWKOC6B3M
+THMuaYtnQNE+Nv1EN0hAeueJAJQDBRAu5/bGMnKIzmztU4kBARU6A/iqMx5/loOA
+Om+pSrIePKWmVoxGWGD+z8tj9ZZJvKR1EoFlRRkBIZgC/PK7INdRUjEIen5g8fUj
+a+UOc/RlzocwhxC7hvSCdTLOlCeTmDA+jWZNKl03EIv3764Jo1mg3Gj2dgUCFORx
+Ug9GDNMwwGIUMuoR5I31WnQHfSwRI6QXiQCVAwUQLugCtUm3tiM0/SFdAQEdMQP/
+b9KidzwGFoOB0h4c+aRlYcpySwwRfCZZnImRv2BBWD6CLqnBO1ydjPP+HuUSmj6j
+AxzmXjt4RjhYRnUXbJ7/GoPyqTl1OFWCkqpoSabV5fAwHZ8Ja+SfznmKi8Z6SuVZ
+aZ0fm6s/VFfTKR2UTnfvaommeC2hpKm0vwLhnm4ajUqJAJUDBRAu5056/x78SGz7
+S60BAfXMA/9hApDQf2eJR6RlCNVN64eFwGrZ7xIONlMC4ASWiShRbhKiDA9zznnn
+SM2yOV/h8qUpu7m8BFWGFJW4aPRksdOtxUESAPOK91eRqLyAscIkmPPVU7pcAj/E
+AJ/d+vFQVeajFHG60FgeR3eHdPoIHxYtolqTG43HL2yf38FgThqTmYkAlQMFEC7m
+xdqr/we0RvMhLQEBSfYD/iobEA5mF1pef4Br0eYhKWglsxPwhQErfkR+dTIuvVGX
+NCCGT/IR2iRhmatPrHQyd9lhSr06ez2vVdzfi7wasKovst1a8inMfDqGC4iGGtjA
+UjHzLTcjv9OnsWBJKW5N7f7h+Wt5JEem+8UXiwdLSOcCujgNZCTm5P1BU8eF1UDk
+iQCVAwUQLua5mYTfuuYtUn4xAQGSRQQAnpVSYDRC86MTIGCmgv9egcxDcqKaQbC3
+6X2yBIGQ6pzMTn653DABlf9v5/LfVXDYy6k7lNo6SUU6UzeqW57kTbTV40ILxCEF
+tddLOL+GdkvH30/JSIpLeS16Do4NBnnSvJIIKQqFqH105+7+iz3iFGMiYG9grC9M
+Em5y0Kl57gOJAJUCBRAuRNpFVN1fojxmJGcBAS3DA/wJ2hJqlEbBcbmCYzDvIibn
+ZetKMdJ95x1zJyBVQ6xep1rsW0eoLrYmGa5yFoQNkuhrsq8eDUqs2eEP91JN4Gp9
+qgfF/Lk+vYHLY9oZwNwLGUwaz66EII4VMrgGTf6mqtSAu3hkqyJi26kgEK0VLgaI
+62kns2tuJk5i2m0ObRKQkIkAlQIFEC4+jLq0/qx5VVBqcQEBp7cD/jtmcBMcyLRL
+Ov5Yfs/ZotSwkUC0vMjsvPl2R1DXPe+EUPWTOiTPemrpUZ5Zuvf/sw4UVZU46qfe
+mHj80cVXuYy/NgjsqvAA6vk9Q4AbrF11/liww+RAyLLuMhDpZDla9GeFHmAzHjxn
+ARRsr1Ea7po+xWPcYls4pPcKMVcc6U1uiQCVAgUQLj2MvZ/rGryoL8h3AQHFYwP/
+QaHXpuRiaUpjfeAuhynZ07a1T99PQufxwRIf2qirgB3ERfjtKnG9pDtfDrABTMPj
+HhNR8+/s/lMuugpiHQY3jrdgx7xkZYR+UYqh6i9xxx6obXoX23az5rCZDNrGHmC8
++mpVaN8KXuVd6iK7S0+quWmfni8m/mzBtcp/7GzJqwGJAJUCBRAuO/m0R8X4o4Eq
+uO0BAYOMBADKuZ1mXo3ax5UXSG5vTSYpWqRO5nPS9E8X9exDkgS5EcYaOUg78exk
+LqzAm4z5nREtnLsEonVZn0KdQso9q1UWLaIQmTSqP+ywnp4wTeI6lIuxj5Hm+llr
+z+LnZMSlVFtEsY2gBxs1JnKUb4Dr6crK1m0XHCUMm3kaLnkev+AynokAlQIFEC41
+5T/6AinYuhgB1QEBMWMD/12bsG0GUo7ts+aLW1Lw0iWNzMMBmWpk97C+wsRIdSY6
+MV1G0iPsxs/Vjyr7TINhsmu8tALCZjRTdx+CMuF9TjqDUROAUr0vUaQnwHjmVGGx
+d76wwzZOG3mzo0DUiOYyJN/A1okAlK4Z5vIUxMkRWqWmHj5/xlxo5zLm8huPwz3c
+iQCVAgUQLjQ7I1+ANxjaDtyBAQFJkAQAsgE0UNP3P3JNwOhVkiL4sm2IpW2GeITv
+xqjaUYbMtuob9T1V/focViOzmVe2oiKewKAZfNmUc2MVxgkLh5aE/zCaUUS6xg3m
+4/WtOmDTXlPnmWtzmbZetgZEoYi5aNUkyRIiIkcu/PH70Hc31G5DElkxVsblSu42
+2M2mHiwKFJyJAJUCBRAuNBI0IBG9vAvZGi0BAUMxA/4/9RvcsUU5JtB5umzXPKje
+RwN2PTmxw6rI1MUwgGkJiHSj6mbxOt0FtGSwaoKeUmYNRJGTaQrN/EenaUJkyh3U
+ijQG0aVxr58ca+urnM9kut8qLCKZy+qv26+idpn9TpnSnFuqBOi2vG2UiincRwjv
++9Io46OoFINwrjuIWws3SYkAlQIFEC4131lf4IHc4DyV9QEBNtID/R9IIUMoPKHJ
+Su19i1cGhxGsr04qf2suZb0iStR2nPZylUW1p/QEAaDWaQQYPUcQRcE40xxKGKdF
+vypGzgwmpKSPtYavX2yI/9f2oocVx/vYgXsXpSEuGPYFCoB61DEXBhsKCJ13GzcE
+kUWpFgUV/p3ONe+5bK1EbWJxGOsEdSG7iQCVAgUQLjXfQydGuTtG77LVAQE6IAQA
+2ymyYLdhQ7TgV0qsDBeLsYdyvkSb3sN11LUcehyjhRjAUFzPuV39pBA69Epw2/N5
+Coizx6uEb5P/YM06TA9fQ1Yr4IEbVzYFVTW/xb9rFmBZwCyJDkXWvPKqls1/sczF
+iYKJ+LaJFTJTPpss4UOvt+Rpc3gVwccRqDv+9WB+nCmJAJUCBRAuNAmL+8I/jbEz
+FDkBARWCA/993nBcSWgxHYBXKgMNR0ml2ZYCbrgt/HAEfnJVXYfMCT79SMK2XdkA
+v8zIh+xMFOPrDw5lDjGe1wjWVd8hfMpEyddwOqZ6qoBFCXZGoyZeQzeZc58NFdZR
+A+9TUCipxCfv6iSbXzmKHJ0sIhewf9d26Zfi4y55qW0mrZfK+og9+okAlQIFEC40
+BlyQ8L5LUUqy1QEBa2oD/A/Koy4UMJR3lX2WQlKw1b/EseSjTFM6BpRiK74mbdjw
+1jG/6laVAvLkBuekmYnoFynrCDtqiqrIhky58Pv+DBp4ksV9lLVlx/35G19P+hpn
+JaeKG3oHg4/goSmRKRZeV28/4T9qh0qmo+5WNjeZLyAAfCHgPuxRsbPWDsOJGXiE
+iQCVAgUQLjLmwFy/7Dlmzom3AQGomwP8CWotl/D9VtRZDewLkCu9WBhNR/OO/ouW
+5x6uw/KmxDGwIEhy8jxX/xm5Wliv1GGvyn9kPGTCBvthBI7g3Y5YIg50Dta6Wjr/
+0/+3mcABfffYo04VSztizlkttqZqgjOM2G7WNufdAMwVJwT/EeWeEVskzh2JtP6o
+VuR0cRW0/W+JAFUCBRAuMua2B4jMrJ+fOLsBAe/4Af0Yu/QTsNnFz90M+pgRitgh
+PuhLcQMD5rw4HWcDlob6z+8DeZICqNwHBl2qg4aRj/G109zx6/l+AA9sFGv6P46y
+iQCVAgUQLjLmMW4LvL5bQVYhAQHe5wQAuZqJxWktZyT/3Hqyx7FStcUBVcHITydQ
+Mcjwr+A72kjY29ARTOHPsRby2HuLfy3GHKtOyYOYNkaON0/gvKHvgAhXL/dygCXh
+sGiymRnqqYNO2lSDj5hIHmwzAGNwWMtAJXvyOuM4yiWHKvRxY7JaFMqNIZkc8P9s
+EvN0YkQstLOJAFUCBRAuMIROVQVm+k0MTuEBAYs+Af9jxMbuS3IXSuCbvPtrhC5o
+ROQslmnR2x5mZcikxlJer83nvfs3edu+792rkEhzvABaMz2+Dkr+usU36JIUUn3I
+iQBuAgUQLjAYIjh0K1zBsGrxAQFkOQLCAvXGviaSPPWJHdNzhPDIY6pTEJv4y+go
+rgq1WEftGwg//oetlTt7UL+ukJNo5c5iTuQ0FjXuibHszvh8rDDzcvffI8Ui3YwQ
+74wYJjcMNZ138RSNWxvKvtyJAHUCBRAuMAG8YNbVLHhmIHcBAQDwAv9Pery4VtiC
+Eta7i0Xt+CnZNAseAZVb6L7akKk6QNMX7BoVgwQjqUqhyAn3/qm/gdQdLa9Mh5U/
+8BsMlhKTrQL2mdhJlg0H/sZEFAtnvpyryTVmYI2YHD30Z9fHhOHPP/g=
+=JY+A
+-----END PGP PUBLIC KEY BLOCK-----
diff --git a/htdocs/sourceforge.css b/htdocs/sourceforge.css
new file mode 100644
index 000000000..a9c9a3474
--- /dev/null
+++ b/htdocs/sourceforge.css
@@ -0,0 +1,30 @@
+BODY { background-color: #FFFFFF; font-family: arial,helvetica,sans-serif; }
+
+A { text-decoration: none; color #6666FF; }
+A:visited { text-decoration: underline; color: #6666AA; }
+A:link { text-decoration: underline; color: #6666AA; }
+A:active { text-decoration: none; color: #6666AA; }
+A:hover { text-decoration: none; color: #FF6666 }
+OL,UL,P,BODY,TD,TR,TH,FORM,SPAN { font-family: arial,helvetica,sans-serif;color: #333333 }
+H1,H2,H3,H4,H5,H6 { font-family: arial,helvetica,sans-serif }
+PRE,TT { font-family: courier,sans-serif }
+
+SPAN.center { text-align: center }
+SPAN.boxspace { font-size: 2pt; }
+
+A.maintitlebar { color: #FFFFFF }
+A.maintitlebar:visited { color: #FFFFFF }
+
+A.sortbutton { color: #FFFFFF; text-decoration: underline; }
+A.sortbutton:visited { color: #FFFFFF; text-decoration: underline; }
+
+A.menus { color: #000000; text-decoration: underline; }
+A.menus:visited { color: #000000; text-decoration: underline; }
+
+A.tabs { color: #000000; text-decoration: underline; }
+A.tabs:visited { color: #000000; text-decoration: underline; }
+
+SPAN.alignright { text-align: right }
+SPAN.maintitlebar { font-size: 10pt; color: #FFFFFF }
+SPAN.titlebar { text-align: center; font-size: 10pt; color: #FFFFFF; font-weight: bold }
+TD.featurebox { font-size: small; }
diff --git a/htdocs/tytso-key.asc b/htdocs/tytso-key.asc
new file mode 100644
index 000000000..e4a84eb9d
--- /dev/null
+++ b/htdocs/tytso-key.asc
@@ -0,0 +1,63 @@
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.0.1 (GNU/Linux)
+Comment: For info see http://www.gnupg.org
+
+mQGiBDeLszwRBADImt2CfItwkMog1id4kERvJ7ElUIBv6AtPC5TJKCfkJm++eNLk
+uOA7C6s9CKyDrzDucUdljsax4+KQjMoYlTHkO4oPqfAVS/IwviCOLZXUDv/hP0HA
+xIPqIjBcfVqNIu4WhmsiT6bBCrMZrXgXCRA2rYjgEx4FMdwCjuTojF7euwCg/0Cu
+w+n0J5dW+kOwlhheGM6d5dUD/RCXYg0VlFc06zel41mEGTlxAhYCL581FxskBHXE
+CEdGX+2pyELG/Ogq3WMw8B/Za66NW9ymRQs+3RzN7uzUXmFNlm3U/KC5GepGjYJO
+2sKEeo/iIcYWWZlYMmw0XlvBf8pWvTpFkHU0aRUV1bDoo22dg6AOay9cbTKRWj20
+4lmFA/9+4Zv5QrUgNJyjPabbJXMXSKA5q1TcvTUT4eIs2OMCYvuXl32UQdJynvcy
+FeA8umPKt2dEJZD7XdTWhsn5E5rUWhq5prm9Iblt6GRV4FawnEapInUmTK2EW9zJ
+fK9XDqKjgeOfynZNctEEiqTzrB9TzHDHID8/dRXPjL3gX+P4dLQhVGhlb2RvcmUg
+VHMnbyA8dHl0c29AdmFsaW51eC5jb20+iEsEEBECAAsFAjeLszwECwMBAgAKCRBH
+X7oNED1AE953AJ9poNqHsbWldmt/8Bo5DNgj2VWvmgCdHtRObkfBTpw1u5QjisJX
+SZBrULSJAJUDBRA3i7RwRBVwzUZrQokBAfGiA/9gLc8ApRvLGVeG/JjmrSnweHAl
+8mGdhuvJ7Nd66ivyz7QqfjuiugiH1zNUnyE814yEf26Oq7QSVFE3Q8PUhFW+fSuW
+/dkZAKu1AbWa692Re+t0Y3T4yccYfU/hR133krQQIvKBIAa6yBOJDbIeDuSm+pNK
+iS/y78OdWsI893kD84hGBBARAgAGBQI45erDAAoJEBdE0doRDRQE8xEAoKLNC8cS
+D+pfOeM2TZ+HAb7QYcJSAKC1b5h+RV9GoYC5iGpufiz4blS5W4hGBBARAgAGBQI4
+4tdgAAoJEDZnYPF9LteIdc0AmgJY/FpTA3PxO4auSO7E4yiNVpuDAJsHQ01689Gj
+1hclCWtbrZuQSVaOAIkAlQMFEDeNBy5lNuPxgektkQEBX4MD/i7ip5eh5Z1wFycr
+1NuS4EEnvO9Qf6wsfF4F9W80p1CIA30lt0JofubNEa2qmDdzeGlby+dCR8x+BCOM
+ZJgbGYH1+hH+bwiuZ8IWEPTcHvqcf427VVwDBo2SmoY0dc9m52VXBerk4xl91j4V
+HYZ8z1qhqhhq36DopDbqD8OlYXwziEYEEBECAAYFAjhVONoACgkQfZ3uzivLxiHq
+1ACdECOYTAk/rouxT6qoJmAejPBXypEAn1ACU+DYlor6iL0BeATgC2lVcMmGiQEV
+AwUQN40NH44QmHz9z6BHAQEebAf7BWJyXtRPqTxpzIJse5ZHVBkLnqTzKXPXgTFI
+sEejCEGzZZTERGAZXI06ejK3AFSqUy7JKHq/tX/p0pAgDCuicDR7+GqxXY6eLkqr
+UrhB7jy0hilkIo0IpiuIWM+fACgV9G2FBY882LJ9WVPVjeHLf/QcUW9wQ09pBoVF
+2G1S0y10iPG5HoZ8CgqL2dcqBxqSuVdbOvb8Dz4ZA2SfZMsG0/nmOIhcDA6ur+si
+mG7d2EQAIe+6U9G5Eyf+tUxOlvWdhYfhtRFpezbq7YCqg9v77vLvdg8UmU/cilac
+N0U4Ev93hs+IlYiKakMyIrYGFSI/czfXzZjIhJGM1boeKIhF5IhGBBARAgAGBQI3
+jQSOAAoJEJWQJPlv1wT4uc0An1ftELDIu5cJue8Pce3d66e4ypjpAJ9nLTkDQbgU
+MluziAUSO6AdODWOB4hGBBARAgAGBQI3jQlhAAoJEKfoWUoGaJhESMsAnRSG/C7r
+o9bRnDNzw4l6ZtF4c7MDAKCl/lAFP/rCCL4XFBn1CgIdJB0UOYkAlQMFEDeNCTW+
+4pcrTzWDFQEBYqIEAIGXU0L+FbqAsxRSo6iT/e24yEZs16ywF2nqWYo+zwIXB5NM
+KIItkGoiZyeoAwVfIgc+GbW7j4YIe1IF5M0k65rhcdg++rQTIm70IXOGcWrzHLrt
+dxyOxSi8PZHuSKRlx0ScuO/PM9sjGORsm/UmodAnLA4lvcLvv3AtjL45etesiEYE
+EBECAAYFAjgrDqgACgkQwM9r9d5kYh7+FQCg0o7aQ2qdkfRbGNKEpo5fC8qY44AA
+n2RfpMbgmlYZeriqeyDfR1dmRTKdiEYEEBECAAYFAjeOEwYACgkQzMsU7mzdljT2
+CACeKTCP1tlCqN7q3VkN9XVPFIq90c0AoO57AB5bBdqqcsyMYqmdLM+gbVDuiEYE
+EBECAAYFAjeaVoYACgkQ7m8pKkseJ4QptwCfR4jJ2QwoCwRdiT63zsd+d7M1N9wA
+oNMtgYj3uhlWkO31qXSKIWf66QlBuQMNBDeLsz4QDADMHXdXJDhK4sTw6I4TZ5dO
+khNh9tvrJQ4X/faY98h8ebByHTh1+/bBc8SDESYrQ2DD4+jWCv2hKCYLrqmus2UP
+ogBTAaB81qujEh76DyrOH3SET8rzF/OkQOnX0ne2Qi0CNsEmy2henXyYCQqNfi3t
+5F159dSST5sYjvwqp0t8MvZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGn
+VqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFX
+klnN/biudE/F/Ha8g8VHMGHOfMlm/xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl
+9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhd
+ONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r
+0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVelMMm8AAgIL/0tHEAYy0t2zc7iu
+h+T4gCKFBEs6bExaXhXowfNe1ZvP4guW9kZcAr9DbLTBRyk0cpeXHtdUGc3T56Am
+KxY3SD0soxFQhniABdoFydYlJI95BkgG2wFdDO3zrvt3teeIHKRLl17LKO8/b8LO
+TLMlOvNgM8u1ji3l1y7MG6qpELWwUREjlmpVwFZ8FA9oEXPhpsByPSETnlQKH6BP
+DYgkJCe8ONshqYGkIzULxQNtsDUdwovPUQZ776nSQiYE7cCMQFyXbHwDcYGvmQw/
+xQnfG+tNdmo8BRjPNQix6bPo2vXnEuCL+Lcc2uDdJnlv9pM5Ic0TPYEHzvckR+PU
+IYRL0GKHeenf183spHSrQGhW7sxTMVOIftbSaAiQCRJbZ0UeadZfhYSAklIaUq8v
+DqxXH+4qz5PxYgxw/bX/O+C51+H9BmU5vUBnKCmUdtZjktoWQWqW38M/646LkGVn
+c33aF4kDokzHj2swkQUE0REFAFSgjawX1tJRayLXNmroVjfTqYg/AwUYN4uzPkdf
+ug0QPUATEQJVBACg02NXLN/nOAGzEFSBwAoDqfNCtkoAoIYM+qfcWeEEAarWKp+N
+oj9BQxFh
+=PCB8
+-----END PGP PUBLIC KEY BLOCK-----
diff --git a/web-update b/web-update
new file mode 100755
index 000000000..da105a57b
--- /dev/null
+++ b/web-update
@@ -0,0 +1,3 @@
+#!/bin/sh
+hg push ssh://tytso@e2fsprogs.sourceforge.net/e2web
+ssh tytso@e2fsprogs.sf.net cd e2web \; hg update
author	tytso <tytso@46e75558-b442-0410-83ab-e6570fdeb8bf>	2008-01-03 21:09:58 +0000
committer	tytso <tytso@46e75558-b442-0410-83ab-e6570fdeb8bf>	2008-01-03 21:09:58 +0000
commit	43aac7f52c5b538133bfa16fc282a32fe159cc81 (patch)
tree	94628450b9218a05da8b327520bb5f35089d2de7
parent	ad24aa9152ef6cd3742279754125af936a5daa12 (diff)
download	e2fsprogs-43aac7f52c5b538133bfa16fc282a32fe159cc81.tar.gz