mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@drgw.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andre Hedrick <andre@linux-ide.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Domian Validation (Re: 2.5.1 - intermediate bio stuff..)
Date: Tue, 18 Dec 2001 00:39:28 -0600	[thread overview]
Message-ID: <20011218003927.D25200@altus.drgw.net> (raw)
In-Reply-To: <20011218000432.C25200@altus.drgw.net> <Pine.LNX.4.33.0112172210470.2416-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0112172210470.2416-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Dec 17, 2001 at 10:12:21PM -0800

On Mon, Dec 17, 2001 at 10:12:21PM -0800, Linus Torvalds wrote:
> 
> On Tue, 18 Dec 2001, Troy Benjegerdes wrote:
> >
> > Translation: Andre has been in a few too many ATA meetings and can't think
> > without using storage industry insider-speak ;)
> 
> We know ;)
> 
> > I only had a 6 months internship in storage, but I believe what he's
> > talking about are sound engineering principles.
> 
> No. Sound software engineering principles is to design good interfaces,
> and make the low level code adhere to them.

Well, I may have mis-stated my intentions in the last email. What I want
to see is some mechanism and *code* to test these interfaces and verify
that the low (AND high) level code is actually adhering to the interface,
as well as attemp to isolate which side of an interface a failure has
occured on. I want fault isolation, and TESTING to make sure that any 
fault we have seen in the past can be detected with easy-to run code.

-- 
Troy Benjegerdes | master of mispeeling | 'da hozer' |  hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's 
why I draw cartoons. It's my life." -- Charles Schulz

  reply	other threads:[~2001-12-18  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17  0:11 2.5.1 - intermediate bio stuff Linus Torvalds
2001-12-17  2:21 ` Richard Gooch
2001-12-17  2:33   ` Dave Jones
2001-12-17  2:52   ` Craig Christophel
2001-12-17 19:11 ` Domian Validation (Re: 2.5.1 - intermediate bio stuff..) Andre Hedrick
2001-12-18  6:04   ` Troy Benjegerdes
2001-12-18  6:12     ` Linus Torvalds
2001-12-18  6:39       ` Troy Benjegerdes [this message]
2001-12-18  6:44       ` Larry McVoy
2001-12-18 12:28         ` Rik van Riel
2001-12-18 13:37           ` [lkml] " Ian Soboroff
2001-12-18 16:43         ` Linus Torvalds
2001-12-18 20:38           ` Larry McVoy
2001-12-18 12:52       ` Matthias Andree

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=20011218003927.D25200@altus.drgw.net \
    --to=hozer@drgw.net \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®