Vue normale
Security updates for Thursday
[$] LWN.net Weekly Edition for October 2, 2025
- Front: Fedora and AI; Linting kernel Rust; openSUSE Leap 16; mmap() file operation; 6.17 statistics; dirlock.
- Briefs: Bcachefs removal; Alpine /usr merge; F-Droid; Fedora AI policy; OpenSUSE Leap 16; PostgreSQL 18; Radicle 1.5.0; Quotes; ...
- Announcements: Newsletters, conferences, security updates, patches, and more.
Alpine Linux plans /usr merge
The Alpine Linux project has announced plans to change its base filesystem hierarchy:
In the future, /lib, /bin, and /sbin will be symbolic links to their /usr counterparts, and every package shall be installed under the /usr paths. For now, /usr/bin and /usr/sbin will continue to be independent paths, but that might change if the Filesystem Hierarchy Standard (FHS) gets updated.
The merge will take place in the upcoming Alpine 3.23 release planned for November; non-merged systems will be considered unsupported when 3.22 is at its end of life in May 2027.
[$] Fedora floats AI-assisted contributions policy
The Fedora Council began a process to create a policy on AI-assisted contributions in 2024, starting with a survey to ask the community its opinions about AI and using AI technologies in Fedora. On September 25, Jason Brooks published a draft policy for discussion; so far, in keeping with the spirit of compromise, it has something to make everyone unhappy. For some it is too AI-friendly, while others have complained that it holds Fedora back from experimenting with AI tooling.
Security updates for Wednesday
OpenSUSE Leap 16 released
This major version update of our fixed-release community-Linux distribution has a fresh software stack and introduces an unmatched maintenance- and security-support cycle, a new installer and simplified migration options.
See our look at this release for more information.
Radicle 1.5.0 released
The previous output would differentiate "updates", where the original author creates a new revision, and "revisions", where another author creates a revision. This could be confusing since updates are also revisions. Instead, the output shows a timeline of the root of the patch and each new revision, without any differentiation. The revision identifiers, head commit of the revision, and author are still printed as per usual.
LWN covered Radicle in March 2024.
[$] Linting Rust code in the kernel
Klint is a Rust compiler extension developed by Gary Guo to run some kernel-specific lint rules, which may also be useful for embedded system development. He spoke about his recent work on the project at Kangrejos 2025. The next day, Alejandra González led a discussion about Rust's normal linter, Clippy. The two tools offer complementary approaches to analyzing Rust kernel code, although both need some additional direction and support from kernel developers to reach their full potential.
Security updates for Tuesday
Bcachefs removed from the mainline kernel
It's now a DKMS module, making the in-kernel code stale, so remove it to avoid any version confusion."
[$] Development statistics for 6.17
NixOS moderation team resigns
The NixOS moderation team, which is theoretically in charge of ensuring that community participation on the project's repositories and discussion forum remains welcoming and useful, has released a joint resignation statement. This action was motivated by conflict with the project's steering committee (SC), which has repeatedly overridden the moderation team, leading the team members to decide that they could not continue acting as moderators. Arian Van Putten, speaking for the whole team, writes:
The SC has also shown, in private and public conversations, their lack of understanding of basic principles of community management and open communication. They have mistaken quiet and a lack of controversy for success and peace. They have consistently become upset when there is criticism, and gone quiet on crucial issues in between. We have some fundamental conflicts in this community, which absolutely require discussion. Meanwhile, discussion with the SC has only become less effective.
We think that the goal of moderation should not be to avoid difficult conversations - it's to navigate those difficult conversations in ways that remain safe and constructive. We believe we've made considerable progress as a community on making those conversations happen, and we believe they need to happen more for the project to grow, not be suppressed. We thank everyone for the growth that we have seen, and for their efforts to avoid personal focus in discussion, especially recently.
The NixOS project has had problems with community moderation stretching back more than a year. With the next steering council election coming up soon, it will be interesting to see whether the community selects a council that feels differently or not.
[$] Managing encrypted filesystems with dirlock
Security updates for Monday
F-Droid and Google's Developer Registration Decree
The F-Droid project cannot require that developers register their apps through Google, but at the same time, we cannot "take over" the application identifiers for the open-source apps we distribute, as that would effectively seize exclusive distribution rights to those applications.If it were to be put into effect, the developer registration decree will end the F-Droid project and other free/open-source app distribution sources as we know them today, and the world will be deprived of the safety and security of the catalog of thousands of apps that can be trusted and verified by any and all. F-Droid's myriad users will be left adrift, with no means to install — or even update their existing installed — applications.
The 6.17 kernel has been released
It's not exciting, which is all good. I think the biggest patch in there is some locking fixes for some bluetooth races that could cause use-after-free situations. Whee - that's about as exciting as it gets.Other than that, there' the usual driver fixlets (GPU and networking dominate as usual, but "dominate" is still pretty small), there's some minor random other driver updates, some filesystem noise, and core kernel and mm.
And some selftest updates.
Significant features in this release include better control over x86 Spectre mitigations, live patching support on 64-bit Arm platforms, a number of pidfd improvements, the removal of special support for uniprocessor systems, initial support for proxy execution, experimental large-folio support in the Btrfs filesystem, the file_getattr() and file_setattr() system calls, and support for the DualPI2 congestion-control protocol.
See the LWN merge-window summaries (part 1, part 2) for more information. In addition, KernelNewbies has a look at the changes that went into 6.17.
[$] Jumping into openSUSE Leap 16
The openSUSE project is nearing the release of Leap 16, its first major release since openSUSE Leap 15 in May 2018. This release brings some changes to the core of the distribution aside from the usual software upgrades; YaST has been retired, SELinux has replaced AppArmor as the default mandatory access control (MAC) system, and more. If all goes according to plan, Leap 16 final should be released in early October, with planned support through 2031.