From: ludo@gnu.org (Ludovic Courtès)
To: rennes@openmailbox.org
Cc: guix-devel@gnu.org, bug-hurd@gnu.org
Subject: Re: boot the Hurd with Guix
Date: Sat, 11 Nov 2017 22:49:39 +0100 [thread overview]
Message-ID: <87h8u0fpu4.fsf@gnu.org> (raw)
In-Reply-To: <20171111180213.B266C4E0002@mta-1.openmailbox.og> (rennes@openmailbox.org's message of "Sat, 11 Nov 2017 18:02:11 -0000")
Hi rennes!
rennes@openmailbox.org skribis:
> Finally I was able to start the Hurd with the binaries generated with the guix package manager.
Woohoo! Does that mean you were able to run packages cross-compiled
with Guix, or packages built natively with Guix?
> At the moment the image of Hurd I have built it manually and does not yet have any functionality like GuixSD / Linux.
… or did you build a VM image of GNU/Hurd?
> Next goal:
> * Generate the image file in the style of guix.
> ** For this I have noticed that it is required to compile qemu for the architecture i586-pc-gnu, at the moment I could not compile qemu in Hurd. I have tried to disable some quemu features that come by default; however, I have not yet achieved it.
Things like ‘guix system vm’ use QEMU because we need to start a VM
because on GNU/Linux one needs to be root to create a file system, mount
it, and populate it.
However, on GNU/Hurd, file systems can be mounted without being root.
So you could in fact skip QEMU altogether, though that’d require
tweaking in the VM-generation code (in (gnu build vm), etc.).
> Other pending things:
> * Some packages fail during the compilation and testing phases.
> * Other packages used by guix, such as lsof are not ported in Hurd yet.
We could probably get rid the lsof dependency. What matters here is a
Linuxish /proc.
Anyway, congrats on this milestone! :-)
Ludo’.
next prev parent reply other threads:[~2017-11-11 21:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 18:02 boot the Hurd with Guix rennes
2017-11-11 18:16 ` Samuel Thibault
2017-11-11 18:47 ` Manolis Ragkousis
2017-11-12 12:16 ` Pjotr Prins
2017-11-11 21:49 ` Ludovic Courtès [this message]
2017-11-18 3:25 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2017-11-11 19:46 rennes
2017-11-12 21:03 rennes
[not found] <20171112210310.80B0E4E0031@mta-1.openmailbox.og>
2017-11-13 10:42 ` Ludovic Courtès
2017-11-13 10:50 ` Samuel Thibault
2017-11-16 10:13 ` Ludovic Courtès
2017-11-16 10:17 ` Manolis Ragkousis
2017-11-27 19:05 rennes
2017-12-01 13:17 ` Ludovic Courtès
2017-12-01 16:16 ` Samuel Thibault
2017-12-01 18:44 ` Vincent Legoll
2017-12-01 18:46 ` Vincent Legoll
[not found] <20171127190559.DB3114E0034@mta-1.openmailbox.og>
2017-11-27 19:25 ` Manolis Ragkousis
2017-11-28 1:16 rennes
2017-11-28 13:36 ` Daniel Pimentel
2017-11-28 15:18 ` ranvijay vijay
2018-01-07 17:12 rennes
2018-01-08 10:13 ` Ludovic Courtès
2018-01-08 10:20 ` Svante Signell
2018-01-08 10:38 ` Svante Signell
2018-01-10 2:03 ` rennes
2018-01-10 1:53 ` rennes
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=87h8u0fpu4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rennes@openmailbox.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).