From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: GuixSD on the SoftIron OverDrive 1000 (AArch64)
Date: Sat, 20 Oct 2018 18:40:16 +0200 [thread overview]
Message-ID: <87sh10a7wv.fsf@gnu.org> (raw)
In-Reply-To: <87d0s4ah5f.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 20 Oct 2018 15:20:44 +0200")
Ludovic Courtès writes:
> Following advice and encouragements from Vagrant and Danny :-), I
> successfully installed GuixSD on the SoftIron OverDrive 1000 machine
> that was donated last January¹ (its PSU died a while back and I just
> received a replacement from SoftIron, and I thought it was also a good
> time to replace the distro.)
Ooh, nice!
> On the first boot, the GuixSD activation snippets fail while trying to
> install /etc, /etc/pam.d, and /etc/skel, and /etc/ssl because these
> directories already exist (from openSuSE) whereas GuixSD assumes that
> they don’t. The solution is just to remove/rename them from the Guile
> initrd REPL. Once this is done, booting proceeds flawlessly and
> happiness ensues.
We could do with a more powerful REPL ;-)
> ¹ https://gnu.org/software/guix/blog/2018/aarch64-build-machines-donated/
So...is there an opportunity for someone to start looking at a Reduced
Binary Seed boostrap for AArch64?
janneke.
next prev parent reply other threads:[~2018-10-20 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 13:20 GuixSD on the SoftIron OverDrive 1000 (AArch64) Ludovic Courtès
2018-10-20 16:40 ` Jan Nieuwenhuizen [this message]
2018-10-22 12:29 ` Ludovic Courtès
2018-10-22 19:17 ` GuixSD on AArch64 Vagrant Cascadian
2018-10-24 13:01 ` Ludovic Courtès
2018-12-12 10:36 ` Andreas Enge
2018-12-12 14:26 ` Vagrant Cascadian
2018-10-20 18:29 ` GuixSD on the SoftIron OverDrive 1000 (AArch64) Efraim Flashner
2018-10-22 12:31 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh10a7wv.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.