This section explains how to install LispWorks, having already mounted the CD-ROM. If you have not done this, refer to The CD-ROM. It also describes how you obtain keys to run LispWorks 7.1.
Once the CD-ROM is mounted, you can begin to unpack the tar files for the products you have purchased. You will need root access to do this.
There are subsections below explaining the process for each supported platform.
When you extract files made with the tar command, they are written into the current directory, and if there are any directories packed up in the tar file, they will be written to the current directory too. For this reason it is best to cd to the correct directory before extracting anything.
Consider who is going to use LispWorks before you decide where to put the extracted files. Once installed and configured, the executable Lisp image should be somewhere in the UNIX file system likely to be on its users' search path. A suitable place might be /usr/local/bin/lispworks.
The run time directory structure (basically, everything except the image file) should be somewhere publicly readable: /usr/lib/lispworks, by default. If there is not enough room in any of the normal publicly accessible locations, you could put a symbolic link there pointing to an installation directory in a partition with more disk space.
To extract the product files from the tar container files, the basic form of the call to tar is:
tar -xof /mount-point/filename
The flag x means extract files from tar-formatted data, and f specifies that the source of the data will be a file.
mount-point is the point in the UNIX filesystem at which the CD-ROM is mounted, while filename is the name of the tar file containing the product files.
For example, to extract the files for LispWorks (32-bit) on SPARC Solaris, with the CD-ROM mounted at /cdrom/lw_71/, you would type
tar -xof /cdrom/lw_71/lw71-sparc.tar
This section applies only to 32-bit LispWorks for SPARC Solaris.
LispWorks is protected against unauthorized copying and use by a simple key protection mechanism. LispWorks will not start up until it finds a file containing a valid key.
The image looks for a valid keyfile in the following places, in order:
keyfile.hostname in the current working directory, where hostname is the name of the host.keyfile in the current working directory, where hostname is the name of the host.config/keyfile.hostname, where hostname is the name of the host on which the image is to execute. The config directory is expected by default to be located at /usr/lib/lispworks/lib/7-1-0-0/config (see If you are using the keyfile system.config/keyfile, where the config directory is as above.
The directory config is an indirect subdirectory of the directory specified by the LispWorks variable *lispworks-directory*. Note that until you have configured and saved your image, as described later in this section, this variable is set to /usr/lib/lispworks. When starting the generic image, you must therefore ensure that the keyfile is either in your current directory or in /usr/lib/lispworks/lib/7-1-0-0/config.
If you try to run LispWorks without a valid key, a message will be printed reporting that no valid key was found, and LispWorks will exit.
Keyfiles contain one or more keys. A key is a sequence of 28 ASCII upper case letters and digits between 2 and 9, inclusive.
Each key should be placed on a separate line in the file. There should be no leading white space on a line before the start of a key. Characters after the key but on the same line as it are ignored, so may be used for comments. Indeed it is helpful to comment each line with the name of the product that key enables.
Key files for more than one host can exist in the same keyfile.
A single key allows you to use a particular major version of LispWorks (in this case 5), on one host machine, until the expiry date of one license, where relevant. To run LispWorks on a different machine you will need another key.
Delivery, KnowledgeWorks, LispWorks ORB and CLIM 2.0 each need their own keys.
To obtain your keys, contact Lisp Support.
You can get your key by phone, fax or email. Every key is unique: in order to generate keys, we need to know the unique ID of the machine on which you intend to run LispWorks.
To find out your machine's ID, try to start up the LispWorks image. LispWorks spots that there is no valid key available, and prints a message saying so, along with the ID you need to let us know. In any case, Lisp Support will be able to provide assistance in determining the identifier of a specific machine. We will also retain a copy of the key supplied.
Send email containing the message printed to
lisp-keys@lispworks.com
. Or contact Lisp Support as described in Reporting bugs.
Once you have the key, write it into a file in one of the places listed in Where LispWorks looks for keyfiles, and start up the LispWorks image.
This section applies only to LispWorks (32-bit) for SPARC Solaris. There is no license server for LispWorks (64-bit) for SPARC Solaris.
If you prefer, you can run LispWorks using the License Server instead of the keyfile system. This system will control license allocation across your LAN, and you may find it more convenient.
See the LispWorks Guide to the License Server for full details.
As with the keyfile system, you will need to contact Lisp Support to obtain the necessary permissions.
LispWorks Release Notes and Installation Guide - 19 Oct 2017