unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@dismail.de>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: indieterminacy <indieterminacy@libre.brussels>,  guix-devel@gnu.org
Subject: Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic
Date: Tue, 12 Jul 2022 09:36:16 -0400	[thread overview]
Message-ID: <87lesytpv3.fsf@dismail.de> (raw)
In-Reply-To: <87bktuspp0.fsf@jpoiret.xyz> (Josselin Poiret's message of "Tue,  12 Jul 2022 10:25:15 +0200")

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hello,
>
> Joshua Branson <jbranso@dismail.de> writes:
>

To be clear, I did not write the next paragraph.  I was quoting the
previous discussion.  :)

>> I would love for Guix to be a Multi Kernel package manager (I mean it
>> works on the Hurd also, but I have never encountered a Hurd user in real
>> life). My dream would be to port Guix to Plan 9 ;-)
>
> I don't think Guix runs on the Hurd in the same way that Guix runs on
> Linux: the (gnu system hurd) tells me that the daemon is started with
> --disable-chroot, which actually disables all isolation mechanisms.
> There would need to be a significant effort to port the isolation
> mechanisms to the Hurd.
>
> Seeing how the daemon is in general left alone since C++ is hard
> compared to Scheme (and there's always the "but we could rewrite it in
> Guile" excuse), combined with the difficulty of interfacing with
> kernels, I'm not sure BSD support (or even Hurd support) will appear
> anytime soon.
>

To be fair, Guix does support the Hurd. You can run the guix package
manager on the Hurd. Guix System does not yet support the Hurd. Though I
believe I talked with a user in the guix community that was running GNU
Guix System/Hurd, but the issue he ran into was that he has no wifi
support. Then something broke in GNU Guix System/Hurd and he no longer
run GNU Guix System/Hurd on real hardware.

>
> Best,


  reply	other threads:[~2022-07-12 13:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 22:44 Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic Joshua Branson
2022-07-12  0:16 ` indieterminacy
2022-07-12  2:18   ` Joshua Branson
2022-07-12  3:56     ` Akib Azmain Turja
2022-07-12 13:39       ` Joshua Branson
2022-07-12  8:25     ` Josselin Poiret
2022-07-12 13:36       ` Joshua Branson [this message]
2022-07-12 20:12       ` Csepp
2022-07-14 10:23 ` zimoun
2022-07-14 10:40   ` Tobias Geerinckx-Rice
2022-07-14 13:06     ` zimoun
2022-07-14 15:38       ` Vagrant Cascadian
2022-07-15 11:09         ` Csepp
2022-07-19 21:46         ` jbranso
2022-07-19 21:44       ` jbranso
2022-07-19 21:43     ` jbranso
2022-07-19 21:41 ` jbranso
  -- strict thread matches above, loose matches on Subject: below --
2022-07-20 16:03 Raghav Gururajan
2022-07-20 16:49 ` Maxime Devos
2022-07-21 16:27 ` zimoun

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=87lesytpv3.fsf@dismail.de \
    --to=jbranso@dismail.de \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=indieterminacy@libre.brussels \
    /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).