X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=TODO;h=e9716f23d4ce1edbc787bd17467c52d9ce0ecbe4;hp=e90d408d45b933884dcfef009e4dc73b26fd15a5;hb=61da709722ec244da1c3c7d4f1a8706f76687cb3;hpb=e832959a4d5645cb0168bd7b810d5cfcd6767168

diff --git a/TODO b/TODO
index e90d408..e9716f2 100644
--- a/TODO
+++ b/TODO
@@ -29,6 +29,11 @@ Haskell bindings
 
 Complete the Haskell bindings (see discussion on haskell-cafe).
 
+PHP bindings
+------------
+
+Add bindtests to PHP bindings.
+
 Complete bind tests
 -------------------
 
@@ -85,11 +90,6 @@ This is mainly useful from live CDs, ie. virt-p2v.
 Should we bother having the daemon at all and just link the guestfsd
 code directly into libguestfs?
 
-Supermin appliance to febootstrap
----------------------------------
-
-Supermin appliance functionality should be moved into febootstrap.
-
 Ideas for extra commands
 ------------------------
 
@@ -279,8 +279,7 @@ http://sourceforge.net/projects/tripwire/
 -N option should be generated
 -----------------------------
 
-'-N' option should be generated code, and should generate
-documentation in guestfish(1) manpage.
+'-N' option should generate documentation in guestfish(1) manpage.
 
 Fix 'file'
 ----------
@@ -295,6 +294,9 @@ Occasionally we break virt-inspector through some change.  We should
 add a regression test for it.  However this is hard because we'd need
 to avoid having to carry huge images.
 
+Update: I managed to fit a real-but-minimal Fedora 13 image into 6.2 MB.
+See: http://rwmj.wordpress.com/2010/09/07/tip-pack-files-into-a-new-disk-image/#content
+
 Freeze/thaw filesystems
 -----------------------
 
@@ -323,6 +325,15 @@ New guestfish commands
 
 'list-filesystems' => list mountable filesystems
 
+We could implement this as a new API call, replacing a number of areas
+of the current code where this is done already (in virt-inspector and
+elsewhere).  What we normally do to find out if a partition contains a
+mountable filesystem is to just blindly mount it, and see if that
+succeeds.  However the kernel won't let us do this if the filesystem
+is already mounted somewhere, so a naive implementation of this in the
+daemon won't work.  We would have to check if the partition was
+already mounted.
+
 Could we make guestfish interactive if commands are used without params?
 ------------------------------------------------------------------------
 
@@ -336,7 +347,61 @@ Common problems
 
 How can we solve these common user problems?
 
-- http://lists.fedoraproject.org/pipermail/users/2010-June/374931.html
-  In guestfish, specified -m non-existent filesystem.  We could suggest
-  a list of filesystems, or suggest they run the virt-list-filesystems
-  command.
+[space for common problems here]
+
+Better support for encrypted devices
+------------------------------------
+
+Currently LUKS support only works if the device contains volume
+groups.  If it contains, eg., partitions, you cannot access them.
+We would like to add:
+
+  - An easier way to use this from guestfish.
+  - Direct access to the /dev/mapper device (eg. if it contains
+    anything apart from VGs).
+
+Display image as PS
+-------------------
+
+Display the structure of an image file as a PS.
+
+Greater use of blkid / libblkid
+-------------------------------
+
+guestfs_zero should use wipefs.  See wipefs(8).
+
+There are various useful functions in libblkid for listing partitions,
+devices etc which we are essentially duplicating in the daemon.  It
+would make more sense to just use libblkid for this.
+
+There are some places where we call out to the 'blkid' program.  This
+might be replaced by direct use of the library (if this is easier).
+
+Remove repo from appliance name
+-------------------------------
+
+There's no need to have the appliance name contain the repository name
+(ie initramfs.x86_64.img instead of initramfs.fedora-13.x86_64.img).
+
+Visualization
+-------------
+
+Eric Sandeen pointed out the blktrace tool which is a better way of
+capturing traces than using patched qemu (see
+contrib/visualize-alignment).  We would still use the same
+visualization tools in conjunction with blktrace traces.
+
+Virt-df UUID
+------------
+
+Virt-df and any other tools with --csv output should be able to print
+UUID of domain.  This allows you to track the real domain across
+renames etc.
+
+Add-domain command
+------------------
+
+guestfs_add_domain (g, "libvirt-dom");
+
+However this would need to not depend on libvirt, eg. loading it
+on demand.