Re: Document support for @ character in UNC paths

On Mar 19 04:31, Takeshi Nishimura via Cygwin wrote: > On Tue, Mar 18, 2025 at 8:19 PM Corinna Vinschen via Cygwin > wrote: > > > > On Mar 18 15:57, Takeshi Nishimura via Cygwin wrote: > > > On Tue, Feb 25, 2025 at 4:59 PM Takeshi Nishimura > > > wrote: > > > > > > > > Subject says it all, please

Re: Document support for @ character in UNC paths

On Tue, Mar 18, 2025 at 8:19 PM Corinna Vinschen via Cygwin wrote: > > On Mar 18 15:57, Takeshi Nishimura via Cygwin wrote: > > On Tue, Feb 25, 2025 at 4:59 PM Takeshi Nishimura > > wrote: > > > > > > Subject says it all, please document that @ characters in UNC paths > > > are now supported, for

Re: Document support for @ character in UNC paths

On Mar 18 15:57, Takeshi Nishimura via Cygwin wrote: > On Tue, Feb 25, 2025 at 4:59 PM Takeshi Nishimura > wrote: > > > > Subject says it all, please document that @ characters in UNC paths > > are now supported, for WebDAV and BeeGFS > > Was this ever added to the Cygwin documentation for Cygwin

Re: Document support for @ character in UNC paths

On Tue, Feb 25, 2025 at 4:59 PM Takeshi Nishimura wrote: > > Subject says it all, please document that @ characters in UNC paths > are now supported, for WebDAV and BeeGFS Was this ever added to the Cygwin documentation for Cygwin 3.6? -- Internationalization&localization dev / 大阪大学 Takeshi Nish

Re: Document support for @ character in UNC paths

On Feb 26 15:45, Corinna Vinschen via Cygwin wrote: > On Feb 25 16:59, Jeremy Drake via Cygwin wrote: > D'uh. My reading skills are detoriating. I tried RESOURCE_CONNECTED > and RESOURCE_REMEMBERED, but always with lpNetResource set up for a > certain server... *facepalm* > > I reworked the netd

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

On Feb 26 17:46, Cedric Blancher via Cygwin wrote: > On Wed, 26 Feb 2025 at 17:29, Corinna Vinschen via Cygwin > wrote: > > I wasn't aware there are other projects using the undocumented NFS > > interfaces. As far as Cygwin is concerned, it would be the simplest > > thing to add a check for the "

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

On Wed, 26 Feb 2025 at 17:29, Corinna Vinschen via Cygwin wrote: > > On Feb 26 17:13, Cedric Blancher via Cygwin wrote: > > On Wed, 26 Feb 2025 at 16:50, Corinna Vinschen via Cygwin > > wrote: > > > > > > On Feb 26 16:23, Roland Mainz via Cygwin wrote: > > > > On Wed, Feb 26, 2025 at 2:36 PM Cori

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

On Feb 26 17:13, Cedric Blancher via Cygwin wrote: > On Wed, 26 Feb 2025 at 16:50, Corinna Vinschen via Cygwin > wrote: > > > > On Feb 26 16:23, Roland Mainz via Cygwin wrote: > > > On Wed, Feb 26, 2025 at 2:36 PM Corinna Vinschen via Cygwin > > > wrote: > > > > > > > > On Feb 26 11:15, Roland Ma

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

On Wed, 26 Feb 2025 at 16:50, Corinna Vinschen via Cygwin wrote: > > On Feb 26 16:23, Roland Mainz via Cygwin wrote: > > On Wed, Feb 26, 2025 at 2:36 PM Corinna Vinschen via Cygwin > > wrote: > > > > > > On Feb 26 11:15, Roland Mainz via Cygwin wrote: > > > > On Wed, Feb 26, 2025 at 2:22 AM Jerem

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

