X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <48B7B1AB.1080200@go4more.de>
Date: Fri, 29 Aug 2008 10:22:03 +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: Managed mounts and cygwin 1.7
Content-Type: text/plain; charset=ISO-8859-15; 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

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?

If this is all clear already, please don't flame me - but
if not, then IMHO it's time to think about this.

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