Release notes

Every entry names the releases it applies to. Where a change affects how a system behaves rather than only what it contains, the reason is given as well as the change.

Downloads and licence renewal are in the customer portal.

Upgrading an rpm installation of Xi-Batch 1.7.0 or Xi-Text 1.24.1

Critical · Installations from the Xi-Batch 1.7.0 and Xi-Text 1.24.1 rpm packages; resolved in Xi-Batch 1.9.3 and Xi-Text 1.25.6

Changes

• Xi-Batch 1.9.3 and Xi-Text 1.25.6 upgrade a 1.7.0 / 1.24.1 rpm installation in place: the new package declares the earlier package names as the package it replaces, sets the configuration, licence, spool directories and service user aside before rpm removes the old package, restores them afterwards, and starts the service.
• Before these releases an upgrade from a 1.7.0 / 1.24.1 package was refused with file conflicts, because those packages carry a different rpm package name: they were issued as standard, and as xibatch_legacy_standard or xitext_legacy_standard. Packages from 1.9.0 / 1.25.0 onward are named xibatch_standard and xitext_standard. Check yours with rpm -qa | grep -i -E 'xibatch|xitext|^standard-'.
• Removing a 1.7.0 / 1.24.1 package deletes the installation. Its removal step deletes, for Xi-Batch: the configuration files /etc/xi/batchconfig and /etc/xi/batch-hosts, the licence file /usr/libexec/xi/.xibatch.lic, the spool directories /var/spool/xi/batch and /var/spool/xi/btuds and everything in them, and the batch service user. For Xi-Text: /etc/xi/textconfig, /etc/xi/text-hosts, /etc/Xitext-extern, the licence file /usr/libexec/xi/.xitext.lic, the spool directories /var/spool/xi/spd, /var/spool/xi/spuds and /var/spool/xi/printers and everything in them, and the spooler service user.
• Packages of 1.9.0 and later and 1.25.0 and later upgrade to 1.9.3 / 1.25.6 directly, as before.

Intent and impact

rpm treats a changed package name as a different package, so a 1.7.0 / 1.24.1 installation could be neither upgraded nor replaced without losing it. The upgrade was refused with file conflicts. Removing the old package first, which is the obvious way round that, runs its removal step: that deletes the configuration files, the licence file, the spool directories with any queued jobs in them, and the service user, as listed above. It reports nothing: the command succeeds and the files are gone. An installation on one of those packages therefore had no supported way to reach a later release. From 1.9.3 / 1.25.6 the new package names the earlier ones as what it replaces and carries the installation across itself. Verified against the 1.7.0 and 1.24.1 packages under both of their earlier names: after the upgrade only the new package is installed, the configuration and licence are in place, and the service is running.

Until 1.9.3 / 1.25.6 is installed, stay on the installed package - it keeps running, and it must not be removed. If a later package has to go on before then, copy aside everything the removal deletes and put it back afterwards, with the service stopped throughout:

1. Note the service user's ids: id batch (Xi-Text: id spooler).
2. Copy aside: /etc/xi/batchconfig, /etc/xi/batch-hosts, /usr/libexec/xi/.xibatch.lic, /var/spool/xi/batch, /var/spool/xi/btuds (Xi-Text: /etc/xi/textconfig, /etc/xi/text-hosts, /etc/Xitext-extern, /usr/libexec/xi/.xitext.lic, /var/spool/xi/spd, /var/spool/xi/spuds, /var/spool/xi/printers).
3. systemctl stop xibatch (or xitext), remove the installed package with rpm -e <name>, install the new package with rpm -i <package>.
4. If id batch now shows a different uid, re-create the user with the noted uid and gid before the next step (userdel batch; useradd -r -d /var/spool -u <uid> -g <gid> batch).
5. Put the copies back, chown -R batch /var/spool/xi/batch /var/spool/xi/btuds (Xi-Text: spooler and its three directories), then systemctl start xibatch.

A drop-in under /etc/systemd/system/xibatch.service.d/ is untouched by any of this and stays in force.

Package upgrade keeps the service running

High · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• An rpm upgrade (rpm -U, dnf upgrade) onto 1.9.3 / 1.25.6 from 1.9.1 / 1.25.4, or any earlier package named xibatch_standard / xitext_standard, ends with the service unit present, enabled and started.
• From 1.9.3 / 1.25.6 onward, an upgrade leaves an existing unit file as it finds it, edits included; only a removal deletes it.
• Packages issued in 2025 carry a different rpm package name (standard, or xibatch_legacy_standard / xitext_legacy_standard). 1.9.3 / 1.25.6 refuse to install beside or over one of those; how such an installation moves to the current release is described in the entry above.

Intent and impact

On an rpm upgrade the previous package's removal step runs after the new package's install step. Every earlier release stopped, disabled and deleted the service unit in that step unconditionally, so an upgrade left the scheduler or spooler stopped, disabled and without a unit file until someone noticed. 1.9.3 / 1.25.6 write, enable and start the unit in a final step that runs after the previous release's removal step, and their own removal step touches the service only on a removal. A direct edit to the unit file is still lost by the upgrade onto these releases, as the old package deletes the file; from these releases onward it is kept. Debian packages were not affected. Every package of this release was installed over the previous release (1.9.1 / 1.25.4) in a systemd container before it was published, and the build tooling now does so for every build. The 2025 packages under their earlier rpm names are a separate case, stated above.

Raspberry Pi and SUSE Linux Enterprise 15 added; Debian 11 retired

Info · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• New: Raspberry Pi OS 64-bit (Debian 12 on ARM64) as a Debian package, and SUSE Linux Enterprise Server 15 / openSUSE Leap 15.6 as an rpm.
• Unchanged: Red Hat Enterprise Linux 7, 8, 9 and 10 families (rpm) and Debian 12 and 13 (deb) on x86_64.
• Retired: Debian 11, whose security updates left the Debian mirrors on 31 August 2026.

Intent and impact

Each platform package is built in a clean image of that platform, installed in a clean system of it, upgraded in place over the previous release, started under systemd and exercised with jobs before it is published; the test report sits beside every package on the portal. Builds for POWER and IBM Z (Red Hat 9 and 10 families, Debian 12 and 13) have been verified the same way and are available on request; they are not published as routine releases.

Scheduler stop at a job start or completion resolved

Critical · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• Messages between the Xi-Batch scheduler and its execution workers are now sent as a single unit, so two senders can never interleave.
• The execution worker, not the job itself, reports a job's start, and a completion can never be reported before the start it belongs to.
• A malformed internal message is now reported with its cause rather than an unrelated system error.
• Xi-Text: the same single-unit send on the connection its network server shares, so overlapping requests to the programming interface no longer drop it.

Intent and impact

A customer's Xi-Batch scheduler stopped without warning up to twice a day, always at the instant one job started as another finished, and had to be restarted by hand. The cause was found in how the scheduler's worker processes send it their reports: each report went as two writes, and two workers reporting at the same instant could interleave them, leaving the scheduler with a message it could not read, at which point it stopped. Reports are now sent whole, and a second, independent guard orders a job's start before its completion. The same two-write pattern existed in Xi-Text on the connection shared by its network server, where overlapping requests could silently close the connection until the server was restarted; it is fixed the same way. Nothing changes in normal operation. Updating is recommended for every Xi-Batch installation, and for any Xi-Text installation that uses the network server.

Queue growth beyond the configured size now works

High · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• When the number of jobs, variables or printers exceeds the size allocated at start-up, the enlarged shared memory is now usable by every command.
• The scheduler's report file records its list capacities at start and each growth as it happens.
• Xi-Batch's "Cannot allocate any more jobs" message now says what the condition is and what to do.

Intent and impact

Both products grow their shared memory when a list fills beyond its start-up size. On Xi-Batch the grown segment was created with the wrong identity, so every command lost sight of the queue, and on some builds the scheduler stopped; on Xi-Text the grown segment kept the old identity, so every command reported that it could not read the job queue while the spooler ran on. The growth now hands over correctly, and the report file shows the capacities and each growth so an administrator can size the start-up allocation from evidence. Installations whose job, variable or printer counts stay within the start-up allocation never reached this code and see only the new report lines.

Scheduler and spooler explain a failure to start or stop

Medium · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• A fatal error in the scheduler or spooler is now written to the system journal as well as to its report file.
• A failure at start-up names its cause, for example a missing licence file, instead of reporting that the control file could not be opened.
• The tarball installer writes the same service unit as the packages: Xi-Batch's now restarts the service on failure; Xi-Text's carries the stop timeout that lets printers finish cleanly.
• Xi-Text logs the network ports it resolved at start, warns when its network server could not start, and says so when a port came from an unexpected services entry.
• Xi-Text: a leftover diagnostic handler that made an abnormal termination look like a normal exit is removed, as it was for Xi-Batch in 1.9.1.

