This is the mail archive of the cygwin-developers mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Fw: File name too long problem -- maybe fix coming?


On 19 December 2007 10:36, Corinna Vinschen wrote:

> On Dec 18 21:06, Eric Blake wrote:
>> According to Linda Walsh on 12/18/2007 3:30 PM:
>>> Is it possible the update quoted at the bottom will address or fix
>>> the path-len problem, mentioned below, in cygwin?
>> 
>> Why not try out the snapshots, and see for yourself?  But yes, it looks
>> like Corinna is slowly getting to the point where cygwin uses native NT
>> functions (which support absolute paths up to 32k in length), in such a
>> way that you can access relative path names whose absolute name happens to
>> be longer than PATH_MAX.  And I'm sure that she will be adding openat()
>> and friends along the way, which is what coreutils and findutils (and any
>> other gnulib fts client) wants to use for optimal directory recursion.
> 
> Maybe that goes without saying, after all this is an Open Source
> project, but I could really need some help here.  The progress is
> extremly slow.  There's just too much code to keep an eye upon.
> When I started I imagined we could release 1.7.0 in 2007 but as long as
> I have to do this conversion to unicode paths alone, it will take a lot
> more months.  2008?  Well, maybe...

  Is there an overall TODO list?  Any notes/designs/specs/back-of-an-envelope
sketches?  Are you following an overall strategy to do the conversion?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]