Mk.558
Well-known member
I have 2.1.6 installed in the VM now, I'm going to do a test run to confirm anything before I push all throttles forward. Some more questions:
1) sudo update-rc.d netatalk defaults -- When is this supposed to be run? I ran it just after the install (sudo make install) and I get this:
From your earlier configuration files as shown here, which one is the /etc/default/netatalk? I'm not sure if any of the daemons in /etc/default/netatalk like ATALKD_RUN should be changed to "yes" or anything else.
EDIT: Finished, probably. Running sudo gedit /etc/init.d/netatalk restart results in an error: "45: eth1: not found". eth1 is how the Debian VM sees the ethernet port, and connects out to the web fine. eth0 in the config files doesn't work, replacing it with eth1 does nothing either.
1) sudo update-rc.d netatalk defaults -- When is this supposed to be run? I ran it just after the install (sudo make install) and I get this:
Code:
floe@debian:~/Downloads/netatalk-2.1.6$ sudo update-rc.d netatalk defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: netatalk stop runlevel arguments (0 1 6) do not match LSB Default-Stop values(1)
floe@debian:~/Downloads/netatalk-2.1.6$
EDIT: Finished, probably. Running sudo gedit /etc/init.d/netatalk restart results in an error: "45: eth1: not found". eth1 is how the Debian VM sees the ethernet port, and connects out to the web fine. eth0 in the config files doesn't work, replacing it with eth1 does nothing either.