Comment 68 for bug 448095

My apologies, I have to backtrack on my prev statement. I thought to have read that on LWN
some time in the past, but I cannot find such statement anymore through google.

Fact is, that Debian hasn't moved to upstart OR systemd (or initng for that matter) yet,
even in unstable, and is using insserv (optional) to parallelize the boot sequence. They
are still contemplating which direction to take.

see
http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot and
http://lists.debian.org/debian-devel-announce/2009/09/msg00003.html

and the most recent announcement
http://lists.debian.org/debian-devel-announce/2010/05/msg00009.html

.. where upstart is described as 'the most promising candidate'.

Again, sorry for the confusion :)

On Monday 27 September 2010 11:52:48 you wrote:
> Isn't Debian still planning on moving to upstart? If so that would be a
> major vote of confidence and would guarantee upstart sticks around for a
> while longer.
>
> systemd looks very neat. That both RedHat and OpenSUSE are moving to
> adopt it is telling but I don't think it's very likely Ubuntu will give
> up upstart any time soon. More likely we'll see some borrowing of code
> and ideas. FWIW, SysVinit compatibility is the highest on my wishlist.
>
> OTOH, if Debian decide to move to systemd all bets are off. In that case
> I hope Ubuntu does the right thing and chucks upstart out rather than
> increase Ubuntu's divergence from the rest of the Linux world.
>
> --
> resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines
up from /etc/network/interfaces
> https://bugs.launchpad.net/bugs/448095
> You received this bug notification because you are a direct subscriber
> of the bug.
>