On Sun, Nov 09, 2003 at 10:45:54PM -0500, Joey Hess wrote: >> If one first runs a module that fails (for instance, install LILO on a >> non-existant drive, or install base from network with cable unplugged) >> and then run hw-detect, weird stuff happens: > Can you provide an easier way to reproduce this? hw-detect here does > skip loading a few modules that are not present, but that's the closest > it comes to failing, and I'm pretty sure I've never seen the priority > bumped up to super-critical.
Well, other people have reproduced it this way only -- I could of course try playing a bit with priorities and see what happens. :-) > I don't understand how the unplugged network cable is interacting with > hw-detect at all, really. The unplugged network cable makes the _previous_ module fail, and main-menu sets priority to low. That might be related somehow. :-) Without the pcmcia line, main-menu (at least main-menu from CVS) correctly bumps the priority back to medium, with no notion of "Priority was changed externally" as happens with pcmcia. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
