Updated TODO:
(notes:
- this list doesn't include all actually waiting patches
- "mount -a" ideas are just ideas only...)
Your suggestion and comments, as always, are welcomed!
Karel
* 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@xxxxxxxxxxxx>
Subject: Re: [PATCH] losetup: support password hashing and specifying the key length
* add an option to the cal command to control highlight date
* 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@xxxxxxxxxxxx>
Subject: non-linux support
* CFS aware chrt in util linux (the patch is on the way)
From: Christian Casteyde <casteyde.christian@xxxxxxx>
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@xxxxxxx>
To: util-linux-ng@xxxxxxxxxxxxxxx
Subject: [PATCH] mount: nofail mount option
* mount -a -- reorder fstab entries by paths before mount (just idea only)
* mount -a -F -- (just idea only)
fstab:
/dev/foo /usr
/dev/bar /usr/local
/dev/xxx /xxx
= two processes:
1) /usr, /usr/local
2) /xxx
(now there is process per fstab entry, so /usr and /usr/local
could be mounted in wrong order))
* mount -a (just idea only)
Date: Sun, 3 Jun 2007 18:04:24 +0300 (MET DST)
From: Szabolcs Szakacsits <szaka@xxxxxxxxx>
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)
--
Karel Zak <kzak@xxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
