all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Tip of the day: storing your GuixSD config in the instantiated system
Date: Tue, 29 Aug 2017 12:10:13 +0200	[thread overview]
Message-ID: <877exmhegq.fsf@elephly.net> (raw)
In-Reply-To: <871snzfl4s.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> But wait: we can already store the config file in the instantiated
> system!  Here’s how:
>
>   (operating-system
>     ;; …
>     (services (cons (simple-service 'store-my-config
>                                     etc-service-type
>                                     `(("config.scm"
>                                        ,(local-file (assoc-ref
>                                                      (current-source-location)
>                                                      'filename)))))
>                     …)))
>
> You instantiate that, and then /etc/config.scm (aka.
> /run/current-system/etc/config.scm,
> aka. /var/guix/profiles/system/etc/config.scm) contains the config file.

When the system is “checked out” during boot, would it fail when
/etc/config.scm already exists?  It certainly won’t just overwrite an
existing /etc/config.scm.

Also, this $profile/etc/config.scm would be read-only.  So far we have
encouraged people to store their configuration file at /etc/config.scm.
If this service became a default then we probably should encourage
people to store their system config file template under version control
in the root user’s home directory (or similar), rather than recommending
the file to be placed in /etc.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  parent reply	other threads:[~2017-08-29 10:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 20:27 Tip of the day: storing your GuixSD config in the instantiated system Ludovic Courtès
     [not found] ` <87a82mp2jq.fsf@gmail.com>
2017-08-28 12:04   ` Ludovic Courtès
2017-08-28 16:46     ` Alex Kost
2017-08-28 20:23       ` Peter Mikkelsen
2017-08-29  8:10         ` ng0
2017-08-29  9:26           ` Peter Mikkelsen
2017-08-29 10:13         ` Ricardo Wurmus
2017-08-28 16:41 ` Alex Kost
2017-08-29 10:10 ` Ricardo Wurmus [this message]
2017-08-29 22:20   ` Ludovic Courtès
2017-08-29 10:30 ` Andreas Enge
2017-08-29 22:42   ` Ludovic Courtès
2017-08-30 16:07     ` Andreas Enge
2017-08-30 21:25       ` Ricardo Wurmus

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

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

  git send-email \
    --in-reply-to=877exmhegq.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.