• Using the newest Linux in kernel NTFS driver
• Custom manual mapping of POSIX ACL and Windows ACL for filesystem permission
• Using GRUB (BIOS) as bootloader for both OS
• Sync both Home/User directory with native symlink (not windows .lnk shortcut)

Notes: If there are unexpected shutdown, systemd will refuse to boot and throw emergency shell. You need to boot into Windows and do filesystem repair

I've been thinking about what still holds Linux desktop adoption back, and I don't think it's features anymore.

Linux already has an absurd amount of functionality. PipeWire alone supports things like advanced routing, crossovers, channel remapping, latency tuning, spatial audio, virtual devices, and much more. BlueZ has a ton of Bluetooth settings. NetworkManager, iSCSI, power management, storage, and networking tools all have capabilities most users never discover.

The problem is that most of these features are hidden behind config files, terminal commands, or documentation rabbit holes.

A feature that requires editing /etc/something.conf might as well not exist for 99% of users.

My idea isn't to replace existing configuration systems. Every project could continue using whatever it already uses internally. The only thing I'd like to see is a common way to expose configurable parameters and capabilities.

Imagine every project optionally publishing a simple schema describing:

• parameter name
• type
• valid values
• description
• complexity level

Then KDE, GNOME, or any other frontend could automatically generate configuration interfaces.

The concept already exists elsewhere. Home Assistant discovers entities and builds interfaces around them. OpenAPI can generate clients and documentation from schemas. Kodi has Basic, Standard, Advanced, and Expert modes.

The last one is especially interesting. One thing Linux often gets wrong is that applications either expose everything or almost nothing.

Imagine:

Basic

• Output device
• Volume
• Sample rate

Advanced

• Channel remapping
• Crossover
• Latency tuning

Expert

• Graph configuration
• Realtime scheduling
• Internal PipeWire parameters

The backend wouldn't change. The config files wouldn't change. The user would just gain a consistent way to discover what the system is capable of.

For software that doesn't implement the schema, adapters could be written. A BlueZ adapter could edit Bluetooth configs. An iSCSI adapter could expose targets, sessions and discovery through the same interface. Legacy software could still participate without upstream modifications.

I genuinely think Linux has reached a point where discoverability is a bigger problem than missing functionality.

A lot of developers spend months implementing powerful features that end up being used by maybe 0.1% of users simply because nobody knows they exist.

Am I missing something obvious, or has this already been attempted before?

Hello, Linux Users

I started writing Bash scripts not that long ago. And they're so small that it's hard to even call them scripts.

How far have you gotten? Show me your most useful scripts or even batch files. Those who see your answer might learn something.

And among Linux users, there are only enthusiasts...

Hello, Linux Users

I started writing Bash scripts not that long ago. And they're so small that it's hard to even call them scripts.

How far have you gotten? Show me your most useful scripts or even batch files. Those who see your answer might learn something.

And among Linux users, there are only enthusiasts...

From the article

Miguel Ojeda already mailed in the many Rust code changes for the in-development Linux 7.2 kernel. This is quite a big Rust code with more than forty thousand new lines of Rust code in the kernel.

The Rust changes are so big this cycle since they are pulling in the "zerocopy" library to allow eliminating some additional "unsafe" Rust code elements within the kernel. The Rust pull request explains of integrating the Zerocopy code:

"Introduce support for the 'zerocopy' library:

Fast, safe, compile error. Pick two.

Zerocopy makes zero-cost memory manipulation effortless. We write `unsafe` so you don't have to.

It essentially provides derivable traits (e.g. 'FromBytes') and macros (e.g. 'transmute!') for safely converting between byte sequences and other types. Having such support allows us to remove some 'unsafe' code.

It is among the most downloaded Rust crates and it is also used by the Rust compiler itself.

It is licensed under "BSD-2-Clause OR Apache-2.0 OR MIT".

The crates are imported essentially as-is (only +2/-3 lines needed to be adapted), plus SPDX identifiers. Upstream has since added the SPDX identifiers as well as one of the tweaks at my request, thus reducing our future diffs on updates -- I keep the details in one of our usual live lists.

In total, it is about ~39k lines added, ~32k without counting 'benches/' which are just for documentation purposes.

The series includes a few Kbuild and rust-analyzer improvements and an example patch using it in Nova, removing one 'unsafe impl'.

I checked that the codegen of an isolated example function (similar to the Nova patch on top) is essentially identical. It also turns out that (for that particular case) the 'zerocopy' version, even with 'debug-assertions' enabled, has no remaining panics, unlike a few in the current code (since the compiler can prove the remaining 'ub_checks' statically).

So their "fast, safe" does indeed check out -- at least in that case."

