HP-UX
Hewlett-Packard's proprietary Unix operating system
HP-UX is a proprietary Unix operating system developed by Hewlett-Packard (later Hewlett Packard Enterprise) for its line of business-critical servers, originally designed to run on HP's PA-RISC processors and later ported to Itanium-based…
Definition
HP-UX is a proprietary Unix operating system developed by Hewlett-Packard (later Hewlett Packard Enterprise) for its line of business-critical servers, originally designed to run on HP's PA-RISC processors and later ported to Itanium-based systems. It is one of the long-running commercial Unix variants historically deployed in enterprise data centers for mission-critical workloads requiring high availability, alongside competitors like Solaris and AIX.
Overview
HP-UX traces its lineage to the broader Unix System V family, adapted and extended by HP with its own enterprise-oriented features layered on top of the standard Unix kernel and userland tools. Like other System V-derived Unixes, it provides the familiar Unix process model, filesystem hierarchy, and command-line tooling that Unix and Linux administrators generally recognize, while adding HP-specific subsystems for managing storage, clustering, and system resources tailored to HP's own server hardware. A defining characteristic of HP-UX is its tight coupling to HP's own hardware platforms: it was built to run on PA-RISC processors and later extended to support Itanium-based Integrity servers, meaning the operating system and hardware were historically developed and sold together as an integrated enterprise computing platform rather than HP-UX being a general-purpose OS installable on arbitrary hardware. HP layered enterprise features on top of the base Unix system, including HP Serviceguard for high-availability clustering and its own logical volume management tools, aimed at the reliability and uptime requirements of large-scale business systems like databases and transaction processing platforms. HP-UX belongs to the category of commercial, vendor-specific Unix variants that dominated enterprise server rooms in the 1990s and 2000s, alongside Sun's Solaris and IBM's AIX, each tied to its vendor's own hardware line and each offering broadly similar core Unix functionality with different proprietary management tooling layered on top. This differs sharply from the open-source Linux distributions that have since become the default choice for new enterprise Unix-like deployments, since Linux runs on commodity x86 hardware from many vendors and is not tied to purchasing a single company's servers. In practice, HP-UX has historically been used for large enterprise workloads such as relational databases, ERP systems, and transaction processing applications where organizations had already invested in HP's Integrity server hardware and valued the platform's high-availability clustering and long-term vendor support commitments. Its usage today is largely confined to legacy enterprise systems that have not been migrated to Linux or other platforms, rather than new deployments, as the broader industry has shifted decisively toward Linux on commodity hardware. HP-UX's tight hardware coupling, once a selling point for integrated support, has become a limitation as Itanium's market position declined and HP wound down active hardware development for the platform; organizations still running HP-UX face a shrinking pool of new hardware and a narrowing set of migration paths. Compared to Linux, HP-UX also has a much smaller open ecosystem of third-party software and community tooling, making it a platform mostly relevant to maintaining existing enterprise systems rather than building new ones.
Key Features
- Proprietary Unix derived from the System V Unix lineage
- Originally built for HP's PA-RISC processors, later ported to Itanium
- Includes HP Serviceguard for high-availability clustering
- Tightly coupled to HP's own Integrity server hardware line
- Targeted at mission-critical enterprise database and ERP workloads
- Peer to other vendor Unix variants like Solaris and AIX
- Usage today largely confined to legacy enterprise deployments