Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Down in the Dumps (a true story)
Keywords: dump
Message-ID: <11706@mimsy.UUCP>
Date: 28 May 88 05:05:36 GMT
References: <611@eplrx7.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 21

In article <611@eplrx7.UUCP> mcneill@eplrx7.UUCP (Keith McNeill) writes:
>I like what sys5 dangerous utilities (volcopy & mkfs) do.  
>They tell you what you are doing and wait 5-10 seconds 
>before they do anything.  This gives you a chance to 
>change you mind. ...

The old `restor' program (no `e') did this for `restore r'.
This sort of `countdown to disaster' is fine in its place, but
that place does not include something that is done often (e.g.,
several times a day for /etc/dump).  When you do something often
enough, you wind up doing it by rote:

>DUMP: Date of this level 0 dump: Thu May 26 09:03:42 1988
>DUMP: Date of last level 0 dump: the epoch
>DUMP: Dumping /dev/rra0a (/) to /dev/rra0a 
>DUMP: Sleeping 10 seconds...Hit BREAK to quit....

Chances are that, after a few months, the operator would not notice
anything odd about this until the dump finished.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris