noacl functionality for MS-DOS destination paths?

Lawrence Mayer
Fri Dec 19 04:53:00 GMT 2008

Is there any way to get noacl functionality when using MS-DOS 
destination paths?

My etc/fstab file (below) applies noacl for UNIX destination paths e.g.

C:\cygwin\bin\mkdir.exe /c/foo

creates directory C:\foo with NTFS default permissions inherited from 
parent directory C:\ (the same as DOS mkdir C:\foo would do).

But an MS-DOS destination path, e.g.

C:\cygwin\bin\mkdir.exe C:\foo

causes Cygwin to ignore noacl in etc/fstab and create C:\foo with 
POSIX-like permissions (non-NTFS default and not inherited from parent 
directory C:\).

According to

"Otherwise, the handling of MS-DOS filenames bypasses the mount table"

But if Cygwin 1.7 bypasses etc/fstab for MS-DOS filenames and no longer 
supports the nontsec option, I'm stuck.

When using MS-DOS destination paths in Cygwin 1.7, is there any way to 
get noacl functionality - i.e. where Cygwin creates objects with NTFS 
default permissions inherited from their parent directory rather than 
POSIX-like permissions?

If not, are there any plans to add such functionality to Cygwin 1.7?

Destination paths can be converted from MS_DOS to Unix (e.g. with 
cygpath) in order to prevent Cygwin from bypassing etc/fstab and hence 
noacl, but is there a solution which doesn't require path conversion?


Details: Cygwin v1.7.0-35 on NTFS drive C: running Windows Server 2003 
sp2 32-bit


none / cygdrive text,noacl,posix=0,user 0 0
C:/cygwin/bin /usr/bin ntfs text,noacl,posix=0 0 0
C:/cygwin/lib /usr/lib ntfs text,noacl,posix=0 0 0
C:/cygwin / ntfs text,noacl,posix=0 0 0

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list