unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: znavko@disroot.org
Cc: guix-devel@gnu.org
Subject: Re: What is the philosophy behind shepherd?
Date: Sat, 06 Apr 2019 16:21:10 -0500	[thread overview]
Message-ID: <87bm1in83d.fsf@gmail.com> (raw)
In-Reply-To: <7ccb4af5361a225750d4c90dc78abc3e@disroot.org> (znavko's message of "Sat, 06 Apr 2019 21:02:42 +0000")

znavko@disroot.org writes:

> 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.

While I would not characterize myself as a sysadmin, nor an init system
expert, I use systemd just about every day. I'm familiar with the
generalities of how it works, and why.

> 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.

I think it does more than to serve a unified interface to sysadmins. For
example, its built-in DNS server can dynamically update a `resolv.conf`
which some systems symlink `/etc/resolv.conf` to. This allows systemd to
handle signals of connecting to networks or VPNs, and update the systems
DNS servers dynamically. The acceptance of these types of signals and
the actions they spawn are what I think make up the "system layer" Benno
Rice was discussing.

-- 
Katherine

  reply	other threads:[~2019-04-06 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 19:30 What is the philosophy behind shepherd? Katherine Cox-Buday
2019-04-06 21:02 ` znavko
2019-04-06 21:21   ` Katherine Cox-Buday [this message]
2019-04-07  8:08   ` znavko
2019-04-06 23:08 ` Christopher Lemmer Webber
2019-04-07 13:35   ` Pjotr Prins
2019-04-07 17:52 ` Adam Pribyl
2019-04-08  9:25 ` Ludovic Courtès
2019-04-11  1:21 ` Danny Milosavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bm1in83d.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=znavko@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).