• jg1i@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    “a popular init system”? It’s the main init system now. Look at it. Systemd is the captain now.

    You’ll have to learn it if you use any mainstream distro. Like at work. It is inevitable.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Yes, that’s what ‘popular’ becomes.

      Note that it’s often labeled as ‘popular’ and not ‘good’.

      I’m sick of redhat’s internal junk. It’s just to sell courses anyway.

  • chronicledmonocle@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    I knew a Arch guy who called it Sys-dumb-d. He refused to run systemd.

    I could mostly care less. It’s…fine. I miss upstart and it’s simplicity. Kind of wish it had been actually developed to maturity, but here we are with an init system that also wants to do DNS.

    • ozymandias117@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      You need to use its init system (systemd), its logging system (systemd-journald, and can be forwarded to old school syslog), and some dbus implementation.

      If that’s an unreasonable requirement for your usecase, check out OpenRC

      • SuperIce@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It’s a system daemon that manages way more than an init system, hence the name “systemd”.

  • TheInsane42@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    2
    ·
    1 year ago

    It’s never been popular by anybody except RedHat, that’s how they sell courses end certifications.

    Still haven’t found a way to start something after networking has finished when it takes a bit to set everything up. (and no, not going to limit vlans, tunnels,…)

    It’s a technical ‘solution’ for a marketing problem.