From: David Masover <ninja@slaphack.com>
To: Valdis.Kletnieks@vt.edu
Cc: Pysiak Satriani <pysiak.satriani@wp.pl>, reiserfs-list@namesys.com
Subject: Re: Reiser4 O_DIRECT
Date: Sun, 22 May 2005 19:22:51 -0500 [thread overview]
Message-ID: <4291225B.5090503@slaphack.com> (raw)
In-Reply-To: <200505222247.j4MMlr85008867@turing-police.cc.vt.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Valdis.Kletnieks@vt.edu wrote:
> On Sat, 21 May 2005 23:49:00 +0200, Pysiak Satriani said:
>
>
>>I remember Hans saying that r4 is so stable that the developers themselves
>>can not find any more bugs.
>
>
> Which in reality probably means "It *probably* won't eat your data".
>
> Remember that the developers have a limited number of different hardware
> configurations, and a limited number of test tools, and a limited number
> of ways they use the file system.
>
> So there's probably *plenty* of bugs still to be found - most of them the sort
> that nobody will expect, and won't be found until some user's creeping-horror
> database application that's written half in Cobol and half in Python does something
> totally stupid but legal.....
This is exactly why it should be in the kernel once the developers can't
find any more bugs. Marked as experimental, mainly, but in the kernel
where real users can throw cobol/Java/sql bastardizations at it and
break it.
Of course, I've worked on sufficiently few big projects that I'm still
naive enough to believe that unit tests _can_ catch everything, if
they're done right. I'm sure I'll eventually be proven wrong...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQpEiWngHNmZLgCUhAQKsfhAAmIMqe5C76D4TkbEHON261LgFS5wpqe+W
zhe2NlIk8BesA3YhYDFt/4zwQuVMZKkyFH5Np5N1dzfnP0ztpunfovKNApuYz7NH
qxIfbH0QCRHcXX7RrrChLZcpyXy1+hbIa71KmpoaciE30SEOxR3M8DlCO6uIhlGq
kjIJmO0YzIKECSmlHTbZEr0ox23C+fc1kGnH+KWq5qr2kyR0PIhUaqAn8lKMBDE6
vITNk/AodtFZgkJJytEcGU30ZAx4mLH2L/VH1oOM08huEuJjxB8stBlXU09Z/j4o
lowI4gK/N6vRqwHGQ2U0DZSyFqt9nKM72gzfN4gz8yZJgI8BUANLjHEEbnmCnwMJ
nNeoMlyanZPhnk5/C1ISnjL6z+bqWa/SduZExeauXbDYwemJpZzyqOShccsGONbO
Y2dPO3oW/CM0nPjoFTM6TtAGwybA6BsO7WFdyGwq75bCqnN5o2W1oc1o9K5ZiPJ/
obzxmPSMpOcrY/vo7knzBd37oQHBZUFI8lxwaMO+GgZaBzSOVDVaCEtQzBc98MPP
JHNJXmeOWUI0KYVDyd5ACjlhjjvpp0NEGgbMEqNgZy6oNmP734YSUeIVBONpPg2g
/ra+qyL/zji21r93bNUhuIvoX1EUl0/FvFk+0q1S3P5DaCBpn8vz8jqO1Rr3ZvWb
Qd3c53MrHZE=
=b8kU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-05-23 0:22 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 [this message]
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
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=4291225B.5090503@slaphack.com \
--to=ninja@slaphack.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=pysiak.satriani@wp.pl \
--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.