[comp.unix.questions] INFO-UNIX Digest V3#066

black@ee.UCLA.EDU (02/18/87)

> >> users should be careful 
> I was not careful enough.  But, I know it is hard for me to keep
> cool during a hot discussion using a poor  terminal through 
> a  noicy telphone line. 
> In many cases, such mistakes may be more serious than 'rm *'.

Somehow, I have a *real* hard time imagining something that one
said via e-mail that could be more serious than 'rm *'.  So, spill
the beans Yao--what exactly was it you said that was "more serious"
than removing six weeks worth of code, the root directory or last 
year's stock price database for 30,000 issues?  (All witnessed or
committed by yours truly at one point or another.)

I'm not just trying to be flippant here.  As a System Admin., I
get tired of users who keep screaming for code to hold their
hands.  If you want to talk about serious, read section 8 of
the BSD Programmer's Manual.  Those are programs where one must
closely inspect each character of the command line before hitting
return, not simply flip into vi at the end of a mail session
and reread for typos!

Look at the bright side--you could be using JCL!

Rex Black
	
black@ee.ucla.edu                                          ARPA        
...!{ihnp4,ucbvax,sdcrdcf,trwspp}!ucla-cs!uclaee!black     UUCP

Disclaimer:  I work for the state.  States have programs, not opinions.
Ergo, the state has my programs but my opinions are mine!

Richard_Conto@um.cc.umich.EDU (02/18/87)

This is a side issue to the the problems inherent in mail
systems that export mail to unreachable places asap, but
Rex Black's (of <black@ee.UCLA.EDU>) message which said:
 
>        If you want to talk about serious, read section 8 of
>the BSD Programmer's Manual.  Those are programs where one must
>closely inspect each character of the command line before hitting
>return, not simply flip into vi at the end of a mail session
>and reread for typos!
>
 
 ... is just evidence of a poorly designed program, and not an excuse
excuse for poor design in programs.  (I prefer keyword oriented
commands instead of letter oriented commands.)
 
On the other hand, for most mail systems I know of, once you've
posted a message, that's it, and users will always be asking to
'unpost' a message after they've gone past the point of no return.
 
And in general, that applies to most systems.. from manipulating files
to driving automobiles.  There's a point of no return that you cann't
back off from, and users just have to be careful at those points.
 
--- Richard
 
Arpa/Internet:   Richard_Conto@um.cc.umich.edu
 
Usnail:  Richard Conto             Ma Bell:  (313) 764-9423
         Computing Center
         1075 Beal ave.
         University of Michigan
         Ann Arbor, Mi. 48109
 
If you want a witty saying, don't look here.