Intent and impact

When a service stopped, the reason was in a report file in the spool directory and nowhere else, and systemd showed only an exit code; a missing licence file produced a misleading message about the control file. The reason now reaches the journal, the start-up messages say what is actually wrong, and a tarball installation gets the same service unit as a package installation, so it behaves the same way under systemd. These changes add output and change no behaviour on a healthy system.

Installation completes on hosts without a resolvable address

Medium · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• The installer no longer stops when the host's address cannot be determined; the hosts file is written without that entry and the installation continues.
• The starter reports a missing licence file as such.

Intent and impact

On a host whose name does not resolve, or a minimal system without the hostname command, the package installation stopped part way: the configuration was written but the trial licence was not, and the service could not start, with a message that did not say why. Found while verifying the SUSE Linux Enterprise 15 packages, which now install and start cleanly. The local-address entry is a convenience, not a requirement, and its absence is now reported as a warning.

Further input, file and privilege hardening

High · Xi-Batch 1.9.3 and later, Xi-Text 1.25.6 and later

Changes

• Xi-Batch: a job or variable log destination set over the network can no longer name a command; only local administration can.
• Xi-Batch: a peer that disconnects in the middle of a message can no longer leave the scheduler using released memory.
• The password helper used by the network interfaces now takes the same time whether or not a user exists.
• Privileged changes of file ownership and permissions refuse a path whose last component is a symbolic link.

Intent and impact

These complete the hardening review published with Xi-Batch 1.9.1 and Xi-Text 1.25.4. Each closes a way in which hostile input, a hostile peer or a local user with write access to a directory could influence a privileged process. Well-formed traffic and normal administration are unaffected. Updating is recommended for any installation whose components are reachable over a network or shared by several local users.

Support horizon extended to at least 2035

High · Xi-Batch and Xi-Text, all supported releases

Changes

• The support horizon for the current products is extended to at least 2035.

Intent and impact

Customers asked for a longer commitment than the 2030 horizon recorded in Legacy line and sun-setting below, and it has been extended: Xi-Batch and Xi-Text are supported until at least 2035. Extended support beyond that can still be arranged case by case.

This entry supersedes the horizon stated in that earlier entry, which is left as published. The current products are the products: they are actively developed and released - the entries above this one are this year's work - and nothing on this page should be read as a reason to wait for something else before deploying them.

Product Management portal replaces the download portal

Info · All versions

Changes

• Downloads and licence management move to the Product Management portal at product-management.xisl.com.
• Sign-in is by account reference and email address, with a one-time code.
• The serial-number requirement is withdrawn.

Intent and impact

This supersedes Download portal and Download portal lists RPM packages below, both of which describe a self-service portal at downloads.xisl.com requiring a serial number. Neither the address nor the method still applies.

Sign in with your account reference and the email address held for you; a six-digit code is sent to that address. There is no stored password. If no code arrives, or you have no account reference, contact Support - the usual cause is that the contact details held for the account need bringing up to date, and that is quickly fixed.

Full detail, including what a past customer can expect, is on Downloads and licensing.

Motif and GTK3 interfaces ship as installable sub-packages

Info · Xi-Batch 1.8.0 and later, Xi-Text 1.25.0 and later

Changes

• The graphical interface is modernised from GTK2 to GTK3.
• Motif and GTK3 are each packaged as an installable sub-package.

Intent and impact

This supersedes Motif interface removed from the standard package below. Motif was removed from the standard package, not withdrawn: both the Motif and the GTK3 interfaces ship, each as a sub-package you install if you want it. A system that needs neither does not carry them; a system that needs both can have both.

The current interface set is therefore the command line, the full-screen character interface, Motif and GTK3 - as described on Platforms.

Fail-safe privilege handling across all commands and services

Critical · Xi-Text 1.25.4 and later, Xi-Batch 1.9.1 and later

Changes

• Every command and service now stops immediately if it cannot switch to the intended user identity.

Intent and impact

