Frequently Asked Questions about HyperbolaBSD

What is HyperbolaBSD exactly?

HyperbolaBSD is a complete new and to emphasize, independent fully free (as in freedom) BSD descendant operating system, based on the Unix modular design1) and minimalism2). It is explicite not meant as common system-distribution or downstream project from another one. All parts of the system are ported towards the used system-parts of Hyperbola GNU/Linux-libre as system-distribution. When HyperbolaBSD is reaching its first stable release (look there on our roadmap) it will replace all current parts in usage also for our own infrastructure and services hosted under this domain.

So HyperbolaBSD is no distribution but an operating-system, do you have made it from scratch?

Kernel and userspace are based on hard-forked code from different BSD descendant systems (mostly from OpenBSD 7.0), as a starting point for the development of the first HyperbolaBSD version. We have taken much time to investigate possible license-issues, done a clear auditing for all files and ported all for newer technology-stack to compile. HyperbolaBSD is under a progressive migration by replacing all non GPL-compatible code. It will be replaced with new compatible code under Simplified BSD License3). We do this in order to incorporate GPL code from other projects such as ReactOS, as well new code from scratch. HyperbolaBSD is a change of paradigm so all elementary parts are coming from one place and everything is oriented to be only free and libre software.

What is the diference towards other systems?

In common said HyperbolaBSD is an operating-system meant to be done from one source as all is in the hand of the users and the project itself. So the system is trying to be as most near towards essential Unix-principles and structures as possible without loosing its own identity for minimalism, security and privacy. There are no frameworks with overboarding dependencies in the risk for your own system or your control.

Do you include more than only basic parts?

Yes, as already now with Hyperbola GNU/Linux-libre we are planning to provide further packages for a complete offering towards a fine working operating-system granting the most common wishes and usecases. Nevertheless we stay true towards our Social Contract for all future packages. This means we only include really free and libre software, without any compromise being made.

How is the scheme for the repositories in the near future?

We will have the repository named [core] with all elementary parts for HyperbolaBSD itself. Everything else will be part within our repository named [extra]. This also means that we for sure remove further packages only working on GNU/Linux-systems when needed.

What kind of init-system you are planning to use for HyperbolaBSD and how to manage packages?

HyperbolaBSD uses the hyperman utility 4) for package management and runit 5) as its default init system.

How about different and more CPU-architectures?

As long as we don't have the financial support to pay developers further for porting towards other CPU-architectures besides x86 we do not plan adding support for multi-architectures. So if you have interest in doing, please take a look out for donations.

Sounds interesting, but can you please add another package?

No, we only provide packages we see needed and have already included in our previous releases. We don't plan adding more packages or follow requests as we are again to repeat not a system-distribution but providing a complete operating-system based on . And we don't change on this plan as to remember that we seek minimalism and lightweight components.

When will the release of HyperbolaBSD be approximately?

The following table shows the release estimates:

OS Version Release name Release date End of life date
HyperbolaBSD 1.0 - 1.x Canis Major Q4 2024 approx. 2028 (stable) / approx. 2030 (old-stable)
HyperbolaBSD v0.99.0-beta - v0.99.x-beta Canis Major Q2 2024 Q4 2024
HyperbolaBSD v0.99.0-alpha - v0.99.x-alpha Canis Major Q4 2023 Q2 2024

You ask often about donations and financial support, what about funding?

We have already tried applied for those, but as to be mentioned those do not cover the essential needs of a project like Hyperbola and the corresponding provided systems: A funding is inbound for clear goals to reach and with every new reached one there is some amount of money paid. Development is not working in goals and also is not always planned when complications are found in between. So we would have no financial support for our provided infrastructure when we fail to reach one goal in time. Also after further rejections we decided against and for the community-focussed approach. Free and libre software stays free, libre with this perspective and not with further demands from others.

You take your principles and values very strict, would it be not better for more pragmatism?

No, we are surely not taking it very strict and follow only our essential beliefs within our core focussed on technical emancipation. Hyperbola, Hyperbola GNU/Linux-libre and finally HyperbolaBSD are all going into this direction as we want the users being always in control for all parts and components of the operating-system. We have no interest for software taking this away by using questionable interfaces. And we see this not as problem also as there are enough other choices for everyone around.

How could I contribute if I can?

There are many ways for contribution: You can engage within packaging and porting of our existing software provided. You have interests in further documentation and writing texts helping others with installation and management of the system. You can also support us financial as every amount helps us further with the infrastructure and payment for development on HyperbolaBSD. In general it is a good idea to get in touch with the team to select therefore an open task from the current roadmap.

Modular design, or modularity in design, is a design principle that subdivides a system into smaller parts called modules (such as modular process skids), which can be independently created, modified, replaced, or exchanged with other modules or between different systems.
In computing, minimalism refers to the application of minimalist philosophies and principles in the design and use of hardware and software. Minimalism, in this sense, means designing systems that use the least hardware and software resources possible.
Known also as FreeBSD License or 2-clause BSD License
hyperman is a hard-fork based on pacman, but with BSD-compatibility.
runit is a cross-platform Unix init scheme with service supervision, a replacement for sysvinit, and other init schemes.