From: Vagrant Cascadian <vagrant@debian.org>
To: ryan <rysa88@posteo.net>, help-guix@gnu.org
Subject: Re: Help installing on Cubox-i/Arm Boards
Date: Thu, 05 May 2022 08:26:40 -0700 [thread overview]
Message-ID: <87o80cuhjj.fsf@contorta> (raw)
In-Reply-To: <341dbfa19c60b49fd54c77f9f264207d1a8793e2.camel@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
On 2022-05-04, ryan wrote:
> I would like to build a disk image for a Cubox-i variant that I have,
> it currently has nothing on it.
Which variant? You'll really want one of the 4GB ram variants... it will
be slow regardless; there are very few substitutes available for armhf
at the moment, so you'll have to build almost everything yourself.
Even with offloading builds to a faster machine, it's likely going to be
a bit slow for some things (you still have to compute what you're asking
the other machine to build for you).
> If setup guix on my x86_64
> device/laptop using the guided installer, can I build it from there
> easily using the instructions here?:
> https://guix.gnu.org/manual/en/html_node/Building-the-Installation-Image.html
Not sure the installer is supported for armhf yet...
> I also see there is a binary tarball, but not sure what to do with it?
You could use the binary tarball to install guix on another OS as a
"foreign distro" installation, and then proceed to use "guix system init
YOURCONFIG.scm" to install Guix System.
> or am I jumping ahead? I see that uboot in guix is available for the
> cubox-i, but I am not sure where I need to start?
I did some basic testing when I added it some years ago, but haven't
maintained any cubox-i family systems with guix...
> Any help with getting guix setup on the armvh device would be most
> useful and appreciated.
It will definitely be a project; if you're primarily interested in
learning about armhf and are already familiar with guix and want to
learn more about the gritty details... it might be a good project.
If you just want something that will work easily... it will likely be
pretty frustrating.
Good luck!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2022-05-05 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 4:56 Help installing on Cubox-i/Arm Boards ryan
2022-05-05 5:25 ` Julien Lepiller
2022-05-05 15:26 ` Vagrant Cascadian [this message]
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=87o80cuhjj.fsf@contorta \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=rysa88@posteo.net \
/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).