Messages in this thread | | | Date | Fri, 10 Mar 2000 23:58:14 +0000 (GMT) | From | Riley Williams <> | Subject | Re: [patch-2.3.51-pre2] misc cleanups |
| |
Hi Werner.
>> At the end of "make config", check a set of declared >> "dependency rules" and if they are violated, just give a >> warning-message and run a "make quietoldconfig" so that >> only the relevant questions are asked again.
> Sounds like the third best solution:
> best: rearrange configuration such that the structure is > clear, easy to understand, and no conflicts can arise > (only problem: may be impossible ;-)
> 2nd best: catch conflicts in the configuration editor and > let users resolve them there
> 3rd best: catch them outside of the editor and use a > different procedure to resolve them
Make that 2nd, 3rd and 4th best respectively. Best has to be to scrap the current unwieldy config altogether, and replace it with one that isn't anywhere near as confusing in the first place.
> The 3rd best may still be better than nothing at all, > provided that there is a useful migration path to a more > integrated solution.
WHat that needs is somebody to have a real good think, and to actually document ALL the places where the autoprobing of interface cards can conflict, along with how they conflict. Given that, an "integrated solution" couldn't be that hard to do...
Best wishes from Riley.
* Copyright (C) 2000, Memory Alpha Systems. * All rights and wrongs reserved.
+----------------------------------------------------------------------+ | There is something frustrating about the quality and speed of Linux | | development, ie., the quality is too high and the speed is too high, | | in other words, I can implement this XXXX feature, but I bet someone | | else has already done so and is just about to release their patch. | +----------------------------------------------------------------------+ * http://www.memalpha.cx/Linux/Kernel/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |