From 701667b6f581a824059c4da50eb4df176decbb82 Mon Sep 17 00:00:00 2001 From: Cole Robinson Date: Thu, 31 Jul 2025 15:27:38 -0400 Subject: [PATCH] docs: Fix dead ntfs-3g doc links --- generator/actions_core.ml | 4 ++-- lib/guestfs.pod | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/generator/actions_core.ml b/generator/actions_core.ml index 0f39fd509..108494ece 100644 --- a/generator/actions_core.ml +++ b/generator/actions_core.ml @@ -4661,8 +4661,8 @@ as F may appear as F or F they were created. In Windows itself this would not be a problem. -Bug or feature? You decide: -L +Bug or feature? You decide. See the relevant entry in the ntfs-3g FAQ: +L C attempts to resolve the true case of each element in the path. It will return a resolved path if either the diff --git a/lib/guestfs.pod b/lib/guestfs.pod index f69d5a070..505978aa1 100644 --- a/lib/guestfs.pod +++ b/lib/guestfs.pod @@ -984,7 +984,7 @@ Ntfs-3g tries to rewrite "Junction Points" and NTFS "symbolic links" to provide something which looks like a Linux symlink. The way it tries to do the rewriting is described here: -L +L The essential problem is that ntfs-3g simply does not have enough information to do a correct job. NTFS links can contain drive letters @@ -1003,7 +1003,7 @@ format documented in various places around the web). There are other useful extended attributes that can be read from ntfs-3g filesystems (using L). See: -L +L =head3 WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP -- 2.47.1