CWD and long paths

Corinna Vinschen corinna-cygwin@cygwin.com
Sat Oct 13 15:12:00 GMT 2007


On Oct 13 13:03, Corinna Vinschen wrote:
> So, for now we have four options(*)what to do in exec(3) when trying to
> start a native child process from a long CWD (> MAX_PATH):
> 
> 1. Return ENAMETOOLONG and don't start the native child.
> 
> 2. CWD for the native child is set to $SYSTEMROOT.
> 
> 3. CWD is set to the root of the current drive (either X:\ or
>    \\server\share).
> 
> 4. CWD is set to the longest leading path component of CWD which still
>    fits into MAX_PATH.

I forgot the fifth option, suggested by Pierre:

5. Start the native app in the last CWD we were in which was < MAX_PATH.

> As an additional possible feature, regardless of which of the above
> options we choose:
> 
> - Print a longish message along the lines of what's printed by CMD.
> 
> Now we just have to make a decision.  Opinions?  Personally I tend
> to opt for 1 or 3.


Corinna


-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat



More information about the Cygwin-developers mailing list