Linux Journal - The Original Magazine of the Linux Community

Fedora Governance Changes Take Effect as Project Refines Leadership, Policy, and Contributor Oversight

George Whittaker — Tue, 23 Jun 2026 16:00:00 +0000

A series of Fedora governance updates are now taking effect, marking another step in the project's ongoing effort to modernize decision-making processes, improve transparency, and better support Fedora's growing contributor community. The changes come as the Fedora Council and other leadership bodies continue refining how one of the Linux world's largest community-driven projects is managed.

While these updates may not be as visible as a new desktop environment or kernel release, they play a critical role in shaping Fedora's future direction, community initiatives, and long-term sustainability.

How Fedora Governance Works

Fedora's governance structure is built around several key organizations that guide different aspects of the project.

These include:

The Fedora Council, which oversees strategic direction
FESCo (Fedora Engineering Steering Committee), responsible for technical and engineering decisions
Mindshare, which focuses on community outreach and contributor engagement
Various Special Interest Groups (SIGs) and working groups that manage specific initiatives and technologies

Together, these groups help coordinate thousands of contributors spread across the globe.

Greater Focus on Strategic Planning

Recent Fedora Council discussions have emphasized long-term planning and governance modernization. One major area of focus has been defining clearer processes for evaluating and managing new initiatives through what Fedora leaders call an Innovation Lifecycle framework.

The proposed framework aims to:

Better evaluate experimental projects
Establish clearer entry and review phases
Define expectations for community initiatives
Improve oversight as projects mature

The goal is to create a more predictable path for new ideas while maintaining Fedora's culture of innovation.

Refining Contributor Representation

Another governance topic receiving significant attention involves contributor participation and voting eligibility.

Fedora leadership has been examining questions such as:

What defines an active contributor?
How should voting rights be determined?
How can elections remain fair while staying inclusive?
How should dormant accounts be handled?

These discussions stem from concerns that existing systems may not always accurately reflect current contributor activity.

While no single solution has been finalized, governance bodies are actively working toward policies that balance openness with accountability.

Go to Full Article

The Growth of Vulnerability Management: The Rise of Agentic AI Pentesting

Malana VanTyler — Thu, 18 Jun 2026 16:00:00 +0000

by Malana VanTyler

Cybersecurity shifts fast. Manual penetration tests remain valuable, especially for nuanced attack paths and business-logic issues, but they are expensive, point-in-time, and difficult to run continuously. By the time a report is delivered, the environment may have already changed. Automated scanners improved coverage and frequency, but most still rely on known signatures, templated checks, and shallow validation. They can find obvious issues, but they rarely match the adaptive reasoning, chaining, and persistence of a skilled attacker.Platforms like XBOW help security teams move toward continuous validation by running AI-driven tests that mimic large-scale human attackers. This shift moves the focus from periodic assessment and reactive patching toward ongoing exposure management and earlier prevention.

From Automation to Agency

To appreciate the value of these modern platforms, it’s important to separate traditional automation from what is called “agentic” AI. Earlier AI pentesting tools mostly worked like advanced “if-then” systems, running preset scripts and looking for known patterns. While useful to automate some tasks pentesters perform, these tools lack the ability to pivot.

If a standard tool hits a non-standard login portal, it generally stops. An agent platform, however, can identify and adapt to the obstacle, reason through potential bypasses, and attempt alternative tactics.

This core differentiator is the “agent,” a specialized model capable of goal-oriented planning. These platforms employ real-time attack path analysis tools. They identify a low-severity vulnerability and assess whether it could be exploited to gain access

to a high-value asset. This approach imitates how an advanced attacker moves laterally within a system. The result is a clearer and more realistic view of the organization’s real risk compared to just listing bugs in a spreadsheet without context.

Comparing Methodologies: Strategy and Execution

When comparing platforms in this area, the industry is shifting focus from just ticking off features to demonstrating how effectively those features can be used. Modern platforms, including XBOW, focus on high-fidelity testing that avoids disrupting production environments while still proving that a vulnerability is reachable.

Three main architectural approaches have emerged as standouts:

Go to Full Article

Linux Kernel 7.1 Officially Released with New NTFS Driver, Intel FRED, and Major Code Cleanup

George Whittaker — Tue, 16 Jun 2026 16:00:00 +0000

