From: David Masover <ninja@slaphack.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Hans Reiser" <reiser@namesys.com>, "Markus �" <mjt@nysv.org>,
"Pysiak Satriani" <pysiak.satriani@wp.pl>,
reiserfs-list@namesys.com
Subject: Re: Reiser4 O_DIRECT
Date: Tue, 24 May 2005 18:28:58 -0500 [thread overview]
Message-ID: <4293B8BA.20808@slaphack.com> (raw)
In-Reply-To: <200505242155.j4OLt9mD023120@turing-police.cc.vt.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 24 May 2005 16:35:51 CDT, David Masover said:
>
>
>>My feeling is that you create the standard as you create the test, not
>>the other way around. If the test works, then there are by definition
>>few bugs if any in the system itself -- any other bugs are actually in
>>the application, not the system.
>
>
> That's even worse. Then if somebody bodgers it all up with some corner case
> that your test system didn't cover, you're by definition screwed, as the
> standard won't say what it *SHOULD* do....
>
> Consider the vast philosophical difference between "This is what the FS *should*
> do" and "This is what we tested the FS for". You want the standard to be the
> first, not the second.....
No, you want them all to be the same thing. You want "This is what we
tested the FS for" to be broad enough that you really don't have very
many bugs at any stage in development.
But then, I'm being overly optimistic.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQpO4ungHNmZLgCUhAQKDIg//S5gF75thisHjI7DjzecyVCjhvSJxNIX6
aTljjVP9QjNu85X2q7QFHvqoKL8frrn+nTZ+70gUdN9FQL4S7nn0SbtBED/Rra9A
C2vPDr89yoCOpP1mTVw/0URnDtwV3AmFxwnMYrfz1nfBReCUcYKeY6NBUNeS/eWV
h51FvSc10r7dxsI287svUlxpNTeyySogvjhhTa6C2v1kkLAyvgJ5AEmTDXkE01k9
aaJ+YJgAfgu5l1TRQHpZm9ck7ikBkXqGMrc/+vb6L3AHnMGfbinIDN8x8UD/l7XB
0nF4sgh+h30bjwF08+B5vc6SQeTSKL/L5ZxUg6J3G0GhduS9wAYb5bvGxZUYd79X
Va+/M1kWjFF14o9ORGIfsNDNXxzM1dPL+0JjtnDwnqF2ahuKEYfIq67A4ggRFL3+
HkZb1p4cVi0YaGG39nADEiOOddyL/5vQxIyRgbY/j7gZWORZd3XS0tYGRfyz4lBF
8WLLvoKtO3PEVF89KSFj4nOUR9piIbHt96zEckbX11v4igskl5Uf9VZzTfuUzzlY
Fhr22FPJLCBmYQGljjBguwOExYHbATCPaYjFwl99SHx7XAAc0ezz5qwP+UUMcRUc
riiYaHN0MgSctz3h/D1KeiUvyMjpm2QTKOAw59h0/XB0owfnpovnW9xznPIlu5e4
f4CR1VQPMfI=
=c/WP
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-05-24 23:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 17:53 Reiser4 O_DIRECT Martin Piayda
2005-05-20 8:42 ` Vladimir Saveliev
2005-05-21 21:49 ` Re[2]: " Pysiak Satriani
2005-05-22 7:43 ` Hans Reiser
2005-05-22 17:12 ` mjt
2005-05-22 17:31 ` Hans Reiser
2005-05-22 17:38 ` Martin Piayda
2005-05-26 19:25 ` evilninja
2005-05-22 22:47 ` Re[2]: " Valdis.Kletnieks
2005-05-23 0:22 ` David Masover
2005-05-23 1:04 ` Valdis.Kletnieks
2005-05-23 9:52 ` mjt
2005-05-23 16:53 ` Valdis.Kletnieks
2005-05-23 17:53 ` Hans Reiser
2005-05-24 21:35 ` David Masover
2005-05-24 21:55 ` Valdis.Kletnieks
2005-05-24 23:28 ` David Masover [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=4293B8BA.20808@slaphack.com \
--to=ninja@slaphack.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=mjt@nysv.org \
--cc=pysiak.satriani@wp.pl \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.