Linux

12320 readers

377 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

KaOS Linux Drops KDE Plasma After 12 Years for Niri/Noctalia to Escape systemd (9to5linux.com)

submitted 1 day ago by cm0002@mander.xyz to c/linux@programming.dev

17 comments fedilink hide all child comments

KaOS Linux 2026.02 was released today as the February 2026 ISO snapshot for this independent GNU/Linux distribution, which uses Arch Linux’s pacman package manager, and the first release to ship with the Niri Wayland compositor.

After using the KDE/Plasma desktop environment by default for more than 12 years since its initial release under the name of KdeOS, the KaOS Linux distribution will no longer ship with its unique Plasma desktop setup, as the devs do not want to use the systemd init system anymore in the distro.

Instead, they put a Niri/Noctalia setup into the KaOS Linux 2026.02 release, while retaining the distribution’s unique look and still offering users access to popular KDE applications that were shipped with the Plasma desktop. However, this release still ships with systemd as the default init system.

you are viewing a single comment's thread
view the rest of the comments

[–] epik_kiwi@piefed.blahaj.zone 5 points 1 day ago (1 children)

Why is running in pid1 an issue?

[–] Neptr@lemmy.blahaj.zone 14 points 1 day ago

Compromising/crashing pid1 (which becomes increasing likely when the program is massive) takes down the entire system. pid1 should only be the initial init (which should be as small as possible, basically a stub) and start the service manager as a separate pid. This allows the system to gracefully recover by restarting other processes without fully locking-up/crashing. It is a bad practice.