X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received-SPF: pass (google.com: domain of nick.lowe@gmail.com designates 10.52.23.5 as permitted sender) client-ip=10.52.23.5; Authentication-Results: mr.google.com; spf=pass (google.com: domain of nick.lowe@gmail.com designates 10.52.23.5 as permitted sender) smtp.mail=nick.lowe@gmail.com; dkim=pass header.i=nick.lowe@gmail.com MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 21 Feb 2012 09:52:54 +0000 Message-ID: Subject: Re: shared_info::init_obcaseinsensitive implemented incorrectly From: Nick Lowe To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com OK, fair enough, it is an edge case... I am a stickler for correctness! :P Looking at previous threads though actually, I notice that the following is documented by Microsoft regarding the obcaseinsensitive value: "If this setting is enabled, case insensitivity is enforced for all directory objects, symbolic links, and IO objects, including file objects. Disabling this setting does not allow the Win32 subsystem to become case sensitive." You could just get away with therefore, in theory, a call to NtOpenSymbolicLinkObject for \SYSTEMROOT. If it fails because it cannot be found, you know that the system is running with case sensitivity, otherwise, it is case sensitive. Regards, Nick -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple