You try to link my small error on a 'ls' option to the QI of the systemd-proponents. If you think this is not unrelated I let you prove the relation to all the systemd-proponents. :-D

Contrary to you claim, I have nothing against peoples that prefer to use sysvinit over systemd. It there are happy with it, them there simply must take care of it themselves, because I am afraid for them that most of the maintainers of the leading distributions will probably not support system V init in the long term.

Now you can ignore systemd if you are just happy with system V init, or you can try to improve systemd if you think that you can propose a better architecture. But trying to keep everyone using system V init is not a acceptable position for too many peoples.

I know nothing about Powershell, but want I can say is that systemd uses declarative unit configuration files to get the information on how it must manage a service. Given how the systemd binary work, I fail to see how you can compare it to a shell.

Ok, you have see it and I did not notice. Happy ?

It just delicious how you can link completely unrelated things trying to prove your point. That certainly would explain a lot of your inability to show real facts about how systemd architecture should be improved.

I have no problem (serious enough) with systemd, you claim that systemd have problem regarding UNIX philosophy rules, and I still waiting the various reasons you have to think that way so.

I have read some parts of the systemd source code, and you? Why do you refuse to give any of your various reason why you disagree on the systemd architecture?

I have read this document more than ten years ago.
Now, please show the "various reasons" why you disagree.

Hint: http://interviews.slashdot.org... (read the answer about systemd).

You did no explain anything at all about your reasons to disagree! Stop trying to escape the discussion. You have claimed that you have various reasons to disagree that Systemd is in line with the UNIX philosophy. I still waiting a list of your reasons.

I should have to used 'login" instead of "logind", sorry.

systemd-logind can replace the traditional login, but it uses the systemd infrastructure to do his job, what's a surprise.

It's simply because there choose to store the code of multiple applications in the same repository. There is already a lot of projects that do the same since a long time.

Then show to us what's we don't want to see, and explain what UNIX philosophy systemd breaks.

I don't give any credit to your conspiracy theory. Yes systemd is now a dominant component of the last distributions, like udev, dbus, xorg, NetowrkManager when there was introduced into the distributions at there time. This don't make them evil projects with the goal of controlling the ecosystem. An other example is git that have largely take over the others SCM in the open source community, do this make it an evil project that control an ecosystem? From the reactions I read, even get the feeling that it's just a few systemvinit fans that try to control the Linux evolution to keep them in the past forever.

Yes systemd is designed to make the maintainers work easier, your analysis is correct. Now what's broken for the users of systemd?

I don't comment on the RH support, as I only use Debian distribution or derived from Debian.

Without investigating the problem in detail, how can you be certain that systemd is the fundamental cause of your problem ? You hate it, ok, but this is not enough to make is the real cause of your problem, especially on Fedora that uses systemd since now, full 4 years. Searching on the internet, most of the USB mouse hang problem seem to be related to the kernel/udev management of the device suspend. Did you a least report the problem to the Fedora community?

I also pretend to have enough experience to very well know almost all this points. I am perfectly ready to listen at your explanations why the actual systemd architecture break any of this rules.

So it's your turn now.

The systemd project have different parts:

The systemd binary itself is essentially to replace the init scripts by service files.

The systemd-* binaries are applications that can replace some traditional applications by using libsystemd instead of using others librairies. There are all optional.

Among those systemd-* binaries there is a bunch of them specifically designed to provides minimal basic services on tiny diskless machines without /etc. There are completely optional and normally not activated on a normal distribution.

Try a Debian Jessie of a Ubuntu 15.04, you will see very few systemd-* binaries running:
systemd-journald
systemd-udevd
systemd-logind
That's all.

Agree that systemd did not make a server boot in a significant better way (I doubts that it degrade it either). But systemd on a server add some cool features to manage all the services in a standard way and to introspect into the details of how there run.

Agree that journald need a bit more care, this is a known issue.

Tell us more what the real cause of your mouse problem, because from what you wrote, this is more likely to have something related to udev.

And "systemctl start foo bar" will start the 2 services foo and bar in a single command. There just require the related service files (instead of scripts) and systemd (instead of a shell).

Good luck to write a single init scripts that are directly usable on many distributions for a service that depend on multiples others services to run properly. Can you provides a like to one of them please?

Yes inittab can be configured to make sysvinit starting almost anything, I used this many time on embedded systems. I see two bigs problems with inittab:

1) From the maintainer point of view, it's not practicable to have any package adding or removing his rules directly into the file. The sysv-rc idea was a way to solve this problem.

2) There is no dependencies between services. This problem is still not well enough addressed in sysv-rc, but sysemd is specifically designed to take care of the dependencies between services.

I don't see the dependency on systemd so much a problem. Try to purge udev or dbus to see what happens for example.