AerynOS 2026.08 ISO Released with OpenZFS Support and systemd 261

1. AerynOS 2026.08: Release Overview

AerynOS is an independent Linux distribution built around its own package-management and operating-system tooling. Its development approach places emphasis on controlled repository updates, reproducible package definitions, and a system that can evolve without requiring users to reinstall for every repository-level change.

The August 2026 ISO is a refreshed installation image rather than simply a single desktop package update. It consolidates recent repository and system changes into installation media, so new users can begin with a more current system. The project says the image includes the latest updates available at the time of its release.

2. Experimental OpenZFS Support

One of the most significant additions in AerynOS 2026.08 is experimental support for OpenZFS data drives. The project describes this as support for user-managed data drives, alongside its existing Btrfs and Bcachefs options.

ZFS is known for features such as checksumming, snapshots, storage pools, and data-integrity capabilities. These features make it relevant to users who manage large data sets, home-lab storage, and systems where filesystem-level storage management is important. However, the AerynOS announcement specifically describes the new integration as experimental, not as a blanket recommendation for production storage.

What this means for users

• More filesystem choice: OpenZFS joins Btrfs and Bcachefs for user-managed data-drive scenarios.
• Potentially useful for storage labs: Users experimenting with ZFS can evaluate its integration on AerynOS without treating the feature as production-ready.
• Hardware testing matters: Drive controllers, disk layout, firmware, and the exact use case can influence results.
• Keep independent backups: Filesystem features are not a substitute for a separate backup and recovery strategy.

Administrators evaluating the feature should use disposable test data first, confirm the project’s current installation guidance, and test recovery procedures before considering any important workload.

3. Systemd 261.2 and Packaging Changes

AerynOS has completed a substantial systemd packaging overhaul, moving from systemd 257.13 through intermediate releases to version 261.2. The project says the rework addresses an issue in which manually enabled or disabled systemd units could have their state overwritten during Moss package transactions.

In practical terms, the change is intended to preserve administrator choices when packages are installed or updated. This is particularly relevant on systems where services have been deliberately enabled, disabled, or customized to match a particular workload.

Systemd components are now split into separate packages

The AerynOS announcement lists several systemd components that are now distributed as separate packages:

The project notes that some components, including systemd-boot, systemd-coredump, systemd-resolved, and systemd-udev, are installed automatically when required by package sets or direct package dependencies.

Network interface names may change

A particularly important user-facing note concerns network interface naming. The AerynOS project warns that interface names may change after the next reboot. Its example is a change from a name such as eth0 to a predictable name such as enp12s0.

For remote servers, make sure you have console or out-of-band access and a tested recovery plan before applying major system updates that may affect networking.

4. Versioned Repositories and Moss Improvements

The AerynOS team also reports completing the second phase of its Versioned Repositories work. This effort changes the on-disk repository layout and moves Moss configuration to the KDL format.

The goal is to let the Moss package manager update itself across incompatible repository-format changes without requiring users to carry out a manual migration. According to the project, users should be able to receive these infrastructure changes through the regular system-update process.

Additional reliability checks for package assets

Moss has also gained extra reliability checks for downloaded assets stored in its content-addressable storage. The project says these checks provide stronger guarantees that cached files have been downloaded and stored correctly, although some operations may temporarily become slower as a result.

Native reflink support on XFS

Another improvement introduces native reflink handling for AerynOS users running XFS. Reflinks allow multiple files to refer to the same underlying data blocks while retaining separate file names, permissions, and ownership metadata. This can avoid copying all file data when creating a supported copy.

On filesystems without reflink support, such as ext4 and F2FS, AerynOS continues to use its hardlink fallback behavior as described in the project update.

5. Kernel and Desktop Updates

The refreshed AerynOS 2026.08 ISO includes the Linux 7.1.5 kernel series and an updated GNOME environment for the live installer. The project’s network-based installation approach also allows users to select KDE Plasma 6.7.3 or COSMIC Desktop 1.5.0 during installation, retrieving packages from the unstable repository at installation time.

Because the installer retrieves packages from the unstable repository, the exact packages available during installation can change as the repository evolves. Users should consult the current installation documentation rather than assuming the repository will always contain the same versions listed in this release announcement.

6. NVIDIA Driver and Other Project Updates

The AerynOS repositories also received NVIDIA driver version 610.43.03. The project said it was seeking feedback from NVIDIA hardware owners as part of its testing effort. Users with NVIDIA GPUs who want to evaluate the driver should follow the current project instructions and report issues through the project’s supported channels.

Other development work mentioned in the project update includes ongoing evaluation of Codeberg as a possible alternative to GitHub. The redesigned AerynOS website, built with Hugo, was being developed on Codeberg as part of that evaluation.

The project is also preparing to move package recipes from the existing YAML format to a KDL-based schema. The announcement describes YAML as transitional and says additional capabilities for that format have been postponed while the new schema is developed and validated.

7. What Existing AerynOS Users Should Know

AerynOS says existing installations do not need to be reinstalled just to receive the software and system changes included with the 2026.08 update. The same changes can be obtained through the regular Moss update process.

Before updating, users should still read the project’s announcement and pay particular attention to the systemd changes and possible network interface renaming. A system that uses custom network configuration may need manual attention after the update or before the next reboot.

Practical preparation checklist

• Back up important user data and system configuration.
• Make sure you understand how to recover the machine if a boot or network issue occurs.
• Record current network interface names and review configurations that reference them.
• Review manually enabled or disabled systemd units and any custom service dependencies.
• Check the project’s current update guidance before applying changes to a critical machine.
• Test the update on a non-production system if the machine supports important services or data.

For systems that rely on remote access, network bridges, static interface names, or custom firewall rules, plan the update as a maintenance activity rather than treating it as an unattended routine operation.

8. Download and Test AerynOS 2026.08

The AerynOS project provides its installation media and project information through its official website. Before downloading, confirm that the image and installation instructions match your hardware and intended installation method.

For release details, read the project’s original announcement, “Solid foundations are leading to expanding horizons.” It provides the project’s own explanation of OpenZFS, systemd, repository changes, package updates, and the refreshed ISO.

9. Who Should Consider AerynOS?

AerynOS is an actively evolving independent distribution. Users who need a conservative platform with a long-established enterprise support ecosystem should evaluate its maturity, hardware compatibility, software availability, and support model against their operational requirements before adopting it for production.