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]

Re: CWD and long paths


On Oct 13 12:12, Christopher Faylor wrote:
> On Sat, Oct 13, 2007 at 09:20:20AM -0600, Eric Blake wrote:
> >
> >According to Corinna Vinschen on 10/13/2007 9:12 AM:
> >> 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.
> >
> >I would like 1 (if possible), otherwise 3.
> 
> I think 1 makes sense but it does raise the question of whether we
> should be doing something similar when cd'ed to /proc and just not
> allowing the exec to continue.

I agree.  The behaviour should be consistent.

> Otherwise, I'd opt for 3.

I'd prefer 1 as well so we have 6 points for 1, 3 points for 3 and
0 points for 2, 4 and 5 so far.


Corinna

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


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