loaExMachina@sh.itjust.works to linuxmemes@lemmy.world · 9 months agoSystemd controversy be likesh.itjust.worksimagemessage-square117fedilinkarrow-up1494arrow-down118
arrow-up1476arrow-down1imageSystemd controversy be likesh.itjust.worksloaExMachina@sh.itjust.works to linuxmemes@lemmy.world · 9 months agomessage-square117fedilink
minus-squareAatube@kbin.melroy.orglinkfedilinkarrow-up11·edit-29 months agobootload, 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)
minus-squarewildbus8979@sh.itjust.workslinkfedilinkarrow-up7·9 months agoYou forgot manage containers, manage system timers, manage network interfaces (in some cases)…
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up6·edit-29 months agoDNS 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.
minus-squareAatube@kbin.melroy.orglinkfedilinkarrow-up1arrow-down1·9 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
minus-squareSuperIce@lemmy.worldlinkfedilinkEnglisharrow-up8·9 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.
minus-squarewildbus8979@sh.itjust.workslinkfedilinkarrow-up3·9 months agoYou’re right about the first two, but as someone pointed out already, wrong about the last. Also see machinectl
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)
You forgot manage containers, manage system timers, manage network interfaces (in some cases)…
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.
I said “manage the network interface” and “schedule stuff”
That requires podman or some other program, so that’s like saying shell does container management
No,
systemd-nspawndoesn’t need any other container management program, it’s its own thing.You’re right about the first two, but as someone pointed out already, wrong about the last.
Also see
machinectl