On Feb 26 11:15, Roland Mainz via Cygwin wrote: > On Wed, Feb 26, 2025 at 2:22 AM Jeremy Drake via Cygwin > <[email protected]> wrote: > > On Tue, 25 Feb 2025, Takeshi Nishimura via Cygwin wrote: > > > No, it's beegfs.sys you install. > > > SMB is not used, it uses its own protocol. If you do a > > > FileRemoteProtocolInfo query the protocol field says it's a > > > WNNC_NET_RDR2SAMPLE. > > > > Always nice when a driver doesn't change "sample" idenfiers. It seems > > Virtualbox shared folders also squats on this identifier. I imagine > > things don't go well if one attempts to install beegfs.sys on a virtualbox > > virtual machine with their guest drivers installed... > > I think the problem is that no one in the OpenSource world really > knows how to register new |WNNC_NET_*| keys. QEmu shared folders, > DOKANY, ms-nfs41-client, etc. all use |WNNC_NET_RDR2SAMPLE| because > the sample filesystem code uses that.
So if ms-nfs41-client uses WNNC_NET_RDR2SAMPLE, we don't have to handle these shares when checking the WNNC_NET_MS_NFS provider. While it would be nice if the nfs v4 driver would use some other WNNC type, this is at least helpful for handling WNNC_NET_MS_NFS shares, because they have more than one quirk... Corinna -- 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
