unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Csepp <raingloom@riseup.net>
To: Ian Eure <ian@retrospec.tv>
Cc: help-guix@gnu.org
Subject: Re: GuixSD automated installation
Date: Wed, 03 Jan 2024 04:39:32 +0100	[thread overview]
Message-ID: <86mstnf599.fsf@riseup.net> (raw)
In-Reply-To: <87o7e3ff61.fsf@meson>

Ian Eure <ian@retrospec.tv> writes:

> Hello,
>
> On Debian, you can create a preseed file containing answers to all the questions
> you’re prompted for during installation, and build a new install image which
> includes it.  When booted, this installer skips any steps which have been
> preconfigured, which allows for either fully automated installation, or partly
> automated (prompt for hostname and root password, but otherwise automatic).
>
> Does Guix have a way to do something like this?  The declarative config is more
> or less the equivalent of the Debian preseed file, but I don’t see anything that
> lets you build an image that’ll install a configuration.
>
> I see there’s `guix deploy’, but that requires an already-installed GuixSD to
> work, which isn’t helpful for getting it installed in the first place.
>
> Thanks,
>
>  — Ian

guix system image is maybe closer, but it doesn’t automate everything that the
installer does.
But the installer can be used as a Scheme library, at least in theory.  The way
I would approach the problem is by creating a Shepherd service that runs at boot
from the live booted ISO.

  reply	other threads:[~2024-01-03  3:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  0:01 GuixSD automated installation Ian Eure
2024-01-03  3:39 ` Csepp [this message]
2024-02-26 13:25   ` Guix System " Giovanni Biscuolo
2024-02-27 20:37     ` Ian Eure
2024-02-28  7:33       ` declarative partition and format with Guix (was Re: Guix System automated installation) Giovanni Biscuolo
2024-02-28  9:53         ` Giovanni Biscuolo

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=86mstnf599.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=ian@retrospec.tv \
    /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).