Hi, Sven Luther writes:
> Why not use discover in the initrd ? This has gotten hold of you and won't let you go, eh? > Would this be too place consuming ? Yes. Also, discover is meant to detect all the hardware no matter where you run it. If you want this, you should build as many drivers as possible into the kernel and let it handle the detection itself. The initrd approach, on the other hand, goes in exactly the opposite direction. You build as many drivers as possible as modules, and just put enough of them into the initrd to bring up the root filesystem of one specific hardware configuration. Anyway, the problem was not that some hardware was not detected, but that the drivers were probed in a different order than before and therefore the harddrives ended up with different names. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
