From: Andreas Enge <andreas@enge.fr>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: Guix on Novena
Date: Mon, 7 Sep 2020 14:11:26 +0200 [thread overview]
Message-ID: <20200907121126.GA7342@jurong> (raw)
In-Reply-To: <20200906084522.GA1900@jurong>
Replying to self:
On Sun, Sep 06, 2020 at 10:45:22AM +0200, Andreas Enge wrote:
> Will mounting /dev/sda1 to /mnt and issuing "guix system init config.scm /mnt"
> work? (The handbook suggests to do "herd start cow-store /mnt", but I forgot
> what this is needed for.) Will it populate only /mnt/gnu/store, or also
> /gnu/store from the place where I call "guix system init"? Since the latter
> is almost full.
Indeed this is a big problem: Everything is first stored in the local store:
The linux source, the deblobbing scripts, the deblobbed linux-libre source,
and so on; including a copy of guix as well as a grafted copy of guix.
Deduplication should help a little, but it appears only at the end of the
build. And being too generous with "guix gc" risks wasting hours of
compilation time. Instead I should have been more generous and replaced the
old micro-SD card :)
On Sun, Sep 06, 2020 at 07:23:33AM -0700, Vagrant Cascadian wrote:
> Thanks for working on getting some armhf build machines going!
Well, it had been working previously with Guix on Debian, but the Novena
support has improved so much over the years that I wanted to try the full
Guix experience. If I do not manage, I can still do a Guix on Debian...
Andreas
next prev parent reply other threads:[~2020-09-07 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 9:38 Guix on Novena Andreas Enge
2020-09-01 16:41 ` Vagrant Cascadian
2020-09-01 18:06 ` Andreas Enge
2020-09-02 17:30 ` Vagrant Cascadian
2020-09-02 18:05 ` Andreas Enge
2020-09-02 18:33 ` Vagrant Cascadian
2020-09-06 8:45 ` Andreas Enge
2020-09-06 14:23 ` Vagrant Cascadian
2020-09-07 20:12 ` Andreas Enge
2020-09-07 12:11 ` Andreas Enge [this message]
2020-09-08 10:56 ` Andreas Enge
2020-09-08 12:30 ` Efraim Flashner
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=20200907121126.GA7342@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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).