unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Install `guix pull'ed Guix to target partition on system install
Date: Mon, 21 Dec 2020 18:53:19 +0100	[thread overview]
Message-ID: <861rfj9hbk.fsf@gmail.com> (raw)
In-Reply-To: <87mty7krqn.fsf@ambrevar.xyz>

On Mon, 21 Dec 2020 at 18:12, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> Well, I do not understand what is your issue.  Because I am probably not
>> enough familiar with the installation process.
>
> It's actually quite simple: The "guix pull" done when running the
> installation media is not persisted on the target disk.

The “guix pull” done by root.  But then you run “guix pull” as user;
your words. :-)

Anyway, the consuming part should not be the cloning but the computing
and building derivations.

As I said, maybe what is done on the installation media could be
transferred to the target installation via “guix archive --export” and
“guix archive --import”, probably via piping.


> Maybe there is something else.  Could it be slow hardware?  I'm not
> sure, but it took hell of a long time to fetch check out the repository.

I do not know what you are doing but in this half an hour, the cloning
part is nothing, or you have a network at 125Kbits/s and not at
6Mbits/s.  Well, by default the repo is 230Mbits or I miss something.
It is not nothing but not huge neither; compared to video streaming for
example.  (I speak for French network infrastructures, because I lived
in place where 125Kbits/s is a dream.)

Maybe your roommates or neighbor are enjoying the connection. ;-)

Or maybe, you had bad luck with Savannah.

Cheers,
simon


  reply	other threads:[~2020-12-21 18:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20  9:12 Install `guix pull'ed Guix to target partition on system install Pierre Neidhardt
2020-12-21 11:57 ` zimoun
2020-12-21 12:26   ` Pierre Neidhardt
2020-12-21 13:07     ` zimoun
2020-12-21 13:33       ` Pierre Neidhardt
2020-12-21 13:56         ` zimoun
2020-12-21 14:47           ` Pierre Neidhardt
2020-12-21 16:26             ` zimoun
2020-12-21 16:49               ` Pierre Neidhardt
2020-12-21 17:06                 ` zimoun
2020-12-21 17:12                   ` Pierre Neidhardt
2020-12-21 17:53                     ` zimoun [this message]
2020-12-21 19:39                       ` Pierre Neidhardt
2020-12-21 23:50                         ` zimoun
2020-12-22 12:28                           ` Ricardo Wurmus
2020-12-22 13:16                             ` zimoun
2020-12-22  0:29 ` zimoun
2020-12-22  9:44   ` Pierre Neidhardt
2020-12-22 10:46     ` zimoun
2020-12-22 11:51       ` Carlo Zancanaro
2020-12-22 13:06         ` zimoun

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=861rfj9hbk.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).