unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Tomás Chapunov" <tomaschapunov@gmail.com>
To: help-guix@gnu.org
Subject: updating takes so much memory
Date: Tue, 1 Jun 2021 09:00:47 -0300	[thread overview]
Message-ID: <CAB3e=nfVJj7ZszCzCg634qRYTR7KkhLBccOHPrG4dAdtvtwuxQ@mail.gmail.com> (raw)

Can I move the Store to another disk?

I have two installations of Guix.
- One Guix SD, it works fine. I'm fiddling with it, but it's a work in
progress.
- One Guix package manager on top of my main debian 10 system. I have some
packages installed, but texlive is giant. When I do:

$ guix package -u

it uses so much memory that always exhaust my PC.

I wonder if I can symlink the store, and relocate it in another disk. I
have more than one.
Is there any best practices recommendation about doing this? Can I break
something?
Is there any issue I have to consider about performance or anything like
that?

Thanks! Guix is marvelous, but it takes a steep learning curve.

             reply	other threads:[~2021-06-01 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 12:00 Tomás Chapunov [this message]
2021-06-01 12:18 ` updating takes so much memory Julien Lepiller

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='CAB3e=nfVJj7ZszCzCg634qRYTR7KkhLBccOHPrG4dAdtvtwuxQ@mail.gmail.com' \
    --to=tomaschapunov@gmail.com \
    --cc=help-guix@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. 
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).