unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "zimoun" <zimon.toutoune@gmail.com>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>,
	guix-devel@gnu.org
Subject: Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic
Date: Tue, 19 Jul 2022 21:43:31 +0000	[thread overview]
Message-ID: <2c61ba509e245c0c8578c6ecbf83f531@dismail.de> (raw)
In-Reply-To: <86fsj33ku8.fsf@gmail.com>

July 14, 2022 9:06 AM, "zimoun" <zimon.toutoune@gmail.com> wrote:

> Hi Tobias, All,
> 
> (French Bastille Day is a day off, so a day for trolling. ;-))
> 
> On Thu, 14 Jul 2022 at 10:40, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> 
>> https://www.hyperbola.info/news/announcing-hyperbolabsd-roadmap
> 
> Thanks for the link. It is helpful for understanding. :-)
> 
>> Far from 'recent' in my book.
> 
> Indeed, the announcement is from 2019-12-21. :-)
> 
> Quoting:
> 
> This will not be a "distro", but a hard fork of the OpenBSD
> kernel and userspace
> 
> Not being a new distro means using the venerable pkg_* package manager,
> right? Well, I am confused by the aim…

They want to use pacman apparently.  :)

> 
>>> 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).
> 
> …because HyperboladBSD seems a new distro as gnewSense is a new distro
> free from problematic parts but based on an existing other one. Well,
> since it had been announced on late 2019 and we are in 2022, it could be
> interesting to know the status on this project.
> 
>> 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.
> 
> Just to be sure to understand, the initial question is to port Guix to
> HyperbolaBSD which is a variant of OpenBSD (kernel and userland).
> 
> Therefore, correct me if I misunderstand something, it means:
> 
> 1. port Guix to a new kernel not using the GLibc
> 2. package all the (free) userland OpenBSD managed by Guix
> 
> Bah I wish all the best for people who would tackle this. :-)
> 
> Well, dreaming about science fiction,

Thanks for speaking plainly.  I did not realize how difficult this project
would be.  :)

> it appears me more approachable to
> have Guix running on something as Debian/kfreeBSD – it could be an
> interesting project with the help of Debian folks. Other said, “just”
> replace the Linux kernel by a variant of the FreeBSD one running with
> GNU GLibc.
> 
> However, doing so, the point #2 (BSD userland) is lost.
> 
> My understanding is: #1 and #2 require more work than the union of the
> Guix community *and* the other kernel community could provide, IMHO.
> Assuming both communities would be interested in. :-)
> 
> Cheers,
> simon


  parent reply	other threads:[~2022-07-19 21: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
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 [this message]
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=2c61ba509e245c0c8578c6ecbf83f531@dismail.de \
    --to=jbranso@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    --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).