![](https://midwest.social/pictrs/image/c3ec3360-e8b2-43cf-9d7c-cc6b87c2f98b.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Their complaint was that people bitch about systemd. The issue people have is that systemd does too much.
Born a sconie right on Lake Michigan, lived in Iowa for a handleful of years for college, then moved to Sota where I live currently. Software Engineer for 20+ years, Ham Radio Operator, lover of retro graming, old time radio and the outdoors.
Mastodon: jecxjo@mastodon.sdf.org
Their complaint was that people bitch about systemd. The issue people have is that systemd does too much.
And systemd is far more resources intensive than runit. Wasn’t really the point.
Kind of nice to not have a bug in my container service possibly have access to pid 1.
Personally I’d like my container/vm/chroot handled by something detached from pid 1. I get that much of the overal systemd project is separate blocks of code but it’s the fact they are bound together that it becomes an issue. I would have loved for the systemd team yo first publish a set of APIs that all their components would us and allow the same integration while being completely different projects.
That is pretty cool.
But its also another example of systemd doing stuff other services already did (see lxc).
Soon systemd will include a feature where it replaces the user and does all the computing for you.
The name Debian comes from the original creator, Ian Murdock, and his wife Debra.
Sure but that’s always going to be sub par experience.
Red Hat brought us systemd…
Not only can you make your own OS but you can use one of the package managers and build your own repo and do a whole ecosystem yourself.
I used LFS to build a distro for embedded systems I designed at work. Was a fun experience but way too much work.
The issue is a lack of an app ecosystem with actual AAA apps.
That would be true if other systems and services depend on them. Would have been nice to come out with a standard and designed systemd around that standard. Then you pick the tool you want that follows the standard rather than be tied into systemd.
I would disagree. A compromised Docker doesn’t mean i have access to things managed by PID1. The entire control model is based around moving your publicly available services further away from something with the highest level of access. Be it users or processes.