unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Please put the system-configuration into the image
Date: Thu, 7 Sep 2017 12:43:06 +0000	[thread overview]
Message-ID: <20170907124306.yy7seidv66ajlkka@abyayala> (raw)
In-Reply-To: <9d3029d4-8069-4c95-702e-6194f7fa8cd2@crazy-compilers.com>

[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]

Hartmut Goebel transcribed 1.3K bytes:
> Am 07.09.2017 um 10:30 schrieb Ludovic Courtès:
> > However, I don’t quite understand the use case: you’d like to hack on
> > the OS declaration of the image from within the image?  That sounds
> > inconvenient no?
> 
> My use case is this:
> 
> I plan to use GuixSD for one of my systems. Prior to installing GuixSD
> on real hardware, I want to test it and see how a GuixSD system would
> work and feel. And taking the perspective of a non-developer, I don't
> have any GuixSD yet. I may be using Fedora or Debian and want to try out
> GuixSD. For this I use the QEMU image

You can take any system configuration file and build a shared or free-standing
vm with the "guix system" function. It's really easy this way.
"guix system vm config.scm" would produce a vm and in the end you get a
shell script you can use to start this vm.

> My understanding is that I would have a system-definition describing
> this very system and if I want to change the system-configuration, I
> change the system-definition. On e.g. Debian I would apt-get software
> and change config-files, while on GuixSD I would change the
> system-definition and reconfigure.
> 
> And I imagine to have the corresponding system-definition *in* the
> system, since in this use-case there is no separate "main GuixSD
> installation". Like when using ansible, puppet, etc. for managing *this*
> system, I need the system definition *for* this system *in* this system.
> 
> I hope this is clearer now.

Wouldn't simply keeping the configuration file(s) in a git help
(for a start)? This is what I do personally:
https://gitweb.krosos.org/systems

For infotropique I have this combination of plain config files (templates)
and (almost) the same content in variations of the before referenced "install.scm".
> -- 
> Regards
> Hartmut Goebel
> 
> | Hartmut Goebel          | h.goebel@crazy-compilers.com               |
> | www.crazy-compilers.com | compilers which you thought are impossible |
> 
> 
> 
> 

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-09-07 12:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 17:44 Please put the system-configuration into the image Hartmut Goebel
2017-09-05 17:55 ` Adam Pribyl
2017-09-05 18:05 ` ng0
2017-09-06 17:23   ` Hartmut Goebel
2017-09-07  8:30     ` Ludovic Courtès
2017-09-07  9:20       ` Hartmut Goebel
2017-09-07 12:43         ` ng0 [this message]
2017-09-08 10:11           ` Hartmut Goebel
2017-09-08 11:42             ` Vincent Legoll
2017-09-08 11:45             ` Julien Lepiller
2017-09-08 12:07               ` Vincent Legoll
2017-09-10 20:48             ` 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=20170907124306.yy7seidv66ajlkka@abyayala \
    --to=ng0@infotropique.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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).