From: Peter H. <hoe...@ne...> - 2002-12-30 19:09:09
|
We have, but with mixed results. OS X connecting via Samba stores the resource fork in a different manner than Netatalk. While this is fine in an only-OS X environment, sharing with OS 9 clients can be troublesome. For example, an Mac application copied to a server from OS X via Samba will not be usable by OS 9 clients connected via Netatalk. Also, some DTP apps try to use information in the resource fork in EPS files for placement and preview images. OS 9 clients can't see resource forks created by OS X, and vise versa. That said, Samba can act reliably as a file server for OS X clients - it's just a bit troublesome with a mixed OS 9/X environment. Also, we as well have encountered the -50 error under OS X via Netatalk - it's actually the only thing keeping us from migrating to OS X. - Peter Hoelter EDGE > design > advertising >> i have a user complaining that she can transfer large folder (100Mb) >> from Mac OS X (Jaguar) to netatalk-1.5.3.1 on linux 2.4.7-10 (redhat 7.2). >> So i made a search on the internet and mailing list archive on -50 error >> and find those things about: >> >> -first (the most important) this error exist on all versions of >> netatalk, from 1.4 to the latest 1.6 version > > Given that Mac OS X can be a samba client, has anyone tried to use it > that way and avoid netatalk until all its bugs are resolved? |