DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 51QGEToY226303 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 51QGEToY226303 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=jJF7M06g X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D81773858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1740586468; bh=ETVTEygkVcw8txJmRqnIU9BV2O3lAvVJM2+YL4+1DSs=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=jJF7M06gV6DaKsmtFnXnPFzlD1oGhpcETDVt0xpQb3M8vHp2ld4TOvlRn2KK5bHBS TvQAdVfciKmLKBhzsvXBkgegRJ80zFRYwKIvjaPzhYzp6GCZsk9qJOp3Xb4TNKtrG5 cReLbasvrBJoZYRtFqNWhBIWXWPTKJhGkwjp1WPk= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 697F43858C42 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 697F43858C42 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1740586442; cv=none; b=benaWarv0An6pSMRGm2C5p1yJLhiBGKwOzLL20iy+YDK2juxgNAcqF4OitED1VZzcg9XOBxtuweqbqoccAfNFH1j5vWyMhNr5lY7fIfRP44EAGdJazEkudWC3Gi5BItBHCiLJi3i0ClA5VzMMyGXZ/K1KrXsVUJe+LY1TRk1PN8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1740586442; c=relaxed/simple; bh=ROT4qc2Bz7oOGYX9UBgkkYtv7VWXiV4YPpvldByKO+8=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=tT0vwkVK05fVvg9AwH9ai9ZpH6Mp4eHZC/U9cBuATm3TDWMkXW4GvkiWWTrfR+1gdfxUzr7KQNhSypXOAIvatVktzpALGajur4UeUHsK7/yXw0SmMTmyWO/HsIWx8EAZUMEO4ze+bchs/gfxpF1ZEjvHGv2x7A/8JNwVVygxuTE= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 697F43858C42 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740586441; x=1741191241; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=IFW/tljpttZExZ9fGKD1ZVbeXLoLFSX0moGrFgwr95c=; b=rp7XF24GxW3GkqaWv/zWyiuu7++suukLzcr6kOG6kpIqQas7H4LvbFs+SiTDK2yZ5r UW94MafIUtDG/gXGmizwJ9w324jWy/xXu4DHgfzbGAuG9MoKGcZWydeLpRB+F21M503L 94b9AToaGINvrAlhowMEYLjzxruklJ+sbyYmz3/inrAxBIqXzUtj3Wpeib8WIlbYAS2S geCIM3oDvRn03An711GupgXfkalxPQxptgXUafo8Tdfsm7ZL8prm1FfopgYe6V95DrEV MLqTVMSZYlSawRZRZQBTjYZeM4zpIi/FgES4r3gDJHF+/gfBEyJgr35vrTxCOdICSIDG qkBA== X-Gm-Message-State: AOJu0YxM6XB28Nhf4czhcEiNBBxseBM1FtnnRmn5gFULBz9VgMm/tg30 Vv/oQTTcV2ptk8gUoYU0PhqIwQ//CSU3lotyUESC4UEKD+acJcAnu/kZzEMGSutc+t8LsUP/dTX v8fEawH250RSDNVqKTS+Ameml+kAyzTAt X-Gm-Gg: ASbGnctzcTu/MU6dZLgYRSohF1ZZPUgVrF/mwDXN1TfsUBf+ExeV68UCBTQvdhMAEQ7 hn8LhPwxvWeRbpWBttk3ovqRu5Ppicu3AXdBqYv1Wqq7Oagwq8Wh3z6wdLDCGrTGkDsiL6HDKJI fB/GeZe3Q= X-Google-Smtp-Source: AGHT+IFliPIwPuRvqKOZ5NwZuBTtMewoMK1iLSHt/U3oW478aZy05rz7xOlG3kKlZlEqRp5S1Q6PHApty5DK7OpmB2M= X-Received: by 2002:a17:903:234b:b0:223:325c:89de with SMTP id d9443c01a7336-223325c901dmr37233665ad.1.1740586440976; Wed, 26 Feb 2025 08:14:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 26 Feb 2025 17:13:24 +0100 X-Gm-Features: AWEUYZn7Oy61xc4fMMQdaet16JFG42zNePsO8VdJjoVBRTk1tAYeFLfSdNSZmX8 Message-ID: Subject: Re: Registering new |WNNC_NET_*| keys ? / Re: Document support for @ character in UNC paths To: cygwin AT cygwin DOT com X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Cedric Blancher via Cygwin Reply-To: Cedric Blancher Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 51QGEToY226303 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 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_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, > > > > Our plan is to get our own |WNNC_NET_*| key value if we can find the > > person at Microsoft which is maintaining that list (preferred key > > names would be |WNNC_NET_MSNFS41CLIENT| (for CITI's ms-nfs41-client) > > and |WNNC_NET_MSNFS42CLIENT| for our version. > > > > And at the same time maybe help DOKANY&co to get their own > > |WNNC_NET_*| key, too. > > > > > this is > > > at least helpful for handling WNNC_NET_MS_NFS shares, because they > > > have more than one quirk... > > > > I know... that's one reason we started working on the ms-nfs41-client > > project, and at the same time it's API being compatible with the > > MS-NFSv3 and the Exceed/OpenText-NFS drivers (that's why we support > > the "NfsV3Attributes" (incl. uid/gid), "NfsSymlinkTargetName", > > "NfsActOnLink" etc. Win32 extended attributes; > > https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/ff4df658-7f27-476a-8025-4074c0121eec > > is still on the ToDo list) - but also extend the functionality, e.g. > > support NFSv4.1 ACLs (mapped to Win32 ACLs via a script-driven > > idmapper), sparse file support (for HPC environments), and > > ms-nfs42-client will add AlternateDataStream support if the NFSv4.1 > > server supports NFS "named attributes". > > I mentioned it months ago, and I mention it again: > > It would be really great if the filesystem name returned by > NtQueryVolumeInformationFile(FileFsAttributeInformation) would not be > "NFS", like the MS NFS, but something like "NFS4" or "NFSv4". This > would allow Cygwin's fs_info::update() in mount.cc to recognize the > filesystem as something special, and the code could call either the > special NFS functions, or the Windows functions, or extra functions just > for NFSv4 as time goes by. Well, that backfires because the same applications which want NfsV3Attributes also look at FILE_FS_ATTRIBUTE_INFORMATION FileSystemName, and STOP WORKING using NfsV3Attributes if it's not "NFS". From a driver's vendor position Exceed had that problem, OpenText inherited that problem, CITI had to do it on Microsoft's instructions (the CITI driver was a joint venture of SUN and Microsoft), and now Roland&Tigran&CERN&DESY have to do it too. The alternative is that commercial toolkits&applications break, and in the commercial Windows world (CWW) you cannot just "recompile(TM)". Usually you'll be asked to put in lots of money, and not even CERN's budget was able to deal with that. Ced -- Cedric Blancher [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