From: raingloom <raingloom@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: unifying mcron and shepherd, service woes, improvements
Date: Sun, 16 May 2021 20:17:31 +0200 [thread overview]
Message-ID: <20210516201731.56a80ef6@riseup.net> (raw)
In-Reply-To: <87fsyohr07.fsf@gnu.org>
On Sat, 15 May 2021 18:59:52 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> > Security could also be improved probably. Can we have an OCAP model?
> > I feel like I don't know enough to say, so this mail is meant more
> > as a conversation starter.
>
> I think “having an ocap model” sounds nice but also vague. :-)
>
> A concrete step we can take is follow the principle of least authority
> (POLA) for more services. That was the spirit of
> <https://guix.gnu.org/en/blog/2017/running-system-services-in-containers/>.
By OCAP I was thinking of things like not having global state, or at
least not having it implicitly. Something more functional. The lambda
calculus supports the OCAP model, and Guix is all about being
functional, so service management should not be any different.
Would also be nice if replacing running components was supported, a la
Erlang. Maybe steal the supervisor tree idea as well.
next prev parent reply other threads:[~2021-05-16 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 22:39 unifying mcron and shepherd, service woes, improvements raingloom
2021-05-15 16:59 ` Ludovic Courtès
2021-05-16 18:17 ` raingloom [this message]
2021-05-16 20:47 ` Philip McGrath
2021-05-16 20:49 ` Xinglu Chen
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=20210516201731.56a80ef6@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
--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).