Messages in this thread | | | Date | Fri, 3 Jan 1997 04:08:28 -0500 | From | "David S. Miller" <> | Subject | Re: too much untested code in new kernels |
| |
Date: Thu, 2 Jan 1997 15:22:41 -0600 From: "Ray Van Tassle-CRV004" <Ray_Van_Tassle-CRV004@email.mot.com>
Hence my request for Linus (or _somebody) to make a test compile with every possible option turned on, to make sure the d*mn thing will COMPILE at least!
Whenever anybody mentions this, they get shouted down, claiming (validly) that it is impossible for anybody to test all possible combinations of options. But for CRYING OUT LOUD how about just making sure it compiles!!!!!!!! And verifying that the resultant image boots up.
Thats the most rediculious thing I ever heard someone request.
"Hey, you're writing your thesis, you have a newborn in your life, and you still try to keep the kernel development moving, can you please spend another half a day for every release trying every possible configuration the kernel can be done with, on every supported platform, and don't release a patch until you do this."
No, bullshit, that is the whole purpose of having the entire internet trying out new development releases as they come out, so that the work can be distributed, and Linus doesn't have a fire-hose taped to his mouth.
It compiles on Linus's machine just fine, Linus does not use modules at all, so sue him for christs sake.
If you want stuff that compiles and/or works out of the box, stick with 2.0.X, end of story.
---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><
| |