News for hackers. Stuff that matters.
Re:How to take back control of /etc/resolv.conf on Linux (2018) by fulafel on Wednesday March 20, 2019 @02:00AM (#19439437)
Systemd is still optional in Debian, right?
Re:How to take back control of /etc/resolv.conf on Linux (2018) by dijit on Wednesday March 20, 2019 @04:11AM (#19439973)
Kinda. There are increasing numbers of hard dependencies on systemd components. And systemd components pull in systemd itself more often than not. So while in theory it’s optional, in practice it seems decreasingly so.

I tend to avoid systemd so I’ve taken to running Debian machines without it. But if you’re doing something like ephemeral cloud installations then it’s not “worth” the overhead of swapping out your init (and having the consequential reboot and potential instability) so the default is a required target for automation anyway. And if you’ve already set a target then why have another one?

This is why defaults can be harmful if widely deployed and considered non-optional (as systemd is on Debian). They become enforced by convention because they are the only valid common target without wrangling.

Re:How to take back control of /etc/resolv.conf on Linux (2018) by petre on Wednesday March 20, 2019 @03:41AM (#19439836)
Not really. But you can always install Devuan over it at least, which gives you a choice between sysvinit and openrc (and others like runit or sinit).

https://devuan.org/os/init-freedom/

The runit init Void Linux is quite slick. I also installed an Artix runit image in a virtual machine that works nicely. We are using it as a supervisor on openSuSE piggybacked onto systemd to run critical infrastructure. It works flawlessly, it's also included in busybox but almost always never enabled.

Re:How to take back control of /etc/resolv.conf on Linux (2018) by the_why_of_y on Wednesday March 20, 2019 @07:57AM (#19441172)
https://lists.debian.org/debian-devel-announce/2014/08/msg00...

  For the record, the TC expects maintainers to continue to support
  the multiple available init systems in Debian.  That includes
  merging reasonable contributions, and not reverting existing
  support without a compelling reason.
Re:How to take back control of /etc/resolv.conf on Linux (2018) by gsich on Wednesday March 20, 2019 @03:33AM (#19439801)
no