Lxrun
type of Unix compatiability layer
In Unix computing, lxrun is a compatibility layer to allow Linux binaries to run on UnixWare, SCO OpenServer and Solaris without recompilation. It was created by Mike Davidson. It has been an open source software project since 1997, and is available under the Mozilla Public License. Both SCO and Sun Microsystems began officially supporting lxrun in 1999.
Timeline
August 22, 1997: lxrun is cited as a proof of concept of cross-platform binary compatibility at the 86open conference hosted by SCO in Santa Cruz, CA.
August 29, 1997: lxrun's first mention on Usenet, in comp.unix.sco.misc. Most notably, the post mentions lxrun's availability in source and binary form from the SCO Skunkware FTP site. A later post in the thread mentions contributions by various authors, both inside and outside of SCO.
October 1, 1997: The official lxrun website is established.
June 19, 1998: Ronald Joe Record, Michael Hopkirk, and Steven Ginzburg present a paper on lxrun at the USENIX 1998 Technical Conference in New Orleans, LA.
Mar 1, 1999: SCO announces Linux compatibility in UnixWare 7 and demonstrates lxrun at LinuxWorld Expo and Conference in San Jose, CA.
May 12, 1999: Sun Microsystems announces support for Linux binaries on Solaris using lxrun.
Status
According to the official lxrun website, as of 2003 lxrun is in "maintenance" mode, meaning that it is no longer being actively developed. Reasons cited for the declining interest in lxrun include the wide availability of real Linux machines, and the availability of more capable emulation systems, such as SCO's Linux Kernel Personality (LKP), OpenSolaris BrandZ, and various virtual machine solutions.
The public source identifies “Lxrun” as type of Unix compatiability layer. This brief keeps that definition visible, then builds a research path around Lxrun, type and Unix.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Lxrun”, the useful work is to connect “type of Unix compatiability layer” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 2, 2025. The linked authority identifier is Q4043281. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1997, 1999, 1998 and 2003.
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 “Lxrun”, its source revision and the description used here.
- Expand the search: follow Lxrun primary sources, Lxrun archive and Lxrun 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 “Lxrun”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Lxrun” 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.