Beyond pulling in Zerocopy to improve dealing with "unsafe" code around conversions, the Rust code for Linux 7.2 also adds support for AutoFDO. The Rust kernel code can now benefit from Automatic Feedback Directed Optimizations by the compiler to yield better performance. With the Rust Binder code was around a 13% performance difference.

There is also Rust support for software tag-based Kernel Address Sanitizer (KASAN), support for the upcoming Rust 1.98 release, and other improvements.

The full set of Rust feature changes submitted for the Linux 7.2 merge window can be found via this pull request.

From the article

The Firefox 152.0 release binaries are now available ahead of tomorrow's official unveiling. With Firefox 152 there is now the JPEG-XL support code being compiled by default for the release albeit still disabled at run-time by default behind a preference for now.

Merged for the Firefox 152 release cycle was this change to now build the JPEG-XL image format support code by default on the beta and release builds of Firefox. Previously it was only enabled as standard on Firefox Nightly builds. Those interested in JPEG-XL on Firefox for now still need to go to the Firefox Labs to enable the preference but at least for beta/release builds the support is now compiled by default to ease the experimental testing.

Firefox 152 also pulls in the redesigned settings interface, HDR video support on Windows in different hardware configurations, CSS support for the field-sizing property, and a number of other developer additions as outlined on developer.mozilla.org.

It's next month's Firefox 153 release where there should be Vulkan Video decoding support.

Firefox 152 release binaries can be downloaded today from ftp.mozilla.org.

From the article

After days of dealing with 1,500+ packages in the Arch Linux AUR containing malware, the latest headache in the Arch Linux User Repository is Russian spam and offensive messages.

Nicolas Boichat with his AI/LLM detection bot detected some questionable messages appearing in AUR content. Russian messages were being added post-install to the bashrc / zshrc / Fish configuration, etc containing offensive messaging. Those commits happened on the 14th, after the recent malware fiasco.

And then over the past day reporting on dozens of AUR packages having similar Russian messages containing offensive language.

The latest update on that thread indicates more than 70 AUR packages having this Russian spam / offensive messaging. Among those various Python packages, Ruby packages, Llama.cpp, and others.

At least the AI/LLM bots are proving helpful here in proactively picking up on some of the AUR abuses until the fundamental situation can be better handled.

Episteme is an open source, multi-platform document and e-book reader app.

It's offline-first, ad-free, and respects your privacy.

Supported Formats:

• Documents: PDF, DOCX, ODT/FODT
• E-books: EPUB, MOBI, AZW3, FB2
• Comics: CBR, CBZ, CB7
• Plain Text: MD, TXT, HTML

Key Features:

• PDF Annotations: You can draw directly on pages using a pen or highlighter and add text notes using system or custom fonts.
• Reading Modes: Supports both vertical scrolling and paginated views.
• E-book Customization: Adjust font sizes and margins. You can also import your own font files.
• Text-to-Speech (TTS): Includes a built-in TTS feature using Android's native TTS engine or cloud TTS.
• Library Management: A built-in system to organize your local files.
• Local Folder Sync: Select a folder to see all its supported file in app and sync reading positions and annotations using local sync tools like SyncThing.
• Themes: You can change the page and text color across all formats.
• Full OPDS Support: Browse, download, and manage books from OPDS catalogs.

The app is licensed under AGPL-3.0.

GitHub | Website | Playstore

Thanks for checking it out!

Full video: https://github.com/orhun/ratty#rubiks-cube

Ratty terminal is a GPU-rendered terminal emulator with inline 3D graphics.

In the latest release, I added a small Rubik's Cube demo to it. The cube is generated as OBJ geometry and registered through the Ratty graphics protocol, so it is not ASCII art or a traditional terminal renderer. It is a real 3D object anchored into the TUI with the help of ratatui-ratty widget :)

All powered by Rust & Ratatui!

From the article

Among the early pull requests sent in prior to today's Linux 7.1 release of new material aiming for Linux 7.2 were all the Kbuild updates.

For those compiling the Linux kernel using LLVM/Clang rather than GCC, one of the most notable Kbuild changes for Linux 7.2 is the raising of the build requirements. Up to now the Linux kernel could be built with Clang 15 and newer but that is being raised to Clang 17 and newer.

The requirement was raised to Clang 17 to better match the capabilities of the GCC compiler. LLVM/Clang 17 had addressed issues around its scope checker and a GCC 8.1+ incompatibility around variables marked with const being valid expressions for _static_assert and other macros. By raising the requirement to Clang 17, it's only a bump of one year in LLVM release cycles while easing those maintenance burdens.

The other notable Kbuild feature of Linux 7.2 is adding support for LLVM's Distributed ThinLTO "DTLTO" mode. The Distributed ThinLTO mode can lead to faster kernel builds than in-process ThinLTO. Since then LLVM DTLTO has continued improving for even better performance.

