Subject: Re: Netatalk + Samba together: too many problems...
From: Frank Jördens (frank@joerdens.de)
Date: Mon Nov 13 2000 - 11:28:07 EST
> > 3) "Lock" flag (from a Mac client point of view) and "Read
> > only" flag (from
> > a Win client point of view) are not synchronized.
>
> This is a problem with Samba. Samba maintains its own concept of file
> locking, avoiding the native locking mechanisms for speed. I believe
> the Samba team has plans to change this.
What exactly is the problem with this? We have about 20 Macs and 10 PCs
here, and I haven't noticed any Problems, except for the charset mapping
issue which I am trying to solve with a current developer version of
netatalk (Netatalk 1.4b2+asun2.1.1 - which the original poster mentioned
- does not support the -mswindows option), namely
pre-asun2.1.4-37b.tar.gz, which unfortunately has a broken
authentication module, it seems (at least my efforts to get it to work
so far have been futile). the newer versions 38b and 39b have exactly
the charmapping broken (I did verify that for 38b, not for 39b, which is
just hearsay).
>
> > 4) Last but not least: renaming, deleting, copying files
> > from a Win client
> > are absolutly insane operations. When you rename a file
> > using a Win client
> > for example, the renaming process does not rename the .AppleDouble
> > corresponding file, so the file losts its resource fork
> > from a Mac point of
> > view.
>
> I thought compiling Samba with the "netatalk" option solved some of
> these issues.
What effect does that have exactly (we haven't noticed any issues with
this so far)?
- Frank
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:37 EST