You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cygwin supports user.* XATTRs by encoding them somehow in Windows EAs.
Any chance to see support for reading these via ntfs-3g?
Maybe with default mount options, they could be mapped into some special namespace (like cygwin.*) and with some special mount option like xattr-profile=cygwin they could get mapped directly into user.* ?
I found only little information on how they do it.
Hey.
Cygwin supports user.* XATTRs by encoding them somehow in Windows EAs.
Any chance to see support for reading these via ntfs-3g?
Maybe with default mount options, they could be mapped into some special namespace (like
cygwin.*
) and with some special mount option likexattr-profile=cygwin
they could get mapped directly into user.* ?I found only little information on how they do it.
There's a few words in https://www.cygwin.com/cygwin-ug-net/cygwin-ug-net.pdf on PDF page 4, chapter 1.6.3 File Access.
Other than that, one would probably have to resort to https://www.cygwin.com/git.html where it seems in
winsup/cygwin/fhandler/disk_file.cc
winsup/cygwin/include/attr/xattr.h
winsup/cygwin/ntea.cc
(which seems to contain the beef inread_ea()
)ntfs-3g already has some limited support for getting the data:
Here, on test the following XATTR was set from Cygwin:
Not sure whether support for FAT and exFAT is needed, because it seems Cygwin itself cannot even set XATTRs on them.
Cheers,
Philippe
The text was updated successfully, but these errors were encountered: