[117393] in Cypherpunks
RE: why bad things happen to good systems
daemon@ATHENA.MIT.EDU (jbugden@ALIS.COM)
Thu Sep 2 10:27:04 1999
From: jbugden@ALIS.COM
Message-ID: <D19EFA51B95CD211B89200104B2CC23164BAD4@ALIS-2>
To: cypherpunks@toad.com
Date: Thu, 2 Sep 1999 09:45:46 -0400
MIME-Version: 1.0
Content-Type: text/plain
Reply-To: jbugden@ALIS.COM
An updated version of the Normal Accidents is to be published this month.
http://www.amazon.com/exec/obidos/ASIN/0691004129/qid=936279499/sr=1-2/002-1
507349-5963427
Deborah A. Stone, Technology Review
"[Perrow's] research undermines promises that `better management' and `more
operator training' can eliminate catastrophic accidents. In doing so, he
challenges us to ponder what could happen to justice, community, liberty,
and hope in a society where such events are normal."
One of Perrow's observations was that the reasons for failure are not
visible for a certain critical period of time. I suspect that Jim's failures
were quite visible.
LooseCouplingMonger
> -----Original Message-----
> From: Anonymous [SMTP:nobody@replay.com]
> Sent: Wednesday, September 01, 1999 8:16 PM
> To: cypherpunks@toad.com
> Subject: why bad things happen to good systems
>
> At 10:16 AM 9/1/99 -0500, Jim Choate wrote:
> >We were down because our original ISDN bridge failed. Then SWBT had a
> line
> >outage for 2 days. Then our secondary/back-up bridge had a failed
> ethernet.
> >My ISDN provider provided a tertiary backup which had a failed NT-1.
>
> Three Mile Island also required three simultaneous unlikely
> faults to have an incident. But they happen.
>
> NormalDisastersMonger
>
>
>
>
>
>
>
>
>
>
>
>
