Xref: utzoo comp.sys.next:18671 comp.arch:23158
Newsgroups: comp.sys.next,comp.arch
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!coplex!disk!corpane!herman
From: herman@corpane.uucp (Harry Herman)
Subject: Re: parity is for farmers?
Message-ID: <1991Jun08.174531.26400@corpane.uucp>
Organization: Corpane Industries Inc.
References: <1991May21.232331.24888@cs.umn.edu> <1991Jun03.040242.15406@ariel.unm.edu>
Distribution: na
Date: Sat, 08 Jun 1991 17:45:31 GMT
Lines: 18

In <1991Jun03.040242.15406@ariel.unm.edu> ratshana@triton.unm.edu (R.L.) writes:

>Parity memory isn't really necessary for two reasons:
>1) Unless you buy really cheap memory, you should NEVER have a problem with
>   screwed up RAM. Besides, if the RAM is screwy, whats the worst that can
>   happen? Your term window dies, so you kill it on another task...

Or the screwy memory is in the middle of a disk buffer and you end up
trashing your company's accounting database, which then takes several
days to restore due to having to figure out when the database got
screwed up, restoring backups before that point (hopefully sometime
recently) and re-entering ALL the lost transactions between when the bad
data was written and when it was discovered.

Of course, this assumes that regular backups are taken...

					Harry Herman
					herman@corpane