[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What is the philosophy behind shepherd?
From: |
Pjotr Prins |
Subject: |
Re: What is the philosophy behind shepherd? |
Date: |
Sun, 7 Apr 2019 15:35:15 +0200 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Sat, Apr 06, 2019 at 07:08:55PM -0400, Christopher Lemmer Webber wrote:
> In other words, I think systemd exists in many ways to make up for the
> limitations of a monolithic kernel approach. In that way, it makes
> sense, but I think we could do better with a different fundamental
> infrastructure.
One way to view it is that systemd does a lot of 'magic'. I.e., there
are internal assumptions that are not that clear. A black box.
For most users, or use cases, that is fine, but when it comes to
running robust and reliable systems you want to define a system with
its services as a reproducible 'expression', much in the spirit of
Guix.
That is where shepherd comes in.
Systemd reminds me too much of Microsoft Windows. Things just happen.
Pj.
- What is the philosophy behind shepherd?, Katherine Cox-Buday, 2019/04/06
- Re: What is the philosophy behind shepherd?, Christopher Lemmer Webber, 2019/04/06
- Re: What is the philosophy behind shepherd?,
Pjotr Prins <=
- Re: What is the philosophy behind shepherd?, znavko, 2019/04/06
- Re: What is the philosophy behind shepherd?, Adam Pribyl, 2019/04/07
- Re: What is the philosophy behind shepherd?, Ludovic Courtès, 2019/04/08
- Re: What is the philosophy behind shepherd?, Danny Milosavljevic, 2019/04/10