From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: biz.sco.binaries
Organization: BC News and Mail
Date: Tue, 6 Oct 1992 07:04:24 GMT

biz.sco.binaries                                                Stuart Lynne
Wimsey Information Technologies                 Sat Oct 03 23:59:46 PDT 1992

                biz.sco.binaries Postings/Submissions Policies
                                 & Installation Overview

                Stuart Lynne (sl@wimsey.bc.ca), moderator


INTRODUCTION

biz.sco.binaries (BSB), is a newsgroup in the BIZ hierachy created for the
purpose of distributing programs in executable binary-code format for
SCO XENIX, SCO UNIX, and SCO ODT.


WHAT TO SUBMIT

Programs that are of general use or interest to many people are good
submissions. Programs that would only be useful to a select group of people
would not be ideal, because of the method of distribution and costs
involved.


HOW TO SUBMIT

All submissions should be in the form of custom installable disk images.

By preference the custom installable disk images should be uploaded to
ftp.wimsey.bc.ca. 

Contact the moderator before mailing submissions.


POSTING POLICIES

Use the posted programs at your own risk. Neither the author nor the moderator
accept any responsibility for damage or loss of data resulting from the use of
any posted program.

Anything that is of interest will be posted. Utilities are usually considered
to most useful. Games will be posted as well, but utilities get top billing.

Please make an effort to insure that what you have is the latest version.
Out-of-date programs slow down the process.



QUESTIONS

Questions should be referred to bsb-request@wimsey.bc.ca



FORMAT

Archives

The BSB archives will be organized by topic. For example:

        mail
        news
        networking
        utilities
        editors

Within each directory will be a directory that is the name of the package:

        mail/welm

And within that directory the disk images, and the most current 
posted version that has been split and uuencoded will be found. 

        mail/welm/welm.1.0.0b.01
        mail/welm/welm.1.0.0b.02

The posted version will have the 1.2MB floppy disk images split into 60 parts. 
Each part will be uuencoded. The file will contain the the posting information.


        Posting-number: Volume 13, Issue 354
        Testing-level: 1 (tested by moderator)
        Minimum-SCO-Version: SCO ODT 2.0
        Submitted-by: Stuart Lynne
        Archive-name: mail/welm/1.0.0b/disk2.57


Posting

  1) The release is stored into a series of 1.2MB disk image files:

	  files = package.version.disk_number
	  package = custom package product identifier [<8 chars]
	  version = major.minor.rev
	  major = [0-9]
	  minor = [0-9]
	  rev = [0-9][a-z]
	  disk_number = [0-9][0-9]

  2) This is split into twenty 60kb files:

	  package/version/package.[0-9][0-9].[01][0-9]

  3) This is uuencoded and prepended with release information:

	  package/version/package-[0-9][0-9].[01][0-9]

  4) This is posted to biz.sco.binaries



RE-ASSEMBLY and INSTALLATION

To re-assemble: 

  1) Using the Archive-name: header to save into your archive area:

	  Archive-name: topic/pack/ver/pack-[0-9][0-9].[01][0-9]

  2) Use uudecode to recreate disk images to recreate:

	  package/version/package.[0-9][0-9].[01][0-9]

  eg:
	  cd biz.sco.binaries/topic/package/version
	  for i in *[0-9][0-9].[01][0-9]
	  do
	  echo uudecoding $i
	  uudecode < $i
	  done

  3) Recreate the disk images:

	  package/version/package.[0-9][0-9]

  eg:
	  cd biz.sco.binaries/topic/package/version
	  for i in 01 02 03 04 05 06 07 08 09
	  do
	  [ -f package.$i.01 ] || break
	  cat package.$i.* > package.$i
	  done

  4) Check the checksums of the disk images:

	  cd biz.sco.binaries/topic/package/version
	  sum -r package.[0-9][0-9]


To install: 

You must use the custom command. It requires that the disk images
be copied to a floppy or a block special device prior to using. If you want
to speed custom up you can use a RAM disk or small empty disk partition. 
Simply run custom from one window and copy the required disk images to the
block special device before hitting enter in the custom screen (when asked
to insert disk, switch to the copy screen and copy the disk image).

Two scripts are available that help with this, ddcust assumes that you have
a small disk partition called /dev/custom (it must be 1200 blocks in size
and does not need a file system, use divvy to allocate).  ramcust will 
allocate a temporary RAM disk.

The syntax for invoking custom varies depending on which device you have copied
the disk images to. 'custom' defaults to /dev/install which in most cases is 
linked to /dev/fd0. When using an alternate block special device, custom must
be invoked with the -m</dev/somedevice> argument. For example, if the block
special device is /dev/custom then you would use the following syntax:

        custom -m/dev/custom


