unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: fr33d0m <fr33d0m@agnuwayofthinking.com>
Cc: help-guix@gnu.org
Subject: Re: How to run Guix with Hurd
Date: Sun, 12 Jul 2020 01:05:28 +0200	[thread overview]
Message-ID: <20200712010528.4f4634b2@interia.pl> (raw)
In-Reply-To: <7d75cbb8-6042-f4cb-2c5a-30248acbc3f8@agnuwayofthinking.com>

Hello,

Dnia 2020-07-11, o godz. 14:14:16
fr33d0m <fr33d0m@agnuwayofthinking.com> napisał(a):

> I'm running a standalone GUIX system and have been updating it with
> GUIX pull and upgrading packages.
> 
> I'd like to try running the Hurd instead of Libre-Linux but I don't
> know how to do this.

I guess you read the first April joke post about Linux-libre being
replaced with the Hurd. The Hurd isn't ready to replace Linux-libre
yet, but you can learn and contribute or tell the others to make it
true.

Here, the Hurd's website. It is outdated a bit:
https://www.gnu.org/software/hurd/
And the more updated one (it is down in the time of writing this post):
darnassus.sceen.net/cgit/hurd-web.git/log/index.mdwn
The most up to date discussions:
https://lists.gnu.org/archive/html/bug-hurd/

Hurd lacks SMP (Simultaneous MultiProcessing), is 32-bit only and it
doesn't support modern hardware yet.

You can try Guix GNU/Hurd on a virtual machine (qemu).
If you're interested in it, I can give you instructions to set up a VM
with the Hurd.


Jan Wielkiewicz


  reply	other threads:[~2020-07-11 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 21:14 How to run Guix with Hurd fr33d0m
2020-07-11 23:05 ` Jan Wielkiewicz [this message]
2020-07-12  6:25   ` fr33d0m
2020-07-12  6:59   ` pelzflorian (Florian Pelz)
2020-07-12  8:51     ` Jan Nieuwenhuizen
2020-07-12  8:58       ` Jan Nieuwenhuizen

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=20200712010528.4f4634b2@interia.pl \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=fr33d0m@agnuwayofthinking.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).