Re: [Afpfs-ng-devel] afpcmd

[Alex d. <ale...@gm...>]

On 17-Jun-08, at 1:28 AM, Ralph Böhme wrote:
>
> 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*.

It depends on what the objective of netatalk is, and there may be  
different opinions on that.  I had thought that the objective was to  
make an AFP server that would mimic Apple's AFP servers.  If that were  
the case, then netatalk would provide unix privs for any AFP 3.x  
connection.

But I don't maintain (or contribute to) netatalk, so my opinion  
shouldn't count for much.  I just end up dealing with afpfs-ng bugs  
which are really netatalk config problems.

> 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"

Oh, of course.  And afpfs-ng detects that when it opens the volume.  
There's just bugs with how it handles that :)

- A