2.4 UNIX installation

Introductory remark for Linux-installation:
iXOS-JUKEMAN 2.3 runs on Red Hat Linux 5.0 with preinstalled LinuxThreads. However a modification of the SCSI-interface is required. To put this modification into effect, the kernel must be recompiled. This should be done by experienced Linux users only. Refer to the Linux documentation delivered with your system!
1. Open the file /usr/include/scsi/sg.h with a text editor.
2. Change the value of the constant SG_BIG_BUFF to at least (sizeof(struct sg_header)+12+32768).
3. Save the modified file.
4. Now the kernel needs to be rebuilt. Follow the instructions in your Linux documentation. Since the configuration varies among systems, we can give no general instructions. Take care to enable "generic SCSI support" when rebuilding the kernel.
If you have a different Linux distribution please keep in mind:
iXOS-JUKEMAN requires at least kernel version 2.0.32 as well as at least libc6 (equivalent to glibc2). LinuxThreads, a POSIX-conforming Thread package for Linux, must be installed.
Before you begin the UNIX installation, log on as root.
All the files needed for installation can be found on the iXOS-JUKEMAN CD-ROM or downloaded from the World Wide Web (see page 9). To download, follow the instructions on the web pages. Important files to be downloaded are the operating system-specific file and the file with configuration examples ('examples.tz').
The following table lists the operating system-specific files. These files are compressed 'tar' files. To avoid problems with Windows programs the extension of the files is .tz rather than .tar.Z.

If all files needed are available, installation may begin:
You will need about 4 MB of disk space for installation.
Create an empty target directory (e.g, jukeman):
mkdir <path>/jukeman
If you are using an iXOS-JUKEMAN CD-ROM, you will find the software packages for certain UNIX platforms in a subdirectory called 'os' or 'unix'. For instance, there is a file called solaris.tz for the Solaris platform. Change to the source directory where the software package for your UNIX platform is located.
Copy the file (e. g., solaris.tz) and the examples file (examples.tz) to the target directory, rename the file to solaris.tar.Z (and examples.tar.Z) and decompress the files. This can be done with the following commands:
cp solaris.tz <path>/jukeman/solaris.tar.Z
cp examples.tz <path>/jukeman/examples.tar.Z
cd <path>/jukeman
zcat solaris.tar.Z | tar xvf -
Now you have all the files except license files, device descriptions and configuration.
If you wish to update an earlier version, copy the old configuration files (server.cfg, *.dev, *.sav, *.lic) and the database volumes to the new target directory. For a first-time installation it is recommended to extract template configuration files by issuing the following command:
zcat examples.tar.Z | tar xvf -
The database volumes will be created by cdnfsd automatically. Now that you have all the relevant files, the tar files can be deleted:
rm *.tar.Z *.tz
Note that for further installation all jukeboxes connected to the host need to be operational in order to install the SCSI driver properly.
To install the SCSI driver:
jmsetup
This command installs both the SCSI driver, if needed, and the iXOS devices paths. Some older HP machines (800 series) may tell you to install the SCSI pass through kernel driver (see man scsi_pt(7)).
Since the cdnfsd program runs only under root id and the performance of cdglow is much higher under root id, change the owner to root and the permissions to suid:
chown root cdnfsd cdglow
chmod u+s cdnfsd cdglow
For HP-UX 10.* change the permissions for both the cdadm and the inquiry command:
chown root cdadm inquiry
chmod u+s cdadm inquiry
To set up the software, see "Setting up iXOS-JUKEMAN" on page 27.
If you only want to use the writer software, there is nothing else to set up. The software is described in the section "Burning disks" on page 137. If you have already received a license key for the writer software from your distributor, enter it in the file writer.lic as described in "How to enter license keys" on page 32.