Both products carry out work under the identity of its owner, and drop any elevated privilege before acting. A hardening review extended the fail-safe behaviour already applied to job execution to all of the command-line tools and services: if a required change of identity cannot be completed, the operation now halts rather than continuing under the wrong identity. Correctly-configured systems see no change in normal operation. Updating to this release is recommended for all installations.

Reliable bulk printer start/halt and clean shutdown

High · Xi-Text 1.25.4 and later

Changes

• A bulk "start all" or "halt all" now acts on every printer.
• A graceful shutdown now releases all shared-memory resources.

Intent and impact

A start or halt issued in the wildcard form — for example spstart -f "*" — could act on only a varying subset of printers on large systems, because commands queued by the bulk client were discarded once that client had exited; the scheduler now processes every command it was sent. Separately, on a graceful stop a printer daemon that was slow to stop could keep the scheduler's shared memory attached, so it was not freed until the next restart; the scheduler now ensures such a daemon has stopped before it releases those resources. Together these resolve a customer report of printers not all responding to a bulk start or halt, and of interprocess resources remaining allocated after a stop.

Network and print-protocol input hardening

High · Xi-Text 1.25.4 and later, Xi-Batch 1.9.1 and later

Changes

• The print-protocol (LPD) receiver validates queue names, file names and client-supplied values before use.
• Network job submissions and inter-server messages are bounds-checked before they are unpacked.
• The management-protocol decoder rejects malformed length-encoded input.

Intent and impact

A hardening review across the network-facing components added validation of externally-supplied input — lengths, offsets, names and field values — before it is used, so that malformed or hostile traffic is rejected cleanly instead of risking excessive resource use or memory corruption. Well-formed traffic and normal job submission are unaffected. Updating is recommended for any installation whose components are reachable over a network.

Stronger web-interface session keys

Low · Xi-Text 1.25.4 and later, Xi-Batch 1.9.1 and later

Changes

• Web-interface session keys are now drawn from the operating system's secure random source.

Intent and impact

The keys that identify a signed-in web-interface session are now generated from the kernel's cryptographic random source rather than a time-seeded generator, so that a valid key cannot be predicted. Existing sessions and the interface itself are otherwise unchanged.

Correct repeat scheduling across century years

Medium · Xi-Batch 1.9.1 and later

Changes

• Yearly and monthly repeating jobs now advance correctly across century years.

Intent and impact

The date arithmetic for repeating jobs used a simplified leap-year rule that is incorrect at century boundaries such as 1900 or 2100, so a monthly or yearly repeat spanning such a year could be scheduled a day out. The calculation now applies the full Gregorian calendar rule. Only jobs whose repeat span crosses a century non-leap year were affected; all other schedules are unchanged.

Diagnostics on unexpected scheduler termination

Info · Xi-Batch 1.9.1 and later

Changes

• An unexpected scheduler termination now produces standard diagnostics.

Intent and impact

A leftover diagnostic handler caused the scheduler, in the rare event of an abnormal termination, to exit reporting success and without leaving a diagnostic core file. It has been removed, so an abnormal termination now behaves in the standard way and can be investigated properly. Normal operation is unaffected.

Print job recovery after an untidy printer stop

High · Xi-Text 1.25.3 and later

Changes

• A print job that was held by a printer at the moment the printer stopped abnormally is now re-queued automatically.

Intent and impact

Previously, if a printer stopped untidily part-way through a job, the job could remain attached to that printer indefinitely — it would neither reprint nor delete, even after the printer recovered, and was cleared only by restarting the scheduler. The scheduler now releases and re-queues the held job, so it reprints on the recovered printer (or another) without operator intervention.

Hardened job-execution privilege handling

Critical · Xi-Batch 1.9.0 and later

Changes

• Per-job execution now fails safe if it cannot switch to the job owner's identity.

Intent and impact

The scheduler runs each job under the identity of the job's owner. A hardening review found that if that change of identity could not be completed, execution previously continued regardless. It now stops immediately and the job does not run, closing a local privilege-escalation condition. Correctly-configured systems see no change in normal operation. Updating to this release is recommended for all Xi-Batch installations.

Recovery of undeletable print jobs

Medium · Xi-Text 1.25.2 and later

Changes

• Delete-time reclaim of a job whose printer process ended unexpectedly.

Intent and impact

On busy systems a job could occasionally become impossible to delete after its printer process ended unexpectedly, with a scheduler restart the only remedy. The delete path now reconciles this state and removes the job cleanly.

Terminal-server protocol input hardening

High · Xi-Text 1.25.2 and later

Changes

• The terminal-server protocol decoder now validates encoded field lengths before use.

Intent and impact

The decoder for the terminal-server protocol now rejects malformed length-encoded input that could previously cause excessive memory use or an unbounded processing loop. Well-formed traffic is unaffected.

Job-data network input hardening

High · Xi-Batch 1.8.0 and later

Changes

• Job descriptors received over the network are now bounds-checked before they are unpacked.

Intent and impact

The routine that unpacks a job descriptor arriving over the scheduler's network interface now validates the offsets and counts carried in the message, so malformed data can no longer write beyond the intended buffer. Normal job submission is unaffected.

Binaries report their release version

Info · Xi-Text 1.25.2 and later, Xi-Batch 1.8.2 and later

Changes

• Each program now reports its marketing release version alongside the on-disk format version.

Intent and impact

The version string compiled into each program now carries the release number — for example Xi-Text 1.25.3 (format 23.500) — making it straightforward to confirm exactly which build is deployed. The on-disk and on-the-wire format generation is unchanged.

RPM packages for RHEL 8 & 9 and custom blends

Info · Xi-Batch 1.8.0 and later, Xi-Text 1.25.0 and later; blend RPMs from Xi-Batch 1.9.0 and Xi-Text 1.25.2

Changes

• RPM packages for Red Hat Enterprise Linux 8 and 9 (and compatible clones such as Rocky Linux and AlmaLinux).
• Custom "blend" builds can now also be delivered as RPMs, with their service paths and runtime directories created correctly on install.

Intent and impact

RPM installation manages file permissions, service registration and clean removal for you, and is recommended on all Red Hat and clone systems. Custom blends — builds tailored to a distributor's paths or a site's requirements — are now packaged the same way. RHEL 10 packages will follow; older versions are available on request.

Installation hardening for openSUSE / Leap

Low · Xi-Batch 1.9.0 and later, Xi-Text 1.25.2 and later

Changes

• Package installation made robust on openSUSE and SUSE Leap (service group creation and systemd unit location).

Intent and impact

Installation on minimal openSUSE and SUSE Leap images now creates the required service group and places the systemd unit in the correct location, so the service installs and starts cleanly. Red Hat and clone installs are unchanged.

Download portal lists RPM packages

Info · All versions

Changes

• The download portal now lists RPM packages alongside the binary distributions.

Intent and impact

The software download portal has been updated so that RPMs are listed alongside the binary packages for each product.

Download portal

Info · All versions

Changes

• Self-service download portal available.

Intent and impact

Xi Software applications are available from our web download portal at https://downloads.xisl.com/. A valid serial number is required; once provided, all related files for the latest build are listed, each with a checksum for validation. An advanced "Blend" filter is available for customers who have requested a customised build.

Xi-Batch scheduler responsiveness

Critical · Xi-Batch 1.7.0, Xi-Text 1.24.1

Changes

• Scheduler main loop re-engineered.

Intent and impact

On recent Red Hat and compatible Linux platforms the scheduler could become unresponsive under certain conditions — for example when utilities such as btq or spq were run. The root cause was a logic error in the main loop, which has been reconstructed in this release.

Motif interface removed from the standard package

Medium · Xi-Batch 1.7.0, Xi-Text 1.24.1

Changes

• The Motif graphical interface is no longer included by default.

Intent and impact

Owing to reduced support for Motif on recent platforms, the Motif GUI is no longer included in the standard build. Custom builds including Motif remain available on request.

Legacy line and sun-setting

High · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• The current products are now identified as the "legacy" (V1) line.

Intent and impact

The V1 legacy products are now in a planned sunset and will be supported until 2030; extended support beyond that can be arranged case by case. A replacement V2 line is in development to deliver the product roadmap; it will not be compatible with the V1 products, which have given some forty years of service. Further detail on the replacement products will follow in due course.

Build-system modernisation

Info · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• Rebuilt and automated build system.
• Automated test suite introduced.
• Support for tailored builds ("blends").
• Xi-Util separated from Xi-Text and Xi-Batch.

Intent and impact

