TODO

   1 2.14:
   2 ====
   3
   4  * clean up code, gcc warnings
   5    (try compilation with "-Wall -Wp,-D_FORTIFY_SOURCE=2")
   6
   7  * add --help and --version to all commands
   8
   9  * don't duplicate glibc code when possible,
  10    for example things like:
  11         - err.h (error(), warn(), ...)
  12         - canonicalize_file_name()
  13         - program_invocation_short_name
  14
  15  * try improve compilation against others libc:
  16         - uClibc
  17         - ???
  18
  19  * create lib/blkdevsize.c with blkdev_get_size(), blkdev_get_sectors(),
  20    blkdev_get_pages()  (see mkswap.c and fdisk/disksize.c)
  21
  22  * use EXIT_FAILED and EXIT_SUCCESS
  23
  24  * rewrite the replay script to C to avoid dependence on perl
  25
  26  * cryptoloop support in losetup (the patch is on the way)
  27
  28         Date:   Tue, 28 Aug 2007 15:23:58 -0600
  29         From: LaMont Jones <lamont@mmjgroup.com>
  30         Subject: Re: [PATCH] losetup: support password hashing and specifying the key length
  31
  32  * add an option to the cal command to control highlight date
  33
  34  * convet po/ files to UTF-8
  35
  36  * use rpmatch() for all Y/N questions
  37
  38  * non-linux support
  39
  40         Date:   Sat, 11 Aug 2007 00:43:00 +0200
  41         From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  42         Subject: non-linux support
  43
  44  * CFS aware chrt in util linux (the patch is on the way)
  45
  46         From: Christian Casteyde <casteyde.christian@free.fr>
  47         Subject: CFS aware chrt in util linux
  48         Date: Sat, 21 Jul 2007 19:46:27 +0200
  49
  50  * mount: nofail mount option (the patch is on the way)
  51
  52         From: Matthias Koenig <mkoenig@suse.de>
  53         To: util-linux-ng@vger.kernel.org
  54         Subject: [PATCH] mount: nofail mount option
  55
  56  * mount -a -- reorder fstab entries by paths before mount (just idea only)
  57
  58  * mount -a  (just idea only)
  59
  60         Date:   Sun, 3 Jun 2007 18:04:24 +0300 (MET DST)
  61         From: Szabolcs Szakacsits <szaka@sienet.hu>
  62
  63         In the past the right record order could be figured out easily by just
  64         checking out fstab (if one knew what to look for) but considering the
  65         fastly increasing number of user space file systems and their usage, with
  66         their path, library, etc dependencies, it's getting trickier and is a black
  67         magic for most users because they simply expect drives to be mounted
  68         independently of their order in fstab.
  69
  70         One typical, wrongly edited fstab example is:
  71
  72           /dev/hda2 /             ext3      defaults  1 1
  73           /dev/hda1 /mnt/windows  ntfs-3g   defaults  0 0
  74           /dev/hda3 /usr          ext3      defaults  0 0
  75
  76         The events:
  77
  78           mount  ->  /sbin/mount.ntfs-3g  ->
  79                  ->  resolves to <path1>/ntfs-3g via a symlink ->
  80                  ->  ntfs-3g requires at least <path2>/libfuse*
  81
  82         There are many potential solutions. For example installing everything on
  83         the root file system which may be needed for successful mount. But this
  84         is not always feasible or practical since we could end up putting almost
  85         everything on the root file system in the end.
  86
  87         Another idea is an improved mount strategy:
  88
  89           do {
  90                 try to mount all unmounted entries
  91           } while (not all mounted && at least one new was successfully mounted)
  92
  93
  94 v2.??:
  95 =====
  96
  97  * rewrite ipcs to use /proc/sys/kernel rather than unreliable syscalls
  98    (there are problems with 32bit userspace on 64bit kernel)
  99
 100  * minix v3
 101
 102         From: Matthias Koenig <mkoenig@suse.de>
 103         Date:   Tue, 25 Sep 2007 12:00:01 +0200
 104
 105         It seems that the kernel has support for minix fs v3
 106         (though I have not tried it, just inspected some code when
 107         trying to find a mkfs.minix issue).
 108         It might be worth a thought implementing v3 support
 109         (though I am not really sure how much people us minix fs ;-)
 110         This might require some major code cleanup in mkfs.minix.
 111