set-append and set-kernel parameters are both nullable.

[libguestfs.git] / TODO

diff --git a/TODO b/TODO
index 2109e1d..16d6880 100644 (file)
--- a/TODO
+++ b/TODO
@@ -14,11 +14,11 @@ http://sourceforge.net/project/showfiles.php?group_id=121684&package_id=150116
 
 ----------------------------------------------------------------------
 
-BufferIn and BufferOut should turn into <char *, int> and simple
-strings in other languages that can handle 8 bit clean strings.
+BufferIn should turn into <char *, int> and simple strings in other
+languages that can handle 8 bit clean strings.
+
 Limit on transfers would still be 2MB for these types.
  - then implement write-file properly
- - and implement read-file
 
 ----------------------------------------------------------------------
 
@@ -120,14 +120,10 @@ 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??]
@@ -158,3 +154,47 @@ 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
+
+----------------------------------------------------------------------
+
+Some easy non-Augeas methods to edit configuration files.
+I'm thinking:
+
+  replace /etc/file key value
+
+which would look in /etc/file for any instances of
+
+  key=...
+  key ...
+  key:...
+
+and replace them with
+
+  key=value
+  key value
+  key:value
+
+That would solve about 50% of reconfiguration needs, and for the
+rest you'd use Augeas, 'download'+'upload' or 'edit'.