<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> I have been wrestling with how to create a shared folder for a project team. So far, I have a folder with the group set to a special group created for the team users, and I set the folder's Group ID bit to that special group. All the team users have the special group assigned to them as a secondary group, and the user umasks are 002 so that files and folders they create are writable by the group as well as the owner. This works well for any new files and folders created in the shared folder, but fails for files and folders created elsewhere and then *moved* into the shared folder. Those retain their original group -- the primary group of the owner -- and cannot be edited by other members of the group. I have seen write-ups of people using ACLs to deal with systems where the user umasks are 022, but I don't need it for that purpose here. I have also seen one claim where an ACL setup (the same setup referred to above?) solves the problem of files/folders that are moved into the shared folder. Can someone say more about this? </body> </html>