ChorusOS

from Wikipedia, the free encyclopedia
ChorusOS
Logo Chorus Systems 1171566860225.jpg
developer Chorus Systèmes SA
Sun Microsystems , Inc.
License (s) Sun Public License-Lite Version 1.0 (the "License")
GNU General Public License (GPL)
Mozilla Public License
FreeBSD license
Current  version 5.1
Kernel Microkernel
ancestry CHORUS-V0 \ -V1 \ -V2 \ -V3
Architecture (s) x86 , 68k , PPC , SPARC , ARM , MIPS
compatibility ANSI \ POSIX \ Unix System V
Languages) English
ChorusOS 5.0

ChorusOS is a real-time operating system . The design and technology enables the building of open, distributed and scalable operating systems. The architecture pattern of the software architecture forms an intersection with the categories distributed systems , adaptive systems and chaos to structure . ChorusOS describes the intersection of the three categories as communication. The Nucleus Microkernel provides real-time services that are accessible to system programmers. The modular architecture supports scalability and allows the dynamic configuration of the system and the applications.

history

Most of the documents accessible and published on the Internet indicate 1979 as the founding date of a project group tasked with developing software at the state institute for research, computer science and automation, the "Institut national de recherche en informatique et en automatique" . From the point of view of a software life cycle, this software later became the commercial product ChorusOS.

Another research project that ran at the state institute INRIA was Sol . The aim of this pilot project was to implement the UNIX multi-user operating system environment entirely in Pascal on French computer systems, including the HB Level 6, Center national d'études des télécommunications SM90 (68000) system. In 1984 the research projects merged into a larger team: Members from the Sol research project joined the Chorus research project and brought their experience to bear. The result of the development were three versions, designated as CHORUS-V0, CHORUS-V1 and CHORUS-V2. Research results and system experience from the CYCLADES and ESOPE projects were incorporated into the Chorus research project .

CHORUS-V0 (1980–1982)

The first version experimented with three main concepts:

  • that of the actor whose sequential and invisible operations took place in phases of execution and communication
  • the distributed application as an ensemble of independent actors
  • the small nucleus , a simple and reliable micro-component that can be easily distributed anywhere

CHORUS-V1 (1982–1984)

The second version moved the prototype to a real system. The design had a few changes compared to CHORUS-V0 :

  • on the one hand the introduction of structured messages to embed protocols
  • on the other hand, the concept of the activating message, whose data content was the context for embedded calculations and the graph for future calculations

CHORUS-V2 (1984–1986)

The adaptation to the multi-user operating system made it necessary to redesign the CHORUS interface and to change the system actors. The version CHORUS-V2 offered the possibility to rethink the multi-user operating system and the kernel architecture as a whole. With respect for the two concepts:

  • Modularity: Division of the multi-user operating system services into different, independent actors
  • Distribution: Management of the objects of the system actors, such as files and processes, distributed via CHORUS as services

CHORUS-V3 (1987-1997)

At the beginning of 1987, Hubert Zimmermann and Michael Gien founded the French company Chorus Systèmes Société anonyme as a stock corporation under French commercial law from 1867. Among other things, the small team published the version CHORUS-V3 as a result of this work phase . In 1989 the release of Chorus / MIX V3.2 followed. It was a distributed system with support for real-time and binary compatibility with SCO systems and Intel-based machines.

ChorusOS

The takeover of Chorus Systèmes Société anonyme was described in the quarterly report 10-Q of the US company Sun Microsystems from California . On October 21, 1997, all shares and liabilities , as well as all branches , changed hands for a sum of US $ 26.5 million in cash. A depreciation of $ 13 million was added for integration, research and development.

Due to the hostile takeover of the French company Chorus Systèmes Société anonyme by Sun Microsystems based in California / USA, the real-time operating system was given the new product name ChorusOS. Sun Microsystems completed the hostile acquisition in 2002 with EOL status for ChorusOS. This officially ended the product's life cycle. That meant there was no more support for him. The last source tree of ChorusOS, the further development of Release 5.1, was published as Chorus Open Source by Sun Microsystems on the Sun Microsystems Laboratories Experimental Stuff website .

