Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Thu, 17 Jul 2003 09:23:52 -0400 From: Christopher Faylor Subject: Re: cygwin 1.5.0 managed mode & backward compatibility In-reply-to: <6A3008858445D711A58A00062939B2F1EB0A@EXCHANGE> To: cygwin@cygwin.com Reply-to: cygwin@cygwin.com Mail-followup-to: cygwin@cygwin.com Message-id: <20030717132352.GA13353@redhat.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.4.1i References: <6A3008858445D711A58A00062939B2F1EB0A@EXCHANGE> On Thu, Jul 17, 2003 at 10:12:09AM +0200, Pavel Rozenboim wrote: >> On Wed, Jul 16, 2003 at 01:48:28PM +0200, Pavel Rozenboim wrote: >> directories (/,/usr/bin, >> >/usr/lib) in managed mode. Now I can't access files that >> have a capital >> >letters that were created before upgrade to 1.5.0. >> >> *exactly* >> >> Don't do that. Do not use managed mode on your old >> directories. It is >> called "managed" for a reason. Cygwin wants to manage all >> file creations. >> So, the only way to use it is to create an empty directory, mount it >> as managed, and then populate it with files. > >Do you have any plans to provide backward/windows compatibility for managed >mode? No. None whatsoever. cgf -- 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/