From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>,
Joshua Branson <jbranso@dismail.de>
Subject: Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic
Date: Thu, 14 Jul 2022 10:40:56 +0000 [thread overview]
Message-ID: <2697DE8E-5C5C-4FD4-81E8-7237B5654ADD@tobias.gr> (raw)
In-Reply-To: <86lesw2dsa.fsf@gmail.com>
On 14 July 2022 10:23:49 UTC, zimoun <zimon.toutoune@gmail.com> wrote:
> Well, I am missing where it is announced. Could you be more specific?
https://www.hyperbola.info/news/announcing-hyperbolabsd-roadmap/
Far from 'recent' in my book.
Whatever my opinion on WSL, Darwin, and the Hurd, I must concede that they at least exist.
Porting Guix to something that doesn't is a poor investment in comparison.
> If you run OpenBSD kernel and OpenBSD userland, why not just run an
OpenBSD system? :-)
Because it contains blobs. HyperbolaBSD doesn't, by definition (see above).
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2022-07-14 10:43 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
2022-07-12 20:12 ` Csepp
2022-07-14 10:23 ` zimoun
2022-07-14 10:40 ` Tobias Geerinckx-Rice [this message]
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=2697DE8E-5C5C-4FD4-81E8-7237B5654ADD@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.de \
--cc=zimon.toutoune@gmail.com \
/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).