FreeBSD Status Report Second Quarter 2025

Here is the second 2025 status report, with 32 entries.

As for the preceding quarters, this report is published just a few days before calls for 2025Q3 report submissions are sent. Indeed, although according to our timeline we should have published this report in July (general rule is publication should happen within the month just after the calls for reports are sent), we kept receiving important reports until the end of August. This is both a positive and a negative thing. On one hand, it means that our FreeBSD community is busy fixing existing issues and implementing new features, making the OS we love better and better every day; it means that the community works so intensely that very little time remains for reporting. On the other hand, it means that news in these reports is always two months old when published. Two months is not bad, especially if we consider that FreeBSD communication happens on many other channels too, but it would be nice if we could improve it.

If you are a late submitter, please take some time to evaluate if there is anything you can do to improve your report submission punctuality. The Status Team is always glad to ease the submission process: if there is something we can do for you, just ask. If you are a contributor or just a FreeBSD user, please consider contributing more, if you can. Even working on a single small simple task is useful, it can help to lower the pressure on other developers, for whom it might thus become easier to find the time to document their work.

Have a nice reading!

Lorenzo Salvadore, on behalf of the Status Team.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

A rendered version of this report is available here: https://www.freebsd.org/status/report-2025-04-2025-06/

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Table of Contents

• FreeBSD Team Reports
□ FreeBSD Core Team
□ FreeBSD Foundation
□ FreeBSD Release Engineering Team
□ Ports Collection
□ Bugmeister Team
□ Source Management Team
• Projects
□ Infrastructure Modernization
□ Support for pkgbase in the FreeBSD installer
□ BSD-USER 4 LINUX
□ Sylve — A Unified System Management Platform for FreeBSD
□ Hackathon 202506 Kitchener-Waterloo, Canada
• Userland
□ ucred / group changes in FreeBSD 15.0
□ MIT Kerberos Import into FreeBSD
□ SysctlTui
□ Geomman Development
• Kernel
□ Audio Stack Improvements
□ DRM drivers
□ Suspend/Resume Improvement
□ Named attribute support (Solaris style extended attributes)
□ Packrat — NFS client caching on non-volatile storage
□ LinuxKPI 802.11 and Native Wireless Update
□ USB Kernel Debugging
□ Porting HFS+ to FreeBSD
• Architectures
□ Pinephone Pro Support
• Cloud
□ FreeBSD on EC2
• Documentation
□ Documentation Engineering Team
□ FreeBSD Wiki
□ Vision Accessibility
• Ports
□ Security Hardening Compiler Options for the Ports Collection
□ Improve OpenJDK on FreeBSD
□ GCC on FreeBSD
• Third Party Projects
□ Chinese FreeBSD Community (CFC)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Team Reports

Entries from the various official and semi-official teams, as found in the Administration Page.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Core Team

Contact: FreeBSD Core Team <[email protected]>

The FreeBSD Core Team is the governing body of FreeBSD.

Project roadmap

Core is collecting ideas and comments to draft Project’s roadmap. It is an item
core.13 thinks is worth to continue from core.12. The roadmap is not about restricting or limiting what developers and contributors can do, but about the compiled goals and expectations of the Project and things the community can collaborate on. It will also let the FreeBSD Foundation help the Project more effectively, so, this is an important discussion item for the meetings between core and the FreeBSD Foundation.

Policy on generative AI created code and documentation

Core is investigating setting up a policy for LLM/AI usage (including but not limited to generating code). The result will be added to the Contributors Guide in the doc repository. AI can be useful for translations (which seems faster than doing the work manually), explaining long/obscure documents, tracking down bugs, or helping to understand large code bases. We currently tend to not use it to generate code because of license concerns. The discussion continues at the core session at BSDCan 2025 developer summit, and core is still collecting feedback and working on the policy.

Work in Progress

Core is currently working on the following items:

• Core and the FreeBSD Foundation are working on the 2025 edition of the
Community survey

