From: Vincent Legoll <vincent.legoll@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Please put the system-configuration into the image
Date: Fri, 8 Sep 2017 14:07:34 +0200 [thread overview]
Message-ID: <CAEwRq=rfUA5oaDASLShcoJ-ET4nVqqL1_XoVHo9+kkPPMnNxhg@mail.gmail.com> (raw)
In-Reply-To: <B68E5246-419A-48BF-998C-81BBF92C45F6@lepiller.eu>
On Fri, Sep 8, 2017 at 1:45 PM, Julien Lepiller <julien@lepiller.eu> wrote:
> The qemu image however is meant to be copied directly to the virtual disk of
> a VM, so it is not a live system, but your own system. I think it would be
> better for the user to be able to access the configuration directly from the
> VM and start from a known-good config before reconfiguring.
It's not just a known good configuration that you want here, but the exact one
that has been used to generate the image.
> I now have a
> running GuixSD VM and it was a pain to configure, because the interface to
> the VM did not allow copy-pasting and had a strange plugin for interpreting
> my keystrokes. Had I have this file on the VM, I could have modified only a
> small portion of it and continue with ssh. But I had to copy the sample
> config character by character and hope I did not do any mistake.
Been there, done that too...
--
Vincent Legoll
next prev parent reply other threads:[~2017-09-08 12:07 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=rfUA5oaDASLShcoJ-ET4nVqqL1_XoVHo9+kkPPMnNxhg@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.