2.14:
====

 * clean up code, gcc warnings
   (try compilation with "-Wall -Wp,-D_FORTIFY_SOURCE=2")

 * add --help and --version to all commands

 * don't duplicate glibc code when possible,
   for example things like:
	- err.h (error(), warn(), ...)
	- canonicalize_file_name()
	- program_invocation_short_name

 * try improve compilation against others libc:
	- uClibc
	- ???

 * create lib/blkdevsize.c with blkdev_get_size(), blkdev_get_sectors(),
   blkdev_get_pages()  (see mkswap.c and fdisk/disksize.c)

 * use EXIT_FAILED and EXIT_SUCCESS

 * rewrite the replay script to C to avoid dependence on perl

 * cryptoloop support in losetup (the patch is on the way)

	Date:   Tue, 28 Aug 2007 15:23:58 -0600
	From: LaMont Jones <lamont@mmjgroup.com>
	Subject: Re: [PATCH] losetup: support password hashing and specifying the key length

 * convet po/ files to UTF-8

 * use rpmatch() for all Y/N questions

 * non-linux support

	Date:   Sat, 11 Aug 2007 00:43:00 +0200
	From: Samuel Thibault <samuel.thibault@ens-lyon.org>
	Subject: non-linux support

 * CFS aware chrt in util linux (the patch is on the way)

	From: Christian Casteyde <casteyde.christian@free.fr>
	Subject: CFS aware chrt in util linux
	Date: Sat, 21 Jul 2007 19:46:27 +0200

 * mount: nofail mount option (the patch is on the way)

	From: Matthias Koenig <mkoenig@suse.de>
	To: util-linux-ng@vger.kernel.org
	Subject: [PATCH] mount: nofail mount option

 * mount -a -- reorder fstab entries by paths before mount (just idea only)

 * mount -a  (just idea only)

        Date:   Sun, 3 Jun 2007 18:04:24 +0300 (MET DST)
        From: Szabolcs Szakacsits <szaka@sienet.hu>

	In the past the right record order could be figured out easily by just
	checking out fstab (if one knew what to look for) but considering the
	fastly increasing number of user space file systems and their usage, with
	their path, library, etc dependencies, it's getting trickier and is a black
	magic for most users because they simply expect drives to be mounted
	independently of their order in fstab.

	One typical, wrongly edited fstab example is:

	  /dev/hda2 /             ext3      defaults  1 1
	  /dev/hda1 /mnt/windows  ntfs-3g   defaults  0 0
	  /dev/hda3 /usr          ext3      defaults  0 0

	The events:

	  mount  ->  /sbin/mount.ntfs-3g  ->
		 ->  resolves to <path1>/ntfs-3g via a symlink ->
		 ->  ntfs-3g requires at least <path2>/libfuse*

	There are many potential solutions. For example installing everything on
	the root file system which may be needed for successful mount. But this
	is not always feasible or practical since we could end up putting almost
	everything on the root file system in the end.

	Another idea is an improved mount strategy:

	  do {
		try to mount all unmounted entries
	  } while (not all mounted && at least one new was successfully mounted)


v2.??:
=====

 * rewrite ipcs to use /proc/sys/kernel rather than unreliable syscalls
   (there are problems with 32bit userspace on 64bit kernel)

 * minix v3

	From: Matthias Koenig <mkoenig@suse.de>
	Date:   Tue, 25 Sep 2007 12:00:01 +0200

	It seems that the kernel has support for minix fs v3
	(though I have not tried it, just inspected some code when
	trying to find a mkfs.minix issue).
	It might be worth a thought implementing v3 support
	(though I am not really sure how much people us minix fs ;-)
	This might require some major code cleanup in mkfs.minix.