DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 51PGg35J3919609 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 51PGg35J3919609 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=Msct8kv9 X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8DD2E3858C41 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1740501722; bh=WxmUpIooRBgVdyGUMcSoJih6uiAxrVb0XOCBrDgo5aA=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=Msct8kv9o5Lk2eyAsKNAcq9j+tBgoJJMiqvU7lb0ydwoTsj0OKNM7eo85LBidTFMN Y+NXuDLISrUI/kfMun/+Mhek6R+ZVHs133g/wJN0hZS4ScTYz+X+TZfhc9Mbi7+NuJ a/oTV+DnOo6DrMJmigohUilD5Fth0LXJtX5sSrRU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D99293858D26 Date: Tue, 25 Feb 2025 17:41:02 +0100 To: cygwin AT cygwin DOT com Subject: Re: Document support for @ character in UNC paths Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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) shares as well as //wsl$ (Plan 9 Network Provider) shares, i. e., WSL installation root dirs. We don't have any special code in Cygwin to support BeeGFS, it's kind of a by-product of the WebDAV support. How are the BeeGFS shares exposed to Windows clients? Is a special driver required, or are they just SMB shares? Thanks, 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