manders2k
June 26th, 2005, 04:02 PM
So, I want to want to use an Ubuntu Linux computer as a file and print server for two Macs running OS X. I decided that netatalk was the best (fastest, most mac-integrated) way to go.
The first thing I tried was to compile netatalk 2.0.3 from source, as I've seen conflicting reports about pre-2.0 versions having terrible, horrendous issues with OS X. Anyone know if there is any truth to this, and what the issues are? I ran configure as: "./configure --enable-debian", and attempted to satisfy all the dependencies I could identify before I built it. It built fine, but I was totally unable to connect to the afpd daemon once it was installed and running (when using the Finder to "connect to server", it was unable to authenticate, and refused to ask for a username/password). The configuration was the default as shipped with the source (should offer a home directory).
So, I uninstalled it ("make uninstall") and tried the more obvious "apt-get install netatalk" (even though the version is 1.6.4a, alleged source of problems for OS X). It installed and I was able to connect to it in its default configuration, but could only authenticate with cleartext passwords. A little further investigation shows that uams_dhx.so (the module which allows encrypted password usage) does not ship with the package. The README.Debian file that was included with the package tells me that the Debian project refuses to link programs to OpenSSL due to a possible license conflict, and hence uams_dhx.so is not included. But, I'm welcome to rebuild the package with the DEB_BUILD_OPTIONS environment variable set to "ssl", and everything should be hunky dory. Thank you Debian for making things easy and convenient.
I tried teaching myself to rebuild a Debian package, but have been so far unable to build this package successfully. Currently, it is complaining about being unable to link to cracklib during the build process (though I did install cracklib2 and cracklib-runtime through synaptic or apt-get, I forget which; I also edited /etc/ld.so.conf to include /lib/ and /usr/lib/ and ran ldconfig to try to get it to link properly which didn't work; I didn't investigate what configure was doing to perform the test and re-teach myself all the crazy rules which is the linking process on Linux).
Extreme frustration is starting to set in.
Could someone please explain to me what the proper or best way to get a functioning copy of netatalk running (that does include uams_dhx.so and/or the pam equivalent) on a more or less fresh install of Ubuntu 5.04?
If someone is reading this who has some control of the Ubuntu documentation, I would suggest documenting the limitations of the netatalk package as distributed, and how to get around them.
Also, does anyone know why there isn't a netatalk package from the 2.0 line available?
Thanks for any help.
The first thing I tried was to compile netatalk 2.0.3 from source, as I've seen conflicting reports about pre-2.0 versions having terrible, horrendous issues with OS X. Anyone know if there is any truth to this, and what the issues are? I ran configure as: "./configure --enable-debian", and attempted to satisfy all the dependencies I could identify before I built it. It built fine, but I was totally unable to connect to the afpd daemon once it was installed and running (when using the Finder to "connect to server", it was unable to authenticate, and refused to ask for a username/password). The configuration was the default as shipped with the source (should offer a home directory).
So, I uninstalled it ("make uninstall") and tried the more obvious "apt-get install netatalk" (even though the version is 1.6.4a, alleged source of problems for OS X). It installed and I was able to connect to it in its default configuration, but could only authenticate with cleartext passwords. A little further investigation shows that uams_dhx.so (the module which allows encrypted password usage) does not ship with the package. The README.Debian file that was included with the package tells me that the Debian project refuses to link programs to OpenSSL due to a possible license conflict, and hence uams_dhx.so is not included. But, I'm welcome to rebuild the package with the DEB_BUILD_OPTIONS environment variable set to "ssl", and everything should be hunky dory. Thank you Debian for making things easy and convenient.
I tried teaching myself to rebuild a Debian package, but have been so far unable to build this package successfully. Currently, it is complaining about being unable to link to cracklib during the build process (though I did install cracklib2 and cracklib-runtime through synaptic or apt-get, I forget which; I also edited /etc/ld.so.conf to include /lib/ and /usr/lib/ and ran ldconfig to try to get it to link properly which didn't work; I didn't investigate what configure was doing to perform the test and re-teach myself all the crazy rules which is the linking process on Linux).
Extreme frustration is starting to set in.
Could someone please explain to me what the proper or best way to get a functioning copy of netatalk running (that does include uams_dhx.so and/or the pam equivalent) on a more or less fresh install of Ubuntu 5.04?
If someone is reading this who has some control of the Ubuntu documentation, I would suggest documenting the limitations of the netatalk package as distributed, and how to get around them.
Also, does anyone know why there isn't a netatalk package from the 2.0 line available?
Thanks for any help.