On Tue, 1 Apr 2025 at 13:54, Corinna Vinschen via Cygwin <cygwin@cygwin.com> wrote: > > On Apr 1 12:27, Cedric Blancher via Cygwin wrote: > > On Tue, 1 Apr 2025 at 09:46, Cedric Blancher <cedric.blanc...@gmail.com> > > wrote: > > > > > > Good morning! > > > > > > For your consideration - we need FEEDBACK, please! > > > > > > New is: > > > - 2nd Spring-Release (🐝) > > > - Improved Windows Extended Attribute (EA) support > > > - Sparse file support (https://en.wikipedia.org/wiki/Sparse_file) for > > > HPC environments > > > - Symlink conversion, to make Windows symlinks exchangeable with other > > > NFS clients on other platforms > > > - Windows Server 2019 NFSv4.1 nfsd, Windows Server 2022 NFSv4.1 nfsd, > > > Solaris 11.4 NFSv4.1 nfsd and Illumos NFSv4.2 nfsd support > > > - Better WSL (Windows Services for Linux) support > > > - MSYS2 support > > > - Windows Storage32 API support, required for using MSI installer > > > files on NFS mounts > > > - Support for languages with wide characters (Japanese, Chinese, > > > Hindi, French...) in nfs://-URLs > > > - Display mount points with wide-characters in nfs_mount.exe correctly > > > > New thread: > > Does Cygwin have any requests, or ideas, what could be improved in the > > ms-nfs41-client NFSv4.2 driver for Windows? New features? > > No, but if we want to *better* support this driver, we need either a > patch (preferred) or at least info how to distinguish in > fs_info::update(*) between the MSFT driver and the NFSv4.2 driver.
That is actually easy: Roland implemented support for FileRemoteProtocolInformation in https://github.com/kofemann/ms-nfs41-client/commit/e9f72b61494bebd9e26fefec2659a4511a05b0fd , and the FILE_REMOTE_PROTOCOL_INFORMATION->Protocol field can be used to identify the type of driver. Examples: Windows NFSv3 driver uses WNNC_NET_MS_NFS, OpenAFS uses WNNC_NET_OPENAFS, ms-nfs41-client uses WNNC_NET_RDR2SAMPLE, and OpenText NFS also uses WNNC_NET_RDR2SAMPLE. Plan for ms-nfs42-client is to obtain an own WNNC_NET_MSNFS42CLIENT tag, and also tags for DOKANY. In your case all workarounds for the Windows NFSv3 driver would be enableds just by doing a FileRemoteProtocolInformation query, #define IS_MS_NFSV3_DRIVER(rpi) (rpi->Protocol == WNNC_NET_MS_NFS), and put if(IS_MS_NFSV3_DRIVER(&saved_rpi)) { ... } in places where needed. Same test can be done for SMB, OpenAFS, Windows DAV driver, Windows/WSL 9P, Terminal server. There is also https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/fltuserstructures/ne-fltuserstructures-_flt_filesystem_type but I do not know in which context that is used. Maybe you or Roland know that. Ced -- Cedric Blancher <cedric.blanc...@gmail.com> [https://plus.google.com/u/0/+CedricBlancher/] Institute Pasteur -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
