News for hackers. Stuff that matters.

A comment on The Dawn of a new Command Line Interface (2017). Parent comment

Re:The Dawn of a new Command Line Interface (2017) by monocasa on Tuesday April 13, 2021 @02:13PM (#26796625)
Not just NTFS, but pre OSX Macs would do stuff like this. Like a formatted document would have a text/plain fork, and the formatting information in another fork. Or an executable could keep it's symbol table or relocation information in other forks.
[ Parent | on HN ]
Re:The Dawn of a new Command Line Interface (2017) by watersb on Tuesday April 13, 2021 @09:44PM (#26802022)
You can muck around alternate data streams like a classic resource fork of a file on macOS by appending

   /..namedfork/rsrc
to the file name.

   ls ./groovyFontFile/..namedfork/rsrc
https://stackoverflow.com/a/42216808/8878480

I've tried it with ancient font suitcases -- the ones that pre-date dfont (data fork only) fonts.

It's somewhat ironic that all desktop file systems these days support myriad data streams on a file. I've implemented some on NTFS, played with extended attributes across tar archives between Linux and Mac and Windows. It's all there, but no longer used.

[ Parent | on HN ]
Re:The Dawn of a new Command Line Interface (2017) by TeMPOraL on Tuesday April 13, 2021 @02:30PM (#26796860)
Thanks! I just checked, and it seems that ADS were introduced in NTFS in order to support Mac resource forks.

https://en.wikipedia.org/wiki/NTFS#Alternate_data_stream_(AD...

[ Parent | on HN ]