If your host doesn't have an appropriate tape drive, you may still be able to install your software. Check with your system administrator to see if another machine at your site has a tape drive you can use. If so:
ln -s shared /usr/cygnusRun
Install
from the machine with a tape drive, using the
`extract' argument and the `-installdir' option:
Install extract -installdir=sharedYou still have to finish the installation, but the last two steps (
fixincludes
and test
)
must be run on your host. (If you forget, there's no great harm done:
Install
notices that it can't carry out a full installation on
the wrong machine, and stops with an error message--then you can go
back and try again. When Install
notices a problem like this, it
doesn't carry out any action other than giving a helpful error
message).
Unless you are installing a cross-development tape (the tape label says
`target = target' for cross configurations), the
`fixincludes' part of the installation is essential. Please see
the full explanation (see section Why convert system header files?), if you're curious.
On a machine on your network with a tape drive: ./Install extract -installdir=shared/cygnus ... On your host ln -s shared/cygnus /usr/cygnus cd /usr/cygnus/progressive-95q4If your copy of the Developer's Kit is configured native (to develop software for the same type of machine where the Developer's Kit itself runs), you'll have to run `Install fixincludes' and `Install test' from your host afterwards.
Native configurations only: ./Install fixincludes test
uucp
), read the second file on the tape using a system
utility (for instance, dd
on Unix systems; see the system
documentation for the machine with a tape drive). There are two files
on the distribution tape; the first contains just the Install
script in uncompressed tar
format, and the second is a compressed
tar
format file containing the rest of the release.
Read both of these files separately, using something like the following:
eg$ tar xvf non-rewinding-tape-device Install Install eg$ dd if=non-rewinding-tape-device of=tarfile1 bs=62k messages from dd... eg$ ls Install tarfile1and then transfer them to your own machine using
uucp
,
ftp
, or another appropriate file transfer tool. (The blocksize
is set to 62k in this example simply to speed up the process; the tape
is written with a blocksize of 62k, but dd
should be able to cope
with the task using its default blocksize.)
Then run Install
, but use `-tape=tarfile' to specify
the name of the installation file, instead of
`-tape=device' as shown in the examples. In the simplest
case, for example (starting after you've transferred Install
and
the tar file to your system):
eg$ ./Install -tape=tarfile1