3 ms·
It seems like the biggest reason is "KDE and GNOME need systemd, so we need systemd". In other words, systemd is winning because systemd is winning. Not becaus
by palata 3y ago
It seems like the biggest reason is "KDE and GNOME need systemd, so we need systemd".
In other words, systemd is winning because systemd is winning. Not because it's better.
- MartijnBraam 3y agoExactly, this is straight up pressure from GNOME to get systemd everywhere.
- generalizations 3y agoEh, I'd say it's more likely pressure from RedHat. They benefit hugely from a complex ecosystem that creates demand for their consulting business.
- johnny22 3y agoconsidering gnome runs on freebsd, that's just not true. The only work those folks had to put in was implementing one interface for what logind provides
- NewJazz 3y agoIs gnome feature complete on freebsd? The article mentions gnome clocks wants to use timer units in the future, and gnome-session logs to journald.
- johnny22 3y agoAs far as i know it is. As far as what's in the future no idea. I'm only speaking of the present.
- sleirsgoevy 3y agoNot really, it's garbage to the point that it only runs the X11 session, mutter can't even be compiled with Wayland support because it then tries to include some Linux-only header.
- jeppesen-io 3y agoWhat fancy new features will we get with systemd? Granular privilege controls Powerful service dependency and security analysis features Tight cgroups integration both static and dynamic Socket activation (so you can print from your phone without having CUPS running all the time!) Built in boot-time analysis also What's wrong with the polyfills? ... corecollector (systemd-coredumpd) 1: Not needed to run KDE and GNOME, but a very useful tool that many developers expect to be able to use to easily retrieve coredumps and associated metadata, without first figuring out how to configure them properly. It is great that there is a polyfill for it, but it is unmaintained since 2020. Plasma Mobile developer Devin wrote: "When debugging crashes, it’s incredibly useful to be able to view coredumps and attach a debugger after the fact with coredumpctl, this can help us obtain backtraces that would otherwise be hard to replicate again with a debugger attached. We can also then enable DrKonqi’s coredumpd integration, which can allow users to get notifications about process crashes and see them from a GUI. DrKonqi also has optional integration with our Sentry instance, which we can enable on developer installs to automatically send crashes to a web dashboard for us."
- colinsane 3y ago- Granular privilege controls - Tight cgroups integration both static and dynamic highlighting these in particular because of notable regressions in the systemd 254 -> 255 release. i think there's the perception that "systemd features are so easy to use" so therefore "systemd must be equally easy to maintain". it's not. my advice to pmOS maintainers is to experience at least one systemd upgrade cycle before committing to it in any meaningful sense. that said, if the project has the bandwidth to maintain all of these different service managers/init systems, then yeah absolutely go for it.
- NewJazz 3y agoSame as ten years ago.