• Privacy-friendly web analytics, proposed by the Foundation. An idea is to
compare traffic flows between freebsd.org and freebsdfoundation.org

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Foundation

Links:
FreeBSD Foundation URL: https://freebsdfoundation.org/
Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/
Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
FreeBSD Journal URL: https://freebsdfoundation.org/journal/
Foundation Events URL: https://freebsdfoundation.org/our-work/events/

Contact: Deb Goodkin <[email protected]>

The FreeBSD Foundation is a 501(c)(3) non-profit dedicated to advancing FreeBSD through both technical and non-technical support. Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters.

Here are some of the ways we supported FreeBSD in the second quarter of 2025.

Advocacy

Advocacy work in the 2nd quarter of 2025 included hosting events, launching a new series of video guides and bringing on a new Marketing Coordinator. Florine Kamdem brings social media, branding, and IT skills. She uses storytelling to craft digital campaigns that spark interest and build connection within the community. Read more about Florine, and check out just a few of the ways the Foundation helped advocate for FreeBSD in Q2 of 2025:

• Held the June 2025 FreeBSD Developer Summit June 11-12, 2025, co-located
with BSDCan 2025. Videos of the all day stream are available on the
Project’s YouTube Channel, and videos of the individual talks will be
available in the coming weeks.

• Finalized our Silver Sponsorship of EuroBSDcon 2025, held in Zagreb,
Croatia; September 25-28, 2025. Travel Grants are now available. The
application deadline is Aug 5, 2025.

• Provided updates and announcements about our Software Development work
including:

□ The Road to Better Wi-Fi on FreeBSD

□ April 2025 Laptop Support and Usability Project Update

□ FreeBSD Ports and Packages Security Project

□ Software Bill of Materials (SBOM) for FreeBSD Project

• Published the following blogs and videos to help inform and educate the
community:

□ The Hidden Costs of Stagnation: Why Running EOL Software is a Ticking
Time Bomb

□ How to Unlock High Speed Wi-Fi on FreeBSD 14

□ The Report of My Death Was an Exaggeration

□ ZFS automatic snapshots with Sanoid on FreeBSD

□ Three Ways to Try FreeBSD in Under Five Minutes

• Published the March/April 2025 and May 2025 FreeBSD Foundation Newsletters.

• Released the January/February/March 2025 issue of the FreeBSD Journal with
HTML versions of the articles.

OS Improvements

The Foundation continued to support two major initiatives: the Laptop Support and Usability project (in collaboration with Quantum Leap Research) and an infrastructure modernization project commissioned by the Sovereign Tech Agency. For background on both efforts, see the 2025Q1 quarterly status report.

Throughout the quarter, there were 536 src, 64 ports, and 41 doc commits that identified the FreeBSD Foundation as a sponsor.

Here is a sampling of that work and other sponsored efforts:

• Various improvements to libvirt’s support for bhyve, including:

□ An initial port of the libvirt integration testing project,
libvirt-tck, enabling test execution against libvirt’s bhyve driver on
FreeBSD.

□ Enhancements to the bhyve driver to improve compatibility and
testability.

□ Support for virtio-rnd devices, NVRAM configuration, and extended
domain usage statistics (under review).

□ Initial support for pf(4)-based NAT networking (under review).

• Improved handling of tlsbase (thread-local storage) on amd64, making it
more reliable across context switches and benefiting applications that
manually manage TLS, such as Wine.

• Runtime linker improvements, including support for the -z initfirst flag.
This addresses longstanding issues with RTLD_DEEPBIND and provides better
control over symbol resolution and initialization order in dynamically
linked applications.

• Enhanced ptrace usability by enabling transient PT_ATTACH behavior. This
reduces friction for debugging tools and eliminates spurious EINTR errors
that could interrupt or break tracing workflows.

• kqueue introspection support by extending procstat(1) to report kqueue
state, improving observability into how processes use kernel event
notification mechanisms

