X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=fuse%2Fguestmount.pod;h=338af97bdefd6d4f1ba7b86d65bc7186269a7e34;hb=290e8864fff8a390d6bbbe20fe9781a03edb4c6a;hp=4ddea5fd97ca30add441847fbc462dc572dcb155;hpb=a232e62dcf508517a32b9a8d7e4529e827be721b;p=libguestfs.git

diff --git a/fuse/guestmount.pod b/fuse/guestmount.pod
index 4ddea5f..338af97 100644
--- a/fuse/guestmount.pod
+++ b/fuse/guestmount.pod
@@ -57,9 +57,9 @@ For a libvirt guest called "Guest" you could do:
  guestmount -d Guest -i --ro /mnt
 
 If you don't know what filesystems are contained in a guest or
-disk image, use L<virt-list-filesystems(1)> first:
+disk image, use L<virt-filesystems(1)> first:
 
- virt-list-filesystems MyGuest
+ virt-filesystems MyGuest
 
 If you want to trace the libguestfs calls but without excessive
 debugging information, we recommend:
@@ -143,6 +143,11 @@ mounted on the real virtual machine.
 Read key or passphrase parameters from stdin.  The default is
 to try to read passphrases from the user by opening C</dev/tty>.
 
+=item B<--live>
+
+Connect to a live virtual machine.
+(Experimental, see L<guestfs(3)/ATTACHING TO RUNNING DAEMONS>).
+
 =item B<-m dev[:mnt]> | B<--mount dev[:mnt]>
 
 Mount the named partition or logical volume on the given mountpoint
@@ -203,6 +208,8 @@ disk.  If the guest is running and this option is I<not> supplied,
 then there is a strong risk of disk corruption in the guest.  We try
 to prevent this from happening, but it is not always possible.
 
+See also L<guestfish(1)/OPENING DISKS FOR READ AND WRITE>.
+
 =item B<--selinux>
 
 Enable SELinux support for the guest.
@@ -215,9 +222,14 @@ Enable verbose messages from underlying libguestfs.
 
 Display the program version and exit.
 
+=item B<-w> | B<--rw>
+
+This option does nothing at the moment.
+See L<guestfish(1)/OPENING DISKS FOR READ AND WRITE>.
+
 =item B<-x> | B<--trace>
 
-Trace libguestfs calls.
+Trace libguestfs calls and entry into each FUSE function.
 
 This also stops the daemon from forking into the background.