đŸ Archived View for lofi.haiku-os.org âș get-haiku âș r1b4-notes.gmi captured on 2023-06-16 at 16:12:01. Gemini links have been rewritten to link to archived content
âŹ ïž Previous capture (2023-01-29)
-=-=-=-=-=-=-
The fourth beta for Haiku R1 marks over a year and a half of hard work to improve Haiku's hardware support and its overall stability. Over 400 bugs and enhancement tickets have been resolved for this release.
Please keep in mind that this is beta-quality software, which means it is feature complete but still contains known and unknown bugs. While we are mostly confident in its stability, we cannot provide assurances against data loss.
For most of this release cycle, waddlesplash was employed as a contractor to work on Haiku. His contract is presently ongoing, supported by the generous donations of readers like you to Haiku, Inc., a 501(c)3 non-profit.
To download Haiku or learn how to upgrade from R1/beta3, see "Get Haiku!". For press inquiries, see "Press contact".
This release is available on the x86 32-bit platform, as well as the x86_64 platform.
Note that BeOS R5 compatibility is only provided on the 32-bit images.
+---------------------------------+--------------------------------------+ | Minimum (32-bit) | Recommended (64-bit) | +---------------------------------+--------------------------------------+ | Processor: Intel Pentium II | Processor: Intel Core i3 | | AMD Athlon | AMD Phenom II | | Memory: 384 MiB | Memory: 2 GiB | | Monitor: 800x600 | Monitor: 1366x768 | | Storage: 3 GiB | Storage: 16 GiB | +---------------------------------+--------------------------------------+
Previous releases of Haiku partially supported HiDPI scaling merely by changing the system font size; however, not all metrics were actually tied to the font size as they should be, and not all applications actually obeyed the system-set font size. Much work over the past release cycle has gone into rectifying these problems, and as you can now see in the above screenshots, most native applications now scale sufficiently well. There are still some weak spots, but these should be resolved in time.
Additionally, on first boot Haiku now attempts to automatically detect if you are on a HiDPI display and set appropriate sizes. These can of course be adjusted with the font size settings of the Appearance preferences. For now, it is not possible for changes to these settings to take effect without a reboot.
Some ported applications have already been patched or updated to correctly read and use Haikuâs own settings, but not all of them yet.
For those who find Haikuâs use of gradients a little âmuchâ, there is now a âflatâ decorator & control look available. It does not come installed by default, but can be added via the âHaiku Extrasâ package, and then enabled in the Appearance preferences. (The colors shown are not yet included by default; you will have to use ThemeManager or adjust some preferences manually in order to get a like appearance.)
Requested for many years and now finally a reality: âTrackerâ, Haikuâs native file manager (originally inherited from BeOS), now supports generating and displaying image thumbnails. The thumbnails themselves are stored in extended attributes of the files themselves, which means applications can create their own thumbnails for custom filetypes, if they want (for example, a screenshot might be the thumbnail of an emulatorâs save-state.)
Most âRTLâ and some âRAâ USB WiFi devices (the two most common device families, very often repackaged under other names) are now supported in Haiku thanks to the import of the relevant drivers from FreeBSD, and the implementation of FreeBSDâs basic USB-related APIs in Haikuâs FreeBSD driver compatibility layer. There is one major limitation: these devices must be connected before Haiku is booted; they will not be detected if connected after the boot is finished.
The iwm and iwx drivers from OpenBSD, along with OpenBSDâs 802.11 stack, have been imported into Haiku (and given the native names idualwifi7260 and iaxwifi200 respectively.) These provide support for Intelâs âDual Bandâ and âAXâ families of WiFi hardware. FreeBSDâs version of the iwm driver had been available on Haiku for years, but only supported 802.11a/b/g (not even 802.11n, much less 802.11ac!) and was not very reliable; meanwhile the iwx driver has no direct FreeBSD equivalent.
This means Haiku is only the third open-source operating system (to the best of our knowledge) after Linux and OpenBSD to support 802.11ac WiFi, as not even FreeBSD supports it (yet?) despite having worked on it intermittently for years.
Supporting these drivers required the addition of an âOpenBSD compatibility layerâ, which builds on top of the existing FreeBSD compatibility layer. OpenBSD supporting hardware that FreeBSD does not seems to be an increasing trend (there are some more ethernet and WiFi cards that OpenBSD has drivers for which Haiku could stand to gain), and this work paves the way for such future developments.
A new driver has been added to support âRNDISâ ethernet tethering, which is the most common kind Android phones use when selecting âUSB tetheringâ. It is enabled by default, and supports hot-plugging.
The NTFS filesystem driver (which is a wrapper around the NTFS-3G library) was completely rewritten. The old one hearkened back to the BeOS days and had not kept up with development: it did not support any kind of caching, incorrectly handled file deletions in a way that caused kernel panics, did not support memory-mapping files (making git usage impossible on NTFS partitions), and had plenty of other issues besides.
The new diver is much more idiomatic, supports the major layers of Haikuâs common filesystem caching mechanisms, and resolves all known issues and major missing features the previous one was plagued with. Since it is not FUSE-based (like NTFS-3G is on Linux) but runs in kernel-mode, it is competitive for performance with the other fully native filesystem drivers.
There is now an AVIF image translator available by default, providing both read and write support for this new and advanced image format for all native Haiku applications.
HaikuWebKit has been synchronized to an up-to-date version of upstream WebKit, and contains many bugfixes since the previous release of Haiku. It also now uses the cURL networking backend, which resolved a large number of the network-related issues seen in previous releases.
32-bit EFI support has been added (previous releases only supported 64-bit EFI.) It is possible to boot a 64-bit Haiku installation from a 32-bit EFI loader.
Thanks to (at first) the new X11 compatibility layer, and (now) the new Wayland compatibility layer (more details below), there is now a working GTK3 port for Haiku! Ports of Inkscape, GIMP, and more are now available for immediate install, and more GTK applications are being added to HaikuPorts as time goes on.
One of the newly available GTK applications is GNOME Web aka. Epiphany, which is based on a very recent version of WebKitGTK. This provides an unfortunately non-native but largely functional web browser for Haiku for the first time in many years, with âjust worksâ status for major websites like YouTube and others.
Haiku has had terminal-based GNU Emacs for some time, but now (thanks to Emacs developers!) has a fully-upstreamed, polished-to-a-shine native GUI. You can install it from HaikuDepot already, or check out a development branch of Emacs and build it yourself.
Thanks to community member & contributor X512, Haiku now has a port of WINE! Initially based on the X11 compatibility layer, it now has a fully native Haiku windowing & input backend.
It is somewhat limited at the moment, being available only on 64-bit Haiku and only supporting 64-bit Windows applications. It is also a bit inefficient performance-wise at present due to some limitations in Haiku, but that will likely improve with time as Haiku gains more I/O APIs.
There is now a native compatibility layer for X11 available in the package repositories. Instead of running a full X server as XQuartz or other X11 compatibility packages do on other operating systems, it directly handles Xlib API calls and translates them into Haiku API calls, instead. You can read some more about what and why this was done, install the package directly via pkgman install xlibe_devel, or check out its source code.
This was originally written to port GTK3, and so it may be missing some (or many) API calls needed by other applications, though it has been tested with a wide variety of X11 applications and most non-Motif ones seem to at least partially work already.
Yes, in addition to an X11 compatibility layer, we now also have one for Wayland! It is a little more complicated than the one for X11, running an âin-process Wayland serverâ for each application instead of translating C API calls directly. The GTK3 port now is built atop this instead of the X11 compatibility layer for both features and performance reasons.
Hundreds of bugs and other minor issues were resolved since the previous release, and there are simply too many to try and list them all here. Virtually every area of the system received some amount of attention, and the result is Haikuâs most polished and stable release yet, even if some rough edges remain here and there.
Haiku is always looking to see how we can improve our adherence to POSIX and make it easier for developers to port their software. There are too many changes in this area to individually list, but here are some highlights:
The NVMe driver now supports falling back to âpollingâ mode when interrupts are not working properly, handles âunalignedâ transfers much more reliably, and had a number of performance improvements made to it. Support for TRIM was also implemented.
On 32-bit x86 systems, we still use the ancient GCC 2.95 to compile many parts of the system to maintain ABI compatibility with BeOS. However, in this past development cycle, changes were made so that the kernel and drivers are always compiled with the newer GCC version (presently GCC 11), even when building most of the system with GCC 2.95.
A significant amount of time has been poured into work on stabilizing the whole system, with a great many kernel and driver crashes, hangs, corruptions, and more tested, tracked down, and fixed over this releaseâs development cycle. Overall, the system seems to be the most stable itâs ever been, with plenty of feedback from the community to this effect.
The source code of Haiku itself can be accessed from the GitHub mirror or via Haikuâs own Git instance. Patches can be contributed via Gerrit.
There are over 3,600 open tickets on Haikuâs bug tracker and over 14,300 closed items. If you find what you believe to be an issue, please search the bug tracker to see if it has already been reported, and if not, file a new ticket on the bug tracker.
For information about major issues that have been fixed since the release, visit the Release Addendum page.
For more help, take the âQuick Tourâ and read the âUser Guideâ, both linked on the Haiku desktop.
WebPositive opens by default with our âWelcomeâ page which provides useful information and many helpful links, as does the Haiku Projectâs website.
For support and/or help with anything related to Haiku, feel free to post on our forums, join one of our IRC/Matrix/XMPP rooms, or send a message to one of our mailing lists so our friendly community may assist you.
Press inquiries may be directed to:
waddlesplash (English)
pulkomandy (French)
humdingerb (German)
All three contacts may be reached via <nickname>@gmail.