ACLs are really pretty darn simple once you understand the syntax of 'getfacl' and 'setfacl'. Even Nautilus has integration of ACL administration through Eiciel, so those who are "shell shocked" don't have to fire one up.
IMHO there's no reason to set up some elaborate filesharing mechanism like Samba or a clunky workaround like an FTP server, when native ACL filesystem support has been around for a loooong time. :) Cheers, Jordan/Lns Xavier Brochard wrote: > Le lundi 02 février 2009 21:10:02 Scott Balneaves, vous avez écrit : > >> On Mon, Feb 02, 2009 at 12:54:52PM -0700, David Burgess wrote: >> >>> I'm sure there are other solutions, but mine has been to change the >>> default umask to something like 007 and then if I want user tina to be >>> able to edit files from joe, I just adduser tina joe, then tina can >>> edit joe's files. >>> >> The usual way to handle shared directories, within Unix, anyway, is by a >> combination of umask, and the setgid bit on the directory: >> >> mkdir /home/shared >> chgrp users /home/shared >> chmod g+w /home/shared >> chmod g+s /home/shared >> >> Now, you'll have a directory which is group-owned by "users". All users in >> the group "users" will be able to create content here, and *regardless* of >> their primary group ownership, any file they create within the "shared" >> folder, will be group owned by "user". >> >> This, coupled with a default umask of 007 makes it easy to create shared >> folders that just "do the right thing". >> > > The important word here is "created" > If a user move a file from his home to the shared directory, the group > ownership of the file will not change to "users". > This is a very common case. > So, I do like Jim, I allways set the primary group to "users". But it quickly > became a nightmare when I need different groups for different shared folders. > I > could use ACL but I've found easier to setup the shared directories through > samba or ftp server. > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
