On Thu, 2005-02-03 at 10:46 +0100, Thomas Hood wrote: > This is a case of local misconfiguration, not a bug in discover.
It's important to note that, despite my previous response and my accomodation of the bug request, this is entirely true. The way discover works, it's theoretically possible that a data update or override could change the order modules load, or even the specific modules that load. The ALSA team is already using this capability of discover to ensure that ALSA drivers load under 2.4 kernels, despite the fact that the canonical database reports OSS drivers for 2.4 and previous. That said, gratuitous changes to module load order can and should be prevented, and one such gratuitous change will be fixed with the next discover update. But if order is that critical to your system, I recommend using /etc/modules to load them manually. (Indeed, I do this myself on one of my own systems.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
