From: Ricardo Wurmus <rekado@elephly.net>
To: Attila Lendvai <attila@lendvai.name>
Cc: "Liliana Marie Prikler" <liliana.prikler@gmail.com>,
"Felix Lechner" <felix.lechner@lease-up.com>,
"Edouard Klein" <edou@rdklein.fr>,
"Ludovic Courtès" <ludo@gnu.org>,
"Josselin Poiret" <dev@jpoiret.xyz>,
guix-devel@gnu.org
Subject: Re: Introducing Guix "Features"! (Was: Syntactic Diabetes)
Date: Thu, 01 Feb 2024 22:02:55 +0100 [thread overview]
Message-ID: <87r0hv99oe.fsf@elephly.net> (raw)
In-Reply-To: <POu5ZKchbjEK6CcZ6dOkA7wXf4uYhGxtYlZmYdPQkbb2m-4c8odIgblUrTlGKaTLzNWJorXRCaNMpvDqi7Iqu0SfBE3msVg1H1IL2XKBoxs=@lendvai.name>
> for an average unix user a service is a process that is running in the
> backgroud, doing stuff mostly without any user interaction. you can
> try to argue this away, but i'm afraid that this is the state of
> things.
I don’t think it’s a good idea to aim to satisfy some presumed “average
unix user”, because such a user would not be familiar with many concepts
introduced by Guix (e.g. “guix shell” or “guix system”).
The manual defines system services by referencing users’ expectations:
--8<---------------cut here---------------start------------->8---
11.18.1 Service Composition
---------------------------
Here we define a “service” as, broadly, something that extends the
functionality of the operating system. Often a service is a process—a
“daemon”—started when the system boots: a secure shell server, a Web
server, the Guix build daemon, etc. Sometimes a service is a daemon
whose execution can be triggered by another daemon—e.g., an FTP server
started by ‘inetd’ or a D-Bus service activated by ‘dbus-daemon’.
Occasionally, a service does not map to a daemon. For instance, the
“account” service collects user accounts and makes sure they exist when
the system runs; the “udev” service collects device management rules and
makes them available to the eudev daemon; the ‘/etc’ service populates
the ‘/etc’ directory of the system.
--8<---------------cut here---------------end--------------->8---
Shepherd takes care of monitoring daemons and the like, but services
provided by the system (in the sense of system facilities) don’t have to
be daemons.
--
Ricardo
next prev parent reply other threads:[~2024-02-01 21:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 8:06 A friendlier API for operating-system declarations Edouard Klein
2023-03-23 18:48 ` Josselin Poiret
2023-03-23 20:23 ` Edouard Klein
2023-03-23 21:05 ` Liliana Marie Prikler
2023-04-13 9:42 ` Ludovic Courtès
2023-05-18 14:37 ` Edouard Klein
2023-11-24 21:43 ` Syntactic Diabetes (was Re: A friendlier API for operating-system declarations) Edouard Klein
2023-11-24 22:50 ` Liliana Marie Prikler
2023-11-25 20:14 ` Attila Lendvai
2023-11-26 5:36 ` Michal Atlas
2023-11-26 16:49 ` Edouard Klein
2023-11-26 18:32 ` Liliana Marie Prikler
2023-11-26 20:46 ` Edouard Klein
2023-11-27 21:09 ` Liliana Marie Prikler
2023-11-29 20:12 ` Attila Lendvai
2023-11-29 23:39 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-30 11:16 ` Attila Lendvai
2023-12-01 18:18 ` Michal Atlas
2024-02-01 13:29 ` Introducing Guix "Features"! (Was: Syntactic Diabetes) Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-01 19:43 ` Liliana Marie Prikler
2024-02-01 20:30 ` Attila Lendvai
2024-02-01 20:46 ` Liliana Marie Prikler
2024-02-02 20:11 ` Attila Lendvai
2024-02-01 21:02 ` Ricardo Wurmus [this message]
2024-02-02 19:36 ` Attila Lendvai
2024-02-02 20:21 ` Vagrant Cascadian
2024-02-02 21:25 ` Attila Lendvai
2024-02-02 0:03 ` Introducing Guix "Features"! Carlo Zancanaro
2024-02-18 15:07 ` Introducing Guix "Features"! (Was: Syntactic Diabetes) Edouard Klein
2023-12-09 10:12 ` Syntactic Diabetes (was Re: A friendlier API for operating-system declarations) Ludovic Courtès
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=87r0hv99oe.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=attila@lendvai.name \
--cc=dev@jpoiret.xyz \
--cc=edou@rdklein.fr \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.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).