• Design and implementation of EXTERROR, a mechanism that reports extended
error information to userspace, augmenting the usual errno value. This
enables applications to retrieve more detailed diagnostics beyond standard
error codes.

Other sponsored efforts are covered in separate report entries:

• Vision Accessibility

• Suspend/Resume Improvements

• LinuxKPI 802.11 and Native Wireless Update

• Audio Stack Improvements

• Improve OpenJDK on FreeBSD

• Sylve — A Unified System Management Platform for FreeBSD

• Support for pkgbase in the FreeBSD Installer

• DRM drivers

• MIT Kerberos Import into FreeBSD

• USB Kernel Debugging

• Bugmeister Team

The Foundation is managing FreeBSD’s participation in the Google Summer of Code
(GSoC) program. Twelve projects were accepted this year.

Continuous Integration and Workflow Improvement

As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project’s continuous integration system and test infrastructure.

Legal/FreeBSD IP

The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise.

Go to https://freebsdfoundation.org to find more about how we support FreeBSD and how we can help you!

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Release Engineering Team

Links:
FreeBSD 14.3-RELEASE announcement URL: https://www.freebsd.org/releases/14.3R/announce/
FreeBSD 15.0-RELEASE schedule URL: https://www.freebsd.org/releases/15.0R/schedule/
FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/
FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ISO-IMAGES/

Contact: FreeBSD Release Engineering Team, <[email protected]>

The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.

The Team managed 14.3-RELEASE, leading to the official RELEASE build and announcement in June. Planning has started for the upcoming 15.0-RELEASE, which is due to arrive in December.

The OCI Container Images built by the Release Engineering Team are now being uploaded to Docker and GitHub repositories in addition to being available on the FreeBSD download site.

The Team gained a new member, Jake Freeland, and three members have departed: Konstantin Belousov, John Hixson, Doug Rabson. We thank them for their contributions.

The Release Engineering Team continued providing weekly development snapshot builds for the main, stable/14, and stable/13 branches.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Ports Collection

Links:
About FreeBSD Ports URL:https://www.FreeBSD.org/ports/
Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing
Ports Management Team URL: https://www.freebsd.org/portmgr/
Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/

Contact: Tobias C. Berner <[email protected]>
Contact: FreeBSD Ports Management Team <[email protected]>

The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter.

During the last quarter, we welcomed Älven (alven@) and Jesús Daniel Colmenares
Oviedo (dtxdf@) as new ports committers, and said goodbye to one committer.

According to INDEX, there are currently 36,605 (up from 36,450) ports in the Ports Collection. There are currently about 3,330 (down from 3,333) open ports PRs, of which 832 are unassigned. The last quarter saw 10,294 (down from 10,733) commits by 157 (down from 158) committers on the main branch and 770 (up from 707) commits by 56 (up from 54) committers on the 2025Q2 branch.

The most active committers to main were:

• 3541 [email protected]

• 503 [email protected]

• 439 [email protected]

• 345 [email protected]

• 315 [email protected]

• 301 [email protected]

• 240 [email protected]

• 240 [email protected]

• 183 [email protected]

• 178 [email protected]

A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are:

• pkg 2.2.1

• Default version of Go switched to 1.24

• Default version of Lazarus (non-aarch64) switched to 4.0

• Default version of Linux (non-i386) switched to Rocky Linux 9 (rl9)

• Default version of Perl switched to 5.40

• Default version of PostgreSQL switched to 17

• Default version of Ruby switched to 3.3

• Chromium 137.0.7151.119

• Electron 35.* and 36.*

• Firefox 140.0.2

• Firefox-esr 128.12.0

• Gnome 47

• KDE Plasma 6.4.1

• KDE Framework 6.15.0

• Qt6 6.9.1

• Ruby 3.2.8, 3.3.8, 3.4.4 (new), and 3.5.0-preview1 (new)

• Rust 1.87.0

• SDL 2.32.8 and 3.2.16

• Sway 1.11

• wlroots 0.19.0 (new)

