summaryrefslogtreecommitdiffstats
path: root/clone
diff options
context:
space:
mode:
authorRichard W.M. Jones <rjones@redhat.com>2011-10-13 23:29:58 +0100
committerRichard W.M. Jones <rjones@redhat.com>2011-10-13 23:29:58 +0100
commit248465a6206dd3881adebcd2c17ea0a0c2f59742 (patch)
treefee6faabd636df5d41f71ceaeece75bf33876458 /clone
parent42f3abe42d601c5d0a1521a36db54dea705a03c7 (diff)
downloadlibguestfs-248465a6206dd3881adebcd2c17ea0a0c2f59742.tar.gz
libguestfs-248465a6206dd3881adebcd2c17ea0a0c2f59742.tar.xz
libguestfs-248465a6206dd3881adebcd2c17ea0a0c2f59742.zip
virt-sysprep: More clarifications to the man page.
Diffstat (limited to 'clone')
-rwxr-xr-xclone/virt-sysprep.pod12
1 files changed, 5 insertions, 7 deletions
diff --git a/clone/virt-sysprep.pod b/clone/virt-sysprep.pod
index ecd500f4..eb5c430c 100755
--- a/clone/virt-sysprep.pod
+++ b/clone/virt-sysprep.pod
@@ -240,7 +240,7 @@ undesirable. Erasing the udev persistent net rules avoids this.
Remove the yum UUID.
-yum creates a fresh UUID the next time it runs when it notices that
+Yum creates a fresh UUID the next time it runs when it notices that
the original UUID has been erased.
=head1 COPYING AND CLONING
@@ -412,12 +412,10 @@ thus is ideal for cloning guests from a template.
=head1 SECURITY
-Although virt-sysprep removes some sensitive information from
-the guest, it does not pretend to remove all of it. You should
-examine the L</OPERATIONS> above, and the implementation of
-the operations in the shell script.
-
-You should also examine the guest afterwards.
+Although virt-sysprep removes some sensitive information from the
+guest, it does not pretend to remove all of it. You should examine
+the L</OPERATIONS> above, and the implementation of the operations in
+the shell script. You should also examine the guest afterwards.
Sensitive files are simply removed. The data they contained may still
exist on the disk, easily recovered with a hex editor or undelete