4
2
I have a few OSX systems on my home network and am trying easily share files between them. Each computer has file sharing enabled and I can view and add stuff to their public folders—that's all trivial and not a problem.
My issue is with the underlying ACL permissions of each of the shared files. When I add files to another computer's public folder, the permissions of the file remain. If the file is owned by me and the application that created it made it read only (or worse, gives it no permissions for the group or everyone), my wife can't view the file on her computer. She can't even delete or move it without authenticating.
The only way I've found to get around this is to put all shared files in the write-only Drop Box folder, which adds full permissions of the computer's owner's user account to the any file added to it. For example, if I place a file with 744 permissions for my UID, my wife's UID is added to the file, giving her full access over the file. If I place that same file anywhere else in her public folder, the file remains under UID's control and she can't do anything to it without sudo.
I've repaired permissions and the behavior is still there, so I'm assuming that's the way it's supposed to work.
So, how are we supposed to share files easily between our public folders when permissions are consistently a problem?
Perfect - I was just totally misunderstanding the paradigm. I was trying to put stuff into other people's ~/Public folders instead of having them take it from me. That, um, "fixed" it for me (without having to change anything!) Thanks! – Andrew – 2010-12-24T18:32:29.163