From: Tanguy Le Carrour <tanguy@bioneland.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [BLOG] On migration to the Hurd
Date: Fri, 3 Apr 2020 13:59:39 +0200 [thread overview]
Message-ID: <20200403115939.4iz3w67wvkb5xzbx@melmoth> (raw)
In-Reply-To: <87y2renomm.fsf@gnu.org>
Le 04/02, Ludovic Courtès a écrit :
> 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/
> > […]
> > 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!
> […]
>
> ./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!
I'm not (yet) able to do low-level/system contributions, but I did
contribute some patches upstream to make some programs build and work
on GNU/Hurd. I think I'll keep on doing this kind of things in the
future. Better little than none, right?! :-)
Regards
--
Tanguy
next prev parent reply other threads:[~2020-04-03 11:59 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
2020-04-03 11:59 ` Tanguy Le Carrour [this message]
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=20200403115939.4iz3w67wvkb5xzbx@melmoth \
--to=tanguy@bioneland.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).