Message-ID: <3E7F1A2D.4050306@coyotegulch.com>
Date: Mon, 24 Mar 2003 09:46:05 -0500
From: Scott Robert Ladd <coyote@coyotegulch.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319 Debian/1.3-3
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Testing: What do you want?
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1431
Lines: 32

OSNews and LinuxJournal are urging people to test the Linux kernel. I've 
been doing so for several months now, running the latest kernel live on 
my primary development system. I figure the best way to know if the 
kernel works is to use it when I'm working. ;)

At the moment, my biggest contribution to kernel development is testing, 
given that I'm not yet comfortable hacking kernel code in public. My 
question is: What do the kernel developers want from testers? What sort 
of reports are helpful? Is there anything in particular that needs 
extensive testing?

I haven't found a "Guide to Testing the Kernel" anywhere -- perhaps such 
a document exists, but I've missed it. Such a document could provide 
basic information for "testing newbies."

My experience thus far:
For the most part, the 2.5 series has worked very well for me, albeit 
with a few glitches (radeonfb, for example, as reported last week.) I'll 
build the 2.5.65 kernel on my Sparc later today, and see how well it 
works there.

-- 
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Professional programming for science and engineering;
Interesting and unusual bits of very free code.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/