From: Hans Reiser <reiser@namesys.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Brian Wolfe <ahzz@terrabox.com>,
Ion Badulescu <ionut@moisil.cs.columbia.edu>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
Jan Kasprzak <kas@informatics.muni.cz>
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related)
Date: Mon, 05 Feb 2001 14:35:44 +0300 [thread overview]
Message-ID: <3A7E9010.4D6842D1@namesys.com> (raw)
In-Reply-To: <E14PkEo-0003B2-00@the-village.bc.nu>
Alan Cox wrote:
>
> > administrator that has worked in large multi hundred million dollar compani=
> > es where 1 hour of downtime =3D=3D $75,000 in lost income proactive prevent=
> > ion IS the right answer. If the gcc people need to compile with the .96 rh =
> > version then they can apply a removal patch hans provides in the crash mess=
> > age. This makes it easy to remove the safeguard and blow yourself up at wil=
> > l after being suitibly called a dumbass.
>
> With all due respect, if you are running $75,000/hr of lost income (which btw
> is small fry to a lot of folks) shouldn't you have an engineering team who
> a) read the documentation.
> b) run tests before rolling out software
>
> Alan
Think of it as being like gun safety. You don't seek to develop habits that
protect you when you are awake and alert and paying attention, you strongly seek
to develop the sort of habits that will protect you if for one moment your
attention wanders and you do something completely stupid. Oh dear, there may be
some cultural translation difficulty with this example.:-)
User protection is a variant on that. To have an attitude that if the user was
only alert and intelligent at the moment and as educated as you are in how to
compile a kernel, this is just, ahem, not right.
All things must be kept in balance though, and not taken to extremes. But when
the number of users complaining exceeds some amount relative to the cost to
protect them, they should be protected from their lack of education in what
distro to not trust the compiler on.
You can go ahead and write software for the always alert and always intelligent
and never too hasty and always read the README users, and I'll be happy with
having the rest of the market for ReiserFS.:-)
Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-05 12:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Ion Badulescu
2001-02-02 21:57 ` Alan Cox
2001-02-02 22:06 ` Arthur Erhardt
2001-02-02 22:06 ` Hans Reiser
2001-02-02 22:57 ` Ion Badulescu
2001-02-05 2:50 ` Brian Wolfe
2001-02-05 4:08 ` Albert D. Cahalan
2001-02-05 11:58 ` Alan Cox
2001-02-05 11:36 ` Hans Reiser
2001-02-05 12:44 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16 ` Hans Reiser
2001-02-05 12:52 ` Alan Cox
2001-02-05 12:33 ` Hans Reiser
2001-02-05 12:57 ` Dr. David Gilbert
2001-02-05 16:57 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12 3:41 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12 9:45 ` Hans Reiser
2001-02-05 12:16 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05 5:21 ` Gregory Maxwell
2001-02-05 12:02 ` Alan Cox
2001-02-05 11:38 ` Hans Reiser
2001-02-05 11:55 ` Alan Cox
2001-02-05 11:35 ` Hans Reiser [this message]
2001-02-05 20:19 ` Brian Wolfe
2001-02-02 22:42 ` Ion Badulescu
2001-02-03 3:43 ` Johan Kullstam
2001-02-03 8:57 ` [reiserfs-list] " David Ford
2001-02-03 10:00 ` J . A . Magallon
2001-02-03 23:26 ` Felix von Leitner
2001-02-04 11:04 ` Alan Cox
2001-02-04 3:24 ` John Alvord
2001-02-02 11:28 Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16 ` Jan Kasprzak
2001-02-02 12:34 ` Alan Cox
2001-02-02 13:09 ` Jan Kasprzak
2001-02-02 16:36 ` Jan Kasprzak
2001-02-02 16:46 ` Alan Cox
2001-02-02 12:15 ` John Morrison
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=3A7E9010.4D6842D1@namesys.com \
--to=reiser@namesys.com \
--cc=ahzz@terrabox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@moisil.cs.columbia.edu \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox