X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 4 Dec 2008 11:37:43 +0100 From: ColdShine To: cygwin AT cygwin DOT com Subject: Re: Avoid duplicate names in /proc/registry (which may crash find) ? In-Reply-To: <493546D3.7060808@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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> X-IsSubscribed: yes 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 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 from Win32 (and POSIX) file system functions taking one argument for the file name, and the Win32 registry functions taking two distinct arguments to form a full path (and non-ASCIIZ length-prefixed UNICODE_STRING). CS -- 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/