Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!ut-ngp!melpad!reality1!james
From: james@reality1.UUCP (james)
Newsgroups: net.unix-wizards,net.unix
Subject: Re: 3b2's and elec. codes
Message-ID: <60@reality1.UUCP>
Date: Mon, 27-Oct-86 02:55:56 EST
Article-I.D.: reality1.60
Posted: Mon Oct 27 02:55:56 1986
Date-Received: Mon, 27-Oct-86 20:43:31 EST
References: <105@houligan.UUCP>
Reply-To: james@reality1.UUCP (james)
Organization: Reality Computer Systems, Austin TX
Lines: 17
Xref: mnetor net.unix-wizards:8462 net.unix:6040

The 3b2 meets these requirements.  In the unlikely event that the 3b2 refuses
to recognize the power off request, you just hit the reset button and then
the power switch, and this *will* work every time.  Note that the reset
switch is as destructive as pulling the power cord.  And in any case were
it necessary to meet some law on this, you could put a litte power isolator
with a switch on the power cord, and this would give you that switch and
pulling the plug, or both of the required cutoffs.  So meeting the requirements
is pretty trivial.

Doesn't anybody care about file system integrity any more?  It is exceedingly
rare that power must be cut off without even time for a sync.  I can't even
think of such a case off hand.  If unix machines are ever going to be
used by non-programmers, those people are going to have to be protected from
themselves to a certain extent.  So long as they can cut the power off, what's
wrong with doing a sync and letting their file system survive?
-- 
James R. Van Artsdalen    ...!ut-ngp!utastro!osi3b2!james    "Live Free or Die"