From: <random1@o-o.yi.org>
To: linux-scsi@vger.kernel.org
Subject: Re: Sym53C8xx Driver Hardening
Date: 23 Jul 2002 11:11:15 -0400 [thread overview]
Message-ID: <uptxev5rg.fsf@o-o.yi.org> (raw)
In-Reply-To: 1027437862.31787.136.camel@irongate.swansea.linux.org.uk
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> The high reliability people take a different view. I actually agree with
> them. It isnt about 'oops didnt happen' it is about controlling the
> failure case
"graceful degradation" -- it's been being taught in CS curricula for
*at least* twenty years. I'm disturbed by all the places that people
have chosen, when faced with the unexpected, to just panic, rather
than find a way to get back to some semblence of a running system.
I don't want some goofy UPS hanging off a USB bus, for instance, to
take down a critical storage server.
next prev parent reply other threads:[~2002-07-23 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 13:29 Sym53C8xx Driver Hardening Isabelle, Francois
2002-07-23 13:57 ` Rogier Wolff
2002-07-23 15:24 ` Alan Cox
2002-07-23 15:11 ` random1 [this message]
2002-07-23 15:38 ` Rogier Wolff
2002-07-24 23:11 ` Gérard Roudier
2002-07-25 22:33 ` Jeremy Higdon
2002-07-25 23:53 ` Alan Cox
2002-07-26 22:25 ` Gérard Roudier
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=uptxev5rg.fsf@o-o.yi.org \
--to=random1@o-o.yi.org \
--cc=linux-scsi@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