unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: help-guix@gnu.org
Cc: atai@atai.org
Subject: Re: Guix on 32-bit x86 systems
Date: Tue, 12 Apr 2022 02:23:25 +0200	[thread overview]
Message-ID: <20220412022325.4fa84ffc@riseup.net> (raw)
In-Reply-To: <20220406222036.1e4dce4d@riseup.net>

On Wed, 6 Apr 2022 22:20:36 +0200
raingloom <raingloom@riseup.net> wrote:

> On Tue, 5 Apr 2022 14:43:57 -0700
> Andy Tai <atai@atai.org> wrote:
> 
> > Hi, I wonder do people recommend running Guix as the primary OS on
> > 32-bit x86 systems?  I have some old 32-bit 80x86 (Pentium) PCs that
> > were running Fedora and of course Fedora had dropped support for
> > 32-bit x86 some time ago.
> > 
> > I am curious how would Guix work on such hardware.   These old PCs
> > may have memory of 4 GB or less.  Would that be an issue for
> > running Guix as Guix tries to build software from sources and the
> > build  process may not be possible on systems without much RAM.
> > Thanks for info on this
> >   
> 
> Building large software is definitely an issue, but I think this is
> basically the same problem that ARM systems have.
> 
> I managed to run a very bare bones Guix on an old Pentium II PC once,
> guix pull was very slow, but the main problem was that it only had 4
> gigs of storage.
> 
> You can always offload builds to a more powerful machine, or wait for
> the substitute server to catch up.
> 
> Even pulling should be faster nowadays, since now we have the
> channel-with-substitutes thing, or whatever it's called, so it will
> only pull the channel if substitutes are available for the guix part.
> Note that that does not mean they are available for whatever packages
> are in your profile(s).
> 
> Also if it's a really old system, you might need to compile your own
> kernel without PAE. That can take a while and it's not something
> you'll want to do on an old machine if you can avoid it. Might be a
> good idea to create a custom kernel config that only builds the
> modules you will actually need.
> 

I'm actually going to convert my Windows netbook into a Guix one soon,
so stay tuned for an experience report.
It's too slow for substantial Windows dev, so I'm curious how Guix
fares.
(Might also try NetBSD on it too.)


  reply	other threads:[~2022-04-12  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 21:43 Guix on 32-bit x86 systems Andy Tai
2022-04-06 20:20 ` raingloom
2022-04-12  0:23   ` raingloom [this message]
2022-04-17  1:14 ` Denis 'GNUtoo' Carikli

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=20220412022325.4fa84ffc@riseup.net \
    --to=raingloom@riseup.net \
    --cc=atai@atai.org \
    --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).