From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: help-guix@gnu.org
Subject: Single-board-computer approach: don't make an installer, make the install?
Date: Wed, 13 Jan 2021 09:33:35 -0500 [thread overview]
Message-ID: <87sg74kitc.fsf@dustycloud.org> (raw)
I looked recently at this tutorial:
https://guix.gnu.org/blog/2017/porting-guixsd-to-armv7/
However, it strikes me: maybe there's another nice approach? Would it
be nicer to just make an image that the user boots into directly on the
beagleboard, if it's going onto a microsd card anyway, rather than
building an installer image?
I haven't tried it yet but can't think of a good reason it wouldn't
work. Has anyone tried that?
Side note, a RISC-V Beagleboard SoC is coming. I suspect that might be
very good helping us start ramping up getting Guix very usable on
RISC-V:
https://arstechnica.com/gadgets/2021/01/seeed-and-beagleboard-team-up-to-provide-a-new-risc-v-based-linux-pc/
next reply other threads:[~2021-01-13 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 14:33 Christopher Lemmer Webber [this message]
2021-01-13 14:51 ` Single-board-computer approach: don't make an installer, make the install? Mathieu Othacehe
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=87sg74kitc.fsf@dustycloud.org \
--to=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).