On Thu, 2010-09-02 at 11:11 +0100, Bryn M. Reeves wrote: > Look into groups some time - they're a whole world of fun (and there to > solve the kind of problems you're discussing).
Yes, I've done that before, too. > There are even mechanisms to allow you to create directories that can be > written to by all the group members but where you're not allowed to > delete each others stuff (set group ID (sgid) & sticky bit directories, > also now known as the "restricted deletion" flag). That, too. > You could also solve the above problem just by granting path search > permissions (chmod +x; it re-uses the executable bit for directories) to > a common group, or to all if you're happy with that and then allowing > the recipient read permissions on the file you wanted them to have > access to. Again, it's more or less what I said, earlier. To *give* someone a file, your only options are to let them read the file, and then they copy it. If you want them to *own* the file, instead of you. -- [...@localhost ~]$ uname -r 2.6.30.10-105.2.23.fc11.i686.PAE Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
