Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!pasteur!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: (comp.sources.amiga)  unsharing ...
Message-ID: <8810311852.AA05509@cory.Berkeley.EDU>
Date: 31 Oct 88 18:52:43 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 21

:>In the future, Bob, could you add a "cover letter" to each posting?
:
:    After unshar'ing, one could read the doc's, BUT,
:    I am voting for a footerless comp.[you know].amiga, no offence,
:    but I'm lazy editing those LARGE shar files... B^)
:
:		-Mike

	The 'unshar' program.  One might ask, 'why not just /bin/sh the
file?'  Reason:  The 'unshar' program attempts to skip all the headers
and junk to find the beginning of the actual shell script. (Unix unshar,
that is).

	So, as long as Bob doesn't stick any comments in that look like
the beginning of a shar file, you do not have to edit it at all!

	uudecode does the same thing, but I prefer a shar'd uuencoded file
to a raw one because it removes all superfluous spaces and blank lines,
which makes concating multiple uuencoded pieces together easy.

					-Matt