X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=TODO;h=5b4c8432e2e54548eddc0de23e92afd0d943b664;hp=2109e1dfd5bf227162f41582d573757e4f2dfcfd;hb=2600359b9b520ab386f069fbbcd656e5cdbd9b76;hpb=8f382fd9e7b1745a4b1d6f25f0a775bed2573b8e

diff --git a/TODO b/TODO
index 2109e1d..5b4c843 100644
--- a/TODO
+++ b/TODO
@@ -120,17 +120,15 @@ Extra commands / functionality:
     chgrp
     grep (do it locally using pipe?)
     dd (?)
-    du
     ln / ln -s
-    mknod
     readlink
     utime / utimes / futimes / futimens / l..
-    mkfifo
     more mk*temp calls
-    readdir / readdir-and-stat
     some sort of alloc/fallocate/posix_fallocate call to create empty space
     realpath
     trunc[ate??]
+    getfattr (also useful because gives us access to NTFS datastreams)
+    setfattr
 
   ext2 properties:
     chattr
@@ -158,3 +156,33 @@ Extra commands / functionality:
 ----------------------------------------------------------------------
 
 Allow swap space from the guest to be used.  Is it a good idea?
+
+----------------------------------------------------------------------
+
+Need a way to query a binary or library file for its architecture.
+Using objdump or readelf?
+What about non-ELF files (eg. Windows, BSD).
+
+To do this properly requires some serious logic, eg. to cover Linux
+and Windows we'd need objdump and i686-pc-mingw32-objdump, and more to
+cover a.out, COFF and 64 bit Windows.  Therefore this cannot be done
+inside the daemon, and should be done by a separate, external program
+similar to virt-inspector.
+
+Probably we should go all the way and have virt-inspector able to
+determine kernel and userspace architectures of guests.
+
+----------------------------------------------------------------------
+
+Other initrd-* commands, such as:
+
+initrd-extract
+initrd-replace
+
+----------------------------------------------------------------------
+
+Control guestfish from a pipe.
+
+For shell scripts - they can start up a long-running guestfish process
+and intermittently send it commands.  Avoids the start-up overhead,
+but how do we reliably signal errors?
\ No newline at end of file