[175673] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Linux: concerns over systemd adoption and Debian's

daemon@ATHENA.MIT.EDU (Miles Fidelman)
Mon Oct 27 21:10:37 2014

X-Original-To: nanog@nanog.org
Date: Mon, 27 Oct 2014 21:10:20 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
To: NANOG <nanog@nanog.org>
In-Reply-To: <28793350.624.1414423453599.JavaMail.root@benjamin.baylink.com>
Errors-To: nanog-bounces@nanog.org

Jay Ashworth wrote:
> ----- Original Message -----
>> From: "Chris Adams" <cma@cmadams.net>
>> Once upon a time, Jay Ashworth <jra@baylink.com> said:
>>> "Try to do everything *inside PID 1*" is the real problem.
>> And that is not what systemd is doing; make sure you know what you are
>> complaining about. systemd-the-project != systemd-the-pid-1. PID 1 is
>> responsible for managing services/daemons, and AFAIK that's all
>> systemd's PID 1 does.
> Indeed.  I was quoting (I thought) better read people than me.  If that's the
> case, I retract about 25% of my distaste for it.
>

Well, yeah... but there's this huge (and growing) network of 
interlocking dependencies, and, at least at the moment, no way to avoid 
installing systemd as PID1 during a fresh Debian install (no installer 
choice, and a bug in debootstrap that prevents preseeding).  So, yes, 
you can uninstall systemd as PID1, but it sure seems to be rather difficult.

Miles Fidelman



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


home help back first fref pref prev next nref lref last post