Ernesto Fernández

Sorry for the long delay, but I guess you fixed this yourself and there's nothing much for me to say here.

Hi, thanks for the report, sorry for the long delay. The reason for the difference in output is that firefox runs its reader view on the page after the scripts...

Internally, we have everything in place to read resource forks, because we need it to work with compressed files. The problem is that Linux doesn't have any standard interface to...

I just checked, and the resource fork in the readme appears to be readable if you run: ``` getfattr --only-values -n osx.com.apple.ResourceFork About\ ResEdit\ 2.1.3 ``` The ResEdit file can't...

> Doing some research, it looks like the maximum size a resource fork can be is 16 MiB. There are actually much bigger resource forks in use for compressed files....

Yes, that could be done, but it wouldn't have helped the reporter avoid data loss. The problem is that if we are not exposing the xattrs through the standard interface,...

That's terrible, thanks for the report. I'll see if I can find an unused usb drive and I'll get back to you.

I can't reproduce, the copy takes around 7 seconds for me on the 6.2 kernel. Slower than exfat for sure, but that's expected because I haven't done any profiling for...

Right, that's why I asked him if he had seen this happen more than once, I thought maybe his `sync` flushed some other stuff as well.

I don't think I can help you much if I can't reproduce this. If you are interested, maybe you can try to run the profiler yourself, and then we could...