FreeBSD Archive
This article isn’t meant to be technical. Instead, it offers a high-level view of what happened through the years with GhostBSD, where the project stands today, and where we want to take it next. As you may know, GhostBSD is a user-friendly desktop BSD operating system built with FreeBSD. Its mission is to deliver a simple, stable, and accessible desktop experience for users who want FreeBSD’s power without the complexity of manual setup. I started this journey as a non-technical user. I dreamed of a BSD that anyone could use. ↫ Eric Turgeon at the FreeBSD Foundation’s website I’m very glad to see this article published on the website of the FreeBSD Foundation. I firmly believe that especially FreeBSD has all the components to become an excellent desktop alternative to desktop Linux distributions, especially now that the Linux world is moving fast with certain features and components not everyone likes. FreeBSD could serve as a valid alternative. GhostBSD plays an important role in this. It offers not just an easily installable FreeBSD desktop, but also several tools to make managing such an installation easier, like in-house graphical user interfaces for managing Wi-Fi and other networks, backups, updates, installing software, and more. They also recently moved from UFS to ZFS, and intend to develop graphical tools to expose ZFS’s features to users. GhostBSD can always use more contributors, so if you have the skills, interest, and time, do give it a go.
A complete guide to configuring FreeBSD as an audiophile audio server: setting up system and audio subsystem parameters, real-time operation, bit-perfect signal processing, and the best methods for enabling and parameterising the system graphic equalizer (equalizer) and high-quality audio equalization with FFmpeg filters. Linux users will also find useful information, especially in the context of configuring and personalising the MPD player and filters. ↫ Marcin Szewczyk-Wilgan FreeBSD is a much more capable desktop and workstation operating system than it gets credit for, especially with the Linux world sucking all the air out of the room, but you do often need to do a little more and dive a little deeper into the operating system to get it to do what you want. In the case of audio, Szewczyk-Wilgan explains that he thinks it’s even ahead of Linux, due to being able to “precisely track the parameters of the audio device along with the system kernel parameters and modify them”, as well as FreeBSD having better support for real-time operation. This guide is an incredibly detailed explanation of which options and configurations you should use in FreeBSD to turn it into an audio server. This clearly isn’t for everyone, and I assume most audio experts won’t be considering FreeBSD, but what this article demonstrates is that it’s very, very much possible to do so.
14.2-RELEASE now includes OCI-compatible images, and the Podman toolkit on FreeBSD is ready to use them, on both amd64 and arm64 systems. ↫ Dave Cottlehuber This article from Dave Cottlehuber goes into more detail about the OCI-compatible FreeBSD images and how to use them.
FreeBSD 14.2 has been released, and as the version number suggests, this isn’t a major release with huge changes. Still, it does bring support for downloading and installing necessary firmware packages after installation, the latest versions of OpenZFS and OpenSSL, and much more. FreeBSD 14.2 is available for the main architectures it supports – x86, PowerPC/POWER, ARM, and RISC-V, and can be downloaded from the usual location.
Another excellent guide from friend of the website Stefano Marinelli. A client of mine has several Windows Server VMs, which I had not migrated to FreeBSD/bhyve until a few weeks ago. These VMs were originally installed with the traditional BIOS boot mode, not UEFI, on Proxmox. Fortunately, their virtual disks are on ZFS, which allowed me to test and achieve the final result in just a few steps. This is because Windows VMs (server or otherwise) often installed on KVM (Proxmox, etc.), especially older ones, are non-UEFI, using the traditional BIOS boot mode. bhyve doesn’t support this setup, but Windows allows changing the boot mode, and I could perform the migration directly on the target FreeBSD server. ↫ Stefano Marinelli I link to guides like these because finding such detailed guides born out of experience, written by actual humans with actual experience – instead of bots on content farms – is remarkably hard. There’s more than enough similar content like this out there covering Windows or popular Linux distributions like Red Hat, but the BSDs tend to fall a bit short here. As such, promoting people writing such content is something I’ll happily do. Marinelli also happens to host the Matrix server (as part of his BSD Cafe effort) that houses the OSNews Matrix room, accessible by becoming an OSNews Patreon.
quBSD is a FreeBSD jails/bhyve wrapper which implements a Qubes inspired containerization schema. Written in shell, based on zfs, and uses the underlying FreeBSD tools. ↫ quBSD GitHub page quBSD really seems to build upon the best FreeBSD has to offer. Neat.
It’s the start of the work week, so for the IT administrators among us, I have another great article by friend of the website, Stefano Marinelli. This article covers migrating a Proxmox-based setup to FreeBSD with bhyve. The load is not particularly high, and the machines have good performance. Suddenly, however, I received a notification: one of the NVMe drives died abruptly, and the server rebooted. ZFS did its job, and everything remained sufficiently secure, but since it’s a leased server and already several years old, I spoke with the client and proposed getting more recent hardware and redoing the setup based on a FreeBSD host. ↫ Stefano Marinelli If you’re interested in moving one of your own setups, or one of your clients’ setups, from Linux to FreeBSD, this is a great place to start and get some ideas, tips, and tricks. Like I said, it’s Monday, and you need to get to work.
When I think about bhyve Live Migration, it’s something I encounter almost daily in my consulting calls. VMware’s struggles with Broadcom’s licensing issues have been a frequent topic, even as we approach the end of 2024. It’s surprising that many customers still feel uncertain about how to navigate this mess. While VMware has been a mainstay in enterprise environments for years, these ongoing issues make customers nervous. And they should be – it’s hard to rely on something when even the licensing situation feels volatile. Now, as much as I’m a die-hard FreeBSD fan, I have to admit that FreeBSD still falls short when it comes to virtualization – at least from an enterprise perspective. In these environments, it’s not just about running a VM; it’s about having the flexibility and capabilities to manage workloads without interruption. Years ago, open-source solutions like KVM (e.g., Proxmox) and Xen (e.g., XCP-ng) introduced features like live migration, where you can move VMs between hosts with zero downtime. Even more recently, solutions like SUSE Harvester (utilizing KubeVirt for running VMs) have shown that this is now an essential part of any virtualization ecosystem. ↫ gyptazy FreeBSD has bhyve, but the part where it falls short, according to gyptazy, is the tool’s lack of live migration. While competitors and alternatives allow for virtual machines to be migrated without downtime, bhyve users still need to shut down their VMs, interrupt all connections, and thus experience a period of downtime before everything is back up and running again. This is simply not acceptable in most enterprise environments, and as such, bhyve is not an option for most users of that type. Luckily for enterprise FreeBSD users, things are improving. Live migration of bhyve virtual machines is being worked on, and basic live migration is now supported, but with limitations. For instance, only virtual machines with a maximum of 3GB could be migrated live, but that limit has been raised in recent years to 13 to 14GB, which is a lot more palatable. There are also some issues with memory corruption, as well as some other issues. Still, it’s a massive feat to have live migration at all, and it seems to be improving every year. The linked article goes into much greater detail about where things stand, so if you’re interested in keeping up with the latest progress regarding bhyve’s live migration capabilities, it’s a great place to start.
For nearly 15 years, FreeBSD has been at the core of my personal infrastructure, and my passion for it has only grown over time. As a die-hard fan, I’ve stuck with BSD-based systems because they continue to deliver exactly what I need—storage, networking, and security—without missing a beat. The features I initially fell in love with, like ZFS, jails, and pf, are still rock-solid and irreplaceable. There’s no need to overhaul them, and in many ways, that reliability is what keeps me hooked. My scripts from 20 years ago still work, and that’s a rare kind of stability that few platforms can boast. It’s not just me, either—big names like Netflix, Microsoft, and NetApp, alongside companies like Tailscale and AMD, continue to support FreeBSD, further reinforcing my belief in its strength and longevity (you can find the donators and sponsors right here). Yet, while this familiarity is comforting, it’s becoming clear that FreeBSD must evolve to keep pace with the modern landscape of computing. ↫ gyptazy It’s good to read so many articles and comments from long-time FreeBSD users and contributors who seem to recognise that there’s a real opportunity for FreeBSD to become more than ‘just’ a solid server operating system. This aligns neatly with FreeBSD itself recognising this, too, and investing in improving the operating system’s support for what are not considered basic laptop features like touchpad gestures and advanced sleep states, among other things. I’ve long held the belief that the BSDs are far closer to attracting a wider, more general computing-focused audience than even they themselves sometimes seem to think. There’s a real, tangible benefit to the way BSDs are developed and structured – a base system developed by one team – compared to the Linux world, and there’s enough disgruntlement among especially longtime Linux users about things like Wayland and systemd that there’s a pool of potential users to attract that didn’t exist only a few years ago. If you’re a little unsure about the future of Linux – give one of the BSDs a try. There’s a real chance you’ll love it.
FreeBSD is going to take its desktop use quite a bit more seriously going forward. FreeBSD has long been a top choice for IT professionals and organizations focused on servers and networking, and it is known for its unmatched stability, performance, and security. However, as technology evolves, FreeBSD faces a significant challenge: supporting modern laptops. To address this, the FreeBSD Foundation and Quantum Leap Research has committed $750,000 to improve laptop support, a strategic investment that will be pivotal in FreeBSD’s future. ↫ FreeBSD Foundation blog So, what are they going to spend this big bag of money on? Well, exactly the kind of things you expect. They want to improve and broaden support for various wireless chipsets, add support for modern powersaving processor states, and make sure laptop-specific features like touchpad gestures, specialty buttons, and so on, work properly. On top of that, they want to invest in better graphics driver support for Intel and AMD, as well as make it more seamless to switch between various audio devices, which is especially crucial on laptops where people might reasonably be expected to use headphones. In addition, while not specifically related to laptops, FreeBSD also intends to invest in support for heterogeneous cores in its scheduler and improvements to the bhyve hypervisor. Virtualisation is, of course, not just something for large desktops and servers, but also laptop users might turn to for certain tasks and workloads. The FreeBSD project will be working not just with Quantum Leap Research, but also various hardware makers to assist in bringing FreeBSD’s laptop support to a more modern, plug-and-play state. Additionally, the mentioned cash injection is not set in stone; additional contributions from both individuals and larger organisations are obviously welcome, and of course if you can contribute code, bug reports, documentation, and so on, you’re also more than welcome to jump in.
FreeBSD 13.4 has been released. This is already the fifth release in the FreeBSD 13 series, and contains the usual set of security fixes, driver updates, important updated packages, like openssh, LLVM, clang, and so on. If you’re running FreeBSD 13, you already know how to upgrade, and if you want to start using FreeBSD 13, here’s the download page.
This is freebsd-rustdate, a reimplementation of freebsd-update. It’s primarily written because of how slow freebsd-update is, and is written in rust because I felt like it. In usage, it’s expected to be similar, but not identical to freebsd-update. There are probably a number of minor edge-case differences I don’t even know about, but there are a number of larger ones that are intentional too. ↫ Matthew Fuller I love it when someone takes on a very well-established tool that’s used by countless people who probably barely think about how it could be improved. In this case, the performance improvements are nothing short of extraordinary, but of course, its author Matthew Fuller rightfully points out that you really shouldn’t be using this on any production system. It has not received even one percent of the kind of testing and eyeballs that the regular update tool in FreeBSD has received, so there may be edge cases or bugs. Improving the speed of the update process is always welcome. If it’s slow and time-consuming, people might postpone the updates because they’re getting in the way of what they want to do at the moment. Sure, I doubt the average FreeBSD user is the kind of person to postpone updates and run an insecure system in the meantime, but it might still draw a few people across the line to quickly get them done before continuing their work. This new rust-based FreeBSD update tool is definitely not going to be replacing the current one any time soon, nor is it even a part of the FreeBSD project in the first place, so there’s no need to worry about any potential breakage to your FreeBSD system because they’re replacing a battle-tested tool with a new one. All this does for now is highlight that there’s gains to be made here, and that’s a goal worth pursuing.
One feature I couldn’t live without anymore is snapshots. As system administrators, we often find ourselves in situations where we’ve made a mistake, need to revert to a previous state, or need access to a log that has been rotated and disappeared. Since I started using ZFS, all of this has become incredibly simple, and I feel much more at ease when making any modifications. However, since I don’t always remember to create a manual snapshot before starting to work, I use an automatic snapshot system. For this type of snapshot, I use the excellent zfs-autobackup tool – which I also use for backups. The goal is to have a single, flexible, and configurable tool without having to learn different syntaxes. ↫ Stefano Marinelli I’m always a little sad about the fact that the kind of advanced features modern file systems like ZFS, btrfs, and others offer are so inaccessible to mere desktop users like myself. While I understand they’re primarily designed for server use, they’re still making their way to desktops – my Fedora installations all default to btrfs – and I’d love to be able to make use of their advanced features straight from within KDE (or GNOME or whatever it is you use). Of course, that’s neither here or there for the article at hand, which will be quite useful for people administering FreeBSD and/or Linux systems, and who would like to get the most out of ZFS by automating some of its functionality.
The FreeBSD project has published its latest quarterly status report, and there’s a lot in there. The most prominent effort listed in the report is a close collaboration between FreeBSD and AMD on an IOMMU driver for AMD’s server processors. Work continued on a joint project between Advanced Micro Devices (AMD) and The FreeBSD Foundation to develop a complete FreeBSD AMD IOMMU driver. This work will allow FreeBSD to fully support greater than 256 cores with features such as CPU mapping and will also include bhyve integration. Konstantin Belousov has been working on various parts of the project, including driver attachment, register definitions, an ACPI table parser, and utility functions. Two key components that need to be completed are context handling, which is mostly a generalization of Intel DMAR code, and page table creation. After this, the AMD driver’s enable bit can be turned on for testing. ↫ FreeBSD status report page It’s great to see AMD and FreeBSD working together like this, and it highlights that FreeBSD is a serious player in the server space. Other things mentioned in the status report are continued work in improving the audio experience, wireless networking, RISC-V support, OpenZFS, and more. Through the work of Tom Jones, FreeBSD is also getting the Vector Packet Processor, a userspace networking stack that delivers fast packet processing suitable for software-defined networking and network function virtualization applications. Of course, this is just a selection, and there’s way more listed in the report. I would also like to highlight the ongoing, neverending work of improving the experience of using KDE on FreeBSD. The FreeBSD KDE team notes that due to the massive release of KDE 6, and the associated flurry of follow-up releases, requiring a lot of work and testing, KDE on FreeBSD still hasn’t fully caught up with the latest releases. KDE Frameworks is currently at 6.3.0 (6.5.0 is current), KDE Plasma Desktop is currently 6.0.3 (6.1.4 is current), and KDE Gear 6 hasn’t been ported at all yet. In other words, while progress is being made, it’s clear the team could use a hand, too.
Hetzner no longer offers a FreeBSD rescue system but it is possible to install and manage FreeBSD with OpenZFS from the Linux rescue system on a dedicated server with UEFI boot. The installation is done on a mirrored OpenZFS pool consisting of two drives. ↫ Martin Matuska Not much to add here – Hetzner is a popular hosting and server provider, and if you want to use FreeBSD on their machines, here’s how.
Not too long ago I linked to a blog post by long-time OSNews reader (and silver Patreon) and friend of mine Morgan, about how to set up OpenBSD as a workstation operating system – and in fact, I personally used that guide in my own OpenBSD journey. Well, Morgan’s back with another, similar article, this time covering FreeBSD. After going through the basic steps needed to make FreeBSD a bit more amenable to desktop use, Morgan notes about performance: Now let’s compare FreeBSD. Well, quite frankly, there is no comparison! FreeBSD just feels snappier and more responsive on the desktop; at the same 170Hz refresh it actually feels like 170Hz. Void Linux always felt fast enough and I thought it had no lag at all at that refresh rate, but comparing them side by side (FreeBSD installed on the NVMe drive, Void running from a USB 4 SSD with similar performance), FreeBSD is smooth as glass and I started noticing just the slightest lag/stutter on Void. The same holds true for Firefox; I use smooth scrolling and on FreeBSD it really is perfectly smooth. Similarly, Youtube performance is unreal, with no dropped frames at any resolution all the way up to 4Kp60, and the videos look so much smoother! ↫ Morgan/kaidenshi This is especially relevant for me personally, since the prime reason I switched my workstation back to Fedora KDE was OpenBSD’s performance issues. While those performance issues were entirely expected and the result of the operating system’s focus on security and hardening, it did mean it’s just not suitable for me as a workstation operating system, even if I like the internals and find it a joy to use, even under the hood. If FreeBSD delivers more solid desktop and workstation performance, it might be time I set up a FreeBSD KDE installation and see if it can handle my workstation’s 270Hz 4K display. As I keep reiterating – the BSD world has a lot to offer those wishing to run a UNIX-like workstation operating system, and it’s articles like these that help people get started. A lot of the steps taken may seem elementary to many of us, but for people coming from Linux or even Windows, they may be unfamiliar and daunting, so having it all laid out in a straightforward manner is quite helpful.
Choosing an operating system for new technology can be crucial for the success of any project. Years down the road, this decision will continue to inform the speed and efficiency of development. But should you build the infrastructure yourself or rely on a proven system? When faced with this decision, many companies have chosen, and continue to choose, FreeBSD. Few operating systems offer the immediate high performance and security of FreeBSD, areas where new technologies typically struggle. Having a stable and secure development platform reduces upfront costs and development time. The combination of stability, security, and high performance has led to the adoption of FreeBSD in a wide range of applications and industries. This is true for new startups and larger established companies such as Sony, Netflix, and Nintendo. FreeBSD continues to be a dependable ecosystem and an industry-leading platform. ↫ FreeBSD Foundation A FreeBSD marketing document highlighting FreeBSD’s strengths is, of course, hardly a surprise, but considering it’s fighting what you could generously call an uphill battle against the dominance of Linux, it’s still interesting to see what, exactly, FreeBSD highlights as its strengths. It should come as no surprise that its licensing model – the simple BSD license – is mentioned first and foremost, since it’s a less cumbersome license to deal with than something like the GPL. It’s philosophical debate we won’t be concluding any time soon, but the point still stands. FreeBSD also highlights that it’s apparently quite easy to upstream changes to FreeBSD, making sure that changes benefit everyone who uses FreeBSD. While I can’t vouch for this, it does seem reasonable to assume that it’s easier to deal with the integrated, one-stop-shop that is FreeBSD, compared to the hodge-podge of hundreds and thousands of groups whose software all together make up a Linux system. Like I said, this is a marketing document so do keep that in mind, but I still found it interesting.
This document provides information about the NanoBSD tools, which can be used to create FreeBSD system images for embedded applications, suitable for use on a USB key, memory card or other mass storage media. It can be used to build specialized install images, designed for easy installation and maintenance of systems commonly called “computer appliances”. Computer appliances have their hardware and software bundled in the product, which means all applications are pre-installed. The appliance is plugged into an existing network and can begin working (almost) immediately. ↫ FreeBSD documentation Some of the primary features of NanoBSD are exactly what you’d expect out of a tool like this, such as the system being entirely read-only at runtime, so you don’t have to worry about shutdowns or data loss, and of course, the entire creation process of NanoBSD images using a simple shell script with any arbitrary set of requirements. For the rest, it remains a FreeBSD system, so ports and packages work just as you’d expect, and assuming your specific settings for the NanoBSD image didn’t remove it, anything that works in FreeBSD, works in a NanoBSD image, too. The documentation is, as is often the case in the BSD world, excellent, and very easy to follow, even for someone not at all specialised in things like this. Reading through it, I’m pretty sure even I could create a customised NanoBSD image and run it, since it very much looks like you’re just creating a custom installation script, adding just the things you need. I don’t have a use for something like this, but I’m not sure how well-known NanoBSD is, and I feel like there’s definitely some among you who would appreciate this.
The Vector Packet Processor (VPP) is a framework for moving packets around at high rates. Its core concept is handling packets in groups known as “vectors,” which allows for the native use of vector processor instructions for packet classification and processing in different CPU architectures — currently amd64 and arm64. VPP can process packets at incredibly high rates and competes with many dedicated forwarding appliances. This is achieved using userspace networking that bypasses the host’s normal network stack. This article describes the porting of VPP to FreeBSD and working with the upstream VPP project to include FreeBSD as a supported target. ↫ Tom Jones It’s not unusual for me to link to something a little over my head, and this is another example of something I know y’all will like, but I don’t really understand fully.
A new point release in the FreeBSD 14 series – the first one, in fact, not counting 14.0. FreeBSD 14.1 adds SIMD implementations of string and memory operations on amd64 in the C library to improve performance, improvements to the sound system, such as device hotplug support, and the latest versions of OpenZFS, clang/llvm, and OpenSSH. FreeBSD 14.0 users can just upgrade to FreeBSD 14.1, or you can do a fresh install, of course.