• Xorg server 21.1.18

During the last quarter, pkgmgr@ ran 22 exp-runs to test infrastructure changes and various ports upgrades.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Bugmeister Team

Links:
FreeBSD Bugzilla URL: https://wiki.freebsd.org/Bugzilla

Contact: Bugmeister <[email protected]>

In this quarter we stayed steady-state on the PR count.

Mark Linimon has held some voice chats on the FreeBSD Discord for "Bugmeister Office Hours". The plan is to hold them more regularly and announce them in advance. At the moment the schedule is Mondays at 3pm CDT (1800 UTC).

We still are doing better at triaging PRs than we are generating committer attention to the ones we have triaged. Suggestions welcome.

We have added new search queries about Maintainer Approval (applies to Attachments) and Maintainer Feedback (applies to an entire individual Problem Report). These queries were not easily composable from the various web forms. This work was funded by the FreeBSD Foundation.

Please see the new documentation.

We used these queries to close various PRs, and also to investigate inactive maintainers. As of yet, we have not taken action on the latter.

A problem with the setup of the upgrade to Bugzilla 5.2 has been fixed. Light testing shows no regressions. Switching to this codebase is scheduled for next quarter.

patchQA.py still remains in beta. The patch application code is not up to its task and must be replaced.

The other problem known with patchQA.py is that it does not know the origins of files that are installed into /etc by installworld.

We have created dozens of new Bugzilla accounts by user request.

See also: https://wiki.freebsd.org/Bugzilla/SearchQueries

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Source Management Team

Contact: srcmgr <[email protected]>

The srcmgr@ team aims to make src developers more productive, and works to manage the large number of bug reports, pull requests and code reviews that we receive. Meeting minutes are available on GitHub.

We held a bug-busting session on 2025-05-23 with about 10 attendees.

Members of srcmgr@ gave a presentation at the 2025 FreeBSD developer summit in Ottawa.

Per the discussion at the developer summit, the i386 and 32-bit powerpc targets have been disconnected from the build.

To help ensure continuity of the team, we introduced a "lurkers" program which lets src committers participate in bi-weekly srcmgr meetings, giving developers an opportunity to decide whether they are interested in officially joining srcmgr@ without taking on any specific obligations. After soliciting interested developers, we have five lurkers who have been joining calls over the past couple of months:

• Jake Freeland <[email protected]>

• Olivier Certner <[email protected]>

• Dag-Erling Smørgrav <[email protected]>

• Bojan Novković <[email protected]>

• Kyle Evans <[email protected]>

Aside from participating in discussions, they have been working on src development tasks — especially in preparation for FreeBSD 15.0 — and topics
such as monitoring stale Phabricator reviews, performance regression tracking, and using git notes to track certain types of commit metadata.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Projects

Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Infrastructure Modernization

Contact: Ed Maste <[email protected]>
Contact: Alice Sowerby <[email protected]>

The project started in Q3 of 2024 and was commissioned by the Sovereign Tech Agency with a budget of $745,000, to be spent over about one year. The main goals are to improve security tools for the base system, ports, and packages, update the project’s infrastructure to speed up development, enhance build security, and make it easier for new developers to get started.

Q2 update

All five work packages are now in progress and will run until the end of December 2025, at which time the project will close.

Work Package A: Technical Debt reduction

The majority of the work in this work package is complete, with a small number of hours allocated each month to help support FreeBSD Project’s Source Management team to embed their new processes to make bug management easier and more sustainable. The bug backlog dashboard https://grimoire.freebsd.org remains available to help make the backlog easier to understand.

We have also been upgrading Bugzilla by applying patches from 2023 onward and improving the upgrade process to ensure smoother future updates.

A panel discussion at Open Source Summit Europe in August will share this work with a wider audience. Two members of the Foundation project staff will be present, along with two representatives from Bitergia who delivered the GrimoireLab implementation for this project. (Members of the FreeBSD Project Source Management team were not available to attend.)

