docs: cleanup TODO

Signed-off-by: Karel Zak <kzak@redhat.com>
This commit is contained in:
Karel Zak 2012-11-27 11:13:42 +01:00
parent 742b877b2d
commit bdc251e60a
1 changed files with 0 additions and 65 deletions

View File

@ -1,22 +1,11 @@
Note that items with (!) have high priority.
su
--
- log all attempts to lastlog if authentication by
password is required (pam_authenticate()). See login.c for more details.
https://bugzilla.redhat.com/show_bug.cgi?id=866682
lscpu
-----
- detect more hypervisors, see 'virt-what' shell script
http://people.redhat.com/~rjones/virt-what/
dmesg
-----
- add --color to colorize err and panic messages
minix (fsck, mkfs)
------------------
@ -59,13 +48,6 @@ libmount (mount/umount)
translate the device name to backing file and then search in mtab for the
filename. See loopdev_get_loopfile().
- add ---target-prefix option to specify prefix for mountpoints
so then you can
mount --fstab=/etc/fstab.sandbox -a --target-prefix=/mnt/sandbox
to create a new hierarchy of filesystems at sandbox
libblkd and libmount
--------------------
@ -148,61 +130,14 @@ fdisk(s)
misc
----
- switch_root:
- move all mountpoints to the newroot (there are hardcoded /proc /sys and /dev paths now)
- add --dont-move[=<list of dirs>] options
- use TZ=UTC
- add mllockall() and SCHED_FIFO to hwclock,
see http://lkml.org/lkml/2008/10/12/132
- (!) rewrite ipcs to use /proc/sys/kernel rather than unreliable syscalls
(there are problems with 32bit userspace on 64bit kernel)
---------------
exotic requests
---------------
- 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)
- add SELinux security contexts support to the 'ipcs' utility
http://bugzilla.redhat.com/show_bug.cgi?id=225342