Re: [Netatalk-admins] RE: [Netatalk-devel] File Compatibility (was Re: [ANN] Netatalk 2.0 documentation and archives searchable)

[Craig R. <cr...@po...>]

On Fri, 2004-04-30 at 02:42, Bjoern Fernhomberg wrote:

> Netatalk can and will only talk AFP :-)
> If people really consider SMB a better alternative for accessing a server
> *from an OSX client*, they should use samba. And live with the consequences.

I tend to agree with you there.

> What you want is to be able to access the same share with both Netatalk and
> Samba *from OSX clients*. You can access the same volume with SMB/NFS/you
> name it, just not from OSX clients. Using the same volume with AFP/SMB/NFS
> cannot work anyway, mostyl due to codepage (volume encoding) issues. So
> simply forget about this.

Drat. While I don't need anything like this myself, it'd be nice to have
a solution as there is apparently a desire, if not a need, for it
elsewhere. I just found myself thinking that some trickery could be done
to _Samba_ so that ._ files were actually "virtual" files where samba
would translate access to them to access to the right bits of the
assocated .AppleDouble file on the fly. Unfortunately, as you say this
don't solve the precomposed/decomposed UTF-8 problem. It's also a recipe
for screaming disaster if two clients access the same file at the same
time, and probably horribly complicated.

I guess that serves to illustrate the scope of the problem, and why the
best solution seems to be to say "stuff it", as the benefits are small
anyway.

My organisation uses Samba and NetATalk for access to the same volumes,
with good results. The only thing I'm looking for is a nice way to lock
OSX/SMB clients out. I'm thinking of doing it by using Samba's user
mapping to map all OSX users to a user with no priveleges.

Craig Ringer