This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin 1.5.0 managed mode & backward compatibility
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: Pavel Rozenboim <pavelr at coresma dot com>
- Cc: cygwin at cygwin dot com
- Date: Thu, 17 Jul 2003 10:14:35 -0400
- Subject: Re: cygwin 1.5.0 managed mode & backward compatibility
- References: <6A3008858445D711A58A00062939B2F1EB0A@EXCHANGE>
- Reply-to: cygwin at cygwin dot com
Pavel Rozenboim wrote:
From: Christopher Faylor [mailto:email@example.com]
Sent: Wed, July 16, 2003 6:07 PM
Subject: Re: cygwin 1.5.0 managed mode & backward compatibility
On Wed, Jul 16, 2003 at 01:48:28PM +0200, Pavel Rozenboim wrote:
I installed cygwin 1.5.0 and remounted all cygwin
/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.
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
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
Perhaps I'm being simplistic but I can't see how Windows compatibility
could be added in terms of it displaying the unmanaged names and
understanding which name maps where. I assume that's what you meant.
If not, please clarify. Also, I'm not sure I understand the implication
of 'backward' in your statement, unless it was just a qualifier for
There's no reason that Windows applications can't work with the managed
named files of course. At least, no reason AFAICS.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html