This is the mail archive of the 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]

ntea feature

The docs states:

"When the "ntea" feature is activated, Cygwin will start with basic
permissions as determined above, but can store POSIX file permissions in NT
Extended Attributes.  This feature works quite well on NTFS partitions
because the attributes can be stored sensibly inside the normal NTFS
filesystem structure.  However, on a FAT partition, NT stores extended
attributes in a flat file at the root of the partition called EA DATA. SF.
This file can grow to extremely large sizes if you have a large number of
files on the partition in question, slowing the system to a crawl.  In
addition, the EA DATA. SF file can only be deleted outside of Windows
because of its "in use" status.  For these reasons, the use of NT Extended
Attributes is off by default in Cygwin.  Finally, note that specifying
"ntea" in CYGWIN has no effect under Windows 9x. "

What is suppose to happen on Win2k with FAT32 partitions if ntea is
activated? Is it supposed to create files as stated in the docs.  Well, I
tried it and nothing happens?

Anyway, I what to activate the ntea feature (and possibly the ntsec feature
later), and from the docs, the best option for me seems to be to put Cygwin
on a NTFS partition and leave the rest of the partitions FAT32. Will the
ntea feature only be active on the NTFS partition, or will mounts on FAT32
partitions slow to a crawl as indicated in the docs.

To summarise, what is my best options using ntea with Cygwin where most of
the partitions must remain FAT32?


Want to unsubscribe from this list?
Send a message to

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