copy or move from fork-aware system: forked data is lost

[grahamperrin]

Hi

A highlight from http://fuzzy.wordpress.com/2007/06/10/findercomplements/ :

If the source file is on an HFS+ volume, and has a resource fork, then a copy or move to a volume that lacks native support for forks and the like WILL LOSE the resource fork even if you opt to display both classes of hidden file.

In context, some readers of the post will positively appreciate losses of this nature, so please don't misinterpret the post as detrimental.

However: as the loss is apparently unavoidable, I should treat it as a bug.

If my interpretation of the issue is incorrect, do please let me know and I'll post a correction. My priority has been to share the benefits of muCommander with MacFusion group members.

Kind regards
Graham

[jmurphy]

As far as I can see mucommander is always blind to resource forks, and you will lose the resource fork when you copy or move, regardless of whether the destination volume supports them. Presumably this is a limitation of Java.

As you say, this may sometimes be useful when copying. When moving or deleting a file which has a resource fork, I imagine that you would end up with an orphaned resource fork which would be invisible. Presumably, if you did this a million times it could have an impact on disk space.

(I'm just guessing here, I may be wrong)

Jonathan Murphy