netatalk

manuelsosi · 22. Januar 2016

Hi!
I'm testing version 3 and I'm trying to install the netatalk plugin although I get the following error:

Code

root@omv3:~# apt-cache search netatalk


gosa-plugin-netatalk - netatalk plugin for GOsa²


python-reconfigure - simple config file management library


openmediavault-netatalk - OpenMediaVault netatalk (AppleTalk Protocol Suite) plugin


root@omv3:~# apt-get install openmediavault-netatalk


Reading package lists... Done


Building dependency tree       


Reading state information... Done


Some packages could not be installed. This may mean that you have


requested an impossible situation or if you are using the unstable


distribution that some required packages have not yet been created


or been moved out of Incoming.


The following information may help to resolve the situation:


The following packages have unmet dependencies:


 openmediavault-netatalk : Depends: netatalk but it is not installable


E: Unable to correct problems, you have held broken packages.

Alles anzeigen

subzero79 · 22. Januar 2016

Netatalk is not available yet in omv 3 because debian jessie has no netatalk packages. Is not clear the future of the plugin. Please remove the plugin and use samba or compile your own version of netatalk without the plugin.

Zeitkind · 26. Februar 2016

The old omv plugin uses /etc/netatalk/* for the configuration - which is for version <3.x The newer version >3.x use /usr/local/etc/afp.conf for _all_ configurations.
See http://netatalk.sourceforge.net/3.1/htmldocs/upgrade.html for differences. If you really need Netatalk, you should NOT use the pre-built debian binaries provided by several sites. Most ready-made binaries are compiled with tracker support for Spotlight. This is nice, but has much problems with headless installations like omv. If you build from sources, see
http://netatalk.sourceforge.ne…_3.1.8_on_Debian_8_Jessie
for required packages and use
./configure --with-init-style=debian-systemd --without-libevent --without-tdb --with-cracklib --enable-krbV-uam --with-pam-confdir=/etc/pam.d --with-dbus-sysconf-dir=/etc/dbus-1/system.d
to configure. Do NOT try to install the old plugin, it won't work.
You will need to define your shares manually in /usr/local/etc/afp.conf like

[Public]
path= /media/111a111b-2222-3333-4444-4507f4974ec2/public/
invisible dots = yes

See the man pages for more. To start Netatalk use
systemctl enable netatalk
systemctl start netatalk

If you see a message like
root@omv:~# systemctl start netatalk
Failed to start netatalk.service: Unit netatalk.service is masked.
then recheck your configuration and then unmask with
systemctl unmask netatalk
and try again.

You will get a running AFP-server without control via the omv GUI. It works, but you need to do all configurations manually. If you are not used to fix things on a command shell, I recommend using SMB for now.

subzero79 · 26. Februar 2016

Is your choice to use the official Sourceforge.org tarball but there is an unofficial debian style repo ready for deb packaging here which is up to date with latest version.
https://github.com/adiknoth/netatalk-debian

Zeitkind · 27. Februar 2016

There is a good and easy howto for Debian on the netatalk site and you can control with what options (e.g. using tracker or not and what authentifications) you compile. I know there are also a lot .deb's around for easy install, though I'd only trust the original sources. But well, your choice.
Nevertheless, using Netatalk had always some glitches (cross-protocol file locking with SMB?) and waiting for the next major Samba-release with better built-in support for Macs (ADS) and Spotlight might be a good idea. I need AFP for some very old machines, but most people with newer Macs and OS X >10.7 should be happy with SMB nowadays.

subzero79 · 27. Februar 2016

Well I've built it with the default options and Pam works with default usernames.
Only reason I use it is for time machine.
The tutorial doesn't configure the prefix correctly, as is pointing the configuration to /usr/local/etc.
And also it doesn't package so you have to manually remove then which is not good.

Zeitkind · 27. Februar 2016

The path /usr/local/etc is the default place for the configuration and won't get harmed if old tools mess up the config.
I know, that many people use timemachine via network and use a NAS as target. This works kinda fine for wired networks, but I recommend against if using wifi. I've seen dozens of broken backups whis way.

subzero79 · 27. Februar 2016

What usually do is the first backup is wired (because it takes ages), then over wifi. Never had a problem.
I hope the plugin gets ported, but I'll require some effort to adapt to the new syntax

derbeisser · 25. März 2016

Im interested in AFP aswell.
Of Course because of Time Machine support but I still think AFP has some features which makes it way more comfortable to use with OSX instead of SMB (for example Speed).

I hope this Thread gets an Update, when there is a official Version.

Thx.

Jetzt mitmachen!