X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <48B81D8F.7060000@go4more.de>
Date: Fri, 29 Aug 2008 18:02:23 +0200
From: Albrecht Schlosser <cygwin AT go4more DOT de>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Managed mounts and cygwin 1.7
References: <48B7B1AB DOT 1080200 AT go4more DOT de> <20080829091423 DOT GD29104 AT calimero DOT vinschen DOT de> <20080829135010 DOT GB19947 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20080829135010.GB19947@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Christopher Faylor wrote:
> On Fri, Aug 29, 2008 at 11:14:23AM +0200, Corinna Vinschen wrote:
>   
>> 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.
>>     
>
> Also, just tarring up the files prior to the conversion and untarring
> them afterwards should suffice to do the conversion.
>   
Yes, that's what I assumed, but you would have to know that before you 
press the install
button with cygwin 1.7 selected ;-)

Albrecht


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