David Dennis wrote: > Finally.. this whole conf.modules / modules.conf thing. Kudos to you for > posting it. This is a linux long-standing gotcha, ever since the modules > entity came out. If you are going to ''deprecate'' a file and remove it, > please actually do all the work of testing every potential fail point in > your install suite .. don't just hang a sign up that says 'deprecations > to the rear' then go home. A: This is cooker - if you don't know what it is then go read something on http://www.linux-mandrake.com B: You got problems? Than state them. This is what cooker is for. C: Nothing on cooker makes conf.modules unusable. Just some warnings come when you use some tools. D: In my practice I didn't found any big conflicts with the use of modules.conf. If you cared enough to see the architecture of linux then you would note that mainly problems occur on scripts. Binaries around 2.4.0 do not seem to have any problems (I found none). E: You came here, dropped flame and went home. But note that people come here, drop flame, say "I have a hell of a problem" and after a few posts get to the bottom of the problem. Now I also use Solaris & Windows. For half-year, I couldn't find a damn SMART-2 driver for Solaris. When I call Microsoft representatives they try to show me that I need some damn certificate to be a BIG GUY. However, they don't say a damn word on how to stop their stupid OS crashing because their NetBIOS driver is DAMN BUGGY. Ektanoor
