Archlinux - systemd will cause challenges for Trinity

All, I apologize for my absence, but economic challenges demanded my time elsewhere -- and will for the next little while. I wanted to drop a note on Archlinux changes that impact Trinity. Specifically the massive transition in Arch from an 'initscript' startup to 'systemd'. I have moved a test machine to systemd. Trinity (hal) does not start when systemd is used. The problem appears to be a hang on X startup. However, initscript behavior can be retained even after the move to systemd that allows Trinity to continue to run -- flawlessly (3.5.13-SRU). If any other archer has time, please look into booting to tdm on Arch. Any issues with systemd/hal should be noted on the hal AUR page. Thanks. I will investigate as time permits, but I don't foresee much free time for the next several months. Keep fighting the good fight. -- David C. Rankin, J.D.,P.E.