CHORUS Offerrings to Academic Institutions summary: The offerrings described in this note may be made to Schools, Universities and Academic Research Labora- tories, requesting access to a CHORUS system. These offerings are an integral part of the "Chorus systemes Academic Institutions Marketing Programme". --------------------- I. Objectives ============= The objectives of this programme are to: 1. provide researchers and educators with state-of-the-art modular operating systems technologies, forming the basis of the next gen- eration commerical operatings systems, 2. facilitate the exchange of work among researchers. Main benefits are: 1. low pricing, 2. simplified licensing and easy access, 3. sources freely exchangeable among licensees, 4. free CHORUS tutorials on space-available basis, 5. ftp distribution, 6. mailing lists and news group, 7. clearinghouse for contributed operating system and application software and documentation. Chorus systemes objectives of this programme are to: 1. establish CHORUS as a standard modern operating system for operat- ing systems education and research projects, 2. facilitate the development and integration of new operating system technologies in CHORUS within academic and R&D environments, 3. develop a CHORUS share of mind in the international R&D community, 4. increase CHORUS visibility in the academic and R&D communities. The Education and Research Marketing Programme is based on offering currently available Chorus systemes standard and "special" products, with simple support services provided mostly by "automatic" electronic means. Conditions described below apply to Schools, Universities, and Academic Research Laboratories. II. Academic Binary Licenses ============================ Contents -------- 1. One binary license for one single network of machines running one CHORUS binary product (means machines connected on the same medium), for a given class (or course), or for one given project (1) (class (or course) and/or project must be identified). Chorus binary products will be residing on hosts (referred as the desig- nated machines) fully identified by their CPU/system serial number. 2. ftp retrieval of licensed products & documentation (2) : Chorus allows restricted access by ftp to retrieve licensed products and a full set of on-line documentation in PostScript format (man pages, user's and implementation guides). Access is provided only: o to an identified user (user account & password) ; o from one designated access machine (identified by its IP address) ; o for a limited number of ftp sessions (up to 3 sessions) ; o and for a limited time of retrieval (up to 3 weeks, with effect from date of license agreement). 3. Dial-in access to bug lists and bulletin board information center (mailing-list): Allows free access to bug announcements, and exchange of information with other binary licensees and Chorus staff. 4. Electronic access to "free" contributed software in binary form through the Chorus Clearing House (access by ftp). 5. No support (except limited installation support provided within 2 weeks after receipt of software). III. Support for Academic Binary Licenses ========================================= Licensee will identify one person, in charge of interacting with Chorus systemes for all support related matters. Contents -------- o Automatic electronic update service: allows to automatically receive maintenance updates as they are released. o Up to 10 telephone or e-mail consultations: each consultation is comprised of as many phone or e-mail conversations as are necessary to provide a solution, work-around or otherwise bring closure to a specific problem. Each consultation is limited to one issue. The "limits" of a consultation are defined by Chorus systemes. IV. Academic Source Licenses ============================ Contents -------- 1. One source license of one CHORUS standard or ``special'' product, including known ports of the CHORUS/Nucleus (3) (See Annex D), and the right to produce and run binaries (4), granted to one identified geographic site. Chorus source product will be residing on hosts (referred as the designated machines) fully identified by their CPU/system serial number. 2. ftp retrieval of licensed products & documentation (5) : Chorus allows restricted access by ftp to retrieve licensed products and a full set of on-line documentation in PostScript format (man pages, user's and implementation guides). Access is provided only: o to an identified user (user account & password) ; o from one designated access machine (identified by its IP address) ; o for a limited number of ftp sessions (up to 3 sessions) ; o and for a limited time of retrieval (up to 3 weeks, with effect from date of license agreement). 3. Dial-in access to bug lists and bulletin board information center (mailing-list): Allows free access to bug announcements and fixes, and exchange of information with other source licensees and Chorus staff. 4. Electronic access to "free" contributed software in source form through the Chorus Clearing House (access by ftp). 5. Right to freely exchange modified or extended CHORUS source code with other CHORUS equivalent source licensees (verification by Chorus systemes required). 6. No support (except limited installation support provided within 2 weeks after receipt of software). V. Support for Academic Source Licenses ======================================= Support as defined below is only available for standard CHORUS pro- ducts. No support is provided on ``special'' products, or advanced development snapshots. Licensee will identify one person, in charge of interacting with Chorus systemes for all support related matters. V.1. Basic support for Academic Source Licenses ----------------------------------------------- Contents -------- o Free access for 2 people from the licensed institution to CHORUS training classes in the limit of the available space. o Automatic electronic update service: allows to automatically receive maintenance updates as they are released. o Up to 10 telephone or e-mail consultations: each consultation is comprised of as many phone or e-mail conversations as are necessary to provide a solution, work-around or otherwise bring closure to a specific problem. Each consultation is limited to one issue. The "limits" of a consultation are defined by Chorus systemes. V.2. Enhanced support for Academic Source Licenses -------------------------------------------------- Contents -------- o Free access to people from the licensed institution to CHORUS train- ing classes in the limit of the available space. o Automatic electronic update service: allows to automatically receive maintenance updates as they are released. o Unlimited telephone or e-mail consultations: each consultation is comprised of as many phone or e-mail conversations as are necessary to provide a solution, work-around or otherwise bring closure to a specific problem. VI. Technology Requirements =========================== Chorus systemes is committed to providing state-of-the-art operating system technology for next generation open systems products. Because our technology is sold on a source code and technology license basis rather than as a packaged product, it is expected that customers and academic institutions using our product will have a sufficient develop- ment environment to support CHORUS. The minimum requirement to gen- erate a CHORUS Nucleus or CHORUS/MiX product is a standard UNIX (SCO UNIX R3.2, System V Release 4 or SunOS) "C" development environment. Our products are binary-compatible with either UNIX System V Release 3.2 or UNIX System V Release 4. To achieve this compatibility, and to ensure that our products evolve in step with Novell/USG offerings, our products contain Novell/USG source code. This may require you to obtain additional licenses from Novell/USG, and possibly other companies as well, in order to work with CHORUS products. This is determined on a project by project basis (cf. "Pre-Requisites" section in Product Datasheets). Annex A - Contacts World (except U.S.A. & North America): Chorus systemes 6, Avenue Gustave Eiffel F-78182, Saint-Quentin-en-Yvelines cedex France Tel: +33 1 30 64 82 00 Fax: +33 1 30 57 00 66 Email: info@chorus.fr Attention to: Didier Irlande U.S.A. & North America: Chorus Systems Greenbrier Parkway, Beaverton, OR 97006 U.S.A. Tel: (503) 690 23 00 Fax: (503) 690 23 20 Email: info@chorus.com Attention to: Didier Irlande Other ftp access: A Chorus anonymous ftp server is accessible in: Europe, from Chorus systemes in France: ftp.chorus.fr <192.33.15.3>, directory: pub U.S.A., from Oregon Graduate Institute (6), Portland, OR: cse.ogi.edu <129.95.10.2>, directory: pub Chorus product datasheets are available in pub/chorus-datasheets, as ASCII files. Chorus reports are available in pub/chorus-reports, as compressed PostScript files. Chorus slides are available in pub/chorus-slides, as compressed PostScript files. Annex B - CHORUS Standard products CHORUS/Kernel v3 r5 Delivery date: January 1994 Release number: CHORUS Kernel v3 r5.1.0 Features: o real-time o enhanced distributed IPC o SMMP (Shared Memory Multi-Processors) Reference platform: Compaq 486 (see Annex D) Available as: Source Support: Yes CHORUS/Simulator v3 r4.1 Delivery date: July 1992 Release number: CHORUS SIM v3 r4.1.0 Features: == Kernel v3 r4 with distribution Reference platform: Sun 3/80, SPARCstation, under SunOS 4.1 Available as: Source, or Binary Support: Yes CHORUS/MiX V.4 r3 Delivery date: January 1994 Release number: CHORUS/MiX V.4 r3.0.0 Features: o Kernel v3 r5.1 o MiX V.4 == UNIX SVR4.0 (binary compatible with SVR4.0/386, ver- sion 4) o CHORUS Single Kernel System Image (SKSI): - C_actors - extended CHORUS/GDB (local & remote, for multi-threaded processes, based on GDB4.5 from the Free Software Foundation) o current (temporary) restrictions: - no multi-threaded MiX processes - no transparent distribution of MiX processes Reference platform: Compaq 486 (see Annex D) Available as: Source (7), or Binary Support: Yes CHORUS/Fusion r1 Delivery date: June 1994 Release number: CHORUS/Fusion r1.0.0 Features: o binary product o Kernel v3 r4.2 o source and binary compatibility with SCO UNIX System V/386 Release 3.2 v4.2 o multi-threaded processes (POSIX 1003.1c) o real-time extensions (POSIX 1003.1b) o distributed features: - transparent CHORUS IPC - transparently distributed MiX processes - transparently distributed file system o extended CHORUS/GDB (local & remote, for multi-threaded processes, based on GDB4.5 from the Free Software Foundation) o reduced system for embedded configurations o X11R4 clients and server (on SVGA display) Reference platform: Compaq 486 (see Annex D) Available as: Binary Support: Yes Annex C - CHORUS unsupported ``Special'' Products CHORUS/MiX V.4 on Compaq 386 multi-processor Delivery date: February 1993 Release number: N/A Features: Prototype for validating the multi-processor version of the CHORUS kernel o Kernel v3 r4 o CHORUS/MiX V.4 r2 o local disk support (currently no Ethernet support) Reference platform: Compaq SystemPro 386 (bi-processor) Available as: Source (8) Support: No CHORUS/MiX V.4 on SPARCstation Delivery date: May 1992 Release number: CHORUS/MiX V.4 r1.2.2 Features: Prototype == CHORUS/MiX V.4 r1.2 o Kernel v3 r4 with support for distribution o simple support of console o Ethernet support, (currently no local disk support) Reference platforms: o ``Sun4c'' architecture: SPARCstation 1 series (9), 8 Mb memory or more (for MiX) o ``Sun4e'' architecture: SPARC1E, VME board version of SPARCsta- tion 1 o Cypress SPARC chip set, including Sun Reference MMU (10) Available as: Source (11) Support: No CHORUS/MiX V.3.2 on iPSC2 Delivery date: April 1992 Release number: CHORUS/MiX V.3.2 r3.0.1 Features: Prototype == CHORUS/MiX V.3.2 r3 o Kernel v3 r3 o no device connected to the iPSC2 (if any) is supported o all I/O (disk, terminal) are performed on the host (running UNIX) Reference platform: iPSC2 (i386 based) Available as: Source (12) Support: No CHORUS/MiX BSD on SPARCstation Delivery date: February 1994 Release number: N/A Features: o Kernel v3 r4 o X11R5 client & server support o Ethernet support, (currently no local disk support) o No documentation Reference platform: o ``Sun4c'' architecture: SPARCstation 1 series (13), 8 Mb memory or more (for MiX) Available as: Source (14) Support: No CHORUS/MiX BSD on Mips R3000 Delivery date: May 1993 Release number: N/A Features: o Kernel v3 r3b o simple support of console o Ethernet support, (currently no local disk support) o No documentation Reference platform: o SONY 3410 workstation Available as: Source (15) Support: No CHORUS/Kernel v3 r4 on T805 Delivery date: May 1992 Release number: CHORUS Kernel v3 r4.0.5 Features: o Prototype of CHORUS Kernel v3 r4 on a network of Transputers o No documentation Reference platforms: o Host: SPARCstation/SunOS 4.1 o Target: T805 board, 4 Mbytes memory, SBUS connection to host; T805 network up to 8 sites (Inmos VME backplane). o Environment: Inmos C/C++ TCOFF toolset (version 2.0 or later), modified iserver Available as: Source, Binary Support: No CHORUS/COOL v2 r1 Delivery date: o October 1993 (with CHORUS/MiX V.4) o June 1994 (with CHORUS/Fusion) Release number: CHORUS/COOL v2 r1.0.0 Features: Prototype object-based O.S. platform for the support of object-oriented applications Reference platform: o CHORUS/Fusion (16) on Compaq 386-486 (see Annex D), o CHORUS/MiX V.4 (17) on Compaq 386-486 (see Annex D), using C_actors (CAUTION: AT&T C++ 3.0 compiler is mandatory) Available as: Source Support: No Annex D - CHORUS Reference Platforms and Supported Configurations CHORUS/MiX standard reference platforms Glossary: o Recommended System: recommendation for customer hardware o Supported Hardware: hardware covered by maintenance policy o Reference Hardware: hardware used by Chorus systemes for validation and benchmarking o Example Hardware known to work: clones and other PCs where CHORUS/MiX V.4 has previously run on Recommended System: o Processor = 80486DX or 80386DX with 80387 o Bus = ISA or EISA Master Bus o Memory (RAM) = 12 Mb minimum o Floppy = 3.5" High density (1.44 Mb) o Streamer = QIC 24 streamer drive (60 or 150 Mb) o Disk Controller = Integrated IDE controller o Disk Drive = 110 Mb IDE drive (CMOS type 50) o Display = VGA adapter, standard VGA monitor o Keyboard = standard 102 keys PC/AT (QWERTY) o Network = SMC Ethercard Elite+ 16 bits (formerly Western Digital WD8013) Supported Hardware: o Bus = Any 386/486 ISA or EISA (No MCA support) o Floating Point = Intel 80387 or compatible (ex: Cyrix) (MANDATORY) o Disk Storage = IDE/ESDI/ST506 hard disks o Ports = - Standard PC serial ports with NS16450 UARTs or compatible - Up to 2 ports configured as COM1 & COM2 o Display = CGA, EGA, VGA with monochrome or color monitor o Keyboard = Standard PC/AT with 102 keys (QWERTY) o Network = SMC Ethercard Elite+ 8 bits (formerly Western Digital WD8003), SMC Ethercard Elite+ 16 bits (formerly Western Digital WD8013) and Excelan EXOS 205T (which is not supported with 486/50) Reference Hardware: COMPAQ DESKPRO 486/33M: o System = 80486DX2, EISA Bus, 256 Kb writeback cache o Memory = 16 Mb comprising: - 8 Mb default - 0-60Mb extension board equipped with 1 x 8Mb extension module o Floppy = 3.5" High density (1.44 Mb) o Disk Controller = Integrated IDE controller o Disk Drive = 420 Mb IDE drive (CMOS type 84) o Ports = - 1 parallel port - 2 serial ports (COM1 & COM2) o Display = Standard VGA adapter with standard color monitor [WARNING: QVISION 1024/E NOT SUPPORTED WITH CHORUS MiX V.4] o Network = SMC Ethercard Elite+ 16 bits (formerly Western Digital WD8013) Example Hardware known to work: o Systems = - Compaq Systempro 386/33 - Dell 450/L 486P/50 466/M - Olivetti CP/486 486/25 - various no name clones o Disk Controller = - ESDI: UltraStor 12F, Western Digital WD1007A - IDE: Various no name generic adapters o Disk drive = - Western Digital WDAP 4200 (220 Mb) - Conner CP3111 (110 Mb) - Quantum PRO 425A (420 Mb) - Seagate and others o Display = - Paradise - VGA/Ultra o Monitor = - Nec 3d - Hitachi 15MVX - Samsung - and other standard VGA monitors o Network = - SMC Ethercard Elite+ 8 bits (formerly Western Digital WD8003) - SMC Ethercard Elite+ 16 bits (formerly Western Digital WD8013) - Excelan EXOS 205T IMPORTANT: Chorus systemes has not tested all possible combinations of the hardware listed above and some combinations may produce hardware configurations that will not work correctly. Other Known CHORUS Kernel Ports (18) o M88K (Kernel v3 r4): by Motorola on board MVME187 + SCSI controller board MVME328 o HP-PA (Kernel v3 r3b): by Oregon Graduate Institute, Portland, Oregon o micro-Vax (Kernel v3 r3b): by Trinity College, Dublin, Ireland o M680X0 configurations: - Sun 3/50, Sun 3/60, Sun3E: old CHORUS versions - Sun 3/80 - Gipsi ``Le tX'' (M68030, M68040): by Gipsi, Saint-Quentin- en-Yvelines - Apple Macintosh II: by Institut National des Telecommunications, Evry, France - MVME 147S board: by University of Alberta, BT, Canada - Force 68030 board: by Siemens research group, Munich, Germany - M68040 with MVME167 bus: by Alcatel-NS NOTES: 1. Assumes that licensee has the right to duplicate Novell/USG bina- ries, for those CHORUS products which contain Novell/USG code. If this is not the case, Chorus systemes should be asked to provide additional copies at extra cost. 2. For those sites which do not have ftp access, tapes and/or diskettes can be supplied at extra cost. 3. May involve additional licensing requirements to be discussed on a case by case basis. 4. Assumes that licensee has the right to produce Novell/USG binaries, for those CHORUS products which contain Novell/USG code. If this is not the case, Chorus systemes should be asked to provide additional binary copies (see ``Binary licenses''). 5. For those sites which do not have ftp access, tapes and/or diskettes can be supplied at extra cost. 6. Please note that OGI, who work closely with Chorus, are providing a US site as a favour, try not to swamp them during peak hours. 7. Requires a SYSTEM V, Release 4.0, i386 implementation, version 4, source license from Novell/USG. 8. Requires a SYSTEM V, Release 4.0, i386 implementation, version 4, source license from Novell/USG for the machine dependent parts. 9. Sun 4/20 (SPARCstation SLC) is the only platform actually tested at Chorus but other SPARCstation 1 models should also be supported 10. Since this is just a chip set, a port would still be required to a full machine 11. Requires a SYSTEM V, Release 4.0, i386 implementation, version 4, source license from Novell/USG, and a SunOS 4.1 source license for the machine dependent parts. 12. Requires a SYSTEM V, Release 3.2, i386 implementation, source license from Novell/USG. 13. Sun 4/20 (SPARCstation SLC) is the only platform actually tested at Chorus but other SPARCstation 1 models should also be supported. 14. Requires a BSD 4.4 license from UC Berkeley for the machine dependent parts. 15. Requires a BSD 4.3 Reno license from UC Berkeley. 16. No extra license fee required if ordered with CHORUS/Fusion. 17. No extra license fee required if ordered with CHORUS/MiX V.4. 18. Those ports are NOT currently available through Chorus systemes.