Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.
On Thu, Jan 30, 2014 at 06:47:02PM +0100, Josselin Mouette wrote:
> Le jeudi 30 janvier 2014 à 21:38 +0400, Sergey B Kirpichev a écrit :
> > [Lots of crap]
Nice argumentation, as usual...
> > Where is the list of problems for sysvinit we intend to solve?
>
> https://wiki.debian.org/Debate/initsystem/systemd#sysvinit_.2B-_insserv
* Sysvinit/insserv has very little C code, but the real code size must
take shell scripts into account. These scripts come in huge numbers,
contain bugs and are hard to maintain.
- I don't see that this is a big problem. C is a low-level
language and it's a good idea to implement some logic on
a high-level scripting language.
* Debugging an init script is a tedious task. [...]
- Usually it's as simple as to add set +x
* Sysvinit is insufficient for desktops. [...] But the real problems
arise on big server setups, where Debian is losing ground because of
its antiquated init system.
- Debian is not only about desktops.
- The second part is too subjective. A counterexample was
provided in the reference, mentioned in my previous post.
Is this all? Sounds like a bad joke.
Reply to: