⟦99eaf6c51⟧

TextFile

This is the README file mcsun.eu.net:~ftp/bootstrap/README.

This directory contains the source code of all programs needed to 
unpack files from the EUnet archives (and many other Unix archives too):

  btoa.shar		encode and decode binary files much like 
  			uuencode/uudecode but using less space and
			having no troubles with blanks

  compress.shar		compress files - and uncompress them again

  tar.shar.Z.1		the GNU version of the unix tar command for 
  tar.shar.Z.2		those poor System V users who don't have tar.



       A little guide to filename extensions in the archives
       -----------------------------------------------------

  .shar		shell archive

		This means a bunch of files has been compiled into one
		file. This has been done in a way that allows unpacking
		with the standard unix shell. This is done because a
		shell is available on any Unix system. Really!

		To unpack say 

			sh < thisfile.shar


  .tar		tape archive

		This means a bunch of files has been compiled with the
		tar program. This is the normal way of packing up a bunch
		of files.

		To unpack say

			tar xvf thisfile.tar


  .Z		This means a file has been compressed using the compress
		program. This saves storage space and transmission costs.

		To uncompress say

			uncompress thisfile.Z

		This will create an uncpompressed file named "thisfile"
		and delete thisfile.Z automagically.


  .tar.Z	This means a bunch of files has been packed with tar and then
		compressed. To uncompress and unpack do

		uncompress <thisfile.tar.Z | tar xvf -

		This will create the files from the archives and leave
		"thisfile.tar.Z" intact. If uncompress prints the error
		message 

			"stdin: not in compressed format"
		
		instead, dont despair quite yet.
		Sometimes .Z files have been encoded using btoa/atob in
		order to transmit them more easily along channels that 
		don't carry binary files. You can detect this by the fact
		that the file begins with the line

			xbtoa Begin

		In this case do
			
			atob <thisfile.tar.Z | uncompress | tar xvf -
		
		to unpack.

Other combinations of extensions like ".shar.Z" are possible but less 
frequent. The unpack algorithm for these is left as an exercise to the 
reader.



		Howe to unpack your unpacking kit
		---------------------------------

You will need approximately 1.5 MB of disk space and a machine that
can execute programs with at least 1.2MB of user memory.

The lines beginning with "$" below are examples of what you have to 
type to unpack all this.

First of all get all the files in directory mcsun.eu.net:~ftp/bootstrap
into a directory and change directory to there. Then do ls -l which should 
print something like this:


    $ ls-l
    total 223
    -rw-r-----  1 dfk          5449 Jul 30 12:25 README
    -rw-r-----  1 dfk          8783 Jul 30 12:10 btoa.shar
    -rw-r-----  1 dfk         56324 Jul 30 12:10 compress.shar
    -rw-r-----  1 dfk         77618 Jul 30 12:10 tar.shar.Z.1
    -rw-r-----  1 dfk         80509 Jul 30 12:10 tar.shar.Z.2

Then make a few subdirectories

    $ mkdir btoa
    $ mkdir compress
    $ mkdir tar
    $ mkdir bin

First build the btoa/atob encoding programs:

    $ cd btoa
    $ sh <../btoa.shar
    Start of atob/btoa, part 01 of 01:
    x - Makefile
    x - atob.c
    x - btoa.c
    x - btoa.man
    x - tarmail
    x - untarmail
    Part 01 of atob/btoa complete.
    $ make
    cc -O atob.c -o atob
    cc -O btoa.c -o btoa
    $ mv atob btoa ../bin

Then build the compress/uncompress program:

    $ cd ../compress
    $ sh <../compress.shar
    Start of compress, part 01 of 01:
    x - Makefile
    x - README
    x - USERMEM
    x - compress.c
    x - usermem.sh
    Part 01 of compress complete.

Now you will have to edit Makefile to reflect your machine and OS 
configuration. Read the README file as well. You may want to try
to run usermem.sh too. Afterwards do:

    $ make
    cc -O -DSACREDMEM=256000 -DUSERMEM=`cat USERMEM` -o compress compress.c
    rm -f uncompress
    ln compress uncompress
    $ mv compress uncompress ../bin

Now you have come quite a way. Lets see what we have created so far:

    $ cd ..
    $ ls -l bin
    total 112
    -rwxrwx---  1 dfk         24576 Jul 30 12:11 atob*
    -rwxrwx---  1 dfk         24576 Jul 30 12:11 btoa*
    -rwxrwx---  2 dfk         32768 Jul 30 12:12 compress*
    -rwxrwx---  2 dfk         32768 Jul 30 12:12 uncompress*

You may want to install those programs in /usr/local or some similar
directory to make them generally accessible.

OK, now for the last program: tar. We will unpack it using the
programs we have already made.

    $ cd tar
    $ ../bin/atob <../tar.shar.Z.1 | ../bin/uncompress | sh
    Start of tar, part 01 of 02:
    x - COPYING
    x - README
    x - buffer.c
    x - create.c
    x - extract.c
    x - port.c
    x - tar.c
    Part 01 of tar complete.
    $ ../bin/atob <../tar.shar.Z.2 | ../bin/uncompress | sh
    Start of tar, part 02 of 02:
    x - Makefile
    x - diffarch.c
    x - getdate.y
    x - getoldopt.c
    x - getopt.c
    x - getopt.h
    x - getopt1.c
    x - list.c
    x - msd_dir.c
    x - msd_dir.h
    x - names.c
    x - open3.h
    x - port.h
    x - rmt.h
    x - rtape_lib.c
    x - rtape_server.c
    x - tar.h
    x - update.c
    x - version.c
    x - wildmat.c
    Part 02 of tar complete.
    $

So far the unpacking. Configuring and building tar is left as an exercise
to the reader again.
DataMuseum.dk

DKUUG/EUUG Conference tapes

⟦99eaf6c51⟧ TextFile

Derivation

TextFile
