Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!ames!apple!motcsd!hpda!hpcuhb!hp-ses!hpdml93!campbell
From: campbell@hpdml93.HP.COM (Gary Campbell)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: combine script (was Re: More silence in comp.binaries.ibm.pc)
Message-ID: <1540001@hpdml93.HP.COM>
Date: 3 Aug 89 16:18:23 GMT
References: <24170@iuvax.cs.indiana.edu>
Organization: Hewlett Packard - Boise, ID
Lines: 22

>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.

On my system wildcards generate file names in ASCII order just like
ls.  Is this not true on some UN*X systems?

BTW: Why the cat in

  cat $* | sed '/^END/,/^BEGIN/d'| uudecode

My man page shows that sed will take a series of files like cat, so it could
be:

  sed '/^END/,/^BEGIN/d' %* | uudecode

--

Gary Campbell
Internet: campbell%hpbsla@hplabs.HP.COM
UUCP: ...!hplabs!hpbsla!campbell