unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: Guix on Novena
Date: Wed, 2 Sep 2020 20:05:48 +0200	[thread overview]
Message-ID: <20200902180548.GA15217@jurong> (raw)
In-Reply-To: <87zh6813yp.fsf@ponder>

On Wed, Sep 02, 2020 at 10:30:22AM -0700, Vagrant Cascadian wrote:
> I haven't finished upgrading to a more recent guix, but attached is a
> slightly trimmed down config that I used as recently as March.

Great, thanks!

So far, I have been upgrading the machine to Debian buster. There are
scripts to do so here, prepared by a person formerly active on the Guix
list as well:
   https://github.com/novena-next/docs
But essentially "apt-get dist-upgrade" first to stretch and then to buster
work. So the next step will be to backup the sd card using dd...

As for installing the Guix system on arm machines, I am quite lost.
The installer does not work, or does it? Apart from that, I only know
the dirty way of installing the Guix package manager and running a
"guix system init", thus interleaving the new system with Debian
remainders. Are there better ways?

In this special case of a build machine, we did not want to run the build
on the (moreover small) sd card, so we bind mounted (why that? a normal
mount would have been enough, I think) /tmp and /gnu/store from an external
hard drive. That should be handable in the standard way by a file-systems
entry, I suppose. Or maybe simply mount the complete / from the external
hard drive? That should even be compatible with the dirty "guix system init"
approach, I think.

Your thoughts are welcome.

Thanks,

Andreas



  reply	other threads:[~2020-09-02 18:06 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 [this message]
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
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=20200902180548.GA15217@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).