From: "Quiliro Ordóñez" <quiliro@riseup.net>
To: help-guix@gnu.org
Subject: use case: installing several user administrated workstations
Date: Mon, 13 May 2019 14:19:51 -0700 [thread overview]
Message-ID: <c3faaa4bad4009b51513916394f0f6bf@riseup.net> (raw)
Dear community:
I have noticed Guix System Distribution (I like to abreviate it GSD) is
great for having a predictable, hackable system, which is entirely
auditable. I like this. It is like making your own ... anything (car,
house, clothes,etc). It gives you great power and endless possibilities
of creativity, sharing and learning.
When I think of installing GSD on user machines that I will never see
again (as at an installfest), I feel certain unease. It is so because I
have had to change my desktop.scm system configuration file every time I
want to update my whole operating system. That is a task that no end
user will ever be able to do.
Is there a way that when I run 'sudo guix system reconfigure
desktop.scm', the user (system admin for his machine) can take the
current config and make a new config file (desktop1.scm) with the new
synthax? It is, of course, impossible without a translation from what
was intended in desktop.scm to what is the current situation when
creating desktop1.scm.
Thank you for your responses.
--
Saluton.
Quiliro Ordonez
Do you prefer speaking English?
Vous voulez parler Français?
Çu vi volas paroli Esperanton?
next reply other threads:[~2019-05-13 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 21:19 Quiliro Ordóñez [this message]
2019-05-14 15:54 ` use case: installing several user administrated workstations swedebugia
2019-05-19 14:52 ` Ludovic Courtès
2019-05-20 7:25 ` Quiliro's lists
-- strict thread matches above, loose matches on Subject: below --
2019-05-13 21:19 Quiliro's lists
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=c3faaa4bad4009b51513916394f0f6bf@riseup.net \
--to=quiliro@riseup.net \
--cc=help-guix@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.
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).