guestfish -i /dev/Guests/MyGuest
-You cannot use I<-a>, I<-m>, I<--listen> or I<--remote> in conjunction
-with this option, and options other than I<--ro> might not behave
-correctly.
+You cannot use I<-a>, I<-m>, I<--listen>, I<--remote> or I<--selinux>
+in conjunction with this option, and options other than I<--ro> might
+not behave correctly.
See also: L<virt-inspector(1)>.
This changes the C<-m> option so that mounts are done read-only
(see C<guestfs_mount_ro> in the L<guestfs(3)> manpage).
+=item B<--selinux>
+
+Enable SELinux support for the guest. See L<guestfs(3)/SELINUX>.
+
=item B<-v> | B<--verbose>
Enable very verbose messages. This is particularly useful if you find
rm '/"'
A few commands require a list of strings to be passed. For these, use
-a space-separated list, enclosed in quotes. For example:
+a whitespace-separated list, enclosed in quotes. Strings containing whitespace
+to be passed through must be enclosed in single quotes. A literal single quote
+must be escaped with a backslash.
vgcreate VG "/dev/sda1 /dev/sdb1"
+ command "/bin/echo 'foo bar'"
+ command "/bin/echo \'foo\'"
=head1 WILDCARDS AND GLOBBING
guestfish --remote=$pid1 cmd
guestfish --remote=$pid2 cmd
-=head2 STANDARD OUTPUT DURING REMOTE CONTROL
-
-Because of limitations in the C<eval> statement, stdout from the
-listener is currently redirected to C</dev/null>.
-
-Stderr is unchanged.
-
=head2 REMOTE CONTROL DETAILS
Remote control happens over a Unix domain socket called
the qemu which was found at compile time by the configure script is
used.
+=item LIBGUESTFS_TRACE
+
+Set C<LIBGUESTFS_TRACE=1> to enable command traces.
+
=item PAGER
The C<more> command uses C<$PAGER> as the pager. If not