Economic difficulties as a result of the dot-com bubble prompted Sun Microsystems to take measures to reduce costs in 2002. One measure was to end the life cycle of the ChorusOS product. The publication of parts of the sources of the ChorusOS as open source then took place on the website of Sun Labs. Former employees of Chorus Systèmes SA, who worked in the newly created department for embedded system software after the takeover by Sun, then left Sun and founded the startup Jaluna SA in 2002

The Jaluna company ceased to exist when it was acquired by VirtualLogix . With the company VirtualLogix, the new name VirtualLogix C5 was added for the ChorusOS. In order to improve the opportunities of C5 in the real- time operating system market, the company VirtualLogix named the C5 an embedded system under the Linux operating system and the ChorusOS real-time operating system, with the functionality of a carrier grade class software platform. Sun Microsystems had carrier-grade servers with various operating systems in its portfolio for its high-end systems until the hostile takeover by Oracle. VirtualLogix ceased to exist in September 2010 when it was acquired by Red Band Software .

The Frenchman Michel Gien was co-founder of the companies Chorus Systems, Jaluna and Virtual Logix.

The release of the full sources from the Jaluna project was the release of Jaluna-1 . This was followed by the description of being an RT- POSIX layer based on FreeBSD 4.1 and the CDE development environment .

description

Over time, the direction of development changed from distributed aspects to real-time and modularization ( componentization ). The specification of the distributed operating system kernel of Release CHORUS-V3 was carried out to some extent with the description language for event sequences LOTOS . A descriptive language that the International Organization for Standardization published as the ISO 8807: 1989 standard in 1989. Objectively speaking, the initiative came about when updating from CHORUS V2 to CHORUS V3. Charles Pecheur justifies the decision to experiment with LOTOS as a test of the adequacy of LOTOS for the specification of the operating systems by specifying the basic structures and functionalities of the distributed operating system CHORUS V3. The approach was experimental in nature; validation of the real system was not essential.

Example of the specification

ISO / OSI meeting minutes
specification figure 
specification CHORUS_kernel [TSAP,monitor,trap] (…): noexit:=
… (* Definition der Datentypen *)
behaviour
hide transport,IPC,local in
(   (   (   (   local_call_dispatcher [trap,IPC,local] (…)
(* Empfangen der lokalen Aufrufe,
     Aufrufe des lokalen Kernel oder
      Senden der Nachrichten an einen anderen Kernel *)
    |   |   |
                remote_call_dispatcher [IPC,local] (…) )
(* Empfangen der Nachrichten des entfernten Kernel,
    Aufrufe der lokalen Kernel wenn erforderlich *)
            |[local]|
              local_kernel [monitor,IPC,local] (…) )
(* Abhandlung der lokalen CHORUS objects *)
        |[IPC]|
          IPC_manager [transport,IPC] (…) )
(* Abhandlung der lokalen Kommunikation,
    Weiterleitung der Nachrichten zum Netzwerk Manager,
     wenn das Ziel entfernt liegt *)
    |[transport]|
      network_manager [TSAP,transport] (…) )
(* Abhandlung der Kommunikation mit anderen Standorten *)
where
(* Prozess Definitionen *)
endspec

Fig.5.png

architecture

Depending on the configuration, an existing ChorusOS operating system instance consists of a microkernel and various actors. The various actors contribute to the implementation of the selected services. ChorusOS itself is divided into two different layers, with a third layer communicating with the applications.

The architecture of ChorusOS.png

Microkernel

The descriptions of the microkernel are different in the published documents. In the technical report "CS / TR-90-25.1, 1990" it is declared to the microkernel that the chorus nucleus manages the physical devices in one place at the deepest level. At the highest level, it provides location-transparent communication mechanisms between the processes. It is composed of four main components that support local and global services. The main component at the lowest level, the controller, "CHORUS supervisor" . The two main components based on this, the real-time executive, "CHORUS real-time executive" and the manager of the virtual memory, "CHORUS virtual memory manager" . The main component at the highest level, the inter-process communication manager , "CHORUS inter-process communication manager"

The documentation uses different forms of representation at individual points to depict the details of the microkernel.

Real-time executive

Communications
(Portable)

Memory management

(Portable) (Portable)
Supervisor
(machine dependent) 		(Machine dependent)
hardware
Figure 1.  -  The CHORUS Nucleus

