On 11/10/16 22:30, Craig Sanders via luv-main wrote:
...
I mostly gave in. I converted two of my home systems to systemd a few days ago
(including my primary desktop/server machine). I'm hoping it's easier to work
around systemd'ѕ bugs and annoyances than to have to deal with the (expected
but unwanted) future of packages having sysvinit support dropped. certainly
less work than converting every new debian system I build to sysvinit or
openrc or something.
I was rebooting anyway in order to replace a failed SSD on one machine and
convert both of them to root on ZFS. It booted up OK on both, so I made it
the default. If it refrains from sucking badly enough to really piss me off
for a decent length of time, i'll leave it as the default.
At least debian's systemd disables some of the extra crap by default...and
debian's update-grub makes menu entries for both systemd and sysvinit so you
can test it before committing to it on any given machine.
...
I run Fedora, which has had systemd for a while, and have had few issues
with it.
However Raspian now has systemd, via Debian, and its stock
implementation of NFS doesn't fully implement all the services needed to
run rpc-gssd etc. that are implemented on Fedora.
Needless to say it doesn't work with statd etc as a result.
From that experience I wouldn't be too hasty to lay blame for a failure
at systemd's door per se.
_______________________________________________
luv-main mailing list
luv-main@luv.asn.au
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
