Comment 4 for bug 435935

Converted scripts include GDM, D-Bus, Apport, Anacron, acpid, UFW, avahi-daemon, NetworkManager. The first two are not a problem since there are problems with people stopping them by mistake and breaking their graphical sessions. The others would be good to have, but... On my system, services-admin still manages exim4, klogd, sysklogd, brltty, apmd, alsa-utils, bluetooth, hotkey-setup, powernowd, smartmontools, winbind, ssh, rsync, apache2, samba, ntp and cups. Definitely good to have, I guess.

So I'm done with the basic Upstart "support" (more of a "compliance"). I have a patch here that uses 'service' to start/stop scripts, and that hides services duplicated in /etc/init.d and /etc/init. This is because for compatibility, many scripts in /etc/init.d are links to an Upstart executable that runs actual jobs. So we don't want to mess with that.

I've created a new "upstart" init system, that is used for Debian platforms now. Do you now if Debian is planning to move to Upstart? I could theoretically make my patch for Ubuntu only, but that would mean changing platforms in every module and force a rework of patch at bug 434565. Since the only real requirement of the "upstart" system for now is to have 'service' installed, if Debian wants to get Upstart I'll keep it that way.

About the fixes I've talked above (links and priorities), they are in the gst and in liboobs, so sadly they can't be released now. I could include them in 2.28.1, if that's worth it, or you could cherry-pick them for Ubuntu. But those changes are completely independent from Upstart, actually - they just make services-admin much cleaner.

About releasing the stb: when would Ubuntu need the release so that it can be included properly in Karmic? I can make it very soon, but we have to be sure there are no major bugs (changes are not so complex, though).