• greyscale@lemmy.grey.ooo
    link
    fedilink
    English
    arrow-up
    12
    ·
    19 hours ago

    ok so tell me why I’m waiting for networking to come up before I’m allowed to interact with my computer

    Also, its monolithic as heck, its a giant squid into my networking, time management, access control…

    Ontop of that… binary logs ew.

    • Natanox@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      ok so tell me why I’m waiting for networking to come up before I’m allowed to interact with my computer

      Because your distro sets up stuff weirdly? At least I never noticed networkd to be a dependency of multi-user.target, could be wrong though.

      Also, its monolithic as heck, its a giant squid into my networking, time management, access control…

      That’s all optional though, many distros just use it because it’s easier than the alternatives.

      Ontop of that… binary logs ew.

      Yeah, that’s indeed stupid. No clue why they did that.

    • insufferableninja@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      9 hours ago

      Pervasive, yes. Deeply embedded in the distros that uses it, absolutely. And I get why people don’t like binary logs, although that isn’t exactly relevant to monolithic vs pluggable.

      You seem to think that I’m arguing against your opinion that systemd is bad. I’m not. I’m arguing against the false statement that it is monolithic. It isn’t. It’s modular, like the linux kernel. If you wanted to remove every component except the init system, you could. Big pain in the ass to do that, but you could.