Hyperball is an operating system for i686 and x86-64 architectures, which is based on Arch snapshots and Debian development to increase stability and safety, plus includes GNU components and the Linux-libre kernel instead of the generic Linux kernel. Hyperbola is listed by the Free Software Foundation as a completely free operating system, faithful to the Libre system distribution guidelines.
Unlike Arch, Hyperbola uses the long-term support model like Debian, a model adapted to extend the software maintenance period and alter the type and frequency of software updates (patches) to reduce risk, expense and disruption of software deployment, promoting the reliability of the software.
Hyperball is being developed according to the KISS principle (Keep It Simple Stupid) and aims to provide users with a simple, light, stable and safe environment.
The initialization system is based on sysvinit with the portability of some developments from the Devuan and Parabola projects. The follow-up time to launch is 5 years.
Goodbye Linux, hello OpenBSD
Few days ago the developers who are in charge of the project by Hyperbola, they made known a news in which want to implement a plan to change the use of the Linux kernel towards the OpenBSD user utilities with the transfer of some components from other BSD systems, with which it is planned to distribute the new distribution under the name HyperbolaBSD.
The reason for the transition The OpenBSD code base is called dissatisfaction with trends in Linux kernel development:
- La adoption of technical means of copyright protection (DRM)dthe linux kernelFor example, the kernel included support for HDCP (High-bandwidth Digital Content Protection) copy protection technology for audio and video content.
- Development of a initiative to develop drivers for the Linux kernel in the Rust language. The hyperbola developers are not happy with using a cargo repository centralized and have problems with the freedom to distribute packages with Rust. In particular, the terms of use of the Rust and Cargo trademarks prohibit preserving the project name in case of changes or applying patches (a package can be distributed under the name Rust and Cargo only if it is assembled from the original texts, otherwise, prior written permission from the Rust Core team or name change is required).
- Developing the Linux kernel without regard for security (Grsecurity is no longer a free project and the KSPP (Kernel Self Protection Project) initiative is stalled.)
- Many components of the GNU user environment and system utilities are beginning to impose the use of excessive functionality, without providing the ability to disable it during compilation. As an example, the mandatory PulseAudio dependencies are referenced in gnome-control-center, SystemD in GNOME, Rust in Firefox, and Java in gettext.
It is because of that the development plan for HyperbolaBSD is, to transform the system into a full fork of OpenBSD which will be expanded with new code supplied under the GPLv3 and LGPLv3 licenses.
The code developed on OpenBSD will aim to gradually replace components OpenBSD released under non-GPL-compliant licenses.
While for the maintenance of the Hyperbola branch with the Linux-libre kernel previously formed will be provided until 2022, but future versions of Hyperbola will carry over to the new kernel and system elements.
With all this, the Hyperbola developers have commented that they have a lot of work to do, as they are going to abandon everything that was previously in development and focus their efforts on rebuilding the system from scratch.
Si you want to know more about it, you can check the note In the following link.
¡Olé!
Interesting news because it tells us about the state of the kernel.
Let's see how it ends.
Yep, although I don't think it's just because of the kernel but also because of forcing dependencies. As I have said in another post there seems to be a certain air of change. They are looking a lot towards the BSD world and alternative inits to try to escape from systemd and all that that entails.
As a user, the only fault that I see in the BSD world is the issue of the drivers, otherwise it is perfect since they are complete. If there were something similar to Artix in the BSD I would change without hesitation since I would be in one as it should be and although at the moment I am very happy in Artix I am beginning to worry about some of the things that have been done in recent years and it does not give me good thorn the truth.