Date: Fri, 29 Aug 2008 11:14:23 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Managed mounts and cygwin 1.7
Message-ID: <20080829091423.GD29104@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <48B7B1AB.1080200@go4more.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48B7B1AB.1080200@go4more.de>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Aug 29 10:22, Albrecht Schlosser wrote:
> As I understand it, cygwin 1.7 won't support the old 1.5 managed
> mounts, but will have another filename encoding for non-ASCII
> filenames. IIRC, I read that all code for the old managed mounts
> has been removed from cygwin 1.7.
>
> I'm just curious: How would users of managed mounts transform
> their file(name) data to the new encoding, once they have
> upgraded their cygwin version? Would they need to tar the
> files _before_ upgrading and untar _after_ updrading? Will
> there be a tool to convert the filenames?

There's no conversion path for now.  If somebody is interested in
writing a tool (a shell script would suffice) to convert managed mounted
files to normal filenames, the effort would be highly appreciated.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/