Very Computer

Follow-ups to comp.unix.questions.  If there is sufficient interest, I'll
post a summary on those e-mail responses(If you have objection to posting
any part of your e-mail to the world, please indicate in your mail.
Otherwise I may include part or whole of your reponses to the world if
a summary is requested).

Thanks very much for your time and help.
-- Jun
--


-- Purdue University               UUCP:    {...hplabs!}pur-ee!luj      --
-- W. Lafayette, IN 47907          Phone:317-494-9410  Fax:317-494-0307 --

(btw, it was originally written in sh, then translated into rc. It is based
on the bundle(s) described in K&P)

#!/bin/rc
# bundle: group files into distribution package

echo '#' to unbundle, sh this file
echo '#' bundled by `whoami on `hostname at `date

echo '#' contents of bundle:
for (i)
        echo '#' $i

for (i) {
        echo echo $i
        echo 'sed ''s/^-//'' > '$i' <<''end of '$i''''
        sed 's/^/-/' $i
        echo end of $i

Quote:}

One thing to consider is safety.  If the shar goes haywire you don't
want it trashing your files (or creating things like .rhosts files).
The vanilla shar in K&R works well, and it's a great example of a
recursive script to traverse a file hierarchy, but it doesn't do
anything to insure that the shell commands it uses to unpack the files
won't wreak havoc.

The safer archivers generate sed scripts rather than shell scripts.
Their disadvantage is that the raw archives tend to be bigger and a
bit less easily read.

-r