From: ng0 <contact.ng0@cryptolab.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Services can now have a default value
Date: Wed, 19 Apr 2017 23:22:49 +0000 [thread overview]
Message-ID: <20170419232249.nd6p4i4wzmekyvqv@abyayala> (raw)
In-Reply-To: <87h91n5jsp.fsf@elephly.net>
Ricardo Wurmus transcribed 0.9K bytes:
>
> ng0 <contact.ng0@cryptolab.net> writes:
>
> > Before I lock myself out, this is the definition for defaults.
> > So:
> > (service openssh-service-type
> > (openssh-configuration
> > (port-number 12121)))
> >
> > becomes:
> > (service openssh-service-type
> > (port-number 12121))
> >
> > or is this just a definition for defaults and not the configuration, and
> > when the configuration is specified it is still like before this commit?
>
> The “openssh-service-type” has a default value
> “(openssh-configuration)”. If you want to override parts of the default
> configuration you can use the “modify-services” syntax. Your second
> snippet is incorrect, because “service” expects a type and a
> configuration value, but you gave it a type and “(port-number 12121)”,
> which is not a valid configuration.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
Because I still don't think modify-services is documented well enough
and I have only one case where it's working for me, I assume:
As an example,
(service openssh-service-type
(openssh-configuration
(permit-root-login #t)))
Would still work. If it doesn't, I know there is no lint checking for services
in the system config.
--
PGP and more: https://people.pragmatique.xyz/ng0/
next prev parent reply other threads:[~2017-04-19 23:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 22:51 Services can now have a default value Ludovic Courtès
2017-04-15 23:11 ` ng0
2017-04-17 11:56 ` Ricardo Wurmus
2017-04-19 23:22 ` ng0 [this message]
2017-04-20 8:53 ` Ricardo Wurmus
2017-04-20 9:09 ` ng0
2017-04-23 10:23 ` Ricardo Wurmus
2017-04-17 11:58 ` Ricardo Wurmus
2017-04-19 14:42 ` Carlo Zancanaro
2017-04-19 15:18 ` ng0
2017-04-19 21:20 ` Ludovic Courtès
[not found] ` <8737d32abz.fsf@zancanaro.id.au>
2017-04-20 8:42 ` Ludovic Courtès
2017-04-20 10:19 ` Carlo Zancanaro
2017-04-21 22:04 ` Ludovic Courtès
2017-04-21 23:41 ` Carlo Zancanaro
2017-04-22 0:46 ` We need an RFC procedure [Re: Services can now have a default value] ng0
2017-04-22 7:12 ` Ricardo Wurmus
2017-04-22 10:08 ` ng0
2017-04-22 22:55 ` Ludovic Courtès
2017-04-23 10:13 ` Ricardo Wurmus
2017-04-23 12:02 ` ng0
2017-04-27 13:29 ` Ludovic Courtès
2017-04-27 16:37 ` Petter
2017-05-02 12:42 ` Ludovic Courtès
2017-05-22 21:23 ` Ricardo Wurmus
2017-05-22 22:45 ` Leo Famulari
2017-04-23 11:52 ` ng0
2017-05-13 10:39 ` Services can now have a default value Carlo Zancanaro
2017-05-13 22:53 ` Carlo Zancanaro
2017-05-15 12:48 ` Ludovic Courtès
2017-04-22 14:46 ` Christopher Allan Webber
2017-04-22 14:59 ` Jan Nieuwenhuizen
2017-04-22 22:57 ` 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=20170419232249.nd6p4i4wzmekyvqv@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@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.
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).