• Aatube
    link
    fedilink
    11
    edit-2
    7 months ago

    bootload, manage devices, manage the network interface, manage accounts, log in, provide a host for temp files, schedule stuff, log events

    All of this is background stuff to me so I don’t care

    (n.b.: systemd also suffers from a linux kernel vs linux situation. systemd has a component named systemd that only does services stuff)

    • @[email protected]
      link
      fedilink
      77 months ago

      You forgot manage containers, manage system timers, manage network interfaces (in some cases)…

      • @marcos
        link
        6
        edit-2
        7 months ago

        DNS resolution, clock synchronization, there’s something about keyboard configuration but it stopped to make me problems for no reason so I don’t know what exactly…

        Oh, and IPC so that Gnome can not be done until other inits won’t run!

        But there are a lot of other modules.

      • Aatube
        link
        fedilink
        07 months ago

        manage system timers, manage network interfaces

        I said “manage the network interface” and “schedule stuff”

        manage containers

        That requires podman or some other program, so that’s like saying shell does container management

        • @SuperIce
          link
          English
          87 months ago

          That requires podman or some other program.

          No, systemd-nspawn doesn’t need any other container management program, it’s its own thing.

        • @[email protected]
          link
          fedilink
          37 months ago

          You’re right about the first two, but as someone pointed out already, wrong about the last.

          Also see machinectl

    • @thantik
      link
      English
      57 months ago

      I believe you mean GNU/SystemD/Linux…