#NETATALK HOME DIRECTORY MAC#
Note: You still need to add the MAC Address and server name to the first line. This should be filled out using the values from afp_nf. So using rvice in the tarball, you should concentrate in the first node and the with the uuids as the part to edit. When Netatalk 2.2 becomes part of FreeNAS and has the link to Avahi, this entire file will be generated automagically. If Avahi was integrated with Netatalk, this would all happen automagically. Now we can more properly edit the rvices file. Nas#: cp -rp /usr/local/etc/netatalk /conf/base/etc/local/ It is also important now to make sure that this directory survives a reboot. Either way both values on each line are important You may have more lines, you may just have one. So look inside your afp_nf and you will see something like The second one is of interest and will help us better define the rvice file - which is key to getting these shares visible to Time Machine without first mounting them. If you then look in the /usr/local/etc/netatalk directory you will find two files This would be alot easier with a newer version of Avahi on FreeNAS and also having Netatalk compiled with Avahi support, but for now, for total OS X nirvana, the remaining steps can be followed:įor those that started using the tarballs earlier this week, the creation of /usr/local/etc/netatalk/ is an important step as it lets Netatalk generate and store UUIDs for volumes you have marked for Time Machine in the GUI or command line (indicated by options:tm in fault).Īfter starting Netatalk with that directory created, you should connect from your Mac to your Time Machine share(s). Hopefully by the Fall, Netatalk 2.2 will be in FreeBSD ports and will make its way to FreeNAS 8.x. If this doesn't work for you, it should be straightforward to revert to Netatalk 2.1.5, assuming you followed the backup instructions. It resumed using existing sparsebundle backups. I have tested this afpd binary with both Snow Leopard 10.6.8 and Lion 10.7. You must still connect to the share you want to use for Time Machine before you can select it in the Time Machine system preferences in Lion. Nas# /usr/local/etc/rc.d/avahi-daemon startĪFP shares should mount as normal.
Nas# cp /etc/local/avahi/services/rvice /conf/base/etc/local/avahi/services/ The following will make this change permanent after reboot avahi-services/rvice /etc/local/avahi/services This is necessary since this afpd binary is not avahi aware. Replace the bits with curly brackets with your installation information. uams /usr/local/libexec/netatalk-uamsĬreate a new directory for the signature fileĮdit the rvice file in avahi-services. Nas# mv /usr/local/libexec/netatalk-uams /usr/local/libexec/netatalk-uams-2.1.5Ĭd to the netatalk-2.2 directory that was untarred. Nas# mv /usr/local/sbin/papd /usr/local/sbin/papd-2.1.5 Nas# mv /usr/local/sbin/cnid_dbd /usr/local/sbin/cnid_dbd-2.1.5 Nas# mv /usr/local/sbin/cnid_metad /usr/local/sbin/cnid_metad-2.1.5 Nas# mv /usr/local/sbin/atalkd /usr/local/sbin/atalkd-2.1.5 Nas# mv /usr/local/sbin/afpd /usr/local/sbin/afpd-2.1.5 Untar and you will find the following files: Scp netatalk-2.2.tar.gz to your FreeNAS installation. In order to make your changes survive a reboot you must mount the filesystem read/write: Nas# /usr/local/etc/rc.d/avahi-daemon stop
There is an additional file you will need to edit for Avahi and copy into place. So this afpd binary will not automatically register with Avahi. I could not get the configure script to recognize Avahi on my FreeBSD 8.2 build box. I have compiled Netatalk 2.2 from Frank Lahm's master tag after he merged knu's fixes for FreeBSD.
#NETATALK HOME DIRECTORY HOW TO#
UPDATE 4: How to integrate the contents of the afp_nf file with the rvice file.
UPDATE 3: Tarball for amd64 now available. UPDATE 2: Initial release is for x86 systems. UPDATE: Updated tar ball link below with other binaries included, atalkd, cnid_dbd, chid_metad, papd. If someone is interested in doing this for FreeNAS 7 they can pull a snapshot of Frank Lahm's master branch from Sourceforge git and try themselves. These will not work on FreeNAS 7 and I have no plans to try to compile there. There is no warranty or support for the below. NOTE: This should only be attempted by those who are comfortable mucking about with their FreeNAS installation.
0 kommentar(er)