by George Whittaker

The Linux kernel development team has officially released Linux Kernel 7.1, marking the first major update in the 7.x series. Announced by Linus Torvalds on June 14, 2026, the release introduces a mix of new features, hardware improvements, filesystem enhancements, and large-scale code cleanup efforts that continue modernizing the Linux platform.

While Linux 7.1 is not a long-term support (LTS) release, it delivers several significant changes that will eventually make their way into many Linux distributions over the coming months.

A Brand-New NTFS Driver Arrives

One of the most significant additions in Linux 7.1 is a completely rewritten in-kernel NTFS filesystem driver.

The new implementation has reportedly been under development for several years and replaces older code with a modern design built around Linux’s current storage infrastructure. The driver utilizes technologies such as iomap and folios, which improve efficiency and simplify future maintenance.

Benefits include:

Improved NTFS write performance
Better handling of large files
More modern filesystem architecture
Easier future development and maintenance

For users who regularly exchange data between Linux and Windows systems, this is one of the most important improvements in the release.

Intel FRED Enabled by Default

Linux 7.1 also enables Intel Flexible Return and Event Delivery (FRED) by default on supported hardware.

FRED is a newer CPU mechanism designed to improve how processors handle interrupts and exceptions. By replacing older methods with a more streamlined approach, FRED aims to improve performance and reduce complexity in low-level CPU operations.

The feature primarily benefits newer Intel platforms, including upcoming processor generations.

Graphics Drivers Continue to Improve

Graphics support remains a major focus of kernel development, and Linux 7.1 delivers additional improvements for both Intel and AMD hardware.

Highlights include:

Performance enhancements for Intel Arc GPUs
Continued work on Intel Battlemage graphics
Updates for AMD Radeon hardware
Expanded GPU reliability monitoring infrastructure through DRM-RAS support

These updates help improve gaming, desktop performance, and workstation workloads across modern Linux systems.

Steam Deck OLED Audio Fixes Land Upstream

Linux gamers receive a welcome improvement in this release as audio support fixes for the Steam Deck OLED have finally been merged into the mainline kernel.

Go to Full Article

Canonical Launches ARM Laptop Certification Program to Boost Ubuntu’s Next Generation of Mobile Computing

George Whittaker — Thu, 11 Jun 2026 16:00:00 +0000

by George Whittaker

Canonical is expanding its hardware certification efforts with a new focus on ARM-powered laptops, a move that reflects the growing momentum behind ARM architecture in the personal computing market. As ARM processors become increasingly common in laptops thanks to their impressive balance of performance, battery life, and efficiency, Canonical aims to ensure that Ubuntu users receive a seamless experience on this emerging class of hardware.

The initiative represents another step in Ubuntu’s long-standing effort to provide reliable Linux support across a wide range of devices while strengthening relationships with hardware manufacturers.

Why ARM Laptops Matter More Than Ever

For years, x86 processors from Intel and AMD dominated the laptop market. However, the landscape has changed significantly as ARM-based systems have become more powerful and capable.

Modern ARM laptops offer several advantages:

Longer battery life
Lower power consumption
Reduced heat output
Always-on connectivity capabilities
Competitive performance for everyday workloads

As manufacturers increasingly invest in ARM hardware, Linux distributions face growing pressure to ensure compatibility matches what users expect from traditional x86 systems. Canonical has already spent years supporting ARM across cloud, server, IoT, and embedded environments, making laptops a natural next step.

What the Certification Program Does

The new certification effort builds upon Canonical’s existing Ubuntu Certified Hardware program, which validates systems through extensive testing covering both hardware and operating system functionality. Certified devices undergo comprehensive verification to ensure Ubuntu operates correctly across critical components and daily workflows.

Testing typically includes:

Wireless networking
Audio functionality
Graphics performance
Bluetooth support
USB device compatibility
Power management
Suspend and resume behavior
Firmware integration
Security features such as TPM support

The goal is to eliminate the uncertainty that Linux users sometimes face when purchasing new hardware.

Creating a Better Ubuntu Experience on ARM

Historically, Linux support on ARM laptops has varied significantly between devices. Some systems work exceptionally well, while others require manual configuration, custom kernels, or vendor-specific patches.

Go to Full Article

