CWD and long paths

[Václav Haisman]

Corinna Vinschen wrote, On 13.10.2007 13:03:
[...]
> 
> The spawn code checks if the executable is a Cygwin executable so usually
> we know this.
> 
> Returning ENAMETOOLONG from exec(3) would be another interesting option.
> Maybe it's even the option with the least surprise factor...
> 
[...]
> 
> 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.
[...]

I think that 1 is really the only option. I can imagine users trying to run
batches that do something like RMDIR /S which removes whole directory trees.
If Cygwin were to change directory somewhere else than user intended than it
would be a disaster.

--
VH

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://cygwin.com/pipermail/cygwin-developers/attachments/20071013/b89d3786/attachment.sig>