Re: [Afpfs-ng-devel] afpcmd

[Ralph B. <ra...@rs...>]

Alex,

Am 16.06.2008 um 23:19 schrieb Alex deVries:
> The unix permissions situation in netatalk is a bit odd, and it is  
> likely true that afpcmd is broken in that it expects netatalk to  
> have unix permissions enabled.  I see this as a bug in netatalk, but  
> afpfs-ng should be able to handle a broken netatalk.

Imo it's not a bug and it's not broken, it's just *different*.

> I haven't understood why netatalk doesn't have unix privs enabled by  
> default, and my discussions with the netatalk folks haven't cleared  
> that up.

What happens is (afaikt):
- OS X and Helios signalize to clients "I support UNIX perms", and  
handle all the difference between classic "inherited perms" vs. UNIX  
perms _internally_, you won't see any difference on the wire in the  
packets the server generates.
- netatalk when running withouth "upriv" doesn't set "support UNIX  
perms"

>  Any Apple AFP server released since Mac OS 10.1 (except the airport  
> extreme) has that turned on by default.

See above: the difference is not just what is enabled by default, but  
how it's implemented.

> There's another odd netatalk bug which doesn't let you set certain  
> bits with chmod (like the x bit).  That's in raw 2.0.3 (now three  
> years old), but has been fixed in CVS.

I know. I'm working from CSV Base.

> I try to detect these situations with unix privs in afpfs-ng; you  
> can see this by doing a 'status' command.

That gave me a coredump... ;o) If I have the time I'll look into it,  
but afair it coredumped whe working on a volume without upriv.

> Thanks for using afpfs-ng...

Thanks for writing!

Regards,
-Ralph