Comment 15 for bug 453365

On Thu, Dec 10, 2009 at 01:07, Anders Kaseorg <email address hidden> wrote:

> > Now, if you chain that with the openafs upstart job waiting for DKMS to
> > be done and apache/mysql/$favorite_server_service waiting for network
> > file systems to be ready and you've got a very logical ordering to your
> > boot process.
>
> Yes yes, I understand that. And I want very much to live in that world.
> But we aren’t going to get there overnight, or even in one release cycle
> (especially with packages being imported from Debian, which still uses
> SysV initscripts). So I’m interested in making the transition to that
> world as smooth as possible, especially when it’s easy.
>

What kind of scale of packages are you talking about? I mean adding upstart
scripts isn't very difficult. I just did it for mysql a week or two ago.
 If the effort is just to get any packages in main by Lucid, I don't see why
it's not achievable.

>
> OpenAFS certainly wants to satisfy a network file systems event—but
> again, if openafs depends dkms and dkms runs after rc, then now you’ve
> forced rc to never depend on network file systems.
>
> Someday rc will go away and none of this will be a problem, but until
> then let’s try to get things right with rc.
>

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?

You mean you’re worried about dkms triggering things too early? dkms
> does not trigger anything yet, and when there are packages that trigger
> on dkms, they will ‘start on (stopped dkms_autoinstaller and <other
> conditions…>)’ so that they won’t trigger too early no matter how early
> dkms finishes.
>
> Better yet, you could register an event (say) built-module, and do
> ‘initctl emit built-module MODULE=foo’ for each module foo when it is
> built, so that other services could “start on (built-module MODULE=foo
> and <other conditions…>)”.
>

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

http://linux.dell.com/git/?p=dkms.git;a=commit;h=2acd882f0e28249d05d0bdc88f894cb534824f69

>
> By the way, you can use the starting-dm event instead of ‘starting gdm
> or starting kdm or starting xdm’.
>

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