systemd for 11.10 ?

[Patrick Goetz]

On 05/10/2011 04:55 AM, James Hunt wrote:
>>
>>    https://bugs.launchpad.net/upstart/+bug/406397
>>
>
> This is a nasty bug, but it does not require a complete rewrite of
> Upstart. Indeed, we are currently considering replacing the process
> tracking code to resolve this bug.
>


Hi -

To be clear, the basis for my statement was this comment, found in the 
launchpad bug report referenced above:
------------------------------
Scott James Remnant (Canonical) wrote on 2010-09-01: 	#21

This and bug #530779 are fundamental due to Upstart's use of ptrace() 
for fork following - a rewrite of Upstart is in progress which uses 
other newer kernel mechanisms to follow forks and would not be 
vulnerable to this kind of issue. However there's no "quick fix" to it, 
and no way to backport that code.
------------------------------

+1 to Martin Pitt's suggestion to sync-unblacklist systemd so that 
people can try it out (save for the caveat given below).  This would 
also satisfy Steffen Barszus' comment that only actual real world 
testing matters when evaluating system infrastructure.

My only concern: wouldn't this then require that every binary package 
would have to be built to work with either upstart or systemd?  This 
seems like the kind of system detail that's relatively binary: either 
you use one, or the other, but not both.