Btrfs Snapshot Deletion Gets Faster as Developers Tackle One of the Filesystem’s Biggest Pain Points

George Whittaker — Tue, 09 Jun 2026 16:00:00 +0000

by George Whittaker

The Btrfs filesystem continues to receive significant performance tuning, and one of the latest areas of focus is snapshot deletion performance. While Btrfs snapshots have long been praised for their speed, flexibility, and efficient use of storage, deleting large numbers of snapshots has historically been one of the filesystem’s most resource-intensive operations.

Recent kernel development efforts are helping address that problem by improving metadata handling, reducing lock contention, and streamlining internal cleanup processes. The result is faster snapshot removal and less disruption on systems that rely heavily on snapshots for backups, rollbacks, and system recovery.

Why Snapshot Deletion Has Been Challenging

Btrfs is a copy-on-write (CoW) filesystem that stores data and metadata in a highly interconnected structure. This design enables many advanced features, including:

Instant snapshots
Subvolumes
Checksumming
Compression
Efficient data sharing between snapshots

However, the same architecture that makes snapshots so efficient to create can make them more complex to remove. When a snapshot is deleted, Btrfs must determine which blocks are still referenced by other snapshots and which can be safely reclaimed. On systems with many snapshots, this process can generate significant metadata activity.

Recent Performance Improvements

Developers have been working to reduce overhead associated with Btrfs metadata operations, which directly impacts snapshot cleanup performance.

Recent kernel updates include:

Reduced lock contention during extent tree operations
More efficient extent buffer traversal
Improved handling of internal filesystem structures
Reduced contention during metadata searches
General transaction and cleanup optimizations

These changes help the filesystem spend less time waiting on internal locks and more time performing actual cleanup work.

Less Impact During Cleanup Operations

One common complaint among Btrfs users has been elevated I/O activity during large snapshot deletion jobs.

On systems that maintain dozens, or even hundreds, of snapshots, cleanup operations could temporarily increase:

Disk activity
CPU usage
I/O wait times
Metadata processing workloads

Recent improvements are designed to make these operations less disruptive by reducing bottlenecks inside the filesystem's metadata management code.

For users running backup servers, NAS appliances, or snapshot-heavy desktop systems, these optimizations can improve overall responsiveness while cleanup tasks run in the background.

Go to Full Article

How Digital Software Is Powering Innovation in Modern Product Design

Will Jones — Fri, 05 Jun 2026 16:00:00 +0000

by Will Jones

By enabling digitized production design, this digital software is freeing up businesses and individuals across numerous industries to work smarter, not harder.

To design a new product or tool is often a lengthy, labor-intensive process. Even the most successful and streamlined physical design process is intensive and iterative by nature; it is the process of taking something that begins as little more than an idea and turning it into reality. Inherently, that is going to take a great deal of translation, as well as trial and error. When working with real-world, physical elements, this also makes for a costly endeavor, as each new trial effort may prove essential to the long-term success of the design, but still has adverse financial effects. Dassault Systèmes offers CAD software to help businesses stay on top of advancements in their industries.

Before digital design software became widely adopted, engineers and designers often relied heavily on hand-drawn technical sketches and manual drafting methods during product development. Revising a design could require redrawing entire sections of a project, making the process both time-consuming and resource-intensive. Modern digital design systems have significantly changed these workflows by allowing teams to make rapid adjustments, automate calculations, and store detailed design information within a single platform. This shift has contributed to the broader adoption of digital tools across industries seeking more streamlined development processes.

Fortunately, though, in this new world of ever-advancing technological tools, the design process doesn’t have to be fraught with issues and obstacles anymore, thanks to systems such as CAD software. This new software is now enabling businesses to design smarter, faster, and more accurately by digitizing product development processes and improving collaboration across engineering and manufacturing teams.

Digital Design as the Foundation of Innovation

Digital software allows engineers to create precise digital models that can then serve as the foundation for product development. Compare this to the physical alternative, which has long been a well-thought-out sketch of the product in question. Even the most comprehensive of sketches is only going to be dealing with two dimensions, and is likely to leave room for confusion or error based on the interpretation of the subjective rendering.

Go to Full Article

GNOME Files Supercharges Search with Faster Results, Smarter Filters, and Better File Discovery

