[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE & ACLs
From:       Edoardo Causarano <curious.corn () katamail ! com>
Date:       2001-11-14 22:03:54
[Download RAW message or body]

Alle 17:45, mercoledì 14 novembre 2001, Manuel Amador \(Rudd-O\) ha scritto:
> This is exactly what I have been looking for.
>
> For now, my small installations don't need ACLs, but for big customers
> (with big pockets) I really need ACLs.  Kludging around with standard
> UNIX permissions and umasks does not suffice.  Does anyone know if GNU
> tar support the ACL extensions? 

as far as the authors know no GNU tool handles them. You can cat the getfacl 
output to a file and tell setfacl to get the args from a file. It's a slight 
kludge but...

> Does also anyone know if (at least
> Linux from) any UNIX supports inheriting ACLs in directories (i.e. I set
> a 'bit' on a directory, and all created files into that directory get
> the same standard UNIX permissions and ACLs of the directory - minus the
> execution bits naturally).  

that's the default acl you're talking about
setfacl -m d:u:username::rw /shares/stuff
(notice the d:***)
adds rw access to username to any file created in /shares/stuff
don't know if you can do the X (caps) to add cd'ing to dirs in subtree.

> This has also come to Windows XP and it's
> very needed in our world.  Merely chmod g+s and umask 007 is not okay if
> you are using ACLs to grant a group read permission to all files in a
> directory.
>
> Please 'reply to all'.  Thanks
>
> For now try to begin the transition with StarOffice for windows.  Once
> they get used to it, the introduction of KDE into their desktops (and
> brains) will be extremely easy.  My clients are very happy (and amazed)
> with KDE.  Especially the fact that they get to use their old 486s as
> terminals.  Computers in my country are expensive (or is it that people
> here are poor?).
>
> Thanks again.

Edo
if you feel it's OT well... sorry ;-)

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]