❌

Normal view

There are new articles available, click to refresh the page.
Yesterday β€” 19 September 2024Main stream

Real-time Linux is officially part of the kernel after decades of debate

19 September 2024 at 20:14
CNC laser skipping across a metal surface, leaving light trails in long exposure.

Enlarge / Cutting metal with lasers is hard, but even harder when you don't know the worst-case timings of your code. (credit: Getty Images)

As is so often the case, a notable change in an upcoming Linux kernel is both historic and no big deal.

If you wanted to use "Real-Time Linux" for your audio gear, your industrial welding laser, or your Mars rover, you have had that option for a long time (presuming you didn't want to use QNX or other alternatives). Universities started making their own real-time kernels in the late 1990s. A patch set, PREEMPT_RT, has existed since at least 2005. And some aspects of the real-time work, like NO_HZ, were long ago moved into the mainline kernel, enabling its use in data centers, cloud computing, or anything with a lot of CPUs.

But officialness still matters, and in the 6.12 kernel, PREEMPT_RT will likely be merged into the mainline. As noted by Steven Vaughan-Nichols at ZDNet, the final sign-off by Linus Torvalds occurred while he was attending Open Source Summit Europe. Torvalds wrote the original code for printk, a debugging tool that can pinpoint exact moments where a process crashes, but also introduces latency that runs counter to real-time computing. The Phoronix blog has tracked the progress of PREEMPT_RT into the kernel, along with the printk changes that allowed for threaded/atomic console support crucial to real-time mainlining.

Read 3 remaining paragraphs | Comments

Before yesterdayMain stream

Neofetch is over, but many screenshot system info tools stand ready

13 September 2024 at 17:18
Four terminal windows open to different system information fetching tools

Enlarge / Sorry about all the black space in the lower-right corner. Nerdfetch does not make good use of the space it's givenβ€”unlike the Asahi install on this MacBook. (credit: Kevin Purdy)

Almost nobody truly needed Neofetch, but the people who did use it? They really liked it.

Neofetch, run from a terminal, displayed key system information alongside an ASCII-art image of the operating system or distribution running on that system. You knew most of this data, but if you're taking a screenshot of your system, it looked cool and conveyed a lot of data in a small space. "The overall purpose of Neofetch is to be used in screen-shots of your system," wrote Neofetch's creator, Dylan Araps, on its Github repository. "Neofetch shows the information other people want to see."

Neofetch did that, providing cool screenshots and proof-of-life images across nearly 150 OS versions until late April. The last update to the tool was made three years before that, and Araps' Github profile now contains a rather succinct coda: "Have taken up farming." Araps joins "going to a commune in Vermont" and "I now make furniture out of wood" in the pantheon of programmers who do not just leave the field, but flee into another realm entirely.

Read 5 remaining paragraphs | Comments

❌
❌