Greg Freemyer schreef op 12-04-16 00:30:
It is a hassle to work with, but very flexible at the end of the day.
The syntax is not even inconvenient. It is pretty easy to add something to a group, or even to change the default (for newly created files). It's just that without a GUI you won't have any real awareness of it and now you need to 'constantly' use that getfacl to keep an awareness of the condition of your system. In addition to the fact that it just completely overrides everything. As a test I just gave myself write permission to some file in /etc. No problem at all. Makes system maintenance a lot easier though. Any file you regularly need to change? Just add your user. The issue I have with it is that it breaks all sense of sanity around the organisation of your filesystem. Now no longer need something to be in the right place, every place is now a right place ;-). Oh my user needs to edit a tree in /etc? Sure, no problem. Oh really that tree doesn't belong in /etc? Who cares! The thing doesn't exist on my NAS, not even as a third party package. Of course the NAS uses its own system. (( Funny thing. I map root to guest in NFS. In the NAS configuration, Guest does not have write access. However Guest is a member of Users, and I have given Users write access to a certain folder. Now Guest still has write access, because the NAS config only applies to shares. Ie. stuff exported through samba etc. However I have not set up nfs mapping. The remote user (of the nfs client) is different (in UID) than the local user (on the NAS). So my remote user actually doesn't have access. But root has, because it is guest. My intent was the exact reverse :p. I don't actually want these users to be mapped onto each other. I think I will just be bad and create two "Alien" users. Alien on the NAS will have the UID of the remote user, and Alien on the client will have the UID of my NAS user :p. Then, Alien will have write access on the NAS because I will give it some important group. Also, native files on the NAS will show up as "alien" on the remote. And files written by remote will show up as "alien" on the NAS. I just don't want these names to be linked/coupled. )).
That's why I was surprised the thread was pretty deep and no one had brought it up yet.
fyi: Windows has ACLs for NTFS as well. I find them a nightmare to work with in Windows. I think they are much cleaner in Linux.
Greg -- Greg Freemyer www.IntelligentAvatar.net
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org