Installable disk(s) and files (UNIXPC)

[Thad P Floryan]

horn at rt5.cs.wisc.edu (Mark Horn) in <4319 at daffy.cs.wisc.edu> writes:

"	I have another Q.  What is the process for making installable
	floppies?  I have Interrnet access so it was rather easy for me to get
	the recent FIXDISK.  A friend of mine doesn't have internet access so
	it's hard for him to get that self same FIXDISK.
	.... "

Actually, the procedure to make an installable file or disk (on UNIXPC) is:

	$ cat file.of.files | cpio -ocdBv > FILE+IN
or	$ cat file.of.files | cpio -ocdBv > /dev/rfp021

where the ``file.of.files'' file simply contains the list of files to be
included, one file name per line (including a directory path when/if
necessary, though most installable cpio archives have a relative path (i.e.
"etc/foo.file" instead of "/etc/foo.file") from which the file(s) are later
moved during the actual install process.

If you look at the contents of the INSTALLDOC+IN file that was available on
"The STORE!" (and now available from the alfred archives), all the details of
creating installable applications are documented.

In essence, the installable archive (either file or disk) contains certain
"key" files referenced and used by the install script(s) on the UNIXPC; some
of the files are Size, Install, Files, Remove, etc.  Suggest you look at
several extant FILE+IN archives to get an idea what's going on.

An installable disk(s) or file can be easily processed (note that "FILE+IN"
below can be replaced with "/dev/rfp021" (on UNIXPC)) per:

view contents:			$ cpio -ictBv < FILE+IN

restore contents to curr. dir:	$ cpio -icBdum < FILE+IN

another way to create one:	$ find . -print | cpio -ocB > FILE+IN


Thad Floryan [ thad at cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]