I haven't examined why, but hotplug loads a fb driver for my Matrox. And because normally hotplug is started after consolefont, I've lost my console font (for german umlaute ;) ). So had to change two things: 1. Add "after hotplug" (and modules, just in case) to /etc/init.d/consolefont 2. Move hotplug from default to runlevel boot. The first is easy to change, the second isn't what I want. But if I don't move hotplug from default to runlevel boot, the system silently ignores "after hotplug". It seems runlevel boot will be started allways before runlevel default. Regards, Alexander Reproducible: Always Steps to Reproduce: 1. 2. 3.
Ok, it makes sense. > The first is easy to change, the second isn't what I want. But if I don't move > hotplug from default to runlevel boot, the system silently ignores "after > hotplug". It seems runlevel boot will be started allways before runlevel > default. Expected - you cant really run a boot script after a higher runlevel script.
I don't see the point why dependencies (after and before) should'nt work between different runlevels. "Need" is something other, but "before" and "after" could work flawless.
Because it is not garanteed that you will get both runlevels up. Anyhow, 'after hotplug' added to consolefont in CVS.
But dependencies are generated dynamically, so "after" and "before" should work inbetween runlevels. Nobody garantees that a service is started, so there should be no logical difference if after or before is used inbetween runlevels. (I don't talk about "need" here ;) )
Should I write a new bug/feature request for "after" and "before" inbetween runlevels?
