all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Pribyl <pribyl@lowlevel.cz>
Cc: guix-devel@gnu.org
Subject: Re: Prerequesits GuixSD
Date: Sun, 24 May 2015 20:39:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1505242037120.25067@sandbox.cz> (raw)
In-Reply-To: <1432030017.32161.3.camel@hypermove.net>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1150 bytes --]

On Tue, 19 May 2015, Amirouche BOUBEKKI wrote:

> Le mardi 19 mai 2015 à 10:55 +0200, Ricardo Wurmus a écrit :
>> Hi Fabian,
>>
>>> But the system build broke.
>>
>> What exactly does this mean?
>>
>>> I used a Lenovo T60 with just 1GB RAM. What hardware do i need to
>>> build a Guix system? I used the very tiny system configuration that i
>>> found on the installer USB with slight changes.
>>
>> I use the Guix System Distribution (GuixSD) on both a T60 and an X200s.
>> I did *not* compile everything from scratch but used binary substitutes
>> for the vast majority of packages.
>
> Here on a glublub X60 it installed correctly with substitues. There is
> XFCE and WM maker as WM. And it works quiet good as second workstation.
> GSD hasn't yet, all the s/spies/daemons that other distros can have ;)

This is it, with substitutes, it works, even on 1GB of RAM. But as soon as 
you want to compile, then 1GB of RAM is not enought. I even used 1GB swap 
and still no go.

The question is something I am interest in too - what is the minimum to 
compile the guix(SD)? Does anybody know?

>> ~~ Ricardo

Adam Pribyl

  reply	other threads:[~2015-05-24 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 12:23 Prerequesits GuixSD Fabian Boucsein
2015-05-19  8:55 ` Ricardo Wurmus
2015-05-19 10:06   ` Amirouche BOUBEKKI
2015-05-24 18:39     ` Adam Pribyl [this message]
2015-05-19 14:55   ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.00.1505242037120.25067@sandbox.cz \
    --to=pribyl@lowlevel.cz \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.