X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: mwoehlke Subject: Re: Handling special characters (\/:*?"<>|) gracefully Date: Tue, 23 May 2006 14:16:47 -0500 Lines: 17 Message-ID: References: <2ED63F31975E1E428B3732A68923F480ECA6FC AT rain DOT scur DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.2 (X11/20060420) In-Reply-To: <2ED63F31975E1E428B3732A68923F480ECA6FC@rain.scur.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Hicks,Mike wrote: > There are a number of special characters that cannot be used in > filenames on the NTFS filesystem [snip] > [much snipage] You might want to play around with "managed mounts" ('man mount'), if they do what I think I heard they do (namely, "deal" with such things for you). Supposedly you can get case sensitivity - in the sense that 'Readme' and 'README' can co-exist - out of them as well. (Speaking of case sensitivity, is it a Windows limitation that Cygwin can't do this? I'm pretty sure it isn't an NTFS limitation, as Interix has true case-sensitivity.) -- Matthew Interix, Sphinterix. Cygwin apps don't crash. :-) -- 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/