George Whittaker — Tue, 02 Jun 2026 16:00:00 +0000

by George Whittaker

The GNOME project continues refining one of its most frequently used applications: GNOME Files (formerly known as Nautilus). Recent development efforts have focused heavily on improving the file manager’s search capabilities, making it easier to locate documents, media files, and folders across increasingly large storage volumes.

For many Linux users, file search has become one of the most important daily workflows. As personal data collections grow and SSDs make local storage faster than ever, GNOME developers are investing in tools that help users find information more quickly and efficiently. GNOME Files already relies on indexing technologies such as Tracker (now GNOME LocalSearch) to deliver fast results, and recent improvements are building on that foundation.

A Redesigned Search Experience

One of the most noticeable improvements is a redesigned search interface that makes searching feel more integrated into the overall file management experience.

Recent GNOME development previews introduced:

A cleaner search popover
Inline result previews
Improved keyboard navigation
Faster access to search filters
Better visibility of search options within the file manager interface

These refinements reduce the number of clicks required to narrow down results and help users locate files without leaving their current workflow.

Smarter Filtering Options

Search filters have become increasingly important as users store larger collections of documents, images, videos, and audio files.

GNOME Files has been expanding its filtering capabilities, allowing users to narrow searches more effectively based on:

File type
Media category
Search location
Recent activity
Indexed metadata

Earlier updates expanded support for additional audio and video file formats, making it easier to locate multimedia content directly from the search interface. This is particularly useful for users managing large media libraries.

Improved Search Performance

Fast search results are just as important as accurate ones.

GNOME Files continues leveraging the GNOME indexing framework to provide near-instant search results while minimizing system overhead. The file manager works closely with the LocalSearch indexing service to locate files quickly without repeatedly scanning entire drives.

This approach provides several benefits:

Faster file discovery
Reduced CPU usage during searches
Better scalability on large storage volumes
More responsive user experience

For desktop users who frequently work with thousands of files, these performance gains can significantly improve productivity.

Go to Full Article

NixOS 26.05 ‘Yarara’ Released with Systemd Initrd by Default and Major Infrastructure Updates

George Whittaker — Thu, 28 May 2026 16:00:00 +0000

by George Whittaker

The NixOS project has officially released NixOS 26.05, codenamed “Yarara,” continuing the distribution’s unique approach to Linux system management through declarative configuration, atomic upgrades, and reproducible deployments. The release introduces several important platform-level changes, modernized infrastructure components, and continued refinement of the Nix ecosystem.

As one of the most distinctive Linux distributions available today, NixOS continues attracting developers, DevOps engineers, and advanced Linux users who value predictable system behavior and highly reproducible environments.

What Makes NixOS Different?

Unlike traditional Linux distributions that install packages directly into shared system locations, NixOS is built around the Nix package manager, which stores software in isolated, versioned paths and generates complete system configurations declaratively.

This architecture provides several advantages:

Atomic system upgrades
Reliable rollback capabilities
Reproducible environments
Easier infrastructure automation
Reduced dependency conflicts

These features have helped NixOS gain popularity among developers managing complex systems and cloud infrastructure.

Systemd-Based Initrd Becomes the Default

One of the most significant changes in NixOS 26.05 is the move to a systemd-based Stage 1 initrd by default. The older scripted implementation is now deprecated and scheduled for removal in NixOS 26.11.

The initrd (initial RAM disk) is responsible for preparing the system during early boot before the main operating system loads.

According to the release notes:

Systemd now handles Stage 1 initialization by default
The previous scripted implementation remains temporarily available
Users can still revert using boot.initrd.systemd.enable = false
Long-term migration toward the systemd-based approach is encouraged

This change is expected to improve consistency and simplify maintenance across modern NixOS deployments.

Continuing the Twice-Yearly Release Cycle

NixOS continues its established release cadence of publishing stable versions twice per year—typically around May and November. The 26.05 “Yarara” release follows the previous 25.11 “Xantusia” release and continues the project's steady development rhythm.

The 26.05 development cycle involved extensive staging, package testing, and release management work coordinated through the NixOS community.

Large-Scale Package and Infrastructure Updates

Like previous NixOS releases, 26.05 includes a massive collection of package updates across the software ecosystem.

Go to Full Article

