RE: too much untested code in new kernels

ing. G.A. van Dorth (
Sat, 4 Jan 1997 15:10:41 GMT

It's clear that a volunteer effort with minimal funding can't be
expected to deliver the sort of rigorous testing one hopes a major
company would do but there are all too many posts to this list which,
in effect, say "oh, silly me, make the ':' on line 102 a ';'". These
are not subtle errors or problems of interaction but problems with
typographical errors and misspelled variables, etc.

When there's a major shift in design philosophy (e.g., module
handling in the 2.1.xx tree), errors which have been otherwise
undetected (and, who knows, may not have been errors, strictly
speaking) are inevitable. I even understand that uncommon driver
combinations are capable of producing surprises and finding them is
part of the development process, too.

But there seems to be a disproportionate number of simple blunders
that prompt me to say "jeeze, didn't you compile this before shipping

Before someone thinks I'm dumping this all in Linus' lap, I'm not.
It's clear he's got his hands full and the rest of the developers need
to take up the load he can't be expected to handle with the present
demands on his time.