daemon/readdir: avoid a small leak

[libguestfs.git] / TODO

diff --git a/TODO b/TODO
index 7696daa..6a89409 100644 (file)
--- 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
@@ -155,12 +153,28 @@ Extra commands / functionality:
     pivot_root
     fts(3) / ftw(3)
 
-  guestfish only:
-    more/less (like cat, but pipes it through $PAGER)
-    cmd | pipe
-    cat file | pipe-cmd should have a generic form? like
-      'file | less' or 'file | sort'?
-
 ----------------------------------------------------------------------
 
 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