I wouldn''t say that. Apart from the occasional hang
(now cured), it's fine. What I would like now is more
speeeeeeeeeeed. I have upgraded to a gigabit network (which didn't cost me
much to do) and this helped a bit but build times, especially limited to one
parallel build task, are roughly 3 times as long as on a local file
system. I would imagine an intermediate *nix server would make this even
worse.
I did try a few other things: Sharity (an alternative SMB
client for the Mac, but very slow) and a couple of NFS servers for Windows (also
too slow and unreliable). The other option would be an AFP server for
Windows (such as MacServerIP or ExtremeZ-IP) but these are expensive. If
anyone is using these and gets good results I'd like to know. They do
offer free trials.
Paul Sanders
----- Original Message -----
Sent: Monday, January 11, 2010 4:02 PM
Subject: Re: File encoding for files ported between Mac and
Windows?
In general I've found the SMB client in OS X to be very
buggy, my solution is to have a share available as both SMB and Appletalk.
If the share resides on a 'nix server then it's easy to setup netatalk in an
afternoon. If the share is on a WIN200X server the workaround is a little
more bulky - have a n intermediate'nix server (other then OS X Server) mount the
share SMB share then export that mounted share via netatalk. It's ugly,
but effective.
|