unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: VM image: can we simplify its use?
Date: Wed, 10 Apr 2019 22:52:01 +0200	[thread overview]
Message-ID: <871s29a8i6.fsf@gnu.org> (raw)
In-Reply-To: <20190409204810.GA26383@jasmine.lan> (Leo Famulari's message of "Tue, 9 Apr 2019 16:48:10 -0400")

Hi Leo,

Leo Famulari <leo@famulari.name> skribis:

> Originally I added the VM image to address a specific use case at one VM
> hoster. I had hoped it would catch on more than it did and that the VM
> image would be improved to avoid these manual steps.
>
> In the meantime, people are using the VM image just to try out Guix —
> for example, in a local QEMU instance.
>
> It doesn't give a great impression, so let's change it.

Agreed.

> We should offer something like a "Live Guix" image for people to try the
> full Guix system without installing anything, and this should be more
> fully-featured than the current Guix VM image.
>
> Let's replace the current VM image with this "Live Guix" thing for the
> next release :) Should we adopt 'desktop.tmpl' for this?

I think we could start from there.  With GNOME, that’d be 2+ GiB
probably, which is pretty big; otherwise we could come up with a lighter
setup, say SLiM + Xfce (+ IceCat?).

Thoughts?

> Eventually we should also offer a Guix system service that works like
> cloud-init [0] and can replace the manual work around networking,
> partitioning, etc. Help wanted!

It seems cloud-init is largely about running some sort of a YAMLish
shell script that runs commands to obtain the desired state in terms of
installed packages, system setup, and all that, right?  To some extent
that seems redundant with a typical OS declaration, no?

Thanks for your feedback!

Ludo’.

  parent reply	other threads:[~2019-04-10 20:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 14:56 VM image: can we simplify its use? Ludovic Courtès
2019-04-06 20:12 ` Gábor Boskovits
2019-04-09 20:48 ` Leo Famulari
2019-04-10 18:38   ` Daniel Jiang
2019-04-10 20:54     ` Ludovic Courtès
2019-04-10 20:52   ` Ludovic Courtès [this message]
2019-04-17  5:10   ` Chris Marusich
2019-04-25 16:44     ` New VM image Ludovic Courtès
2019-04-25 17:19       ` Leo Famulari
2019-04-26  8:03       ` Chris Marusich
2019-04-26 13:29         ` Ludovic Courtès
2019-04-26 14:28           ` Danny Milosavljevic
2019-04-27 13:15           ` Ludovic Courtès
2019-04-30  3:09             ` Chris Marusich

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=871s29a8i6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).