Real-time executive

Communications
(Portable)

Memory management

(Thread scheduling) (Linear, segmented or
page virtual memory)
[Portable] [Portable]
Supervisor
(interrupts, exceptions and trap handling)
[machine dependent] 		[Machine dependent]
Figure 2.  -  The CHORUS Nucleus

In the document “Programming under ChorusOS” it is declared to the microkernel that the core executive supports the basic services of the lowest level, corresponding to the KERN actor. In the service requirements of the real-time applications, the management of the actors, the timing, the scheduling, the memory, the synchronization, the crossover actor calls (LAPs) and so on.

implementation

As an embedded system on a number of processor architectures and motherboards systems with peripherals :

  • Intel Corporation x86 like i386 / i486 / Pentium (various PC / ATs)
  • Microsoft Windows NT upgrade, including POSIX Cygwin tools, targets Motorola PowerPC 60x and 750 processor family (ppc60x)
  • Motorola PowerPC 60x and 750 processor family (ppc60x)
  • MPC8xx (Motorola PowerPC: MPC860, MPC821 and MPC823) processors
  • MPC8xxADS (Motorola PLC: MPC860 FADS, MPC821 FADS and MPC823 FADS) motherboard systems
  • MPC8xxADS (Motorola PLC: MPC860 FADS, MPC821 FADS [cpu, flash, quicc-8xx]) motherboard (integrated) peripherals
  • MPC8xxADS (Motorola PLC: MPC823 FADS [cpu, flash, quicc-8xx]) motherboard (integrated) peripherals
  • Motorola mc68030 / mc68360 / mc68040 (MVME147S, QUADS, MVME167S)
  • Motorola mc88k
  • Sun Microsystems UltraSPARC IIi, SPARC (SPARCstation SLC, SPARCstation Classic)
  • Transputer T425 / T805
  • R3000 / R4000 (Sony 3410)
  • PA-RISC (HP 9000/834 and 9000/720)
  • YMP (Cray YMP), Cray T3E

Functionality

The functionalities of the ChorusOS conformed to the following international standards:

  • ANSI
  • POSIX 1003.1b / .1c and e.g. B. Previous interfaces .4 and .4a. (The organizations IEEE and The Open Group took over the official certification of the POSIX functionality since 2007.)
  • Unix System V (R3.2 or R4.0)

Subsystems

The CHORUS subsystems consisted of the following components :

  • CHORUS / Micro, very small (10K), hard real-time embedded kernel that supports hard real-time, mostly (90%) implemented in C ++ .
  • CHORUS / ClassiX, target system development environment (host-target cross-development environment) for applications written in C ++ / C , also called C_actors .
  • CHORUS / MiX V.4, distributed, multi- server implementation of Unix SVR4 , on the level above the CHORUS microkernel.
  • CHORUS / COOL, the CHORUS / C ++ Object Oriented Layer. With the library COOL, a C ++ library developed by Texas Instruments between 1989 and 1990, it was possible to expand the distributed operating system CHORUS with the additional functionality of supporting object-oriented environments. This additional functionality is implemented in one level on the microkernel CHORUS V3 Nucleus. And an expansion of the CHORUS interface to include generic functions for object management, such as creation, deletion, storage, remote access and migration. A major goal of this approach was to examine the feasibility of general object management at the level of the microkernel with the support of several object models at a higher level. The implementation of COOL and the first evaluation of this approach were realized with a C ++ environment that supports the COOL mechanism.
  • CHORUS / COOL-ORB, OMG-CORBA compatible Object Request Broker .
  • CHORUS / JaZZ, is an implementation of the Java runtime environment and selected components from JavaOS , which were integrated into CHORUS / ClassiX in order to personalize the operating system. At Sun Microsystems, the use of the CVM with the Java 2 Platform, Micro Edition and the CDC Profile for version ChorusOS 5.0 is documented.
  • CHORUS / Harmony, C ++ / C and embedded C ++, translators and tool chain from assemblers, linkers, auxiliary programs (assemblers, linkers, utility programs) and profilers , runtime error checkers, simulators and kernel debuggers (profilers, runtime error checkers, simulators and kernel debuggers) .

