public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Michael D. Crawford" <crawford@goingware.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Quality Database on Newsforge
Date: Fri, 18 May 2001 18:17:20 -0400	[thread overview]
Message-ID: <3B059F70.13876@mandrakesoft.com> (raw)
In-Reply-To: <3B059E86.93415132@goingware.com>

"Michael D. Crawford" wrote:
> 
> chromatic has written a very nice article on the Linux Quality database
> at Newsforge:
> 
> Linux Quality Database: One man's quest for kernel quality
> http://www.newsforge.com/article.pl?sid=01/05/17/204213&mode=thread
> 
> The site itself is at http://linuxquality.sunsite.dk/
> 
> You will see it is still in the planning stages.  Life has been quite
> hectic these last months, but I am making slow progress and I'm starting
> to get more time now.  I have written a couple of articles you may find
> useful, one on testing the kernel and the other on testing web
> applications.  The kernel testing article is at:
> 
> Using Test Suites to Validate the Linux Kernel
> http://linuxquality.sunsite.dk/articles/testsuites/

You should definitely link to Cerberus (search for it on sourceforge, I
think the project is "vt-ctcs" but not sure), and also RedHat's
stress-kernel rpms.

The stress-kernel rpms are Cerberus++, ie. with extra goodies that
haven't made it to cerberus yet.

-- 
Jeff Garzik      | "Do you have to make light of everything?!"
Building 1024    | "I'm extremely serious about nailing your
MandrakeSoft     |  step-daughter, but other than that, yes."

      reply	other threads:[~2001-05-18 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 22:13 Linux Quality Database on Newsforge Michael D. Crawford
2001-05-18 22:17 ` Jeff Garzik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B059F70.13876@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=crawford@goingware.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox