• TheInsane42@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    5
    ·
    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.

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

      Wouldn’t you just set “networking” as a dependency on the unit of whatever you need started after?

      • TheInsane42@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        That’s what you would do with the init scripts, as that environment waits until the previous one is finished. (ie you know you have working network) Systemd is in a hurry and there ‘after’ seems to mean ‘not before’ instead of ‘after <specified> is finished’, so after networking is started it advances to the next in line.

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

        I love how fucking lennaert subtly changed that. Who cares that it complicates classic tools.