OpenServer
closed source version of Unix developed by Xinuos, formerly SCO
Xinuos OpenServer, previously SCO UNIX and SCO Open Desktop (SCO ODT), is a closed source computer operating system developed by Santa Cruz Operation (SCO), later acquired by SCO Group, and now owned by Xinuos. Early versions of OpenServer were based on UNIX System V, while the later OpenServer 10 is based on FreeBSD 10. However, OpenServer 10 has not received any updates since 2018 and is no longer marketed on Xinuos's website, while OpenServer 5 Definitive and 6 Definitive are still supported.
History
SCO UNIX/SCO Open Desktop
In 1987 AT&T Corporation, Microsoft, and Sun Microsystems agreed to combine their versions of the Unix operating system. Santa Cruz Operation (SCO) sublicensed Microsoft's Xenix and wanted to retain the Xenix name, but AT&T said "If they want to call it Unix, they've got to use it the way it is. We don't want another set of variants".
SCO UNIX was the successor to Xenix, derived from UNIX System V Release 3.2 with an infusion of Xenix device drivers and utilities. SCO UNIX System V/386 Release 3.2.0 was released in 1989, as the commercial successor to SCO Xenix. The base operating system did not include TCP/IP networking or X Window System graphics; these were available as optional extra-cost add-on packages. Shortly after the release of this bare OS, SCO shipped an integrated product under the name of SCO Open Desktop, or ODT. 1994 saw the release of SCO MPX, an add-on SMP package.
Begin with the source’s own compact description: “OpenServer” is closed source version of Unix developed by Xinuos, formerly SCO. The dossier treats that line as a proposition to test through OpenServer, closed and source, not as a finished interpretation.
Why this record matters
The phrase “closed source version of Unix developed by Xinuos, formerly SCO” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 7, 2026. The linked authority identifier is Q1755887. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2018, 1987, 1989 and 1994.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “OpenServer”, its source revision and the description used here.
- Expand the search: follow OpenServer primary sources, OpenServer archive and OpenServer research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “OpenServer”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “OpenServer” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.