ACKNOWLEDGMENTS

This document was adapted from the Postings/Submissions Policies of
biz.sco.sources (moderated by Michael P. Deignan) which in turn was 
adapted from a document of the same name from the comp.binaries.ibm.pc
newsgroup (moderated by Brian O'Neill).

------- Cut Here for ddcust and ramcust scripts -----
#! /bin/sh
# This is a shell archive.  Remove anything before this line, then unpack
# it by saving it into a file and typing "sh file".  To overwrite existing
# files, type "sh file -c".  You can also feed this as standard input via
# unshar, or by typing "sh <file", e.g..  If this archive is complete, you
# will see the following message at the end:
#		"End of shell archive."
# Contents:  README.CUSTOM ddcust ramcust
# Wrapped by sl@vanbc.wimsey.bc.ca on Sat Oct  3 23:56:53 1992
PATH=/bin:/usr/bin:/usr/ucb ; export PATH
if test -f 'README.CUSTOM' -a "${1}" != "-c" ; then 
  echo shar: Will not clobber existing file \"'README.CUSTOM'\"
else
echo shar: Extracting \"'README.CUSTOM'\" \(1509 characters\)
sed "s/^X//" >'README.CUSTOM' <<'END_OF_FILE'
XFooling CUSTOM							Stuart Lynne
XWimsey Information Technologies			Sat Oct 03 23:50:31 PDT 1992
X
X
XUnfortunately SCO's custom(adm) does not currently support installing software
Xfrom anything other than a floppy disk, or specially prepared cartridge tape
Xand CD ROM's.
X
XWhen you obtain installable software via the network it is annoying to copy
Xthe disk images out to floppy disk just so that custom(adm) can copy it back
Xin again.
X
XThere are several solutions which are faster. If you have enough memory or
Xcan allocate a small disk partition you can simply use a second screen to
Xcopy the individual disk images to either an unused disk partition or
Xtemporary RAM disk. Custom is given the name of the special device you are
Xusing and copies the data from that. At each point that custom asks for a
Xspecific disk in the floppy drive simply copy that file to the RAM disk or
Xdisk partition.
X
XThis file should come with two sample scripts: ramcust and ddcust which will
Xshow you how this can be done. The first allocates a RAM disk and copies the
Xspecified files to it. Pausing in between each image.
X
XCall custom like:
X
X	custom -m /dev/ram200
X	custom -m /dev/rcustom
X
XThis solution is very fast. It's only down side is having to find room on
Xyour disk for a small partition or enough RAM to allocate the RAM disk.
X
XBoth ramcust and ddcust are called with the prefix of the set of files you
Xwish to install. For example if you had a three disk set called foo.0[123]
Xthen:
X
X	ramcust foo
X
Xwould be sufficent.
X
END_OF_FILE
if test 1509 -ne `wc -c <'README.CUSTOM'`; then
    echo shar: \"'README.CUSTOM'\" unpacked with wrong size!
fi
# end of 'README.CUSTOM'
fi
if test -f 'ddcust' -a "${1}" != "-c" ; then 
  echo shar: Will not clobber existing file \"'ddcust'\"
else
echo shar: Extracting \"'ddcust'\" \(254 characters\)
sed "s/^X//" >'ddcust' <<'END_OF_FILE'
X#!/bin/sh
X
X
Xfor i in $1.[0-9][0-9]
Xdo
X    echo "Press return to copy $i to /dev/rcustom:\c "
X    read j
X    echo
X    echo "Copying $i to /dev/rcustom ....\c"
X    dd if=$i of=/dev/rcustom bs=100k 2>/dev/null >/dev/null
X    echo " ... done"
X    echo
Xdone
X
END_OF_FILE
if test 254 -ne `wc -c <'ddcust'`; then
    echo shar: \"'ddcust'\" unpacked with wrong size!
fi
chmod +x 'ddcust'
# end of 'ddcust'
fi
if test -f 'ramcust' -a "${1}" != "-c" ; then 
  echo shar: Will not clobber existing file \"'ramcust'\"
else
echo shar: Extracting \"'ramcust'\" \(3355 characters\)
sed "s/^X//" >'ramcust' <<'END_OF_FILE'
X#!/bin/sh
X#	@(#) ramcust.sh - allow installation of files from a RAMDISK
X#	@(#) V. 1.0 - Sept 5, 1992 - The CEN-TA Group 
X#	writen by Richard Pitt - richard@centavx.wimsey.bc.ca
X#	based on ddcust by Stuart Lynne - sl@wimsey.bc.ca
X#	NOTES:  There are no checks on whether a RAMDISK is already in use.
X#		There is no validity check on a substitue drive number if
X#		entered.
X#
Xif [ "$1" = "" ]
Xthen echo "
X
XUsage: `basename $0` basefilename
X
XWhere basefilename is the name of the package being installed using 
Xthe CUSTOM(ADM) installation script from a RAMDISK instead of a real
Xfloppy disk or tape. The files used (in order) are:
X	basefilename.[0-9][0-9]
X
Xexample:	Files are:	test.1.0.01
X				test.1.0.02
X				test.1.0.03
X
X	basefilename would be:	test.1.0 "
X	exit
Xfi
X#	clear the screen
Xclear
XSLEEPTIME=1200		# may be changed if not long enough
X#	Minor number means a temporary 2 Megabyte RAMDISK - drive 0
XDEVMINOR=56
X#	following takes advantage of SCO's standard installation of
X#	a 64k RAMDISK during installation - it finds the Major Number
XDEVMAJOR=`l /dev/ram00 | cut -c33-36`
XDEVICE=/dev/ram2000
Xif [ "$DEVMAJOR" -eq "" ]
Xthen
X	echo "Can't find Major Device Number for RAMDISK - exiting"
X	exit
Xfi
X
Xecho <<EOSTUFF "
XThis install script tries to allocate a RAMDISK of 2 Megabytes in order to
Xinstall the software from the hard disk without using a real floppy disk
Xdrive. This drive is not permanent - it disappears 20 minutes after the 
Xscript has STARTED.
X
XNOTE: if there is not a contiguous 2 Megabytes of free RAM in your system, 
Xthe script will fail. Try stopping one or more applications that are
Xcurrently running - log out users, etc. If this is not acceptable, try
Xrunning this script very soon after the system has been re-booted, when 
Xthere is more likely to be a free 2 Megabytes of RAM all in one piece.
X
XRAMDISKS are allocated from 0 to 7 - if you already have a RAMDRIVE 0 - please
Xenter a number from 1 to 7 to allocate a different RAMDRIVE number that is
Xnot currently in use - this script does not have any way of checking if a
XRAMDRIVE is currently in use!
X
XOnce you have been prompted to copy the first file to the RAMDRIVE, go to 
Xanother screen and run 'custom -m /dev/ram2000' to install using custom from
Xthe RAMDRIVE. After each disk image has been installed by custom, return to
Xthis screen and press <ENTER> to load the next ...etc. ...etc. ...etc.
X
XPress <ENTER> to continue or enter a new RAMDRIVE number: \c"
XEOSTUFF
Xread garb
Xecho
Xif [ "$garb" -eq "" ]
Xthen
X	:
Xelse
X	rm -f $DEVICE
X	DEVMINOR=`expr 56 + $garb`
Xfi
Xif [ -b $DEVICE ]
Xthen
X	:
Xelse
X	mknod $DEVICE b $DEVMAJOR $DEVMINOR
Xfi
X#while ( while true
X#	do
X#	read stuff < /dev/null
X#	done < $DEVICE & )
X#do
Xwhile ( (sleep $SLEEPTIME) < $DEVICE & )
Xdo
X	PID=$!
X	HERE=`pwd`
X	THERE=`dirname $1`
X	FILE=`basename $1`
X	cd $THERE
X	for i in $FILE.[0-9][0-9]
X	do
X    		echo "Press <ENTER> to copy $i to the RAMDISK:\c "
X    		read j
X    		echo
X    		echo "Copying $i to $DEVICE ....\c"
X    		dd if=$i of=$DEVICE bs=100k 2>/dev/null >/dev/null < /dev/tty
X    		echo " ... done"
X    		echo
X	done
X	cd $HERE
X	echo "
X	Press <ENTER> when CUSTOM has finished installing last disk\c"
X	read garb
X	echo "
X	De-allocating RAMDISK"
X	kill -1 $PID
X	echo "$1: finished"
X	exit
Xdone
Xecho "Can't allocate RAMDISK - please stop some processes and try again,
Xor try again very soon after a re-boot"
X
END_OF_FILE
if test 3355 -ne `wc -c <'ramcust'`; then
    echo shar: \"'ramcust'\" unpacked with wrong size!
fi
chmod +x 'ramcust'
# end of 'ramcust'
fi
echo shar: End of shell archive.
exit 0
-- 
Stuart Lynne <sl@wimsey.bc.ca> ....................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................. ftp.wimsey.bc.ca:~ftp/ls-lR.Z
PD Software for SCO UNIX .................. ftp.wimsey.bc.ca:~ftp/pub/wimseypd
Newsgroups: biz.sco.general