GNOME 51 Development Officially Begins as ‘A Coruña’ Cycle Gets Underway

George Whittaker — Tue, 26 May 2026 16:00:00 +0000

by George Whittaker

The GNOME Project has officially opened the development cycle for GNOME 51, the next major release of one of Linux’s most widely used desktop environments. Following the recent launch of GNOME 50 “Tokyo,” developers are already shifting focus toward the next chapter of the desktop’s evolution, which will carry the codename “A Coruña.”

While it’s still very early in the process, the release schedule is now taking shape, giving Linux users and developers an early look at what to expect over the coming months.

GNOME 51 “A Coruña” Is Now in Development

The new release is named A Coruña, after the Spanish city that will host GUADEC 2026, the annual GNOME Users and Developers European Conference. The event serves as one of the most important gatherings for GNOME contributors, where future desktop plans, technologies, and development priorities are discussed.

As soon as GNOME 50 was finalized, development work for GNOME 51 officially began, continuing GNOME’s well-established six-month release cadence.

Release Schedule Already Published

The GNOME team has outlined the preliminary roadmap for the GNOME 51 cycle.

Current milestone dates include:

GNOME 51 Alpha: June 27, 2026
GNOME 51 Beta: August 1, 2026
GNOME 51 Release Candidate (RC): August 29, 2026
GNOME 51 Final Release: September 16, 2026

These milestones provide time for:

Feature integration
Public testing
Bug fixing
Performance optimization
Final stabilization before release

As always, dates may shift slightly depending on development progress.

Still Too Early for Major Feature Announcements

Because the development cycle has only just started, GNOME developers have not yet revealed a finalized feature list. Most major design discussions and merge requests are still in their early stages.

However, several areas are already attracting attention.

Wayland Improvements Are Likely a Major Focus

One of the biggest transitions in recent GNOME history happened with GNOME 50, which completed the project’s move away from X11 by removing remaining X.Org support from the desktop environment.

Because GNOME is now fully committed to Wayland, many observers expect GNOME 51 to focus heavily on:

Go to Full Article

Alpine Linux Experiments with Systemd Compatibility While Keeping Its Lightweight Identity

George Whittaker — Thu, 21 May 2026 16:00:00 +0000

by George Whittaker

Alpine Linux, one of the most recognizable non-systemd Linux distributions, is reportedly experimenting with an optional systemd compatibility layer, a move that has sparked intense discussion across the Linux community.

For years, Alpine has stood apart from mainstream Linux distributions by avoiding both glibc and systemd, instead relying on:

musl libc
BusyBox
OpenRC as its init system

Now, growing software compatibility pressures, especially around desktop applications, containers, and enterprise tooling, appear to be pushing Alpine developers to explore new approaches.

Why Alpine Linux Avoided Systemd for So Long

Alpine Linux built its reputation around simplicity, security, and minimalism. Unlike many mainstream distributions, Alpine intentionally avoided systemd in favor of the lighter and more modular OpenRC init system.

This design philosophy made Alpine extremely popular for:

Containers and Docker images
Embedded systems
Lightweight virtual machines
Security-focused deployments

Its tiny footprint and reduced dependency chain became major advantages in cloud and container environments.

The Compatibility Problem Is Growing

Despite Alpine’s popularity, avoiding systemd has increasingly created compatibility challenges.

Many modern Linux applications now assume the presence of:

libsystemd
systemd APIs
glibc-specific behaviors

This has become particularly problematic for:

Desktop software
Proprietary enterprise applications
Monitoring agents
Certain gaming and multimedia tools
AI and container orchestration software

Historically, Alpine users often relied on:

Compatibility layers like gcompat
Flatpak containers
Docker workarounds
Manually patched packages

The growing complexity of those workarounds appears to be one reason compatibility discussions are intensifying.

What the Experimental Compatibility Layer Actually Means

Importantly, Alpine Linux is not replacing OpenRC with systemd.

Instead, the project appears to be exploring:

Optional compatibility packages
libsystemd support
Improved API compatibility for software expecting systemd components

Experimental efforts already exist in the broader ecosystem. For example, unofficial projects have packaged portions of systemd, particularly libsystemd, for Alpine systems specifically to satisfy software dependencies without running full systemd services.

Go to Full Article