2008/10/28 Amit Singh <[EMAIL PROTECTED]>: > > Yes, "cp -p"'ing should work on Tiger.
Looking at the 10.4.8 cp implementation, I see that by default cp uses copyfile(COPYFILE_XATTR). -p only adds COPYFILE_ACL. > To get Finder-compatible > behavior on Tiger and have consistency between the Finder and the > command-line, you'd want to use ._ files. I'll gladly use them, but cp is still stubbornly discarding them. > 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. Thanks, I'll check them out. > 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. Heh. That reminds me, has anyone tested their filesystems in the presence of software like BlueHarvest (filters out appledouble files, amongst other things)? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
