Mail Archives: cygwin/2005/03/11/16:48:52
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is there any reason that a managed mount can't treat backslash like it
does for non-printing characters, rather than treating it as an alternate
spelling of a directory separator? True, there isn't much use in naming a
file "foo\\bar", as distinct from the directory/file pair "foo/bar", but
this is a remaining incompatibility with Unix file systems, where `touch
foo\\bar' actually creates a file rather than complaining because
directory foo doesn't exist.
Also, it appears that PATH_MAX, as defined in /usr/include/limits.h (at
259, barely larger than the 256 required by POSIX), applies to the
underlying Windows name and not the length of the cygwin POSIX-style name.
This is rather weird in managed mounts, where in a deep enough hierarchy,
the filename abcd is valid but ABCD causes an ENAMETOOLONG. By the way,
how come /usr/include/limits.h does not define NAME_MAX (required to be at
least 14)?
- --
Life is short - so eat dessert first!
Eric Blake ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCMhI084KuGfSFAYARArC0AJ0eICkuhRdnvQICNWic0hxv7/gyawCgyqUg
D6WdGgIgdtN/KV2VlL4cepA=
=T4W2
-----END PGP SIGNATURE-----
--
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 -