From 52f0d1e1d86548894477f78601e0c1de7a3343f7 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Thu, 6 Sep 2018 17:06:51 -0700 Subject: [PATCH] Changelog, FAQ: add info about reparse point and case-sensitivity fix --- Changelog.asciidoc | 1 + doc/Frequently-Asked-Questions.asciidoc | 6 ++++-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/Changelog.asciidoc b/Changelog.asciidoc index ca1f1fce..18a4c866 100644 --- a/Changelog.asciidoc +++ b/Changelog.asciidoc @@ -12,6 +12,7 @@ Changes since v1.3: * New sample file system "airfs" contributed by @JohnOberschelp. Airfs is an in-memory file system like Memfs on which it is based on; it has received substantial improvements in how the file name space is maintained and has been modified to use modern C++ techniques by John. * New sample file system "passthrough-fuse3" passes all operations to an underlying file system. This file system is built using the FUSE3 API. It builds and runs on both Windows and Cygwin. * The FUSE layer now supports multiple file systems within a single process. This is a long standing problem that has been fixed. (GitHub issue #135.) +* The FSD includes an experimental fix for a Windows problem: that case-sensitive file systems do not work properly when mounted as directories. See the relevant FAQ entry. v1.4B2 (2018.2 B2):: diff --git a/doc/Frequently-Asked-Questions.asciidoc b/doc/Frequently-Asked-Questions.asciidoc index f266a266..cc8d318e 100644 --- a/doc/Frequently-Asked-Questions.asciidoc +++ b/doc/Frequently-Asked-Questions.asciidoc @@ -17,7 +17,9 @@ Disconnecting (unmapping) a network drive does not work.:: Case-sensitive file systems do not work properly when mounted as a directory.:: - Windows and WinFsp support case-sensitive file systems. These file systems work properly when mounted as a drive. Unfortunately when a file system is mounted as a directory over NTFS, Windows expects it to be case-insensitive and will UPPERCASE many of the file names sent to the file system. + This is fixed as of WinFsp 2018.2 B3. ++ +Windows and WinFsp support case-sensitive file systems. These file systems work properly when mounted as a drive. Unfortunately when a file system is mounted as a directory over NTFS, Windows expects it to be case-insensitive and will UPPERCASE many of the file names sent to the file system. + This is an unfortunate but well understood Windows limitation. Case-sensitive file systems should only be mounted as drives. @@ -67,4 +69,4 @@ WinFsp-FUSE does not have the ability to support multiple file systems from with This is supported as of WinFsp 2018.2 B2. + -The core WinFsp layer always supported multiple file systems in the same process either simultaneously or one after another. However this was not the case with WinFsp-FUSE (i.e. the FUSE layer of WinFsp) prior to version 2018.2 B2. This limitation has been rectified as of WinFsp 2018 B2. \ No newline at end of file +The core WinFsp layer always supported multiple file systems in the same process either simultaneously or one after another. However this was not the case with WinFsp-FUSE (i.e. the FUSE layer of WinFsp) prior to version 2018.2 B2. This limitation has been rectified as of WinFsp 2018.2 B2. \ No newline at end of file