From: Simon South <simon@simonsouth.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: more than one target service shehperd-root / possible scheme records terribleness
Date: Wed, 03 Mar 2021 11:07:10 -0500 [thread overview]
Message-ID: <871rcw2pch.fsf@simonsouth.net> (raw)
In-Reply-To: <87czwgv12z.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 03 Mar 2021 14:06:12 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> The issue here is likely that operating-system-services returns all
> services, including those that are added by the operating system
> machinery.
Yes. I ran into this myself the other day.
The solution seems to be to use "operating-system-user-services" in
place of "operating-system-services" (see gnu/system.scm:263). This is
certainly non-intuitive though.
--
Simon South
simon@simonsouth.net
prev parent reply other threads:[~2021-03-03 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 10:59 more than one target service shehperd-root / possible scheme records terribleness raingloom
2021-03-03 12:35 ` Joshua Branson
2021-03-03 13:06 ` Ricardo Wurmus
2021-03-03 16:07 ` Simon South [this message]
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=871rcw2pch.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
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).