• 27 Posts
  • 272 Comments
Joined 3 years ago
cake
Cake day: June 26th, 2023

help-circle

















  • Zucca@sopuli.xyztoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    6 months ago

    Because systemd replaced too many important components users still wanted to keep using… and politics. Not many people like Lennart (the guy who started the project). Politics ruin everything.

    For me the breaking point was systemd-journald. Corrupted journal when you desperatedly needed to know what went wrong was too much. Last time I gave systemd a try was several years ago… Something like 5 to 7 years, so things might have changed a lot.

    Also I’m in the minority here. I like to custom my system components too. systemd just doesn’t fit there. Also I administrate one lightweight, low power box, which uses musl libc. Last time I checked systemd needed glibc.

    Enough ramblings. Here’s some reading for you… note that there’s most probably very biased technical writings here and there, so use common sense and verify the claims if you want the real truth. Then judge yourself, don’t let anyone else judge for you.




  • Zucca@sopuli.xyztoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    23
    ·
    6 months ago

    I wonder what new does this bring into the table?

    I mean we already have at least these in addition to systemd:

    • OpenRC + openrc-init
    • s6 + s6-rc
    • runit
    • Epoch
    • dinit
    • minit
    • GNU Shepherd
    • finit

    The state being stored in RAM seems like a nifty feature. I like it.

    Very quickly glanced… I think it lacks service supervision and user services. Although user services are missing in many others too. Except it looks like users can run Nitro by themselves (autostart via cron @boot maybe?). Somebody correct me if I’m wrong.

    Anyway, more choices leads to more ideas being implemented. 👍