X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 4 Dec 2008 13:30:40 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Avoid duplicate names in /proc/registry (which may crash find) ? Message-ID: <20081204123040.GE12905@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4934461E DOT 5040708 AT t-online DOT de> <20081202120840 DOT GM12905 AT calimero DOT vinschen DOT de> <493546D3 DOT 7060808 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Dec 4 11:37, ColdShine wrote: > 2008/12/2 Eric Blake : > > > > [...] the problem is [...] that Windows allows the registry to violate > > filesystem semantics by giving the same name to distinct contents. > > If I'm allowed to add some further examples (which are probably known > to most, but maybe not to all), registry value names allow *any* > Unicode character (including NUL, sic! - thanks UNICODE_STRING), so > the following is completely ambiguous, even though valid: > > /proc/registry/.../parentkey/subkey/value/with/slashes > > where the actual value name is "value/with/slashes" (sic!). That's why Cygwin prints the file name as /proc/registry/.../parentkey/subkey/value%2Fwith%2Fslashes thanks to a patch from Christian Franke. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/