18 Mar
2013
18 Mar
'13
2:07 p.m.
I think the problem is not the startup scripts, because initscripts
are still compatible, but that HAL has finally gone the way of the
Dodo. I follow the hal package in the AUR and it seems that it hasn't
been working for some time.
As for systemd, most distros, for better or worse, are switching to
it. Ubuntu is, OpenSuse and the lot use it, as well as ArchLinux.
Might be something to be at least aware of.
Good to see you still around,
Calvin
On 18 March 2013 10:03, David C. Rankin <drankinatty(a)suddenlinkmail.com> wrote:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting