Understanding Quick Installation
The INSTALL scripts for both Xi-Text and Xi-Batch support non-interactive installation through command-line options. This approach enables scripted deployments, automated installations across multiple systems, and consistent configuration without manual intervention.
Installation Script Locations
Three levels of INSTALL scripts exist:
Initial/temporary directory : Copies files from media to distribution directory
Distribution directory level : Located in /usr/spool/xi_distrib (or custom base), runs product-level scripts
Product level : Located in /usr/spool/xi_distrib/Text or /usr/spool/xi_distrib/Batch, installs specific product
Quick Installation Requirements
To use non-interactive installation, you must specify the -q option. Without this flag, the script runs interactively regardless of other options provided.
Common Installation Options
Xi-Text Quick Install Options
bash
-q # Quick install (required for non-interactive) -C # Create missing directories automatically -f # Force installation even if appears done -d # Delete old installations instead of saving -s # Halt existing Xi-Text if running -l # Non-network licence -n # Network licence -L # Full licence (not 30-day trial) -x # Autoload full licence key -S # Do not install system start routine -N # Stop after copying (initial install only) -b directory # Specify base directory (default: /usr/spool) -u directory # Specify user programs directory (default: /usr/local/bin) -a directory # Specify app-defaults directory for X programs -h # Display help message and exit
Xi-Batch Quick Install Options
Options are similar to Xi-Text with product-specific variations. Consult the Xi-Batch Quick Start Guide for complete option list.
Example Installation Commands
Complete automated installation with network licence:
bash
./INSTALL -q -C -f -L -n -s -x
This command:
- Runs in quick (non-interactive) mode
- Creates any needed directories
- Forces new installation
- Sets full networked licence
- Halts any existing version
- Downloads licence key automatically
Custom base directory installation:
bash
./INSTALL -q -C -f -b /opt/xi -u /opt/xi/bin -L -n -x
This installs to /opt/xi instead of default /usr/spool with user programs in /opt/xi/bin.
Trial licence installation without network:
bash
./INSTALL -q -C -f -l -s
Installs with 30-day trial, non-networked licence.
Installation Flow
Initial INSTALL script : Copies files from media to distribution directory, then automatically invokes distribution-level INSTALL
Distribution-level INSTALL : Runs product-level INSTALL scripts for each product in turn
Product-level INSTALL : Performs actual installation of binaries, configuration files, and system integration
When to Run Which INSTALL
Initial INSTALL (from media/scratch directory) : First installation, changing base directory, or new version installation
Distribution directory INSTALL : Routine reinstallation, applying configuration changes, or installing additional products
Product directory INSTALL : Reinstalling single product without touching others, forcing reinstall that appears already done
User Account Prerequisites
The installation script checks for system user spooler (Xi-Text) or batch (Xi-Batch). If missing and an Installuser script is available, it runs automatically during quick installation.
Create the user manually beforehand if preferred:
bash
# Create spooler user for Xi-Text useradd -r -s /bin/false -d /var/spool/xi spooler # Create batch user for Xi-Batch useradd -r -s /bin/false -d /var/spool/xi batch
Network Setup
For networked installations (-n option), the installation:
- Adds service entries to /etc/services
- Launches host editor (hostedit) for configuring remote hosts
- Installs network licence
The host editor runs even in quick mode for initial network setup. Configure hosts during first networked installation.
Post-Installation
After quick installation completes:
Verify installation:
bash
# For Xi-Text spstart spq -H # For Xi-Batch btstart btjlist -H
Check version:
bash
# For Xi-Text whatvn /usr/spool/progs/spshed # For Xi-Batch whatvn /usr/spool/progs/btsched
Review system log:
bash
# For Xi-Text tail /var/spool/spd/spshed_reps # For Xi-Batch tail /var/spool/xi/batch/btsched_reps
Combining Options
Options can be combined to match specific requirements:
bash
# Production deployment: custom paths, network, full licence ./INSTALL -q -C -f -b /app/xi -u /app/xi/bin -L -n -x -s # Test environment: default paths, trial licence, no network ./INSTALL -q -C -f -l # Reinstall without changing licence or network config ./INSTALL -q -f -s
Troubleshooting Quick Installation
Installation appears to hang : Check if licence download (-x) is waiting for network access. Omit -x and install licence manually with vwrite command.
"Already installed" message despite -f option : You may be running distribution-level INSTALL. Navigate to product directory and run INSTALL there.
Permission errors : Ensure running as root. Check that spooler or batch user exists with correct permissions.
Service entries not created : Verify root privileges. Check /etc/services isn't read-only. Review system log for errors.
Scripting Installations
Quick installation enables deployment scripts:
bash
#!/bin/bash
# deploy-xitext.sh
# Configuration
BASE_DIR="/opt/xi"
USER_BIN="/opt/xi/bin"
LICENCE_KEY="your-licence-key"
# Prepare
mkdir -p "$BASE_DIR" "$USER_BIN"
# Install
cd /tmp/xi-dist/Linux-ubuntu_64
./INSTALL -q -C -f \
-b "$BASE_DIR" \
-u "$USER_BIN" \
-L -n -s
# Configure licence if not auto-downloaded
if [ -n "$LICENCE_KEY" ]; then
echo "$LICENCE_KEY" | vwrite -
fi
# Verify
spstart
spq -H && echo "Installation successful"
Best Practices
Always specify -C : Prevents failures from missing directories
Use -f for reinstalls : Ensures fresh installation even if system thinks it's done
Stop running instances with -s : Prevents conflicts during upgrade
Backup before -d : The delete option removes old installations permanently
Test without -L first : Use trial licence for testing before committing to full licence
Document custom paths : Non-default base or user directories require documentation for future maintenance