Change build to use netatalk3 instead of netatalk2
Change build to use netatalk3 instead of netatalk2
Merge branch 'netatalk3' of gitserver:/git/repos/freenas-build/freenas into netatalk3
Revert "Dear perl,"

Unfortunately netatalk3 requires perl, so resurrect it from the dead.
This reverts commit 22ebffb61f86475c52532c8b92e0704983c08aa1.
Revert "Revert "Dear perl,""

This reverts commit 68ee6e172578c91c40919f555a0d5696df45401d.
After further consideration, perl can still DIAF.
Use the django ORM to generate the config file for netatalk.

This is currently completely broken, as the startup script simply
calls a python script that then uses the ORM to grab a few things,
but does NOT generate a valid config file for netatalk2 or netatalk3.

In addition because the ORM is so expensive we are going to need
a way to not call it if no config needs to be generated.  So the
rc.d script will need to be smarter.
Only build the config file when the service is enabled.
Incremental work on the config file generator for netatalk3

Fairly soon here I'm going to need to change the GUI as many
options have come and gone.

Also there's a ton of stuff for using netatalk3 with AD and
LDAP that can all get hooked up.
Netatalk3 uses a single rc script to manage it's daemons.

Chase this change.  In addition chase the changes to the startup infrastructure
and the build system that are needed for building, starting, restarting, and so forth.
Changes to the GUI for netatalk3

A number of things change between netatalk2 and 3.
Some options went away, others were added.
Fix typo in field name for migration.
typo fix
Merge remote-tracking branch 'origin/netatalk3'