simulating systemD? [Solved]

[Pretty Vacant]

Plain jane: if you don't like it, move on...

who are you adressing to?

[Eadwine Rose]

You'd deduct I address the same person as the commenter above me. But more in general.

[Pretty Vacant]

What app is it?

Obvious question, very much connected to systemD. But opened a new topic about that: viewtopic.php?t=83777

[Eadwine Rose]

When your question here is answered, which looks like, please mark it solved.

[dreamer]

Maybe too many metaphors in my last post, but my thinking went along these lines:

MX Linux has great hardware support (kernel, firmware and dkms packages). We can check that checkbox.

Mint seems to have more trouble with hardware support because they rely on Debian/Ubuntu for this.

Mint tends to work if hardware is supported. They use systemd and probably 80 % use Cinnamon. I think there are few unknowns here. They can check that checkbox.

So, my conclusion was that no matter how much work the MX devs put into the SysVinit side of MX Linux, it will never work as well as the systemd side (excluding live functionality). Debian is a systemd distro and it can show in subtle ways.

But, SysVinit is the default and people come here with expectations that it will work just as well as the systemd side. They have these expectations because SysVinit is the default. The gap between SysVinit and systemd will grow wider as years go by. No "third party" devs test with SysVinit. And I think the real problem is that most problems are much more subtle than this or that app won't start.

Now, having SysVinit as default in 2025 is actually a great thing. Unix philosophy for the win and I really mean that. However, it is Debian. It is year 2025. If someone has a software related problem the first question that comes to my mind: Does it work if you boot with systemd?

Next logical step... If systemd was default that question would be unnecessary.

You might think this is a bad idea. I also think it is a bad idea... But I also think it is a good idea if "just works" is a goal.

So the idea wasn't to get rid of SysVinit. The idea was to make systemd default. Ideas can be good or bad, but they are just ideas.

This idea was basically born out of laziness. I don't want to ask people to try with systemd first. It feels repetitive. Maybe I'm too lazy for a dual init system. It could be...

[DukeComposed]

Now, having SysVinit as default in 2025 is actually a great thing.

Agreed.

However, it is Debian.

Disagreed. It is not Debian. It is MX. If the difference between them is too fine a point for you to see, you can always switch to Debian. I hear you can even install sysvinit on it these days.