Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ryesone.UUCP
Path: utzoo!utcs!ryesone!mason
From: mason@ryesone.UUCP (Dave Mason)
Newsgroups: net.news.adm,net.news.sa,net.sources.d
Subject: Re: Beware of Blindly Un-SHARing a File
Message-ID: <140@ryesone.UUCP>
Date: Sun, 20-Apr-86 14:37:12 EST
Article-I.D.: ryesone.140
Posted: Sun Apr 20 14:37:12 1986
Date-Received: Sun, 20-Apr-86 18:34:35 EST
References: <947@kitty.UUCP> <3029@amdahl.UUCP>
Organization: Ryerson School of Computer Science, Toronto, ON
Lines: 30
Xref: utcs net.news.adm:609 net.news.sa:276 net.sources.d:128

> And fortunately, the shell provides a nice way to check what sorts
> of things a shar will do.  For example:
> 
> 	sh -x -n foo.shar
> 
> or more verbosely:
> 
> 	sh -v -n foo.shar
> 
> The '-n' means "look at it, but don't do it."  Visit your
> freindly manual page for more details.
> -- 
> Gordon A. Moffett		...!{ihnp4,seismo,hplabs}!amdahl!gam
> 
Unfortunately (at least on this system (sysV on IBM Series/1))
	sh -xn 		- doesn't display anything, as -n says don't execute
			  so -x doesn't have anything to print
and
	sh -vn		- displays the whole file

Does it work better elsewhere?  I was all ready to make this the default
mode in unshar (unless you give a directory for it to use), but the behaviour
isn't what we need.  I may do it anyway here (after hacking sh to make -xn
do what it should).
-- 
usenet:	..!utzoo!ryesone!mason	Dave Mason, Ryerson Polytechnical Institute
	..!utzoo!utcsri!mason	Dave Mason, U. Toronto CSRI
CSNET:	mason@Toronto
ARPA:	mason%Toronto@CSNet-Relay
BITNET:	FCTY7053@RYERSON.BITNET