ai newsDo., 15. Okt.
EilmeldungMeta and Apple team up to make Muse AI models run better on Macs

Rolling Releases werden fuer Linux durch das Tempo der KI-Entwicklung zum Standard

Weil KI die Entwicklungsgeschwindigkeit stark erhöht, kommen klassische Release-Zyklen kaum noch hinterher. Rolling-Release-Distributionen koennen neue Aenderungen deutlich schneller ausliefern.

ZDNetMittwoch 04:00 · 14.10.DE4 Min. Lesezeit
Bild: ZDNet

Tech > Services & Software > Operating Systems > Linux

With the speed of AI pushing the limits of development, only these releases will keep up.

Read full bio October 13, 2026, 10:00 pm ET

Jack Wallen/ZDNET ZDNET’s key takeaways AI increases the speed at which vulnerabilities are found. Linux typically patches vulnerabilities very quickly. There are, however, bottlenecks with standard releases. Linus Torvalds, the creator of Linux, recently used Claude Code to develop new features for the Linux kernel. This came after he made it clear that he uses AI to “ do the things I’m bad at.” He went on to call vibe coding a “wonderful way to find joy in programming.”

Also: My 5 favorite Linux distros for AI – and why

Specifically, Torvalds’ Oct. 10 commit stated, “The code, the test programs, the review behind the list above, and the first draft of this text were done with an LLM coding assistant (Claude Code) under my direction. The measurements were run on my machine.”

Let’s add to that new reality the fact that AI is finding bugs and vulnerabilities within the Linux kernel at an unprecedented pace. Now, layer on the fact that Linux (and open-source) tends to patch vulnerabilities much faster than proprietary projects, and you can see where this might lead: faster vulnerability discovery → faster patching.

The problem: AI will certainly discover bugs and vulnerabilities far faster than human developers can patch them. That’s no slight on human developers. Humans are the heart and soul of development, and that’s not going to change any time soon.

Also: Linus Torvalds on why AI works for him

What it could change, however, is the future of Linux distributions.

Essentially, there are two types of Linux distributions: Standard releases and rolling releases. Standard release distributions are fairly straightforward: they follow a set release schedule (biannual or annual, for example). Take, for instance, Ubuntu, which releases twice a year; the.04 release comes out in April, and the.10 release is available in October. Similarly, Fedora releases a new major version every six months. Debian, on the other hand, releases a new major version every two years.

Also: The 5 best rolling release Linux distros

Now, imagine that Linux development happens at the speed of AI. How will regular release distributions keep up?

A rolling release distribution is quite different, as it doesn’t have major versions. Instead, a rolling release distro offers continuous updates. As soon as upstream developers release an update, the apps, desktops, and kernels associated with a rolling release are individually updated. Unlike traditional distributions, where you upgrade from one release to another, you install a rolling release once, and that’s it. The software within a rolling release is continually updated, so everything is always up to date.

Also: Why I’m a serial Linux distro hopper

Examples of rolling release distributions include Arch, Manjaro, EndeavourOS, openSUSE Tumbleweed, and Gentoo.

This is where things get a bit tricky. You might assume that a standard release distribution only updates software during its release cycle, but that’s not the case. When a vulnerability is discovered, it’s fixed, and the patch is released, and it doesn’t matter whether your distro is a standard or a rolling release — you’ll get the update.

So, I’m not saying that standard release distributions won’t update software when vulnerabilities are found. But what happens when the rate of discovered vulnerabilities increases (which it will)? Will standard release distributions be able to keep up?

Also: 5 reasons why Linux is the future of desktop computing

Here’s why I believe rolling release distributions are better poised to meet the demands that AI will place on vulnerability patch updates:

As AI continues to ramp up the speed at which vulnerabilities are found and patched, backporting is going to become a major problem.

Let’s take Ubuntu, for instance. Canonical is about to release Ubuntu 26.10, which is a short-term release. Currently, Canonical is supporting (via extended security maintenance) the following releases: 26.04, 24.04, 22.04, 20.04, and 18.04. In other words, when AI finds a vulnerability, the patch for it must be backported all the way to 18.04.

Also: OpenSUSE Tumbleweed makes a great case for rolling release distros

On the other hand, Arch Linux only has to support one release — because it’s rolling. There’s no backporting to previous iterations. That equates to much more efficient vulnerability patching.

AI isn’t going away, and given that the creator of Linux has adopted the technology, it’s safe to say the future of Linux development is directly tied to it. Rolling release distributions have a clear advantage over standard release distros.

Originaltitel: Why the future of Linux is rolling – thanks to AIQuelle: ZDNet (ZDNet). Original öffnen