From 38ad8fd27d980056313db9660227d0d8c2df448b Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Thu, 11 May 2017 13:51:56 -0700 Subject: [PATCH] update README --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 71639399..618de248 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,8 @@ The project source code is organized as follows: * src/launcher: Source code to the launcher service and the launchctl utility. * src/sys: Source code to the WinFsp FSD. * opt/cygfuse: Source code for the Cygwin FUSE package. -* tst/memfs: Source code to an example file system written in C++ (memfs). +* tst/memfs*: Source code to an example file system written in C/C++ (memfs) or C# (memfs-dotnet). +* tst/passthrough*: Source code to additional example file systems. * tst/winfsp-tests: WinFsp test suite. ## Building and Running @@ -72,7 +73,7 @@ WinFsp is designed to run on Windows 7 and above. It has been tested on the foll I am looking for help in the following areas: * If you have a file system that runs on FUSE please consider porting it to WinFsp. WinFsp has a native API, but it also has a FUSE (high-level) API. -* If you are working with a language other than C/C++ (e.g. Delphi, C#, etc.) and you are interested in porting/wrapping WinFsp I would love to hear from you. +* If you are working with a language other than C/C++ (e.g. Delphi, Java, etc.) and you are interested in porting/wrapping WinFsp I would love to hear from you. * There are a number of outstanding issues listed in the [GitHub repository](https://github.com/billziss-gh/winfsp/issues). Many of these require knowledge of Windows kernel-mode and an understanding of the internals of WinFsp so they are not for the faint of heart. In all cases I can provide ideas and/or support.