-
All replies
-
Helpful answers
-
Nov 9, 2011 2:29 PM in response to franck1968by jsd2,You can try a method that uses ACLs - see this user tip:
Automatically make shared files writable for others
How much data needs to be shared this way? If it's not a large amount, what I do instead is just keep a USB flash drive always plugged in, with the box in Get Info checked for "ignore ownership on this volume". All users can read and write to items on this drive.
-
Nov 13, 2011 12:06 AM in response to jsd2by franck1968,Finally i decided to use the old way !
I used terminal to change permissions in this way : chmod -R 777 /sharedfilename
With sharedfilename located in the shared folder under Users.
-
Nov 13, 2011 4:44 AM in response to franck1968by jsd2,Yes, that works for items that are already there, but would have to keep being repeated for newly-created items.
Actually, using chmod -R 777 <folder> raises a Unix question for me that perhaps a more knowledgeable person here can answer for both of us.
Setting the "x" bit on an enclosed folder would make it "searchable", which is what you want here, while setting the "x" bit on an enclosed file would make it "executable", which would not be intended. It's my understanding that if you use chmod -R 777 you will set the "x" bit on all enclosed items, including the files, while using, say, chmod -R a+rwX would only set the x bit on enclosed folders, not the enclosed files. My question for someone here is, should you therefore never use chmod -R 777 on an enclosing folder and instead always use something like chmod -R a+rwX? Does it make any difference in practice whether or not your datafiles are inadvertently made "executable?"