unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marco van Hulten <marco@hulten.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix@gnu.org
Subject: Re: upgrading systems with <= 2 GiB RAM
Date: Sun, 3 Nov 2019 15:14:37 +0100	[thread overview]
Message-ID: <20191103151252.0e99e919@jasniac.instanton> (raw)
In-Reply-To: <878sp0pm24.fsf@devup.no>

Marius—

Je 31 okt 23:49 skribis Marius:
> Marco van Hulten <marco@hulten.org> writes:
> 
> > I have an oldish amd64 system with 2 GiB of memory, but it is fast
> > enough to use as a media center.  Guix was last updated early this
> > year.  Upgrading it now takes many days.  It keeps on swapping (using
> > quite consistently 2 of 4 GiB of swap available).
> >
> > Do you think the swapping is the reason that it takes so long?
> >
> > Would it be a general strong advice to use more than 2 GiB, or is it
> > likely useful to give details like which program is compiling (as in a
> > proper bug report)?  
> 
> Ideally you should not have to compile anything.  Have you authorized
> the ci.guix.gnu.org signing key?

I did not authorize that signing key.  Now that I have, upgrading the
system and installing packages goes much faster.

Thanks for this!

—Marco

  reply	other threads:[~2019-11-03 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 14:54 upgrading systems with <= 2 GiB RAM Marco van Hulten
2019-10-31 22:49 ` Marius Bakke
2019-11-03 14:14   ` Marco van Hulten [this message]
2019-11-03 15:48     ` Marius Bakke
2019-11-12  4:32 ` Chris Marusich

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=20191103151252.0e99e919@jasniac.instanton \
    --to=marco@hulten.org \
    --cc=help-guix@gnu.org \
    --cc=mbakke@fastmail.com \
    /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).