Menu
▾
▴
devil-linux-discuss
|
From: Stuart H. <st...@ha...> - 2013-02-26 18:06:32
|
Hello DL Community! Devil-Linux 1.6.3 brings lots of software updates, in addition to support for being a file and backup server for Apple computers. I was very pleased to hear about the support for Apple computer backups. I'm presuming this means support for Apple's proprietary "Time Machine" facility. I've looked into adding this to my own DL box, and the preferred Linux setup seems to be netatalk plus avahi. On my DL 1.6.3 system, I can see the avahi support, but I haven't been able to find netatalk. What am I missing? Does DL 1.6.3 include netatalk/afpd? Am I obliged to configure and build DL myself to get netatalk, or perhaps am I supposed to use samba or nfs instead? Or perhaps I am utterly confused, and the quoted email above is referring to bacula? Thank you in advance, stuart |
|
From: Heiko Z. <he...@zu...> - 2013-02-26 23:49:48
|
Stuart, Netatalk is supported via afp.conf. We have Time Machine support now in DL and it works. This is what you need to add to afp.conf for time machine support, in addition to starting avahi: [Time Machine] path = /var/path/to/backup/dir/ time machine = yes # limit timemachine volume size to 50MB vol size limit = 50000 Best Regards Heiko Zuerker From: Stuart Hastings [mailto:st...@ha...] Sent: Tuesday, February 26, 2013 12:05 PM To: dev...@li... Subject: [Devil-Linux-discuss] Time Machine and netatalk Hello DL Community! Devil-Linux 1.6.3 brings lots of software updates, in addition to support for being a file and backup server for Apple computers. I was very pleased to hear about the support for Apple computer backups. I'm presuming this means support for Apple's proprietary "Time Machine" facility. I've looked into adding this to my own DL box, and the preferred Linux setup seems to be netatalk plus avahi. On my DL 1.6.3 system, I can see the avahi support, but I haven't been able to find netatalk. What am I missing? Does DL 1.6.3 include netatalk/afpd? Am I obliged to configure and build DL myself to get netatalk, or perhaps am I supposed to use samba or nfs instead? Or perhaps I am utterly confused, and the quoted email above is referring to bacula? Thank you in advance, stuart |
|
From: Heiko Z. <he...@zu...> - 2013-02-26 23:57:24
|
Stuart, OOOOPS! I checked and it seems like I forgot to enable netatalk in the build configuration. I fixed it in CVS and I’ll upload the nightly build tomorrow to our testing directory, if it compiles successfully. Best Regards Heiko Zuerker From: Stuart Hastings [mailto:st...@ha...] Sent: Tuesday, February 26, 2013 12:05 PM To: dev...@li... Subject: [Devil-Linux-discuss] Time Machine and netatalk Hello DL Community! Devil-Linux 1.6.3 brings lots of software updates, in addition to support for being a file and backup server for Apple computers. I was very pleased to hear about the support for Apple computer backups. I'm presuming this means support for Apple's proprietary "Time Machine" facility. I've looked into adding this to my own DL box, and the preferred Linux setup seems to be netatalk plus avahi. On my DL 1.6.3 system, I can see the avahi support, but I haven't been able to find netatalk. What am I missing? Does DL 1.6.3 include netatalk/afpd? Am I obliged to configure and build DL myself to get netatalk, or perhaps am I supposed to use samba or nfs instead? Or perhaps I am utterly confused, and the quoted email above is referring to bacula? Thank you in advance, stuart |
|
From: Stuart H. <st...@ha...> - 2013-02-27 02:33:53
|
On Feb 26, 2013, at 3:56 PM, Heiko Zuerker wrote: > Stuart, > > OOOOPS! > I checked and it seems like I forgot to enable netatalk in the build configuration. > I fixed it in CVS and I’ll upload the nightly build tomorrow to our testing directory, if it compiles successfully. Gosh, that was fast! I probably won't get to try it until this weekend, but I'll let you know how I come out. Thank you very much! stuart > Best Regards > Heiko Zuerker > > From: Stuart Hastings [mailto:st...@ha...] > Sent: Tuesday, February 26, 2013 12:05 PM > To: dev...@li... > Subject: [Devil-Linux-discuss] Time Machine and netatalk > > Hello DL Community! > > Devil-Linux 1.6.3 brings lots of software updates, in addition to support > for being a file and backup server for Apple computers. > > > > I was very pleased to hear about the support for Apple computer backups. I'm presuming this means support for Apple's proprietary "Time Machine" facility. > > > > I've looked into adding this to my own DL box, and the preferred Linux setup seems to be netatalk plus avahi. > > > > On my DL 1.6.3 system, I can see the avahi support, but I haven't been able to find netatalk. > > > > What am I missing? Does DL 1.6.3 include netatalk/afpd? Am I obliged to configure and build DL myself to get netatalk, or perhaps am I supposed to use samba or nfs instead? > > > > Or perhaps I am utterly confused, and the quoted email above is referring to bacula? > > > > Thank you in advance, > > > > stuart > > > |
|
From: Heiko Z. <he...@zu...> - 2013-02-28 00:27:25
|
Stuart, The files are uploaded to ftp.devil-linux.org/pub/devel/testing Best Regards Heiko Zuerker From: Stuart Hastings [mailto:st...@ha...] Sent: Tuesday, February 26, 2013 8:33 PM To: Heiko Zuerker Cc: dev...@li... Subject: Re: [Devil-Linux-discuss] Time Machine and netatalk On Feb 26, 2013, at 3:56 PM, Heiko Zuerker wrote: Stuart, OOOOPS! I checked and it seems like I forgot to enable netatalk in the build configuration. I fixed it in CVS and I'll upload the nightly build tomorrow to our testing directory, if it compiles successfully. Gosh, that was fast! I probably won't get to try it until this weekend, but I'll let you know how I come out. Thank you very much! stuart Best Regards Heiko Zuerker From: Stuart Hastings [mailto:st...@ha...] Sent: Tuesday, February 26, 2013 12:05 PM To: dev...@li... Subject: [Devil-Linux-discuss] Time Machine and netatalk Hello DL Community! Devil-Linux 1.6.3 brings lots of software updates, in addition to support for being a file and backup server for Apple computers. I was very pleased to hear about the support for Apple computer backups. I'm presuming this means support for Apple's proprietary "Time Machine" facility. I've looked into adding this to my own DL box, and the preferred Linux setup seems to be netatalk plus avahi. On my DL 1.6.3 system, I can see the avahi support, but I haven't been able to find netatalk. What am I missing? Does DL 1.6.3 include netatalk/afpd? Am I obliged to configure and build DL myself to get netatalk, or perhaps am I supposed to use samba or nfs instead? Or perhaps I am utterly confused, and the quoted email above is referring to bacula? Thank you in advance, stuart |
|
From: Stuart H. <st...@ha...> - 2013-03-01 18:51:56
|
On Feb 26, 2013, at 6:32 PM, Stuart Hastings wrote: > > On Feb 26, 2013, at 3:56 PM, Heiko Zuerker wrote: > >> Stuart, >> >> OOOOPS! >> I checked and it seems like I forgot to enable netatalk in the build configuration. >> I fixed it in CVS and I’ll upload the nightly build tomorrow to our testing directory, if it compiles successfully. > > Gosh, that was fast! > > I probably won't get to try it until this weekend, but I'll let you know how I come out. > > Thank you very much! > > stuart > > >> Best Regards >> Heiko Zuerker I burned a CD with 1.6.4-2013-02-27 this evening, and I tripped over a minor issue. While my system was rebooting, 1.6.4 asked if I wanted to upgrade my configuration (1.6.3 -> 1.6.4). I agreed to the upgrade, and it "broke" my configuration! When DL finished booting, I logged into my personal (non-root) account on the DL box and tried "ping google.com", and it said (paraphrased) icmp open socket; operation not permitted I have no idea what this symptom might imply. (Clues appreciated!) Re-trying the ping from the root account worked, but other machines on my local network couldn't reach the internet; it seems they could get DHCP service from my DL box, but not much else. For example, DNS wasn't working at all ("ping: cannot resolve google.com: Unknown host"). (I didn't think to try pinging a valid IP address from a networked machine. Duh.) I reverted everything, did some experiments, and was able to get 1.6.4 working with an old configuration (old etc-mods.tar.bz2); this time, I did not agree to the upgrade. I did think to preserve the troublesome auto-upgraded etc-mods.tar.bz2 file; I unpacked it alongside an older working counterpart and diff-ed the trees. Alas, I see nothing in the diff that explains the failure to me. I *must* be missing something, because it works with the older one, and fails with the newer, auto-upgraded one... I'll spare you the diff, but here are the files that changed when I diff-ed the tarballs: etc-mods/dhcpcd/db/dhcpcd-eth0.lease etc-mods/dnsmasq.conf (I added a comment) etc-mods/group- (I added a local account) etc-mods/gshadow- etc-mods/passwd- etc-mods/shadow etc-mods/shadow- etc-mods/shorewall/blacklist (I added a comment) root/.bash_history root/.viminfo I don't know what's in the dhcpcd-eth0.lease file (I have only a guess), but it's not clear to me that it could be causing my troubles, either. I think I understand all the rest of the differences, and I'm pretty certain none of them could have caused my breakage. (Recall that the working config file was an older version, saved before I created my local account.) Anyways, I have 1.6.4-2013-02-27 running now, and I can see afpd and afp.conf, so I can take my next baby next step towards Time Machine support. :-) Any clues to help me understand how I broke the auto-upgrade would be greatly appreciated. :-) :-) Thank you very much for Devil Linux, stuart |
|
From: Heiko Z. <he...@zu...> - 2013-03-01 22:34:00
|
Quoting Stuart Hastings <st...@ha...>: > I burned a CD with 1.6.4-2013-02-27 this evening, and I tripped over a > minor issue. > > While my system was rebooting, 1.6.4 asked if I wanted to upgrade my > configuration (1.6.3 -> 1.6.4). I agreed to the upgrade, and it "broke" > my configuration! When DL finished booting, I logged into my personal > (non-root) account on the DL box and tried "ping google.com[1]", and it > said (paraphrased) > > icmp open socket; operation not permitted > > I have no idea what this symptom might imply. (Clues appreciated!) > > Re-trying the ping from the root account worked, but other machines on > my local network couldn't reach the internet; it seems they could get > DHCP service from my DL box, but not much else. For example, DNS wasn't > working at all ("ping: cannot resolve google.com[1]: Unknown host"). (I > didn't think to try pinging a valid IP address from a networked machine. > Duh.) > > I reverted everything, did some experiments, and was able to get 1.6.4 > working with an old configuration (old etc-mods.tar.bz2); this time, I > did not agree to the upgrade. > > I did think to preserve the troublesome auto-upgraded etc-mods.tar.bz2 > file; I unpacked it alongside an older working counterpart and diff-ed > the trees. Alas, I see nothing in the diff that explains the failure to > me. I *must* be missing something, because it works with the older one, > and fails with the newer, auto-upgraded one... > > I'll spare you the diff, but here are the files that changed when I > diff-ed the tarballs: > > etc-mods/dhcpcd/db/dhcpcd-eth0.lease > etc-mods/dnsmasq.conf (I added a comment) > etc-mods/group- (I added a local account) > etc-mods/gshadow- > etc-mods/passwd- > etc-mods/shadow > etc-mods/shadow- > etc-mods/shorewall/blacklist (I added a comment) > root/.bash_history > root/.viminfo > > I don't know what's in the dhcpcd-eth0.lease file (I have only a > guess), but it's not clear to me that it could be causing my troubles, > either. I think I understand all the rest of the differences, and I'm > pretty certain none of them could have caused my breakage. (Recall that > the working config file was an older version, saved before I created my > local account.) > > Anyways, I have 1.6.4-2013-02-27 running now, and I can see afpd and > afp.conf, so I can take my next baby next step towards Time Machine > support. :-) Any clues to help me understand how I broke the > auto-upgrade would be greatly appreciated. :-) :-) > > Thank you very much for Devil Linux, > > stuart Stuart, Yes this is certainly weird. The file dhcpcd-eth0.lease stores the IP address which you got from the DHCP server, so the client can request the same one again after the reboot. Is it possible that with the new config you IP address changed and that this may have caused troubles with a firewall rule which may have the old address configured? Heiko Links: ------ [1] http://google.com -- Regards Heiko Zuerker http://www.devil-linux.org |
