On Monday 31 March 2003 07:38 am, Bruno Prior wrote: > I think Simon has a point. There are plenty of occasions (e.g. IDE > problems in the past) when the recommended solution is to get hold of a > vanilla kernel, apply relevant patches (usually starting with the latest > ac patch) and rebuild the kernel. The trouble is, many patches won't > work on Mandrake kernel source, as it is already so heavily patched, so > you have to patch vanilla kernel source, which loses some > Mandrake-specific features (e.g. Supermount). >
Two points though.. if you want the Mandrake specific features, you WON'T find them in the main tree - and until they're merged back upstream, can't have it both ways. You have to decide which kernel you want and go with it. Second point - we have people who maintain the Mandrake kernel. If there's a useful patch, they'll apply it, no? If it means reading the patch, figuring out what it MEANS, and applying it in the context of the existing patches - it's a little more work than just layering on patches, but isn't that what kernel guru's are supposed to do? > If there were a clear path that showed which patches the Mandrake guys > had applied, in what order, then it might be possible to construct a > hybrid kernel that retained as many Mandrake features as possible but > solved your specific problem. And the information gained would be useful > to Mandrake. But I have never found a document that detailed the patches > applied by the Mandrake guys. Unless it exists, Mandrake are missing an > opportunity to harness community input. > > Cheers, > > Bruno Prior Regards, Vinny
