Registering new |WNNC_NET_*| keys ? / Re: Document support for @ character in UNC paths

[Roland Mainz]

On Wed, Feb 26, 2025 at 2:22 AM Jeremy Drake via Cygwin
<cygwin@cygwin.com> 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.
Also... there is the problem that many OpenSource projects do not have
funding/money, and if the registration costs money, then no one can do
that.

For ms-nfs41-client there is another "solution", the driver only uses
/nfs4/ subdir, so UNC paths usually look like
//derfwnb4966_ipv6linklocal@2049/nfs4/net_tmpfs2/test2

----

Bye,
Roland
-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz@nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)