]>
Commit | Line | Data |
---|---|---|
6d99d91c | 1 | * use TZ=UTC for tests |
f93a4afd | 2 | |
f4a94b4b KZ |
3 | * add NLS and err.h stuff to schedutils (chrt.c, taskset.c) |
4 | ||
846baede KZ |
5 | * move libblkid to util-linux-ng (see the topic/blkid branch) |
6 | ||
7 | * add mllockall() and SCHED_FIFO to hwclock, | |
8 | see http://lkml.org/lkml/2008/10/12/132 | |
3d24cec1 | 9 | |
8f66fc25 KZ |
10 | * partx: copy sun.c, mac.c and dash.c from kpartx |
11 | git://git.kernel.org/pub/scm/linux/storage/multipath-tools/.git | |
12 | ||
13 | It would be nice to merge kpartx and partx to the one project. We duplicate | |
14 | a lot of code (include losetup code in kpartx). | |
15 | ||
66cb1233 | 16 | * swapon -s -- LABELs support |
b622c840 | 17 | |
66cb1233 KZ |
18 | Although mkswap has recently been -L option to create a label nothing appears to |
19 | have been change to swapon to display said labels. (rh#430386) | |
883fff9f | 20 | |
74a9c6f7 KZ |
21 | * use canonicalize_file_name() when exist in glibc (see lib/canonicalize.v) |
22 | ||
d3bb3bc8 | 23 | * try improve compilation against others libc: |
66cb1233 | 24 | - klibc |
d3bb3bc8 KZ |
25 | - ??? |
26 | ||
d3bb3bc8 | 27 | * use rpmatch() for all Y/N questions |
f93a4afd | 28 | |
d3bb3bc8 KZ |
29 | * mount -a -- reorder fstab entries by paths before mount (just idea only) |
30 | ||
31 | * mount -a (just idea only) | |
8b0f4ae9 | 32 | |
883fff9f KZ |
33 | Date: Sun, 3 Jun 2007 18:04:24 +0300 (MET DST) |
34 | From: Szabolcs Szakacsits <szaka@sienet.hu> | |
8b0f4ae9 | 35 | |
883fff9f KZ |
36 | In the past the right record order could be figured out easily by just |
37 | checking out fstab (if one knew what to look for) but considering the | |
38 | fastly increasing number of user space file systems and their usage, with | |
39 | their path, library, etc dependencies, it's getting trickier and is a black | |
40 | magic for most users because they simply expect drives to be mounted | |
41 | independently of their order in fstab. | |
31cc369d | 42 | |
883fff9f | 43 | One typical, wrongly edited fstab example is: |
8b0f4ae9 | 44 | |
883fff9f KZ |
45 | /dev/hda2 / ext3 defaults 1 1 |
46 | /dev/hda1 /mnt/windows ntfs-3g defaults 0 0 | |
47 | /dev/hda3 /usr ext3 defaults 0 0 | |
8b0f4ae9 | 48 | |
883fff9f | 49 | The events: |
1c51a368 | 50 | |
883fff9f KZ |
51 | mount -> /sbin/mount.ntfs-3g -> |
52 | -> resolves to <path1>/ntfs-3g via a symlink -> | |
53 | -> ntfs-3g requires at least <path2>/libfuse* | |
54 | ||
55 | There are many potential solutions. For example installing everything on | |
56 | the root file system which may be needed for successful mount. But this | |
57 | is not always feasible or practical since we could end up putting almost | |
58 | everything on the root file system in the end. | |
59 | ||
60 | Another idea is an improved mount strategy: | |
61 | ||
62 | do { | |
63 | try to mount all unmounted entries | |
64 | } while (not all mounted && at least one new was successfully mounted) | |
09dd84ca | 65 | |
12318be4 KZ |
66 | * agetty: use nl_langinfo() for days and months rather than hardcoded |
67 | English names. | |
68 | ||
669eecf3 KZ |
69 | * rewrite ipcs to use /proc/sys/kernel rather than unreliable syscalls |
70 | (there are problems with 32bit userspace on 64bit kernel) | |
71 | ||
72 | * minix v3 | |
73 | ||
74 | From: Matthias Koenig <mkoenig@suse.de> | |
75 | Date: Tue, 25 Sep 2007 12:00:01 +0200 | |
76 | ||
77 | It seems that the kernel has support for minix fs v3 | |
78 | (though I have not tried it, just inspected some code when | |
79 | trying to find a mkfs.minix issue). | |
80 | It might be worth a thought implementing v3 support | |
81 | (though I am not really sure how much people us minix fs ;-) | |
82 | This might require some major code cleanup in mkfs.minix. | |
d3bb3bc8 | 83 | |
8da18ddb KZ |
84 | * rtcwake does not support wake from S5/off |
85 | http://bugzilla.redhat.com/show_bug.cgi?id=449115 | |
86 | ||
87 | * add SELinux security contexts support to the 'ipcs' utility | |
88 | http://bugzilla.redhat.com/show_bug.cgi?id=225342 | |
89 | ||
90 | Would be great to list the current system IPC Objects with their respective | |
91 | security labels (where allowed) with something like 'ipcs -Z' - following the | |
92 | way other tools reports those. | |
93 | ||
94 |