Systemd 256-rc1 Brings A Huge Number Of New Features

[cutterjohn]

when is systemd {insert old fashioned distro name} version XYZ coming out?

wow '< >' brackets breaks this crap forum sw? hence curly brackets, using angle brackets resulted in an error... someone file a bug report...

[jacob]

Patches welcome. Also, it's not like you could do that with muh plain text logs either.

Thinking about it, this shouldn't be difficult to implement. AFAIK systemd knows when exactly the service was started, so it's simply a matter of setting that as the cutoff time when extracting the log entries. It might create an interaction between journalctl and systemd-pid1 because the former would need to query the latter about the start times but maybe these two already interact anyway, that I don't know.

[jacob]

when is systemd {insert old fashioned distro name} version XYZ coming out?

wow '< >' brackets breaks this crap forum sw? hence curly brackets, using angle brackets resulted in an error... someone file a bug report...

What to you mean? All distros have already switched to systemd except those who have a explicit policy of not using systemd (like devuan, gentoo etc). OK, maybe Slackware is one distro that doesn't have systemd without being specifically anti-systemd, but Volkerding's (very sensible) approach is not to do any disruptive changes since he's building and maintaining the whole distro alone.

[pong]

Not sure what you need the rest of an operating system for anymore. Just tack on a systemd web browser and you are all set.

It's just reinventing the wheel of what features emacs already implemented (somewhere in there) 30+ years before hand.

[duby229]

There seems to be an alternative history of Linux you have conjured for yourself. Please elucidate. Other than that, Gentoo is a nice hobbyist engineering project. I’m glad it’s around. However, compared to just the installs worldwide from IoT to hyper scalers of Red Hat, Suse and Ubuntu alone, Gentoo is a tiny minority. It’s great from an engineering test bed of making optimized and if need be compact builds, but that’s all it’s ever going to be. If it suits your particular compute needs, party on Garth. I’m glad to see that the stupid and unproductive fragmentation that has cursed Linux from the jump is slowly coming to an end at least in terms of frameworks and protocols such as systemd, Pipewire, Vulkan, Wayland. Unfortunately we still have stupid and unproductive fragmentation concerning containerized apps with three, Snaps, Flatpak, and Appimage, and DEs such as KDE and Gnome. Hopefully within a decade IBM will have a confab with Canonical and devise a “best of” unified container scheme combining the best of Flatpak and Snaps. My God, there were at least 4 memory interconnect schemes at one time, Intel CXL, HP Gen-Z, ARM CCIX and IBMs CAPI. Yet they all got together and open sourced their protocols and gave it all to one org. It’s still called CXL but CXL will cover everything that each protocol was originally focusing on. Linux World particularly Corporate Linux World needs to pull their heads out of their asses and do the same. It is beyond stupid and unproductive to have DEBS and RPMs and Flatpaks and Snaps and Appimage. There is one container protocol for Window apps. There’s one for Apple apps. But NOoooo, stupid Linux has 5 ways to package an effing app and that’s not including hobbyist projects like Gentoo. Fortunately the corporate world and the hyper scalers are going to weed this shit out. Everything is being containerized. And right now Canonical Snaps are preferred in this world. Flatpaks might have captured more of the personal Linux user and the anti-Snap zeitgeist, however Microsoft won the PC war vs Apple by making the same experience available to the home user as the corporate user. The same will happen in 5-10 years in Linux. My bet is on Snaps. But it will be better if IBM comes in good faith to Canonical as say “Let’s unify our two containerized app schemes for the betterment of both of us and the larger Linux world.”

Yeah and that tiny minority saved YOUR ass dude.. Whether you recognize it or not.

Hypocrite, right there...

[ahrs]

Maybe, but don't we have cgroup v2 since 2014 -- maybe 2016 at latest?

Even on my non-Systemd, OpenRC using Gentoo system I've long since moved on from CGroup-v1 and /sys/fs/cgroup is mounted as cgroup2 and not in a hybrid configuration.

Most stuff ported over ages ago, with the last real holdout being Docker which did move eventually too after Debian and other distros more or less forced their hands (now do NFTables support, please).

[Jumbotron]

Yeah and that tiny minority saved YOUR ass dude.. Whether you recognize it or not.

Hypocrite, right there...

Still talking out of your ass unless you specifically detail how Gentoo “saved us all”. LOL…

[Blademasterz]

SystemdOS is real boiiis 😂

[Magissia]

Actually, for maximum fun systemd should integrate a wayland compositor

Honestly I'm all up for it. It would help getting a standard compositor quick.

Maybe it could include hyprland?

[Magissia]

"Support for cgroup v1 is now considered obsolete and systemd by default will refuse to boot under it."

This sounds inconvenient.

What is the use case for old cgroups with very recent systemd?