Path: utzoo!attcan!uunet!dino!uxc.cso.uiuc.edu!csd4.milw.wisc.edu!leah!rpi!pawl!shadow
From: shadow@pawl.rpi.edu (Deven T. Corzine)
Newsgroups: comp.sys.amiga
Subject: Re: Problems with comp.binaries.amiga
Message-ID: <SHADOW.89Jun26020320@daniel.pawl.rpi.edu>
Date: 26 Jun 89 06:03:20 GMT
References: <7318@cs.Buffalo.EDU> <5160046@hplsla.HP.COM>
Sender: usenet@rpi.edu
Organization: Rensselaer Polytechnic Institute, Troy, NY
Lines: 78
In-reply-to: davidb@hplsla.HP.COM's message of 23 Jun 89 23:54:50 GMT

In article <5160046@hplsla.HP.COM> davidb@hplsla.HP.COM (David Bakeman) writes:
>you need to cat all the jazz files into one file then uudecode and zoo them.

>i.e. 
>$cat jazzbench.zu1 > jazzbench.zuu
>$cat jazzbench.zu2 >> jazzbench.zuu
>$cat jazzbench.zu3 >> jazzbench.zuu
>$cat jazzbench.zu4 >> jazzbench.zuu
>$uudecode jazzbench.zuu
>etc.

Gak!  How awkward and tedious...

1. cat(1) accepts any number of file arguments, so

cat jazzbench.zu1 jazzbench.zu2 jazzbench.zu3 jazzbench.zu4 > jazzbench.zuu

would have the same effect.

2. uudecode(1) will work equally well from its standard input instead
of being given a filename, so

uudecode < jazzbench.zuu

will work the same (this isn't particularly useful) and

cat jazzbench.zu1 jazzbench.zu2 jazzbench.zu3 jazzbench.zu4 | uudecode

will also work identically, saving the temporary file space and the
hassle of deleting it, etc.

3. The Unix shell (csh or sh) will sort filenames matched with
wildcards (the csh {...,...} form is an exception to this rule), so

cat jazzbench.zu? | uudecode

will match all four sections, sort the filenames, concatenate them and
decode them.

In cases where there are 10 or more sections, if parts 1-9 are
numbered as ...01 through ...09, then using ?? to match the numbers
will still sort them correctly.  (remember, this is an alphabetical
sort)  If numbered ...8, ...9, ...10, etc. then use ...? ...?? for the
patterns.  For example:

Given a 12-part zuu file, big.zuu.  (big.zu1, big.zu2, big.zu3,
big.zu4, big.zu5, big.zu6, big.zu7, big.zu8, big.zu9, big.zu10,
big.zu11, big.zu12.)

cat big.zu* | uudecode

expands to:

cat big.zu1 big.zu10 big.zu11 big.zu12 big.zu2 big.zu3 big.zu4 big.zu5 big.zu6 big.zu7 big.zu8 big.zu9 | uudecode

resulting in a corrupted big.zoo file.  (parts 10-12 end up between 1
and 2 instead of at the end)  [uudecode will probably either truncate
the file or error out, with the "end" line in the middle] on the other
hand,

cat big.zu? big.zu?? | uudecode

expands to:

cat big.zu1 big.zu2 big.zu3 big.zu4 big.zu5 big.zu6 big.zu7 big.zu8 big.zu9 big.zu10 big.zu11 big.zu12 | uudecode

which is correct.

Is that crystal clear now?

[please don't tell me that wasn't verbose enough!  ;-)]

Deven
--
shadow@[128.113.10.2]   <shadow@pawl.rpi.edu> Deven T. Corzine (518) 272-5847
shadow@[128.113.10.201] <shadow@acm.rpi.edu>  2346 15th St.    Pi-Rho America
deven@rpitsmts.bitnet   <userfxb6@rpitsmts>   Troy, NY 12180-2306  <<tionen>>
"Simple things should be simple and complex things should be possible." - A.K.