On Tue Mar 28 14:55:47 2023 +0000, Joel Holdsworth wrote:
The tmpfs filesystem supports extended attributes (see xattr(7)), but user extended attributes are not permitted.
I have been summoned! Yes, I have suggested that we could treat this all as [alternative stream data](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/c54dec...) in an adjacent subdirectory. So, files with additional metadata would look something like this: ``` $ ls -haltr . .NT_STREAMS/myfile/ .: <snip . and ..> drwxrwxr-x 4 ehoover ehoover 4.0K Oct 20 09:58 .NT_STREAMS lrwxrwxrwx 1 ehoover ehoover 20 Oct 20 13:02 myfile -> .NT_STREAMS/myfile/: .NT_STREAMS/myfile/: <snip . and ..> lrwxrwxrwx 1 ehoover ehoover 2 Oct 20 13:02 : -> :: lrwxrwxrwx 1 ehoover ehoover 7 Oct 20 13:02 :: -> '::$DATA' -rw-rw-r-- 1 ehoover ehoover 8 Oct 20 13:03 '::$DATA' ``` [Additional attributes](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/a82e91...) (`$REPARSE_POINT`, etc.) would all be stored here according to the NTFS spec. In this case, I believe that you would want to use `$STANDARD_INFORMATION` ([source](http://inform.pucp.edu.pe/~inf232/Ntfs/ntfs_doc_v0.5/attributes/standard_inf...)). I put together some patches for this, but it gets a little tricky to find the folder under some circumstances. I don't remember where I left off with it, but I can look into it if folks are interested.