Bug#727708: init system other points, and conclusion

[Nikolaus Rath <Nikolaus@rath.org>]

Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> It does, however, have a number of missing features.  Those I have in
> mind are:
>   - ability to log daemon output to syslog
>   - multiple socket activation (systemd socket activation protocol)
>   - socket activation for IPv6 (and datagram sockets)
>
> Of these Russ rightly points out that lack of IPv6 support is rather
> poor; it is arguably not suitable for release in jessie without this.
>
> However, crucially, these are all simple matters of programming,
> without difficult design decisions.  They IMO don't reveal structural
> problems with upstart's approach to things.

I don't understand this argument. Even turning systemd into a 1:1
upstart copy is "simple programming" (and vice versa), so by that argument
there'd be no technical reason to pick one init system over the other at
all. In some sense, it seems to me that you are proposing that the
Debian *Technical* Committee make its decision for the init system based
on the *developers* of each project, because the technical differences
are mere metters of programming.

(I'm not sure why the "structural" and "design decisions" would make a
difference either, changing from one existing design to another existing
design is also just programming).

Best,
Nikolaus


-- 
Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

             »Time flies like an arrow, fruit flies like a Banana.«