The Haiku running device has released R1/beta1
As promised through the Haiku crew in advance this month, Haiku R1 now stands released in its beta model! After the huge gap between Haikus’ brand new launch in November 2012, users can count on greater enhancements within the R1/beta1. The Haiku OS is thought of for its ease of use, responsiveness, and average coherence. With improvements to its package deal manager, WebPositive, media subsystem, and lots greater Haiku have made the wait really worth it’s at the same time as! Let’s dive into a number of the predominant improvements of this release.
#1 Package control
The largest upgrade within the R1 Beta is the addition of an entire bundle management system. Finalized and merged all through 2013, Haiku programs are a special sort of compressed filesystem image. These are ‘mounted’ upon setting up and thereafter on each boot via the packages.
It is really worth noting that in view that packages are “activated”, now not installed, the bootloader has been given a few potentials to affect them. Users can boot into a preceding bundle country -if they took a terrible replacement- or even blocklist character documents. Installations and uninstallations of packages are almost immediately. Users can manage the hooked-up package set on a non-jogging Haiku machine by mounting its boot disk, then manipulating the /gadget/packages directory and related configuration documents.
The Haiku group has also delivered pigman, the command-line interface to the package deal management gadget. Unlike most other package managers where applications can be set up most effective by name, Haiku applications also can be looked for and installed with the aid of offers, e.G. Pkgman installation cmd: sync or pigman installation devel:libsdl2, with a purpose to locate the most relevant package deal that offers that, and installation it. Accompanying the package deal manager is a vastly revamped HaikuPorts, containing a wide array of native and ported software for Haiku.
#2 WebPositive improvements
The crew has made the system web browser plenty more strong than before. Glitches with YouTube now stand fixed. While working on WebKit, the team also controlled to fix a huge number of insects in Haiku itself – along with damaged stack alignment, numerous kernel panics in the network stack, horrific aspect-case coping within app_server’s rendering center GCC upgrades, and lots of more. HaikuWebKit now helps Gopher, which is its own network protocol layer.
#3 Completely rewritten network reflect
The newly rewritten network reflect is designed for ease of use and sturdiness. In addition to the interface configuration monitors, the preflight can now manipulate the network services at the device, including OpenSSH and find. It uses a plugin-based totally API, which enables third-birthday party community services like VPNs, internet servers, and so forth to combine with it.
#4 User interface cleanup & live colour updates
Mail and Tracker now game Haiku-style toolbars and font-size consciousness, amongst other programs. This will permit customers to feature the right DPI scaling and proper-to-left layouts. Instead of asking for a specific device color after manipulating it, maximum packages now educate their controls to undertake certain colorings based on the device color set immediately.
#5 Media subsystem improvements
The Haiku team has made cleanups to the Media Kit to enhance fault tolerance, latency correction, and performance problems. This will help with Kit’s ordinary resilience. HTTP and RTSP streaming help are included in the I/O layer of the Media Kit. Livestreams can now be performed in WebPositive thru HTML5 audio/video support or the native MediaPlayer. Significant improvements to the FFmpeg decoder plugin have been made.
Rather than the historical FFmpeg zero.10, the remaining model that GCC2 can bring together, FFmpeg 4.0 is now used all-around for a higher guide of both audio and video codecs, as well as tremendous performance enhancements. The motive force for HDA saw an excellent range of cleanups and wider audio aid for the reason that is preceding release. The DVB tuner subsystem saw a considerable amount of rework, and the APE reader changed into also wiped clean up and brought to the default builds.
Haiku’s local RemoteDesktop application become stepped forward and introduced to the builds. The RemoteDesktop forwards drawing commands from the host device to the client system, which consumes significantly lower bandwidth for most applications. RemoteDesktop can connect and run applications on any Haiku gadget that customers have SSH admission to; there’s no need for a far-off server.
#7 New thread scheduler
Haiku’s kernel thread scheduler is now O(1) (regular time) with admire to threads and O(log N)(logarithmic time) concerning processor cores. The new limit is 64 cores, an arbitrary constant that can be accelerated at any time. There are new implementations of the memory, and memset primitives for x86 representing full-size will increase their overall performance.
#8 Updated Ethernet & WiFi drivers
The Ethernet & WiFi drivers were upgraded to those from FreeBSD 11.1. This brings in help for Intel’s more recent “Dual Band” family, some of Realtek’s PCI chipsets, and more recent-version chipsets in all other present drivers. Additionally, the FreeBSD compatibility layer now interfaces with Haiku’s assist for MSI-X interrupts, which means that WiFi and ethernet drivers will take gain of it anyplace viable, leading to great enhancements in latency and throughput.
#9 Updated report system drivers
The NFSv4 customer is finally merged into Haiku itself and is covered with the aid of default. Additionally, Haiku’s userland, which helps running filesystem drivers in userland, is now shipped in conjunction with Haiku itself. It helps walking BeOS filesystem drivers, Haiku filesystem drivers and provides FUSE compatibility. As a result, diverse FUSE-based totally filesystem drivers at the moment are to be had within the ports tree, such as FuseSMB, amongst others.