Comment 16 for bug 453365

> If the effort is just to get any packages in main by Lucid, I don't see why
> it's not achievable.

Fixing all of main isn’t good enough for many users (openafs is itself in universe). Whether it’s acceptable to break universe is up to the Ubuntu TB, but there’s absolutely no point in breaking *anything* when it’s totally avoidable by changing “stopping rc” to “starting rc”.

(I’d love to be proven wrong by getting all of Lucid converted to upstart before the release—but that _still_ doesn’t imply we should arbitrarily break things before that happens.)

> So am I mistaken, but stopping rc RUNLEVEL=[2345], that means as soon as
> runlevel 2 is exited or 3 or 4 or 5, then it would run DKMS right?

Perhaps you are mistaken (or I misunderstood you): rc is a task, so it “stops” as soon as all the SysV initscripts have finished starting, not when the runlevel is exited.

But I want dkms_autoinstaller to run before the SysV initscripts start (‘start on (… starting rc RUNLEVEL=[2345])’), rather than running after the SysV initscripts start (‘start on (… stopping rc RUNLEVEL=[2345])’, which is what you currently have).

Are we on the same page here?

> This is a spectacular idea. I've just committed it upstream.

Cool. I think you’re supposed to also declare
  emits built-module
in /etc/init/dkms_autoinstaller.conf; see init(5).

> I heard that this isn't the proper thing to do in Lucid anymore, and
> anything that was doing it will be changed.

gdm and usplash still emit and use starting-dm in current Lucid (but of course it’s possible that’s still planned to change? *shrug*).