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: Tue, 16 Sep 2003 23:34:52 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin, Rsync and 8-bit chars (SJIS) (and managed mounts) Message-ID: <20030917033452.GB10715@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030917015023.GC571@redhat.com> <20030917022527.GA10068@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Sep 17, 2003 at 12:29:27PM +0900, Dylan Cuthbert wrote: >Any trick to get around this "error"? (I presume once -o managed is fully >debugged this limitation will be removed anyway, or overridable by an option >at least?) This is permanent limitation of managed mode. The directory has to be managed from the start. There's really no other way to do it other than to have mount walk the existing directory and "fix" all files with mixed case. So, just use 'cp -a' to copy the existing directory to the managed directory and then delete the original and rename the copy. Hmm. mv may work, too, but I haen't tried it. 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/