![]() Jul 08 11:31:08 rpi41 systemd: Starting Accessibility services bus. Jul 08 11:31:08 rpi41 dbus-daemon: Activating via systemd: service name='' unit='rvice' requested by ':1.3' (uid=2400 pid=785 comm="firefox-esr ") Jul 08 11:30:48 rpi41 systemd: rvice: Succeeded. Jul 08 11:30:46 rpi41 su: pam_unix(su:session): session opened for user root by (uid=2400) Jul 08 11:30:44 rpi41 systemd: Removed slice User Slice of UID 65534. Jul 08 11:30:44 rpi41 systemd: Stopped User Runtime Directory /run/user/65534. Rpi41/home/bls# journalctl -f # No new journal entries caused by the above Rpi41/home/bls# SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online -timeout=5 -i wlan0 Make sure DHX2 is available, if this is not here then something went wrong with libgcrypt.Code: Select all rpi41/home/bls# SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online -timeout=5 -i eth0 ![]() The result should look something like this: AFP reply from localhost:548ĪFP versions: AFP2.2,AFPX03,AFP3.1,AFP3.2,AFP3.3 If you didn’t do this then this doesn’t apply.įinally, if you get the dreaded “The version of the server you are trying to connect to is not supported” when trying to connect to your AFP server from your Mac then you should confirm what your server supports as there is likely something missing. For example, if you crafted an rvice file with record entries for your shares you no longer need this with zeroconf. There are a few things to watch out for, if you have an Avahi configuration from a previous install you may need to remove settings from there. With your configuration file in place, startup the server and connect to it from your favorite Mac: Here is a sample setup to get you started: If you have your file share settings in fault you will need to transcribe them into this new config file. This will be in /etc/afp.conf and is much easier to do than previous releases. Setup a configuration file for your server. The zeroconf attribute provides integration with avahi for resource discovery, and the –enable-fhs will install the server with the main configuration in /etc. The debian style init will create a startup script in /etc/init.d. configure -with-init-style=debian -with-zeroconf -enable-fhs Inside the directory with the extracted source code, do the following: In addition to the standard suite of build tools (make/gcc), you will also need ssl, PAM and crypt development libraries.Īpt-get install avahi-daemon libnss-mdns cracklib2-dev fakeroot libssl-dev libpam0g-dev libgcrypt11-dev ![]() Then use the following steps as a guideline for building and installing your Netatalk distribution: ![]() ![]() The version shipping with Ubuntu currently is rather outdated, so this is a necessity.Īfter downloading, extract everything into a source directory that you will use for building it. You can download the latest version from, which will be required for optimal support. While you can certainly use other methods (NFS/SMB), AFP is able to provide integrated support with your TimeMachine backup. Running AFP allows you to natively mount file shares from your Mac to your Linux based fileserver. This article outlines some of the things you will need to do to configure Netatalk assuming you are running Ubuntu server. Since my original posting on this a few years ago, this is now at version 3.0 and the configuration has changed somewhat. For those of us running Linux file shares at home, AFP support is provided using something called Netatalk. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |