Randy Bush wrote:
the vast majority of negative tongue wagging regarding systemd is ill
informed.
can we skip the ad homina and leave that for the systemd dev fora?
does systemd have growing pains? definitely. are some egos involved?
sure. can systemd be far reaching? yes, is such reach mandated?
no. use the units you want and disregard the rest.
how does this work out in practice? at install, can i choose whether
systemd is used for X as opposed for the separate component? can i
template such choices for cluster deployment with the usual tools?
Right now, the problem is that the installer does not give a choice, and
the preseed function has a bug such that you can't do a systemvinit
install directly at install time; rather you have to let the default
install complete, then replace systemd with sysvinit-core - and there
seem to be cases of dropping into dependency hell when doing so (reports
vary).
Longer term, the above-mentioned bug will (hopefully) be patched (the
patch is there, but not well tested, and has not yet been included into
the installer). Then we get into the question of to what extent
upstream packages start depending on systemd.
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