swell

  • "A Comparison of Three Microkernels" , Andrew S. Tananbaum, English, The Journal of Supercomputing, vol 9, number 1, ISSN  0920-8542 , 1995
  • "A Comparison of Two Distributed Systems: Amoeba and Sprite" , Douglis, F., Kaashoek, MF, Tanenbaum, AS, English, Computing Systems, vol. 4, fall 1991 (sic)
  • "Architectural Issues in Microkernel-based Operating Systems: the CHORUS Experience" , Bricker, A., Glen, M., Guillemont, M., Lipkis, J., Ofr, D., and M. Rozier, English, Computer Communications, Vol 14, No 6, pp 347-357, July 1991
  • "Architectural issues in microkernel-based operating systems: the CHORUS experience." , Bricker. A., M. Gien, M. Guillemont, J. Lipkis. D. Orr, M. Rozier, English, Special Issue of Computer Communications on Platforms for Distributed Applications, Vol. 14 No. 6, July 1992, Pages 347-357
  • "CHORUS / COOL-ORB Programmer's Guide" , Chorus Systèmes, English, Technical Report CS / TR-96-2.1, Chorus Systèmes, 1996
  • "COOL: system support for distributed programming" , Lea, R., Jacquemot. C., Pillevesse, E., English, Communications of the ACM, Volume 36, Issue 9 Pages: 37 - 46 (September 1993)
  • "COOL-2: An Object Oriented Support Platform built above the Chorus Micro-Kernel." , Lea, R. Amaral. P., Jacquemot. C., English, Proceedings of First International Workshop on Object Orientation in Operating Systems, October 17-18, 1991. Palo Alto, California. IEEE Computer Society Press USA
  • "Data Movement in Kernelized Systems" , R. Dean, F. Armand, English, Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, pp. 243-261, April 1992
  • "Distributed Systems, Concepts and Design" , G. Coulouris, J. Dollimore, T. Kindberg, English, Addison-Wesley, second edition, 1994
  • “ÉSOPE: une étape de la recherche française en systèmes d'exploitation (1968–1972)” , Claude Bétourné, Jean Ferrié, Claude Kaiser, Sacha Krakowiak, Jaques Mossière, English / French, Article publié then les Actes du 9-ème Colloque sur l'histoire de l'informatique et des télécommunications (CHIR 2004), Rennes, 16-18 November 2004
  • "Extending tile Chorus Micro-Kernel to Support Continuous Media Applications," Coulson, G., Blair, GS, Robin, P., Shepherd, D., English, Proc. Fourth International Workshop on Network and Operating System Support for Digital Audio and Video, Lancaster House Hotel, Lancaster, UK, published by Springer Verlag, ISBN 3-540-58404-8 , October 93
  • "Implementing a modular object-oriented operating system on top of chorus," Lea, R. Amaral. P., Jacquemot, C., English, IEE Distributed Systems Engineering Journal 1 (1): 11-18 (1993)
  • "Modern Operating Systems" , Andrew S. Tanenbaum, English, Prentice-Hall, 1992
  • "Process Management and Resource Sharing in the Multiaccess System ESOPE" , Claude Bétourné, Jacques Boulenger, Jacques Ferrié, Claude Kaiser, Sacha Krakowiak, and Jacques Mossière, English, Communications of the ACM, vol. 13, no.12, (December 1970).
  • "Programming under ChorusOS" , Jean-Marie Rifflet, English, University Paris VII - Denis Diderot, November 14, 2000
  • "The COOL architecture and abstractions for object-oriented distributed operating systems" , Lea, R., Jacquemot. C., English, Proceedings of 5th ACM SIGOPS European Workshop, September 21-23, 1992, Mont St Michel, France
  • "The CYCLADES Computer Network - Towards Layered Network Architectures" , Louis Pouzin et al., English, Monograph Series of the ICCC, 2, Elsevier Publishing Company, Inc, New-York, NY, (1982), 387 p. ISBN 0-444-86482-2
  • "The Design of a QoS Controlled ATM Based Communications System in Chorus" , Coulson, G., Campbell, A., P. Robin, Blair, GS, Papathomas, M., Shepherd, D., English, IEEE Journal on Selected Areas in Communications, Special issue on ATM LANs, 1994
  • "The Impact of Operating System Structure on Memory System Performance" , J Bradley Chen, Brian N Bershad, English, ACM SIGOPS Dec. '93
  • "The SOL Operating System" , Michel Gien, English, Usenix Summer'83 Conference, Toronto, ON, (July 1983), pp. 75-78.
  • "Using LOTOS for specifying the CHORUS Distributed Operating System Kernel" , Charles Pecheur, English

