From 248465a6206dd3881adebcd2c17ea0a0c2f59742 Mon Sep 17 00:00:00 2001 From: "Richard W.M. Jones" Date: Thu, 13 Oct 2011 23:29:58 +0100 Subject: [PATCH] virt-sysprep: More clarifications to the man page. --- clone/virt-sysprep.pod | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/clone/virt-sysprep.pod b/clone/virt-sysprep.pod index ecd500f..eb5c430 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 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 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 -- 1.8.3.1