nbdkit/0007-vddk-Small-copyedits-t...

48 lines
1.8 KiB
Diff

From 0923b0e70735139e1a548addecf6e20c567a96a0 Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Sat, 30 Oct 2021 08:25:03 +0100
Subject: [PATCH] vddk: Small copyedits to README.VDDK
Clean up the sentence about LD_LIBRARY_PATH which could be
misconstrued to mean that we recommend setting this (we do not).
Remove "bugs" section which was wrong.
(cherry picked from commit 55c2a029692fc20bf4a7d4ae857e3609b45ec3dd)
---
plugins/vddk/README.VDDK | 17 +++--------------
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/plugins/vddk/README.VDDK b/plugins/vddk/README.VDDK
index f2204d75..c38eaa51 100644
--- a/plugins/vddk/README.VDDK
+++ b/plugins/vddk/README.VDDK
@@ -14,21 +14,10 @@ export VMDK files and VMware disks over NBD.
You do NOT require VDDK to compile the plugin, and the plugin does not
contain any VMware code. You only need VDDK at runtime. The plugin
uses dlopen to load the library from a directory determined by the
-configuration parameter libdir (LD_LIBRARY_PATH or the standard shared
-library locations can also be used, although that approach is not
-recommended).
+configuration parameter libdir. It is NOT recommended to put VDDK in
+your regular library path (eg /usr/lib) because it contains components
+that conflict with system libraries.
After building nbdkit-vddk-plugin.so, read the man page to find out
how to use it (nbdkit-vddk-plugin(1)). You'll probably also want to
read the VDDK developer documentation.
-
-Bugs
-----
-
-Write calls sometimes return VIX_E_DISK_OUTOFRANGE even for write
-requests which are well inside the disk.
-
-The way we do threading in nbdkit is not congruent with the way you're
-supposed to call VDDK from multithreaded programs. For more
-information see:
-https://www.redhat.com/archives/libguestfs/2019-October/msg00062.html
--
2.31.1