Xenix

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Xenix
250px
Xenix under Bochs
Developer Microsoft, SCO, various resellers
Written in {{#property:p277}}
OS family Unix
Working state Historic
Source model Closed source
Initial release 1980
Latest release System V release 2.3.4 / 1989
Platforms PC/XT, x86, PDP-11, Z8001, 68k
Kernel type Monolithic kernel
License Proprietary
Succeeded by SCO UNIX
Official website {{#property:P856}}

Xenix is a discontinued version of the Unix operating system for various microcomputer platforms, licensed by Microsoft from AT&T Corporation in the late 1970s. The Santa Cruz Operation (SCO) later acquired exclusive rights to the software, and eventually replaced it with SCO UNIX (now known as SCO OpenServer).

In the mid-to-late 1980s, Xenix was the most common Unix variant, measured according to the number of machines on which it was installed.[1][2] Microsoft chairman Bill Gates said in 1996 that for a long time that company had the highest-volume AT&T Unix license.[3]

History

Bell Labs, Unix's developer, was part of the regulated Bell System and could not sell Unix. It instead licensed the software to others. Microsoft, which expected that Unix would be its operating system of the future when personal computers became powerful enough,[4]:{{{3}}} purchased a license for Version 7 Unix from AT&T in 1978,[5] and announced on August 25, 1980, that it would make it available for the 16-bit microcomputer market.[6] Because Microsoft was not able to license the "UNIX" name itself,[7] the company gave it an original name.

Microsoft, in turn, did not sell Xenix directly to end users; instead, they licensed it to OEMs such as IBM,[8] Intel,[9] Tandy, Altos, SCO, and Siemens (SINIX) who then ported it to their own proprietary computer architectures.

IBM/Microsoft Xenix 1.00 on 5¼-inch floppy disk

Microsoft Xenix originally ran on the PDP-11. The first port was for the Zilog Z8001 16-bit processor: the first customer ship was January 1981 for Central Data Corporation of Illinois,[10]:4 followed in March 1981 by Paradyne Corporation's Z8001 product.[10]:14 The first 8086 port was for the Altos Computer Systems' non-PC-compatible 8600-series computers (first customer ship date Q1 1982).[note 1][10]:3[11][12][13]

Intel sold complete computers with Xenix under their Intel System 86 brand (with specific models such as 86/330 or 86/380X); they also offered the individual boards that made these computers under their iSBC brand. This included processor boards like iSBC 86/12 and also MMU boards such as the iSBC 309. The first Intel Xenix systems shipped in July 1982.[10]:9[note 2] Tandy more than doubled the Xenix installed base when it made TRS-XENIX the default operating system for its TRS-80 Model 16 68000-based computer in early 1983,[14] and was the largest Unix vendor in 1984.[15] Seattle Computer Products also made (PC-incompatible) 8086 computers bundled with Xenix, like their Gazelle II, which used the S-100 bus and was available in late 1983 or early 1984.[10]:17[16]

There was also a port for IBM System 9000.[17]

SCO had initially worked on their own PDP-11 port of V7, called Dynix,[note 3] but then struck an agreement with Microsoft for joint development and technology exchange on Xenix in 1982.[18]

In 1984, a port to the 68000-based Apple Lisa was jointly developed by SCO and Microsoft and it was the first shrink-wrapped binary product sold by SCO.[19]

The difficulty in porting to the various 8086 and Z8000-based machines, said Microsoft in its 1983 OEM directory, had been the lack of a standardized memory management unit and protection facilities. Hardware manufacturers compensated by designing their own hardware, but the ensuing complexity made it "extremely difficult if not impossible for the very small manufacturer to develop a computer capable of supporting a system such as XENIX from scratch," and "the XENIX kernel must be custom-tailored to each new hardware environment."[10]:Introduction

A generally available port to the unmapped Intel 8086/8088 architecture was done by The Santa Cruz Operation around 1983.[20][21][22] SCO Xenix for the PC XT shipped sometime in 1984 and contained some enhancement from 4.2BSD; it also supported the Micnet local area networking.[23]

The later 286 version of Xenix leveraged the integrated MMU present on this chip, by running in 286 protected mode.[24] The 286 Xenix was accompanied by new hardware from Xenix OEMs. For example, the Sperry PC/IT, an IBM PC AT clone, was advertised as capable of supporting eight simultaneous dumb terminal users under this version.

While Xenix 2.0 was still based on Version 7 Unix,[25] version 3.0 was upgraded to a Unix System III code base,[10]:9[26][27] A 1984 Intel manual for Xenix 286 noted that the Xenix kernel had about 10,000 lines at this time.[9]:1–7 It was followed by a System V.2 codebase in Xenix 5.0 (aka Xenix System V).[28]

Microsoft omitted multiuser support from its own MS-DOS operating system because Xenix had it.[29] The company planned to over time improve MS-DOS so it would be almost indistinguishable from single-user Xenix, or XEDOS, which would also run on the 68000, Z8000, and LSI-11; they would be upwardly compatible with Xenix, which Byte in 1983 described as "the multi-user MS-DOS of the future".[30][31] Microsoft advertised DOS and Xenix together, listing the shared features of its "single-user OS" and "the multi-user, multi-tasking, UNIX-derived operating system", and promising easy porting between them.[32]

After the breakup of the Bell System, however, AT&T started selling Unix. Microsoft, believing that it could not compete with Unix's developer, decided to abandon Xenix. The decision was not immediately transparent, and so Xenix gave birth to the term vaporware.[33] An agreement was signed with IBM to develop OS/2,[4] and the Xenix team (together with the best MS-DOS developers) was assigned to that project. In 1987 Microsoft transferred ownership of Xenix to SCO in an agreement that left Microsoft owning 25% of SCO. When Microsoft eventually lost interest in OS/2 as well, it based its further high-end strategy on Windows NT.

In 1987, SCO ported Xenix to the 386 processor, a 32-bit chip, this after securing knowledge from Microsoft insiders that Microsoft was no longer developing Xenix.[33] Xenix System V release 2.3.1 introduced support for i386, SCSI and TCP/IP. SCO's Xenix System V/386 was the first 32-bit operating system available on the market for the x86 CPU Architecture.

Microsoft continued to use Xenix internally, submitting a patch to support functionality in UNIX to AT&T in 1987, which trickled down to the code base of both Xenix and SCO UNIX. Microsoft is said to have used Xenix on Sun workstations and VAX minicomputers extensively within their company as late as 1992.[34]

All internal Microsoft email transport was done on Xenix-based 68000 systems until 1995–96, when the company moved to its own Exchange Server product.[35]

SCO released its SCO UNIX as a higher-end product, based on System V.3 and offering a number of technical advances over Xenix; Xenix remained in the product line. In the meantime, AT&T and Sun Microsystems completed the merge of Xenix, BSD, SunOS and System V.3 into System V Release 4. The last version of SCO Xenix/386 itself was System V.2.3.4, released in 1991.[36]

Features

Aside from its AT&T Unix base, Xenix incorporated elements from BSD, notably the vi text editor and its supporting libraries (termcap and curses).[8] Its kernel featured some original extensions by Microsoft, notably file locking and semaphores,[8][9]:1.12 while to the userland Microsoft added a "visual shell" for menu-driven operation instead of the traditional Unix shell.[8] A limited form of local networking over serial lines (RS-232 ports) was possible through the "micnet" software, which supported file transfer and electronic mail, although UUCP was still used for networking via modems.[8]

OEMs added further modifications to the Xenix system.[8][9]

Trusted Xenix

Trusted Xenix was a variant initially developed by IBM, under the name Secure Xenix; later versions, under the Trusted Xenix name, were developed by Trusted Information Systems.[37] It incorporated the Bell-La Padula model of multilevel security, and had a multilevel secure interface for the STU-III secure communications device (that is, an STU-III connection would only be made available to applications running at the same privilege level as the key loaded in the STU-III). It was evaluated by formal methods and achieved a B2 security rating under the DoD's Trusted Computer System Evaluation Criteria—the second highest rating ever achieved by an evaluated operating system.[38] Version 2.0 was released in January 1991, version 3.0 in April 1992, and version 4.0 in September 1993.[39] It was still in use as late as 1995.

See also

Notes

  1. ↑ The Altos 8086 machines had a custom MMU, which used 4K pages.
  2. ↑ Intel also offered their own iRMX operating system as an alternative for these.
  3. ↑ Unrelated to the later Dynix from Sequent Computer Systems

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ http://channel9.msdn.com/Series/History/The-History-of-Microsoft-1980
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.0 8.1 8.2 8.3 8.4 8.5 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 9.2 9.3 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 10.2 10.3 10.4 10.5 10.6 Microsoft Xenix Operating System OEM Directory, May 1, 1983, Part No. OEM0091B
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ http://bitsavers.trailing-edge.com/pdf/seattleComputer/brochures/Gazelle_II.pdf
  17. ↑ BYTE Guide to the IBM PC, fall 1984, p.61
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Microsoft Xenix 3.0 ready for 286
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.; review of the beta SCO Xenix on an XT
  • Lua error in package.lua at line 80: module 'strict' not found. Covers and compares PC/IX, Xenix and Venix.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Xenix&oldid=56015"