Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!dogie.macc.wisc.edu!uwvax!astroatc!brown
From: brown@astroatc.UUCP (Vidiot)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: More silence in comp.binaries.ibm.pc
Message-ID: <2501@astroatc.UUCP>
Date: 2 Aug 89 21:37:45 GMT
References: <8472@bsu-cs.bsu.edu> <2487@astroatc.UUCP> <8478@bsu-cs.bsu.edu>
Reply-To: brown@astroatc.UUCP (Vidiot)
Organization: Vidiot's Hangout
Lines: 33

In article <8478@bsu-cs.bsu.edu> dhesi@bsu-cs.bsu.edu (Rahul Dhesi) writes:
<In article <2487@astroatc.UUCP> brown@astroatc.UUCP (Vidiot) writes:
<>Since when has the combine script become "lazy"?  A long time ago a better
<>combine script was posted.  It works much nicer, especially on programs with
<>MANY parts.  Who wants to type in the names of all 11 pieces :-)
<
<Maybe I'm missing something, but the good old "combine" script
<
<     cat $* | sed '/^END/,/^BEGIN/d'| uudecode
<
<does happily accept usage like
<
<     combine part*
<
<provided the parts are numbered in sequence, and will happily combine
<and extract all of them.

True, using wild cards will get you the whole list.  But who says that it
will be in order.  Sure, you do a ls and they 'look' in order, but how did
you actually store them.  Do a tar or cpio and you will see that your disk
isn't necessarily in order.

I have received postings out-of-order.  If I saved them in the order I
received them, I just can't be sure that the wildcard will give them to me
in order.

Hence, I like using the combine script that was posted a long time ago.  It
gets around the problem of directory entry ordering.
-- 
	        harvard\     att!nicmad\
Vidiot            ucbvax!uwvax..........!astroatc!brown
	        rutgers/  decvax!nicmad/
	ARPA/INTERNET: brown%astroatc.UUCP@spool.cs.wisc.edu