Filenames with Win32 special characters (or: Interix filename compatibility)

Christopher Faylor
Tue Mar 11 16:34:00 GMT 2008

On Tue, Mar 11, 2008 at 03:22:17PM +0100, Corinna Vinschen wrote:
>On Mar 11 06:42, Brian Dessent wrote:
>> Corinna Vinschen wrote:
>> > Reserved DOS device names are no problem in the NT name space.  In 1.7.0
>> > you can create a file "nul" in your cwd and access it as file, as long
>> > as you use Cygwin or Interix.
>> I'm always glad to see another nail in managed mounts' coffin!  However:
>> > Case sensitivity is still not possible with this approach.  You
>> > can get generic case sensitivity in Cygwin with a bit of work.  The
>> > magic flag is OBJ_CASE_INSENSITIVE in the object attributes.  However,
>> > this would not work for fork/exec.
>> Sadly Linux netfilter source still contains stuff like xt_connmark.h as
>> well as xt_CONNMARK.h as separate files in the same dir, so anyone
>> wanting to cross compile a kernel will have to continue to use managed
>> mounts.
>We could enhance the method to handle uppercase ASCII chars as well.
>Managed mounts could use the same method as normal mounts, just with
>upper case ASCII chars transformed, too.
>This would have the additional advantage that filenames on managed
>mounts not only look almost normal, the length of the real path
>also isn't changed due to the char transformation, like it is today.

Wow, it took six message in for someone to mention the fact that managed
mounts use up extra space in the path name.  Usually that is the first
revelation imparted whenever someone starts discussing them.

You all are slipping!


More information about the Cygwin-developers mailing list