So,

I’ve never bothered with this before, since systemD seems to work just fine.

But I did this year stop using Ubuntu for most of my hosting needs and moved to Alpine or Debian, depending on what I’m doing.

So it makes sense to optimize even more. I read up a little about why people dislike systemD. Good reasons if mainly you’re worried that it’s doing too much and is too heavy.

So what are the alternatives that work with both Alpine and Debian? What are people using? Is it relatively easy to move from systemD to whatever is your alternative?

Thanks!

  • bacon_pdp@lemmy.worldEnglish
    1·
    11 hours ago

    Well futex based high performance mutex support which is 400x faster than what existed back when 4MB systems were sold. A Constraint solver that doesn’t deadlock, support for a boatload of functionality that didn’t even exist back then.

    And most of the size comes from -O3 compiler optimizations that didn’t exist back then and if you build with -Os it is about 512KB of a memory footprint which is smaller than SysV out of the box on Debian. So it is snappy on a 386SX with 4MB of RAM if you go the gentoo route.

    People use SystemD because it works better than what came before it and it will be replaced when something actually better shows up. No one happens to have found a generally better solution yet.

    OpenRC, Gnu Shepherd, runit and S6 are available for people who like them better but don’t assume that they are generally better for someone else’s use cases until you know what they are.