> I think depmod -a do a major of job. But i dont know how it works on tomsrtbt.
No, you don't understand. I am *NOT* talking about dependencies *BETWEEN* modules. I'm talking about dependencies that modules have on the static part of the kernel *having been compiled with that module enabled*. That is, *some* modules, (not all), when you set configure to give you the module, they *also* make a difference in the *non module* part of the kernel, and depend on that difference, *in the kernel*. So, I have decided to: 1) Turn all the modules on. 2) Compile them and put them in the add-ons. 3) Turn all the modules off. 4) Compile the static part of the kernel. This will undoubtedly break *something*. In *some modules*. Many modules work fine, and have no such dependency or effect. But I don't have any way to identify which modules, how they will break, or anything useful, without first grepping all of the kernel source and makefiles for various strings, then going into the kernel sources for every grep hit and reading it until I have a clue what they are doing. Or, tesing every module out. But, since I don't have every possible piece of hardware, nor the time or inclinattion to start at the source code for something like a combination retinal scanner and gps receiver that I don't care if it works anyway, I'm just sticking it all in, some broken. -Tom