Progress is being made to reduce technical debt by creating an automated method for evaluating patches (code improvements) attached to existing pull requests for source and ports trees to see whether they are still relevant, and applying them if they are. This tool is in beta.

Work Package B: Zero Trust Builds

This work package intends to improve tooling and processes to support Zero Trust Builds of FreeBSD by extending the current components to enable the project to build release artifacts (package sets, ISO images, etc.) without requiring any special privilege.

The detailed scope was co-created with core@, srcmgr@, secteam@. Work items are as follows:

• Must

□ No-root for all source release build cases/artifacts (in progress)

□ Src artifacts to build reproducibly (in progress)

□ Formalize and document make world and release.sh (in progress)

• Should

□ Remove privilege from orchestration tooling (not started)

□ Move build scripts into the public repository (not started)

• Could

□ Environment Standardization (not started)

□ Ports to build reproducibly (not started)

□ CI to verify reproducibility (in progress)

□ Documentation to allow 3rd parties to confirm reproducibility (not
started)

Work Package C: CI/CD Automation

This work package intends to improve CI/CD automation to streamline software delivery and operations for new and existing software by modernizing and securitizing the existing CI/CD system and extending it to cover the third party packages in the FreeBSD Ports Collection.

The detailed scope was co-created with core@, srcmgr@, portmgr@, doceng@.

• Must

□ Improve quality of incoming commits (completed)

□ Pre-merge CI (completed)

□ Environment Metadata (not started)

□ Extend CI to the Ports tree (in progress)

□ CI Threat Model (not started)

□ CI Management Process (in progress)

□ Documentation (not started)

• Should

□ 3rd-party Interoperability (in progress)

□ Automated analysis in tests (in progress)

□ Test Case Management (not started)

• Could

□ Granular Debugging (not started)

Work Package D: Ports and Packages security improvements

This work package intends to modernize and extend security controls in the FreeBSD Ports and Package Collection by:

• migrating from our VuXML Vulnerability Database to OSV or similar
contemporary format

• developing a package audit backend and server to reliably fetch
vulnerability data from global agency databases in any format (JSON - NIST)
and produce insight

• improving CI tooling for FreeBSD Ports.

The detailed scope was co-created with core@, portmgr@, pkgmgr@, secteam@.

• Must

□ New Database Format (in progress)

□ Set up 2+ Database Instances (not started)

□ Migrate Data from old to new database (in progress)

□ Add support for new format in pkg(8) (in progress)

□ Upstream engagement (not started)

□ SBOM on demand (not started)

□ Document how to set up build and test targets (not started)

□ Integrate 3rd party test targets (not started)

□ Continuous Testing (not started)

• Could

□ Make CI artifacts available (not started)

Work Package E: SBOM improvements

This work package intends to improve existing, and implement new, tooling and processes for FreeBSD Software Bill of Materials (SBOM) by implementing: tooling to roll up the individual provenance data/markers from across the tree into a higher-level view; developing tooling to parse/review/inspect the FreeBSD source tree and produce a comprehensive/holistic report to act as a SBOM for the full software stack and; extending pkg to enable this capability for software installed from ports/packages.

The detailed scope was co-created with core@, portmgr@, pkgmgr@, secteam@, releng@

• Must

□ Evaluate projects/solutions available in the wider ecosystem (in
progress)

□ Propose the target solution for SBOM (not started)

□ Produce an SBOM in CI (e.g. weekly builds) (in progress)

□ Produce an SBOM as an artifact as part of the release process (in
progress)

□ SBOM artifact on demand (in progress)

□ Roll up existing data (not started)

□ Record and explain decisions made (not started)

• Could

□ Engage with other similar projects (not started)

Commissioning body: Sovereign Tech Agency

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Support for pkgbase in the FreeBSD installer

Contact: Isaac Freund <[email protected]>

The FreeBSD installer now supports installing a pkgbase system.

Recent FreeBSD 15.0 snapshots have a new dialog in the installer that allows the user to fetch and install packages from pkg.freebsd.org instead of using the legacy distribution sets.

