# NetBSD ## Identification [[Xenix|Xenix]], [[IBM AIX|AIX]], [[HP-UX|HP-UX]], [[IRIX|IRIX]], [[Tru64 UNIX|Tru64]], [[Solaris|Solaris]], [[NetBSD|NetBSD]], and [[SCO OpenServer|SCO OpenServer]] belong to different Unix and Unix-like branches. The notebook’s arrows compress a complicated corporate and code lineage and should not be treated as exact genealogy. [[Xinuos|Xinuos]] currently documents SCO OpenServer and UnixWare products; the Open Group separately governs use of the UNIX trademark ([Open Group UNIX standard](https://www.opengroup.org/membership/forums/platform/unix); [Xinuos OpenServer documentation](https://osr5doc.xinuos.com/en/GetStart/gsgC.doc_runtime.html)). ## Notebook evidence - [[Scanned_20260730-1719#PDF page 62 — Unix lineage, HP-UX, Xinuos, and remote enterprise systems|PDF page 62: Unix lineage, HP-UX, Xinuos, and remote enterprise systems]] — The author is searching for continuity across “dead,” legacy, or proprietary operating systems: archived kernels, virtual machines, remote desktops, standards, current custodians, and compatible modern hosts. ## Relationships and overlays The source places this note in a shared evidence cluster with [[HP-UX|HP-UX]] · [[IBM AIX|IBM AIX]] · [[IRIX|IRIX]] · [[SCO OpenServer|SCO OpenServer]] · [[Solaris|Solaris]] · [[Tru64 UNIX|Tru64 UNIX]] · [[Xenix|Xenix]] · [[Xinuos|Xinuos]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Build a dated lineage table separating code ancestry, trademark ownership, corporate acquisition, current product stewardship, and virtualization availability. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]