Arch Linux User Repository

With the help of WarheadsSE (Mostly him. Alright basically only him. BUT I BUGGED HIM TO HELP) this PKGBUILD allows for hamachi installation on arm device. https://github.com/WarheadsSE/PKGs

Thanks for your feedback. I have made a revision to Haguichi that removes any dependencies on the scripts' output (http://bazaar.launchpad.net/~ztefn/haguichi/trunk/revision/306). If your not afraid of Mono you should try running Haguichi some day! With these changes the next release should work seamlessly on Arch too. :D

I was referring to you, not your Haguichi application. *People* using 'systemd' should only control daemons via 'systemctl'. Quamachi has been around for over five years, which means I introduced that Bash script long before 'systemd' came into existence. The other 'sysvinit' scripts output the same errors when using 'systemd'. For that reason, I don't want to change this one. By the way, I'd like to mention that I think Haguichi looks pretty impressive from the screenshots. Keep up your good work!

Yes, that's obvious. The reasoning for doing so was not obvious to me because you stated earlier on that one should _only_ attempt to control the daemon via systemctl. I think it's perfectly fine if packagers do it their own way and alter the script to work (better) with the distribution. In fact, I currently prefer to utilize these (optimized) scripts rather than shipping my own (generic) script like Quamachi. For that reason, I would just like to see these scripts to standardize on start/stop/restart output and not throw any errors when executed manually. If your not willing to alter your sysvinit script, then no harm is done. I will adapt Haguichi to rely less (or not at all) on the scripts' output.

I thought it would have been pretty obvious that the Bash script you referred to removes the need to care about whether a system uses 'sysvinit' or 'systemd'. It's foolish to assume that all Linux distributions will use the daemon controller supplied with Hamachi. Some of them will always want to do it their own way.

Quamachi doesn't seem to use the systemctl command either. Instead it uses it's own shell script that --just like the sysvinit script-- starts or kills /opt/logmein-hamachi/bin/hamachid. Seems duplicate effort to me. Why is reinventing the wheel any better than using what's already provided by the logmein-hamachi package? I'm actually the Haguichi developer... *waves hands*

If you're using 'systemd', you should only attempt to control the daemon via "systemctl [action] logmein-hamachi.service". Haguichi shouldn't rely on the 'sysvinit' script and its description string. Tell the developer to fix his code or just use Quamachi.

Using this package on Cinnarch the sysvinit script produces the following errors when using start/stop/restart: /etc/rc.d/logmein-hamachi: line 30: /etc/rc.conf: No such file or directory /etc/rc.d/logmein-hamachi: line 31: /etc/rc.d/functions: No such file or directory /etc/rc.d/logmein-hamachi: line 88: stat_done: command not found /etc/rc.d/logmein-hamachi: line 88: rm_daemon: command not found /etc/rc.d/logmein-hamachi: line 78: stat_done: command not found /etc/rc.d/logmein-hamachi: line 78: add_daemon: command not found /etc/rc.d/logmein-hamachi: line 103: stat_done: command not found Also, because the sysvinit script has a different DESC than the original hamachi-init script Haguichi doesn't recognize the output.

I have removed all custom variables.