The Grumpy Editor's guide to surviving the systemd debate [LWN.net]

The Grumpy Editor's guide to surviving the systemd debate

Posted Nov 13, 2014 18:06 UTC (Thu) by bronson (subscriber, #4806)
In reply to: The Grumpy Editor's guide to surviving the systemd debate by rvfh
Parent article: The Grumpy Editor's guide to surviving the systemd debate

This sounds fascinating! Any chance you wrote it up? I've been meaning to do it too but haven't found the round tuits yet.

to post comments

The Grumpy Editor's guide to surviving the systemd debate

Posted Nov 16, 2014 11:22 UTC (Sun) by jonnor (guest, #76768) [Link] (2 responses)

systemd on Raspberry PI you mean? I use Arch Linux on my RPis, which comes with systemd by default. I'd expect installing systemd on RPi on the default Debian-based image to be like in https://wiki.debian.org/systemd
In general I'd recommend not installing the package which replaces /sbin/init until working with init=/bin/systemd has been confirmed. Its just good practice.

The Grumpy Editor's guide to surviving the systemd debate

Posted Nov 17, 2014 12:37 UTC (Mon) by peter-b (guest, #66996) [Link]

I use systemd on my Pidora print server. It works beautifully. *shrug*

The Grumpy Editor's guide to surviving the systemd debate

Posted Nov 17, 2014 13:41 UTC (Mon) by rvfh (guest, #31018) [Link]

Well, I have a spare one that I use for all kinds of tests before I apply them to the 'production' ones (those that manage my lights, gates, radiators...)

I also run the upgrades on that one to make sure things don't break before upgrading the rest :-)

Example of SysVinit and SystemD configs

Posted Nov 17, 2014 13:46 UTC (Mon) by rvfh (guest, #31018) [Link]

If you look in http://sourceforge.net/p/hnet/code/ci/master/tree/etc/dae..., there are two files of interest:
* hnet is the sysvinit script
* hnet.service is the systemd service file

Seems I did not commit the upstart one but I can do if that's of interest to somebody (I'll have to test it first though...)

Also, I am not sure the sysvinit one is on par with the systemd one, as systemd restarts my daemon if it disappears for any reason...