29 lines
1.1 KiB
Diff
29 lines
1.1 KiB
Diff
From cc0ae4acabfc857f2bcee828e725a9d69dab5735 Mon Sep 17 00:00:00 2001
|
|
From: "Richard W.M. Jones" <rjones@redhat.com>
|
|
Date: Tue, 12 Mar 2024 09:42:30 +0000
|
|
Subject: [PATCH] sysprep: Make clearer that we do not support Windows
|
|
|
|
Thanks: Dan Kenigsberg
|
|
(cherry picked from commit 82c0fb1231c1a9250104cff278f1c67ab482fa4b)
|
|
---
|
|
sysprep/virt-sysprep.pod | 6 ++----
|
|
1 file changed, 2 insertions(+), 4 deletions(-)
|
|
|
|
diff --git a/sysprep/virt-sysprep.pod b/sysprep/virt-sysprep.pod
|
|
index 0bcdc4dec..b48ac55c1 100644
|
|
--- a/sysprep/virt-sysprep.pod
|
|
+++ b/sysprep/virt-sysprep.pod
|
|
@@ -30,10 +30,8 @@ disk image to be writable as the non-root user running virt-sysprep.
|
|
|
|
"Sysprep" stands for "system preparation" tool. The name comes from
|
|
the Microsoft program F<sysprep.exe> which is used to unconfigure
|
|
-Windows machines in preparation for cloning them. Having said that,
|
|
-virt-sysprep does I<not> currently work on Microsoft Windows guests.
|
|
-We plan to support Windows sysprepping in a future version, and we
|
|
-already have code to do it.
|
|
+Windows machines in preparation for cloning them. (Virt-sysprep does
|
|
+not work on Microsoft Windows guests.)
|
|
|
|
=head1 OPTIONS
|
|
|