On 17/12/11 17:41, Bernhard M. Wiedemann wrote:
yes most of those are bugs elsewhere..
As I understood it, native unit files are not needed for the goal of fully switching to systemd and dropping sysvinit - so this step (and all other steps about /etc/init.d/ replacement) should be optional.
no, there should not be optional, as does solve the problem of supporting two different ways to do things.
Add documentation, HowTos etc. for developers and users of systemd and its service files so that they can tweak and extend their system as easily as with sysvinit. This might be inherently hard, because some things that used to be in easily changeable /etc/init.d/boot.* scripts were hardcoded into systemd's C code.
There is more documentation, than the old system ever had, including full grown how-tos to convert both units and daemons, example c code, libraries, tools, whatever..
This step will ideally still be some years ahead,
it cannot be some years ahead, we cannot support two systems for large periods of time, with the current amount of developer power is imho, completely out of the question.
so that as many use-cases as possible will be known to work with systemd.
your sugestion will actually delay those cases being known.
People don't
like being forced into something that does not work properly.
It works, it has bugs like any software, and people complain for everything either if it works or not, without having any idea where the problem is.
If they dont like it, they are free to find another distribution that does not "force" you to use it, that currently reduces to debian, gentoo, an a few other players. (ubuntu has upstart, mandriva,fedora, have systemd..etc)