unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [BLOG] On migration to the Hurd
Date: Thu, 02 Apr 2020 12:55:13 +0200	[thread overview]
Message-ID: <87y2renomm.fsf@gnu.org> (raw)
In-Reply-To: <20200402063213.kd6d5iz36qxwbcro@melmoth> (Tanguy Le Carrour's message of "Thu, 2 Apr 2020 08:32:13 +0200")

Hi!

Tanguy Le Carrour <tanguy@bioneland.org> skribis:

> Le 04/01, Jan Nieuwenhuizen a écrit :
>> We are thrilled to have published a post about migrating to the Hurd:
>> 
>>     https://guix.gnu.org/blog/2020/deprecating-support-for-the-linux-kernel/
>
> So, I guess I was not the only one to figure out that it was a joke! A
> good one, but still… a joke!
>
> But anyway, I clicked and read the post! And I couldn't help but feel…
> mmm… nostalgic for the future!? Is that even possible?!
>
> The question is now: if not yesterday, when!?
>
> Thanks to all the people who will help make it a reality!

Yup, it can actually become a reality!

Yesterday led us to hack some more.  The new ‘wip-hurd-vm’ branch is
based on ‘core-updates’, which includes Janneke’s Hurd work, notably
supporting native builds on GNU/Hurd.  On that branch, from a GNU/Linux
box, one can run:

  ./pre-inst-env guix build -f gnu/system/hurd.scm

That gives you a QEMU image containing a cross-built GNU/Hurd system,
which is pretty cool.

Unfortunately, the bootstrap ext2fs.static server currently hangs early
on for reasons that haven’t been elucidated yet.  For anyone who wants
to fiddle with the Hurd, here’s a good hacking opportunity!

The branch is almost mergeable, I think.  With that in place, it’ll be
trivial to provide a “GNU/Hurd VM service” for Guix System running on
GNU/Linux, and we can use that to provide GNU/Hurd build VMs on berlin,
for instance.

Currently, unlike ‘qemu-image’, the new ‘cross-hurd-image’ doesn’t
expect a full-blown <operating-system> but simply a bunch of store
items.  However, we can hopefully use that as a starting point to port
Guix System itself to GNU/Hurd.

Food for thought!

Ludo’.

PS: In the meantime, Linux-libre support remains available, fear not!

  reply	other threads:[~2020-04-02 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 21:39 [BLOG] On migration to the Hurd Jan Nieuwenhuizen
2020-04-02  0:56 ` Bengt Richter
2020-04-02  6:32 ` Tanguy Le Carrour
2020-04-02 10:55   ` Ludovic Courtès [this message]
2020-04-03 11:59     ` Tanguy Le Carrour
2020-04-06  7:53       ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2020-04-04  1:47 Rene
2020-04-04  7:38 ` Rene
2020-04-04 10:05 ` 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=87y2renomm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tanguy@bioneland.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 public inbox

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

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).