Web links

Individual evidence

  1. ↑ Abstract: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, ABSTRACT, pp. 1 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  2. ↑ Background and early research, Chapter 2, Paragraph 1, Sentence 1: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2. BACKGROUND AND RELATED WORK, pp. 3 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  3. Jump up ↑ Early Research, Chapter 2, Chapter 1, Section 2, Movement 1: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.1 Early Research, pp. 3 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  4. ↑ Research Reports, Chapter 1, Subchapter 2, first subsection, first paragraph, first sentence: Kevin G. Pammett: Final Report on Research Activities or "Fifteen Months at INRIA" . Ed .: INRIA Center de Rocquencourt. RR-0310, May 1984, 1.2.1 The Sol Project, p. 4/156 ( archives-ouvertes.fr [PDF] American English: Mouse-Driven Menu Interfaces for Software Tools On A Bitmap UNIX System .).
  5. ↑ Research Reports, Chapter 1, Subchapter 2, first subsection, first paragraph, first sentence: Kevin G. Pammett: Final Report on Research Activities or "Fifteen Months at INRIA" . Ed .: INRIA Center de Rocquencourt. RR-0310, May 1984, 1.2.1 The Sol Project, p. 4/156 ( inria.fr [PDF] American English: Mouse-Driven Menu Interfaces for Software Tools On A Bitmap UNIX System .).
  6. Jump up ↑ Early Research, Chapter 2, Chapter 1, Paragraph 2, Movement 2: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.1 Early Research, pp. 3 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  7. ↑ Background and early research, Chapter 2, Paragraph 1, Movement 2: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2. BACKGROUND AND RELATED WORK, pp. 3 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  8. ↑ Background and early research, Chapter 2, Paragraph 1, Movement 2: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2 BACKGROUND AND RELATED WORK, p. 3 ( ecorelocation.de [PDF] American English: Overview of the CHORUS® Distributed Operating Systems .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / www.ecorelocation.de  
  9. ↑ Early research, Chapter 2, first subsection, first paragraph, first sentence: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.1 Early Research, pp. 3 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  10. ↑ Nucleus, Chapter 1, Subsection 1, Section 4, Sentence 1: SGS THOMSON MICROELECTRONICS (Ed.): ST9040 . 1994, 1.1 General Description, p. 5/57 ( elmicro.com [PDF] American English: 8 BIT 16K HCMOS MCUS WITH EEPROM / RAM AND A / D CONVERTER .).
  11. ↑ V2, 2nd chapter, 4th subchapter, 1st paragraph, 1st sentence: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.4 CHORUS-V2 (1984–1986), pp. 4 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  12. ↑ V2, 2nd chapter, 4th subchapter, 2nd paragraph, 1st sentence: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.4 CHORUS-V2 (1984–1986), pp. 4 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  13. ↑ V2, 2nd chapter, 4th subchapter, 1st list, 1st point: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.4 CHORUS-V2 (1984–1986), pp. 4 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  14. ↑ V2, 2nd chapter, 4th subchapter, 1st list, 2nd point: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 2.4 CHORUS-V2 (1984–1986), pp. 4 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  15. ↑ Subsequent Events, PART I, ITEM 1: SEC (Ed.): Quarterly report [Sections 13 or 15 (d)] . 1997, SUBSEQUENT EVENTS, p. 7/7 ( sec.gov - American English: Quarterly report [Sections 13 or 15 (d)] .).
  16. ↑ Chorus Open Source ( Memento of the original from October 17, 2008 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice. @1@ 2Template: Webachiv / IABot / www.experimentalstuff.com
  17. ^ "Nous avons créé une des premières start-up de l'INRIA": L'HEBDOMADAIRE DES 40 ANS DE L'INRIA - NO 16-23 AVRIL 2OO7 (ed.): Code source . 2007, “Nous avons créé une des premières start-up de l'INRIA”, p. 2/2 ( google.com - French: “Nous avons créé une des premières start-up de l'INRIA” .).
  18. ↑ Jaluna on SourceForge
  19. ↑ Introduction, Chapter 1, Paragraph 5, Movement 1: Charles Pecheur: Using LOTOS for Specyfing the CHORUS Distributed Operating System Kernel . 1. Introduction, p. 2 (American English: Using LOTOS for Specyfing the CHORUS Distributed Operating System Kernel .).
  20. ↑ Abstract, 1st paragraph, 1st sentence: Charles Pecheur: Using LOTOS for Specyfing the CHORUS Distributed Operating System Kernel . Abstract, p. 1 ( ecorelocation.de - American English: Using LOTOS for Specyfing the CHORUS Distributed Operating System Kernel .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / www.ecorelocation.de  
  21. ↑ a b The architecture of ChorusOS, 1st chapter, 6.1 subchapters, 1st paragraph: Jean-Marie Rifflet: Programming under ChorusOS . Ed .: Université Paris 7 - Denis Diderot. November 14, 2000, 1.6.1 Overview, p. 8th f . ( ecorelocation.de - American English: Programming under ChorusOS .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / www.ecorelocation.de  
  22. ↑ Mikrokernel, 3rd chapter, 1.1.1 subchapter, 1st paragraph: Marc Rozier, Vadim Abrossimov u. a .: Overview of the CHORUS® Distributed Operating Systems . Ed .: Chorus Systèmes. CS / TR-90-25.1, February 1, 1991, 3.1.1.1 The CHORUS Nucleus, p. 7 ( psu.edu - American English: Overview of the CHORUS® Distributed Operating Systems .).
  23. ↑ ChorusOS 4.0 Installation Guide for Windows NT Hosts, Chapter 2, Section 1, Subsection 2, Section 1: Sun Microsystems, Inc .: ChorusOS 4.0 Installation Guide for Windows NT Hosts . Ed .: Sun Microsystems, Inc. November 1999, Chapter 2. Installing on the Host, p. 11 ( sun.com [PDF] American English: ChorusOS 4.0 Installation Guide for Windows NT Hosts .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / dlc.sun.com  
  24. ↑ a b Device Reference, Processor Reference and BSPs, Chapter 1, Sun Microsystems, Inc. (Ed.): ChorusOS 4.0 MPC8xx Target Family Guide . tape 806-3964-10 , December 1999, 1. ChorusOS 4.0 MPC8xx Target Family Guide, p. 16 ( ecorelocation.de [PDF] American English: ChorusOS 4.0 MPC8xx Target Family Guide .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / www.ecorelocation.de  
  25. ↑ a b Device Reference, Processor Reference and BSPs, Chapter 1, Sun Microsystems, Inc. (Ed.): ChorusOS 4.0 MPC8xx Target Family Guide . tape 806-3964-10 , December 1999, 1. ChorusOS 4.0 MPC8xx Target Family Guide, p. 17 ( ecorelocation.de [PDF] American English: ChorusOS 4.0 MPC8xx Target Family Guide .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / www.ecorelocation.de  
  26. ↑ Certification ( memento of the original from March 10, 2010 in the Internet Archive ) Info: The archive link was automatically inserted and not yet checked. Please check the original and archive link according to the instructions and then remove this notice. @1@ 2Template: Webachiv / IABot / get.posixcertified.ieee.org
  27. ↑ Overview, Chapter 3, Section 3.1, Section 5: Philippe Robin: comp.os.chorus Frequently Asked Questions (FAQ) . Ed .: Chorus Systèmes. tape 1.32 , February 2, 1998, 3. Chorus Product Offering ( ecorelocation.de - American English: comp.os.chorus Frequently Asked Questions (FAQ) .).  ( Page no longer available , search in web archives )  Info: The link was automatically marked as defective. Please check the link according to the instructions and then remove this notice.@1@ 2Template: Dead Link / www.ecorelocation.de  
  28. ↑ CVM (5FEA): Sun Microsystems (Ed.): ChorusOS 5.0 . tape 5.0 , December 10, 2001, Reference Manual Collection ( sun.com - American English: CVM (5FEA) - C Virtual Machine component for Java applications (ChorusOS man pages section 5FEA: ChorusOS Features and APIs) .).