2008/10/28 Rhythmic Fistman <[EMAIL PROTECTED]>:
> 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.
Hey all, I've been fooling around with appledouble files on Tiger
and found that this simple round trip test (HFS->HFS) fails with
permission denied in the appledouble unpack phase:
#include <copyfile.h>
#include <stdio.h>
int
main(int argc, char** argv) {
int r;
if(argc != 3) {
fprintf(stderr, "fc to from\n");
return 1;
}
r = copyfile(argv[1], "packed", 0, COPYFILE_ALL | COPYFILE_PACK);
if(0 != r) perror("pack");
r = copyfile("packed", argv[2], 0, COPYFILE_ALL | COPYFILE_UNPACK);
if(0 != r) perror("unpack");
return 0;
}
Running as root works fine. I don't know why setting finder info or
creating a resource fork should require privileges, but it does.
On a hunch, even though it shouldn't have anything to do with
appledouble unpacking, I retried my xattr fusefs, this time
sudo-cp-ing my file off and it worked. Ditto for the appledouble
version.
I'm a hair's breadth from moving this to "known issues w. work arounds",
but one small detail still bugs me: non-HFS->HFS copying works fine,
e.g. from a fat32 usbkey. I have no idea why or how, but it looks like, in
certain situations, creating xattr-style metadata on Tiger is privileged.
It sounds like a Tiger bug, especially since you can't do it on your
own HFS volume, however is it possible that there's a part of MacFUSE
that should be running with slightly higher permissions?
Yours,
Confused.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