On Feb 26 16:23, Roland Mainz via Cygwin wrote: > On Wed, Feb 26, 2025 at 2:36 PM Corinna Vinschen via Cygwin > wrote: > > > > On Feb 26 11:15, Roland Mainz via Cygwin wrote: > > > On Wed, Feb 26, 2025 at 2:22 AM Jeremy Drake via Cygwin > > > wrote: > > > > On Tue, 25 Feb 2025, Takeshi Nishimura

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

On Wed, Feb 26, 2025 at 2:36 PM Corinna Vinschen via Cygwin wrote: > > On Feb 26 11:15, Roland Mainz via Cygwin wrote: > > On Wed, Feb 26, 2025 at 2:22 AM Jeremy Drake via Cygwin > > wrote: > > > On Tue, 25 Feb 2025, Takeshi Nishimura via Cygwin wrote: > > > > No, it's beegfs.sys you install. > >

Re: Document support for @ character in UNC paths

On Feb 25 16:59, Jeremy Drake via Cygwin wrote: > On Tue, 25 Feb 2025, Cedric Blancher via Cygwin wrote: > > > WebDAV and BeeGFS are not alone, the Windows ms-nfs41-client and > > ms-nfs42-client ALWAYS (even with default NFSv4.1 port TCP/2049) use > > UNC paths with "@" character, like > > \\stri

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

On Feb 26 11:15, Roland Mainz via Cygwin wrote: > On Wed, Feb 26, 2025 at 2:22 AM Jeremy Drake via Cygwin > 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 > > > FileRemoteProtoc

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

On Wed, Feb 26, 2025 at 2:22 AM Jeremy Drake via Cygwin 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_RDR

Re: Document support for @ character in UNC paths

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. I

Re: Document support for @ character in UNC paths

On Tue, 25 Feb 2025, Cedric Blancher via Cygwin wrote: > WebDAV and BeeGFS are not alone, the Windows ms-nfs41-client and > ms-nfs42-client ALWAYS (even with default NFSv4.1 port TCP/2049) use > UNC paths with "@" character, like > \\stripe02.zebracluster.intra.pasteur.fr@2049\nfs4\disk02\ > OpenT

Re: Document support for @ character in UNC paths

On Tue, 25 Feb 2025 at 19:54, Corinna Vinschen via Cygwin wrote: > > On Feb 25 17:53, Takeshi Nishimura via Cygwin wrote: > > On Tue, Feb 25, 2025 at 5:41 PM Corinna Vinschen via Cygwin > > wrote: > > > > > > On Feb 25 16:59, Takeshi Nishimura via Cygwin wrote: > > > > Subject says it all, please

Re: Document support for @ character in UNC paths

On Tue, 25 Feb 2025 at 17:00, Takeshi Nishimura via Cygwin wrote: > > Subject says it all, please document that @ characters in UNC paths > are now supported, for WebDAV and BeeGFS > WebDAV and BeeGFS are not alone, the Windows ms-nfs41-client and ms-nfs42-client ALWAYS (even with default NFSv4.1

Re: Document support for @ character in UNC paths

On Feb 25 17:53, Takeshi Nishimura via Cygwin wrote: > On Tue, Feb 25, 2025 at 5:41 PM Corinna Vinschen via Cygwin > wrote: > > > > On Feb 25 16:59, Takeshi Nishimura via Cygwin wrote: > > > Subject says it all, please document that @ characters in UNC paths > > > are now supported, for WebDAV and

Re: Document support for @ character in UNC paths

On Tue, Feb 25, 2025 at 5:41 PM Corinna Vinschen via Cygwin wrote: > > On Feb 25 16:59, Takeshi Nishimura via Cygwin wrote: > > Subject says it all, please document that @ characters in UNC paths > > are now supported, for WebDAV and BeeGFS > > Right now it's only documented that WebDAV shares are

Re: Document support for @ character in UNC paths

On Feb 25 16:59, Takeshi Nishimura via Cygwin wrote: > Subject says it all, please document that @ characters in UNC paths > are now supported, for WebDAV and BeeGFS Right now it's only documented that WebDAV shares are supported: - Expose WebDav shares, //tsclient (Microsoft Terminal Services)