Yes, "cp -p"'ing should work on Tiger. To get Finder-compatible behavior on Tiger and have consistency between the Finder and the command-line, you'd want to use ._ files.
You can always use the two canonical reference file systems to see how they behave: fusexmp_fh and sshfs. See http://groups.google.com/group/macfuse/browse_thread/thread/a65c82fe5db9073d. If you see incorrect behavior in a reference file system, then it could be a bug or regression. Amit PS: All bets are off if you guys tweak your system or use alien software. Things in OS X are pretty confusing as it is. Only yesterday there was somebody for whom installation didn't work because he didn't have awk in /usr/bin. Similarly, if you use a copy command ported over from CP/M or some such, you can't really complain that it's not working. On Oct 27, 5:43 pm, "Rhythmic Fistman" <[EMAIL PROTECTED]> wrote: > 2008/10/27 Amit Singh <[EMAIL PROTECTED]>: > > > So, the real reason is that on Tiger, the Finder (the File Manager) > > refuses to believe that the volume in question can support extended > > attributes. > > Does this mean that cp-ing a resource fork should work on Tiger > and that I'm just doing something wrong? > > RF --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
