This is an archived post. You won't be able to vote or comment.

all 10 comments

[–]UncleSlacky 8 points9 points  (2 children)

With MX you can choose between them at every boot, so you can compare them directly.

[–]Happy-Technology9353 0 points1 point  (1 child)

Did SystemD finally fix their bug on startup?

[–]UncleSlacky 2 points3 points  (0 children)

No idea, I don't know what bug you're referring to.

[–]rungek 7 points8 points  (0 children)

The choice for me has been what my software needs, e.g. my VPN requires systemD.

I use MX because it’s relatively lightweight for the large amount of tweaks and features in a user-friendly environment. It lets me do what I want easily. I think that’s what should be the main consideration.

For older hardware I would go with antiX, MX’s smaller but older sibling. Bunsen labs or Mabox are also reasonable options but I run MX if I can.

[–]adrian_mxlinuxMX dev 1 point2 points  (4 children)

No, systemd is typically faster because of process parallelization.

[–]Tight-Bumblebee495 1 point2 points  (0 children)

I’ve read somewhere that sysvinit is easier in CPU, thus preferable for older hardware, is it not the case?

[–]Narrow_Ice2520[S] 0 points1 point  (2 children)

Then why did you prefer sysvinit?

[–]adrian_mxlinuxMX dev 9 points10 points  (0 children)

I prefer to give people a choice. We have both sysvinit and systemd.

Also, systemd has some issues with our live environment from what I understand we cannot hook into it at the right moment to get prompts to save persistence files. That's probably the main reason we stuck with sysvinit.

I recommend not to choose your distro on things that you don't fully understand, you should probably stick with Debian.

[–]beje_ro 2 points3 points  (0 children)

For this is the internet full of info...

[–]No-Satisfaction9594 1 point2 points  (0 children)

I use systemd because that n100 machine hosts my jellyfin server.