Extended attributes (xattrs) provide a way to attach key/value metadata to inodesโfiles, directories, and the likeโin a filesystem. As with many Linux filesystems, the FUSE filesystem supports xattrs. In a filesystem-track session at the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit, FUSE maintainer Miklos Szeredi led a discussion about caching xattrs in kernel memory; he would like to create some common infrastructure that could be used by FUSE and shared with other filesystems.
The future is already here. And in the history recounted by this series, the reason is remarkably simple: it never went anywhere. We live in an era where technology permeates every moment of our existence; where the consolidation of technological ... Read more The post Linux Is Already the Future. It Never Left appeared first on Linux Professional Institute (LPI).
After backlash from the Linux community, California may be backing off on its promise to force all operating systems to verify age, but one platform may still have to comply.
Clonezilla Live 3.3.2 disk cloning/imaging tool is now available for download with Linux kernel 7.0, Partclone 0.3.47, improved MDRAID support, gocryptfs mechanism for image encryption, and other changes.
Maybe it was a one-line typo fix in the docs. Perhaps it was a package youโd been maintaining in secret for months before you finally submitted it. Maybe it was completely terrifying, or maybe it just felt like the most natural thing in the world. Whatever it was we want to hear about it. Ahead [โฆ]
Package managers for operating systems and programming languages have been around for decades. Each package manager, and its accompanying packaging format, has been shaped by the needs of its respective ecosystem, but there is a growing need to make use of package metadata for more than software management: for example, in vulnerability scans, software bills of materials (SBOMs), and more. On May 19, Damiรกn Vicino spoke at the Open Source Summit North America 2026 about his experiences in the past year trying to make sense of the varied metadata provided by more than 20 package managers.
Version 8.3 of Vim Classic has been released. This is the first release of the Vim fork since the project was announced in March. This release is based on Vim 8.2.0148, with a number of bug fixes and patches conservatively backported from future versions of Vim upstream. We elected to clean up this version of Vim, prepare it for a release, and imagine an alternate history where Vim 8.3 was released without Vim9 script. The result is Vim Classic 8.3. We chose to take this approach in order to reduce the long-term maintenance burden of Vim Classic, acknowledging that our fork lacks the resources and institutional knowledge available to Vim upstream. However, a consequence is that there are some Vim plugins which are not compatible with Vim Classic. We have made a special effort to assess patches from Vim upstream which mitigate some of the many CVEs affecting Vim which were discovered and fixed between versions 8.2 and modern-day Vim, but we can't be sure we've got all of the security pa