Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From:	"linda w \(cyg\)" <cygwin AT tlinx DOT org>
To:	<cygwin AT cygwin DOT com>
Subject:	pathname lenth maximums and cygwin conversions
Date:	Wed, 23 Apr 2003 16:04:40 -0700
Message-ID:	<000001c309ec$b8550fa0$1403a8c0@sc.tlinx.org>
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

If I have a windows path that is exactly 255(6?) characters
long, that is a valid windows path.  But because cygwin
mangles the path from C:\foobar to C:\/... it exceeds the
allowed path length.  I'm guessing that cygwin just uses
the 256 character limit of the underlying OS.  Perhaps
cygwin should 'cut some slack' for its conversions --
things like converting c:\, in some cases to /c/cygwin.

Worse, if I remember, it just used \xxxx\xxx..., meaning
it assumed the drive.  I could easily see cygwin conversions
driving a near 256 byte path over the limit...

-linda



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

- Raw text -