undefined | Better HN

0 pointszozbot2343y ago0 comments

But it's not Poettering, it's the Gnome folks in general. These controversies have been around since the early Gnome 2.x days. Nothing much has changed.

What we really need is for people to propose alternatives to systemD that address its purported use cases while removing some of the needless complexity it introduces, and restoring the primacy of general mechanisms over hacked-together policy. This has happened with some components, e.g. elogind but not really as a comprehensive effort.

0 comments

_ofdw3y ago

>But it's not Poettering, it's the Gnome folks in general.

It might also be the Gnome folks but it's definitely also Poettering. Let's not pretend he's some blameless martyr. The guy's a jerk.

traverseda3y ago

OpenRC and alpine are nice.

corrral3y ago

OpenRC is the only Linux init I've used that I actually enjoyed using, not just could-tolerate.

hakfoo3y ago

What was wrong with Slackware's bag full of shell scripts?

Maybe I'm misunderstanding what people want an init system for, but I'd expect to need little more than "run these 10 tasks. Potentially, wait for A to finish before starting B". Its job should be over when you see the login prompt.

It feels like modern inits are more like a watchdog/messaging system-- which seems like something which would be an optional add-in atop a real init system.

I want to run a custom utility at power on. It's not a weird expectation. This should take no more than one line of code to achieve, adding "/usr/local/bin/toolname &" to some sort of rc.local file.

0des3y ago

sysvinit did nothing wrong.

nathants3y ago

this is the way.

j / k navigate · click thread line to collapse