]> git.ipfire.org Git - thirdparty/util-linux.git/blame - TODO
setarch: add --3gb option fot compatibility with Debian linux{32,64} command
[thirdparty/util-linux.git] / TODO
CommitLineData
f93a4afd 1
f93a4afd 2
883fff9f
KZ
3- convet po/ files to UTF-8
4
883fff9f
KZ
52.14:
6====
f93a4afd 7
b622c840
KZ
8- add an option to the cal command to control highlight date
9 (cal -v YYYY/MM/DD)
10
883fff9f
KZ
11- use rpmatch() for all Y/N ?
12
13- rewrite ipcs to use /proc/sys/kernel rather than unreliable syscalls
14 (there are problems with 32bit userspace on 64bit kernel)
15
16- remove support for old system headers (like missing ioctls, ..)
f93a4afd
KZ
17
18- remove from all places direct calls of ioctl(BLKGETSIZE) and move it
19 lib/blkdevsize.c: blkdev_get_size(), blkdev_get_sectors(), blkdev_get_pages()
20 (see mkswap.c and fdisk/disksize.c)
21
85ffb958 22- use EXIT_FAILED and EXIT_SUCCESS from stdlib.h for exit() codes
b8d1314d 23
883fff9f
KZ
24- rewrite the replay script to C to avoid dependence on perl
25
26- "mount -a":
8b0f4ae9 27
883fff9f
KZ
28 Date: Sun, 3 Jun 2007 18:04:24 +0300 (MET DST)
29 From: Szabolcs Szakacsits <szaka@sienet.hu>
8b0f4ae9 30
883fff9f
KZ
31 In the past the right record order could be figured out easily by just
32 checking out fstab (if one knew what to look for) but considering the
33 fastly increasing number of user space file systems and their usage, with
34 their path, library, etc dependencies, it's getting trickier and is a black
35 magic for most users because they simply expect drives to be mounted
36 independently of their order in fstab.
31cc369d 37
883fff9f 38 One typical, wrongly edited fstab example is:
8b0f4ae9 39
883fff9f
KZ
40 /dev/hda2 / ext3 defaults 1 1
41 /dev/hda1 /mnt/windows ntfs-3g defaults 0 0
42 /dev/hda3 /usr ext3 defaults 0 0
8b0f4ae9 43
883fff9f 44 The events:
1c51a368 45
883fff9f
KZ
46 mount -> /sbin/mount.ntfs-3g ->
47 -> resolves to <path1>/ntfs-3g via a symlink ->
48 -> ntfs-3g requires at least <path2>/libfuse*
49
50 There are many potential solutions. For example installing everything on
51 the root file system which may be needed for successful mount. But this
52 is not always feasible or practical since we could end up putting almost
53 everything on the root file system in the end.
54
55 Another idea is an improved mount strategy:
56
57 do {
58 try to mount all unmounted entries
59 } while (not all mounted && at least one new was successfully mounted)
09dd84ca 60