The build system has been rebuilt to make it easier to compile and test new versions across Linux distributions and Unix variants, and to deliver custom distributions ("blends") from the same core code — for example a distributor's custom paths, or compile-time options to meet a platform's security profile. An automated test suite now guards against regressions across target platforms. These changes mainly affect development, but should improve product quality and the customer experience. Note that Xi-Util is now separate and must be installed alongside the product if you require it.

Release naming and version numbering

Info · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• Versions now use the semantic-versioning (semver) standard, prefixed with "1.".
• Release naming structure is : CPU-MFR-OSNAME-PRODUCT-BLEND-VERSION
• The version carries both the code version and a build suffix (identifying a rebuild of the same code).
• "Blend" identifies a custom variant; "standard" indicates no customisation.
• The installer displays the full build information.

Intent and impact

Xi-Batch was created in the 1980s, well before Linux. As most users have moved to Linux — with its variation in libraries, versions and profiles — the release naming has been updated to capture the build target precisely and to speed delivery from code change to distribution. Distributed file names now follow the new format, for example:

x86_64-linux-rockylinux9.3-xibatch-standard-1.9.0+.tar.gz x86_64-linux-rockylinux9.3-xitext-standard-1.25.3+.tar.gz Each archive unpacks to a folder named PRODUCT-BLEND-VERSION (excluding the build suffix), for example xibatch-standard-1.9.0/.

Installer updates

Info · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• Updated installer and system messages.

Intent and impact

System messages have been revised for improved readability, with various quality improvements throughout the installer.

Licence management system

Low · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• Licence logic and enforcement updated.

Intent and impact

The licence logic has been updated to better handle 64-bit processors and virtualised environments. New installations will need a new key; existing serial numbers remain valid.

Automated licence server

Low · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• Automated licence service re-introduced with security enhancements.

Intent and impact

The automated licence service was withdrawn in 2020 pending a security assessment — not because of any compromise, but to reflect a changed threat landscape that the original system predated. Following the system updates it is available again via vwrite -I.

vwrite licence tool

Low · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

New options for unattended licence renewal:

• -s [serial number] — specify an existing serial number.

• -o "[Organisation name]" — quote the name if it contains spaces.

• -q — non-interactive; succeed or fail with no prompts (requires -s and -o).

Intent and impact

As many systems are now internet-connected, the licence process can be further automated. The new options let the serial number and organisation name be passed on the command line, making vwrite scriptable so a customer can automate renewal. Example:

sudo /usr/local/bin/xb-vwrite -I -q -o "Your Org name" -s 00000000 sudo /usr/local/bin/xt-vwrite -I -q -o "Your Org name" -s 00000000 To protect performance and security, a high frequency of requests will result in the sending network being temporarily blocked.

DEINSTALL path fix

High · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

• Corrected a path error in the de-installation process.

Intent and impact

The DEINSTALL process could fail to complete following a change to the installation paths. It now operates as expected.

Default path changes for FHS compliance

High · Xi-Batch 1.7.0, Xi-Text 1.24.0

Changes

Installation paths updated to align with the Filesystem Hierarchy Standard.

Xi-Text

• Spool directory: /var/spool/spd -> /var/spool/xi/spd

• Sockets directory: /var/spool/spuds -> /var/spool/xi/spuds

• Printers directory: /var/spool/printers -> /var/spool/xi/printers

• Internal program files: /var/spool/progs" -> /usr/libexec/xi

• Help files: /var/spool/progs -> /usr/share/xi

  Xi-Batch:

• Spool directory: /var/spool/batch -> /var/spool/xi/batch

• Sockets directory: /var/spool/btuds -> /var/spool/xi/btuds

• Internal program files: /var/spool/progs" -> /usr/libexec/xi

• Help files: /var/spool/progs -> /usr/share/xi

  All other paths are unchanged.

Intent and impact

The original Unix layout evolved decades ago around early hardware limits, leaving ambiguities about where programs should live. The 2015 Filesystem Hierarchy Standard (FHS), and the subsequent usr-merge across most Linux distributions, addressed this. The product paths have moved to align with FHS. Original paths can be retained in your master configuration file; if that is not possible, files from a previous installation must be migrated. Note: DEINSTALL removes your master configuration. If changing file locations is not possible, contact your distributor for a custom build that reuses your existing paths.

Getting a release

Licensed customers download releases and renew licences through the customer portal. Support is by telephone and email.

Downloads and licensing · Contact support