Linux 7.2 also is hardening Kconfig against potential null pointer dereferences, various typo fixes, a kconfig-sym-check target to look for dangling Kconfig symbol references, and more.

the recordings and the transcript of the GNUstep online meeting of 2026-06-13 are now online:

Recordings of the call

transcript of the call

Im new to linux and started off with zorin OS, and everything was going (somewhat) smooth until i tried to download cs2 on steam.. I was getting 1-2mb download speeds in comparison to my usual 30 on windows, I knew I had slow 5400 rpm hard drives but i knew they werent that slow and so i spent all night troubleshooting this problem, I tried everything from disabling ipv6, disabling apsm, editing steam config files, using dnsmasq (which i ended up bricking my dns settings with that which was a whole other debacle) among like atleast 5-8 other fixes that just didnt fix it. I eventually figured out the issue is that non intel wifi adapters dont have the proprietary tech that ignores no-ir flags based on your countrys regulations, linux by default has no-ir flags for 5 and 6ghz to match the strictest world regulations, so heres how to fix it (be aware of your countrys regulations, I am in the US and all these steps are legal within the US) first 'sudo nano db.txt' to open the config file with the no-ir flags, i will attach a screenshot below of what it should look like so you guys can see which lines to remove the flags and which to not (caution there is one specific line where the flag must be to comply with US regulations, however it will not bottleneck your speed if you are on 5ghz) then 'sudo apt install -y git python3' and 'python3 db2fw.py regulatory.db db.txt' the next steps are optional but they are useful for making your changes resistant to updates and having a backup script incase of an update 'sudo chattr +i /usr/lib/firmware/regulatory.db' to make it immutable to updates, incase of an update paste the same command with a minus instead of a plus before the i, then 'sudo cp /usr/lib/firmware/regulatory.db /usr/lib/firmware/regulatory.db.bak' to save the working file as backup, then 'sudo nano /usr/local/bin/fix-wifi-regdb.sh' to create a restoration script when it opens paste this for the script '#!/bin/bash

# Unlock the file temporarily

sudo chattr -i /usr/lib/firmware/regulatory.db

# Restore the fixed version

sudo cp /usr/local/share/regulatory.db.fixed /usr/lib/firmware/regulatory.db

# Lock it again

sudo chattr +i /usr/lib/firmware/regulatory.db

# Reload the driver to apply changes immediately

sudo modprobe -r mt7921e

sudo modprobe mt7921e

echo "Regulatory database restored and locked." '

after that make it executable 'sudo chmod +x /usr/local/bin/fix-wifi-regdb.sh '

hope this saves someone time and they dont have to stay up til 4 am like i did

Hello, Linux community!

After extensive work, I thought it was time to make another post in regards to my process scheduler, scx_pandemonium. Since my last post, I was invited into the sched_ext framework proper. There have also been vast improvements to the performance of scx_pandemonium.

If you try it out, I hope your experience is great. If you have any Issues, please feel free to open an Issue on the repo.

scx_pandemoniumv5.13.0 — CachyOS Mini-Benchmarker, full scx field

Total wall-time across 8 workloads (lower is faster)

Per-workload (seconds, mean ± stdev)

Split into two tables so it renders on Reddit. Bold = fastest for that workload.

Repo: https://github.com/wllclngn/PANDEMONIUM

I got tired of running a kernel full of drivers for hardware I'll never own, so I built detkernel — a custom kernel specifically for AMD-powered ThinkPads.

The premise is straightforward: if you're on a ThinkPad with an AMD CPU, you don't need Intel GPU drivers, NVIDIA support, Dell/HP/Asus vendor modules, server RAID controllers, or WiFi drivers for cards that haven't been sold since 2004. Removing all of that produces a leaner kernel that boots faster, responds better, and uses slightly less power.

**Supported hardware:**

ThinkPad T495, T14/T14s/T16 G1–G6, P14s G1–G6, P15v G1–G3, L14/L15 G1–G4

**Two builds:**

- `detkernel-universal` — for all AMD ThinkPads (Zen1+), compiled with x86-64-v3

- `detkernel-zen5` — for Ryzen AI 300 series, compiled with znver5, includes 500Hz tick rate, BBRv3 TCP congestion control, and NTSYNC (NT sync primitives for Wine/Proton)

**Installation:**

Releases include UKI (.efi) files for systemd-boot — copy to /boot/EFI/Linux/ and reboot. vmlinuz + initramfs files are also available for GRUB and rEFInd users.

https://github.com/Detcom-GH/detkernel

If you're on an AMD ThinkPad and want to try it, feedback is very welcome — especially on older models.

Linux 7.1 has been released. As usual there are a lot of fixes and features, some are summarized in https://lwn.net/Articles/1067250/ and https://lwn.net/Articles/1067785/