From: Mathieu Othacehe <othacehe@gnu.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org
Subject: Re: Single-board-computer approach: don't make an installer, make the install?
Date: Wed, 13 Jan 2021 15:51:03 +0100 [thread overview]
Message-ID: <87k0sgvqjs.fsf@gnu.org> (raw)
In-Reply-To: <87sg74kitc.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Wed, 13 Jan 2021 09:33:35 -0500")
Hello Christopher,
> I haven't tried it yet but can't think of a good reason it wouldn't
> work. Has anyone tried that?
Sure, I would advise you to read this[1], which is a sort of follow-up
of this article. You can also listen that talk[2].
I have been successfully producing ready to use disk-images for Pine64,
Danny has done the same for Novena and there are a few people trying to
do so for their Pinebook-pro.
Thanks,
Mathieu
[1]: https://othacehe.org/the-guix-system-image-api.html
[2]: https://archive.fosdem.org/2020/schedule/event/ggaaattyp/
next prev parent reply other threads:[~2021-01-13 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 14:33 Single-board-computer approach: don't make an installer, make the install? Christopher Lemmer Webber
2021-01-13 14:51 ` Mathieu Othacehe [this message]
2021-01-13 15:53 ` Christopher Lemmer Webber
2021-01-13 19:55 ` Joshua Branson via
2021-01-14 3:42 ` Christopher Lemmer Webber
2021-01-14 8:54 ` Mathieu Othacehe
2021-01-14 18:05 ` Joshua Branson via
2021-01-17 13:10 ` [PATCH] * doc/guix-cookbook.texi (Guix System Image API): new section Joshua Branson
2021-01-18 13:29 ` Mathieu Othacehe
2021-01-18 16:08 ` Joshua Branson
2021-01-18 16:38 ` jbranso--- via
2021-01-21 20:39 ` Single-board-computer approach: don't make an installer, make the install? Joshua Branson
2021-01-22 13:32 ` Mathieu Othacehe
2021-03-21 13:51 ` Joshua Branson
2021-03-29 7:39 ` Mathieu Othacehe
2021-03-31 16:40 ` Joshua Branson
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=87k0sgvqjs.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=cwebber@dustycloud.org \
--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).