Re: What is the philosophy behind shepherd?

[znavko]

Hello, Katherine! I've tried a little systemd, openrc and now I am using GuixSD 
with shepherd.
Lot of people and developers use systemd.
Here it is a link you may get info from 
http://without-systemd.org/wiki/index.php/Main_Page
Here some theses https://ihatesystemd.com it was interesting for me cause I am 
not as deep in init systems.

I think need to define criterion to get appreciation of something. Think that 
layer is not a criteria.
Systemd works fine for some cases when you are sysadmin that want to control 
lot of things in one general interface - init system.

April 6, 2019 7:30 PM, "Katherine Cox-Buday" <address@hidden> wrote:

> I must preface this email with the assurance that there is no agenda
> behind my questions; only ignorance and curiosity. Please read it with
> that in mind!
> 
> A couple weeks ago, I was watching a video called "The Tragedy of
> Systemd"[1]. In it, Benno Rice discusses the need for a so-called
> "system layer" which is responding to the many complicated signals
> coming into a system from thing happening (e.g. networks becoming
> available/unavailable, VPNs mucking with DNS and routing tables, etc.).
> He characterizes systemd and things like it as something that lives
> between kernel-space and user-space.
> 
> It really opened my eyes to why something like systemd exists rather
> than sticking with the old-style init systems.
> 
> Does Shepherd take the stance that it is, or is to become a "system
> layer"?
> 
> If so, one of the criticisms he has for systemd is that instead of
> pulling in protocols for things (e.g. DNS), and allowing best-of-breed
> software to handle the implementation, it has pulled in the
> responsibility for implementation as well. Any thoughts on that?
> 
> [1] - https://www.youtube.com/watch?v=o_AIw9bGogo
> --
> Katherine