Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: compsos on August 10, 2004, 04:55:09 AM
-
Hi
We have been working on problems with netatalk and Mac OS9.2. So far have compiled the BerkeleyDB updtae and Netatalk 2.0.2beta2. But the new version seems to be using different conf file paths to the original SME version 1.5.
Does anyone know or know how to find out what might have to be customisized for SME 6.0.1 for Apple computers.
Regards
Gordon
-
it was discussed some time ago - so search might help.
There are 14 Macs behind a sme 601 as I type and none has a problem (hm - :lol: all are OSX)
try conecting to sme using ip and see if your problem goes away - anyway - get osx - it's a speed demon on a net.
-
it was discussed some time ago - so search might help.
There are 14 Macs behind a sme 601 as I type and none has a problem (hm - :lol: all are OSX)
try conecting to sme using ip and see if your problem goes away - anyway - get osx - it's a speed demon on a net.
Unfortuneatly we have to work with the OS9.2 but the netatalk 2.0.2 is required for OSX (documentation).
What protocols are you using with the Macs?
Is there a download for OS9.2 to use IP and not Appletalk?
-
slect appletalk in the chooser - there should be "ip address" or somelike button....
then once connected either one can use autoconnect or make an alias of the mounted volume -
it's interesting - how exactly something is misehaving? say files damaged or whatelse.
how many users / systems etc are there.
have you set up the ip's on macs correctly?
Have you tried connecting using samba (ie DAVE or was there another tool)
Is this misbehavious only for connecting to sme?
Do you use antivirus software on macs ?? :lol: :lol: :lol: :lol:
(really think one is needed?(
-
We are progressing.
Our problems have been documented elsewhere. So I doubt if this is the only system to suffer this problem.
The problem : files on the SME Server not being handled correctly by Mac OS9.2 (ie) problems with moving and deleting and the associated resource fork file.
We had no problems in email or internet access only file handling.
The Solution:
1 Upgrade BerkeleyDB system. Files avaialable from http://www.sleepycat.com
2 Upgrade Netatalk (sourceforge) to 2.0-beta2 (currently the latest with additional support for OSX)
3 Configure the conf files. This is now my current stumbling point. The new netatalk has its configuration files at /usr/local/etc/netatalk and SME templates the /etc/atalk. Does anyone know how to either
1 modify SME to template on the netatalk system
or
2 permanently get netatalk to refer to the SME conf files.
The 2nd choice is perferable for any future post-upgrade commands etc.
Also would like to build a set of RPMs to handle all this. Again if anyone has any ideas on how to construct these RPMs so they would not break everything, I would like to hear from you.
The new netatalk appears to be very stable. More testing still needs to be done.