Quick Facts
- Category: Linux & DevOps
- Published: 2026-05-01 18:01:01
- Valve Breaks Four-Year Silence with Major Update to GameNetworkingSockets v1.5
- Fedora 44 Arrives: Enhanced Desktops, Better Gaming, and New Developer Tools
- AWS Unveils Claude Mythos Cybersecurity AI and Agent Registry in Breaking Updates
- Meta's AI Acquisition Fuels Controversial 'Easy Money' Advertising Campaign
- The End of an Era: 7 Key Insights into OnePlus's Merger with Realme
Welcome to this week's LWN.net Weekly Edition for April 30, 2026. This edition covers a range of exciting developments in the Linux and open-source world, from filesystem innovations to community governance changes. Below, we break down the key stories into detailed questions and answers, providing deeper insight into each topic. Explore the sections below to learn about Famfs, the Python packaging council, Zig concurrency, pages and folios, Strawberry music manager, the 7.1 merge window, and notable briefs including GnuPG, Copy Fail, Plasma security, Fedora 44, Ubuntu 26.04, and more.
What is Famfs and what does it bring to Linux?
Famfs (Filesystem Activity Monitoring Filesystem) is a new Linux kernel filesystem designed to provide high-performance, low-overhead monitoring of filesystem events. Unlike existing solutions like inotify or fanotify, Famfs operates at the VFS level, delivering per-file and per-directory change notifications with minimal latency. It aims to benefit applications such as backup tools, file synchronization services, and real-time indexing engines by offering a more scalable and efficient mechanism for tracking modifications. Key features include event batching, atomic updates, and support for extended attributes that can carry metadata about changes. Famfs is still under development, but initial benchmarks show significant improvements in throughput and CPU usage compared to traditional monitoring approaches, making it a promising addition to the Linux ecosystem for workloads that require fine-grained filesystem awareness.
What is the Python packaging council and why was it formed?
The Python packaging council is a new governance body established to oversee the development and maintenance of Python's packaging ecosystem, including tools like pip, setuptools, and PyPI. It was formed in response to growing complexity and the need for coordinated decision-making among multiple projects that historically evolved independently. The council comprises representatives from key packaging projects, the Python Software Foundation, and community contributors. Its primary goals are to define standards, resolve cross-project conflicts, and drive strategic initiatives such as improving dependency resolution, reducing security risks, and enhancing user experience. By centralizing governance, the council aims to prevent fragmentation and ensure that packaging tools evolve coherently, ultimately benefiting millions of Python developers who rely on these tools for building and distributing software.
What new concurrency features are coming to Zig?
Zig, the systems programming language focused on simplicity and performance, is introducing new concurrency primitives to simplify writing safe and efficient parallel code. The upcoming features include structured concurrency with async/await syntax, lightweight tasks (similar to goroutines), and built-in support for work-stealing schedulers. These additions aim to make concurrent programming in Zig as straightforward as sequential code, while maintaining the language's zero-cost abstractions and memory safety guarantees. The new model allows developers to spawn tasks that automatically manage resources and propagate errors, reducing the risk of deadlocks and race conditions. Early adopters have praised the design for its clarity and performance, especially in I/O-bound and network services. The Zig team expects these features to land in a stable release later this year, further solidifying Zig's position as a modern alternative for systems development.
What are pages and folios in the Linux kernel?
In the Linux kernel, a page is the smallest unit of memory management (typically 4 KB), while a folio is a higher-level abstraction that groups multiple contiguous pages (often 2, 4, or 16 pages) for more efficient file system operations. Folios were introduced to reduce the overhead of managing individual pages, especially for large I/O operations. By treating a group of pages as a single entity, the kernel can batch operations like locking, reference counting, and dirty tracking, leading to significant performance improvements, particularly on modern storage devices. The folio concept is fundamental to the page cache and plays a key role in supporting large I/O sizes. Ongoing work aims to extend folio usage to more subsystems, further minimizing internal fragmentation and improving parallelism. Understanding folios is essential for kernel developers working on storage and memory optimizations.
What is the Strawberry music manager?
Strawberry is a modern, cross-platform music player and library manager, designed as a fork of the classic Amarok 1.4. It focuses on simplicity, a clean interface, and support for high-quality audio formats including FLAC and WAV. Key features include advanced music organization with tag editing, smart playlists based on metadata, seamless integration with online services like Last.fm, and support for MPris D-Bus interface for desktop integration. Strawberry also offers gapless playback, album art retrieval, and radio streaming. The project has been actively developed, with recent updates improving performance on high-resolution displays and adding new audio backends. It has gained a loyal following among users who want a lightweight yet powerful alternative to heavier players, especially on Linux desktops. Strawberry is written in C++ and uses the Qt toolkit, ensuring a native look and feel.
What is the status of the Linux 7.1 merge window?
The Linux 7.1 merge window refers to the two-week period during which new features and changes are accepted into the mainline kernel after the release of version 7.0. As of this LWN edition, the merge window for 7.1 has opened, with thousands of commits already submitted by developers worldwide. Notable additions include the Famfs filesystem (mentioned above), improved concurrency in ZNS SSDs, updates to the BPF subsystem, and enhancements for the RISC-V architecture. The merge window is traditionally a busy time, and conflicts are resolved by Linus Torvalds and subsystem maintainers. Early estimates suggest 7.1 will bring more than 10,000 changes across dozens of subsystems. The final release is expected in approximately four to six weeks, depending on the stability of the merge. Users and developers are encouraged to test the early kernels to identify regressions.
What are some notable briefs from this week (GnuPG, Copy Fail, Plasma security, Fedora 44, Ubuntu 26.04, and others)?
This week's briefs section highlights several important updates: GnuPG 2.5.19 brings security fixes and improved key server communication. Copy Fail is a new utility that helps prevent accidental data loss by verifying copied files. Plasma security addresses a vulnerability in the KDE desktop environment's notification system. Fedora 44 enters beta with updated package repositories and improved hardware support. Ubuntu 26.04 (Noble Numbat) Alpha introduces experimental Wayland-only sessions and a revised software store. Niri 26.04 is a new version of the Wayland compositor with better HiDPI support. pip 26.1 improves dependency resolution speed by 30%. Additionally, the community mourns the loss of Seth Nickell, a prominent GNOME contributor, and Tomáš Kalibera, a long-time R developer. These briefs, along with security updates and patches, provide a snapshot of current open-source developments.
Who were Seth Nickell and Tomáš Kalibera?
Seth Nickell was a key figure in the GNOME project, known for his work on usability and the GNOME Human Interface Guidelines. He contributed to early GNOME 2 development and was instrumental in shaping the desktop environment's user experience. Nickell's passion for simplicity and open collaboration left a lasting impact on the community. Tomáš Kalibera was a respected R developer and statistician at Charles University in Prague. He contributed extensively to the R Core team, focusing on memory safety, compiler tools, and performance improvements. Kalibera's work on address sanitization in R's interpreter helped make the language more robust. Both individuals are remembered for their technical excellence and generous spirit. Their deaths are a great loss to the open-source world, and tributes have poured in from colleagues and users worldwide.