Home > Uncategorized > Netatalk 3.1 installation on Debian 6.0

Netatalk 3.1 installation on Debian 6.0

I use a Debian 6.0 box running Netatalk to backup my Mac using Timemachine. This all worked nicely until recently upgrading to Mountain Lion when, big surprise, Timemachine/Netatalk became unreliable. This seems to happen pretty much every time Apple bumps OSX – for reasons know only to them, all sorts of breaking changes are required to change from one feline to another, while providing minimal value to users.

Some research later, it became clear that Mountain Lion needs Netatalk 3.1 (post 12/8/22) to run reliably.

The instructions here worked well: https://gist.github.com/2856490

Note: do not forget the “./bootstrap”. Also, missing from the requirements are autotools (automake) and libtool.

Quoted from github:

Install prerequisites:

    $ sudo apt-get install build-essential pkg-config checkinstall git-core avahi-daemon libavahi-client-dev

Download src:

    $ cd /usr/local/src
    $ git clone git://netatalk.git.sourceforge.net/gitroot/netatalk/netatalk
    $ cd netatalk
    $ ./bootstrap

Find current version of Berkeley DB available

    $ apt-cache search libdb

Mine was 5.1, so I'll install that

    $ sudo apt-get install libdb5.1-dev db-util db5.1-util

Same for libgcrypt:

    $ apt-cache search libgcrypt
    $ sudo apt-get install libgcrypt11 libgcrypt11-dev

Configure install

    $ ./configure --with-init-style=debian --with-zeroconf

Build!

    $ make
    $ sudo checkinstall

Config is in /usr/local/etc/afp.conf
Categories: Uncategorized Tags:
  1. uccoffee
    January 17th, 2013 at 02:23 | #1

    I m up to this step… fail 🙁

    [email protected]:/usr/local/src/netatalk# ./configure –with-init-sty –with-zeroconf
    -bash: ./configure: No such file or directory

    • peterk
      January 17th, 2013 at 02:34 | #2

      If you followed the steps, you should be in /usr/local/src/netatalk, where you have cloned netatalk from github.
      And in that folder, you should find “configure”. If not, something is wrong.
      Did the you run the ./bootstap and did it complete successfully?

  1. No trackbacks yet.