There is also support in the build system to build FreeBSD installation media with offline pkgbase packages included, enabling fully offline installation of a pkgbase system. These offline pkgbase packages are not yet included in 15.0 snapshot release installation however, as including both the offline legacy distribution sets and pkgbase packages would significantly increase the size of the installation media. There is however a -DPKGBASE build-time switch ready to be flipped by the FreeBSD Release Engineering team, hopefully in the near future.

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

BSD-USER 4 LINUX

Contact: Maksym Sobolyev <[email protected]>

Links: Project Page URL: https://github.com/sobomax/qemu-bsd-user-l4b
Tooling URL: https://github.com/sobomax/qemu_l4b

The bsd-user-4-linux project ports BSD user-mode emulation for QEMU to Linux. The primary goal is to enable unmodified FreeBSD binaries to run on modern Linux systems. Additionally, the project aims to provide multi-platform container images with a functional FreeBSD environment and ready-to-use GitHub Actions templates.

News:

• Two new pull requests have been received since the initial project
announcement:

□ Diagnostic output cleanup;

□ kqueue() support using libkqueue library on Linux.

• The latest set of changes has been pulled from the Warner’s qemu-bsd-user
project bringing Qemu version to 9.2.0 along with some fixes and
improvements.

Current Status:

• The initial port successfully runs make -jN buildworld.

• Most command-line tools are working as expected (sh(1), bash(1), find(1),
grep(1), git(1), clang(1), etc).

• A GitHub Actions pipeline builds x86_64 emulation images for:

□ linux/386

□ linux/amd64

□ linux/arm/v5

□ linux/arm64/v8

• A pre-built Docker container with FreeBSD 14.1 binary world is created and
pushed to the GitHub Container Registry.

□ FreeBSD Image @ GHCR

• Special pre-built "admin" container with Linux user-mode qemu binary for
the FreeBSD/amd64 emulation is also published at the GHCR.

□ FreeBSD binfmt Image @ GHCR

Next Steps: * Bump FreeBSD version to 14.3; * Rebase onto Qemu 10.0.x.

How You Can Help:

• Test with your preferred toolchain, report issues, or contribute fixes.

• Identify and implement missing system calls.

• Support us on Patreon.

Sponsor: Sippy Software, Inc.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Sylve — A Unified System Management Platform for FreeBSD

Links:
GitHub URL: https://github.com/AlchemillaHQ/Sylve
CI URL: https://sylve-ci.alchemilla.io
Discord URL: https://discord.gg/bJB826JvXK

Contact: Hayzam Sherif <[email protected]>

Sylve is a modern, unified system management platform for FreeBSD, inspired by Proxmox. We aim to provide an integrated web interface for managing virtual machines (via Bhyve), Jails, ZFS storage, networking, and firewalling. The backend is implemented in Go, while the frontend uses SvelteKit with Tailwind CSS and ShadCN UI components.

The project emphasizes a minimal system footprint, currently requiring only sysutils/smartmontools, sysutils/tmux, and libvirt as runtime dependencies.

Sylve continues to address a key gap in the FreeBSD ecosystem by delivering a cohesive, user-friendly interface for system administration tasks.

Q2 Progress Highlights

Dashboard

Added dynamic charts to the main summary page, including real-time visualization of CPU usage, RAM usage, and network throughput.

Networking

Interfaces can now be viewed in detail through the UI, with all relevant metadata presented in a structured format.

Users can also create "switches" — simple layer 2 switches built on top of
FreeBSD bridge interfaces.

Storage

ZFS integration is nearing completion. Users can now:

• Create and destroy pools, filesystems, volumes, and snapshots.

• Delete multiple datasets at once.

• Schedule automatic (timed) snapshots.

Initial dashboard work for ZFS monitoring has started, with further enhancements planned in Q3.

Utilities

A built-in downloader was introduced that supports both HTTP and magnet links.

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)