Web site:
Origin: USA
Category: workstation, embedded
Desktop environment: CLI
Architecture: x86, Motorolla 68000, PowerPC, SPARC, ARM, MIPS
Based on: Mach kernel
Wikipedia: ChorusOS
Media: Install
The last version | Released: 5.1 | 2011

ChorusOS – a highly scalable and reliable embedded operating system that has established itself among top telecommunications suppliers. The ChorusOS operating system is used in public switches and PBXs, as well as within access networks, cross-connect switches, voice-mail systems, cellular base stations, web-phones, and cellular telephones.

The Sun Embedded Workshop software provides a development environment with the necessary tools to build and deploy the ChorusOS operating system on a telecommunications platform. The ChorusOS operating system is the embedded foundation for Sun’s Service-Driven Network. Offering high service availability, complete hardware and software integration, management capabilities and JavaTM technology support dedicated to telecom needs, the ChorusOS operating system allows the dynamic and cost-efficient deployment of new features and applications while maintaining the reliability and functionality of existing networks.

The ChorusOS operating system supports third-party protocol stacks, legacy applications, and applications based on real-time and Java technology, on a single hardware platform.

The ChorusOS operating system can be tuned very finely to meet the requirements of a given application or environment. The core executive component is always present in an instance of the ChorusOS operating system. Optional features are implemented as components that can be added to, or removed from, an instance of the ChorusOS operating system.

Each API function in the ChorusOS operating system is contained in one or more of the configurable components. As long as at least one of these components is configured into a given instance of the operating system, the function is available. Some library functions are independent of any specific component and are always available.

ChorusOS 5.0 runs over Solaris operating environments, and supports the following targets:
– UltraSPARC II (CP1500 and CP20x0)
– Intel x86, Pentium
– Motorola PowerPC 750 and 74×0 processor family (mpc7xx)
– Motorola PowerQUICC I (mpc8xx) and PowerQUICC II (mpc8260) microcontrollers


No download is available.



Web site:
Origin: USA
Category: Desktop
Desktop environment: CLI
Architecture: PowerPC
Based on: Independent
Wikipedia: MkLinux
Media: Install
The last version | Released: Pre-R2 | August 5, 2002

MkLinux – an Open Source operating system which consists of an implementation of the Linux operating system hosted on the Mach microkernel. We estimate that there are somewhere between 50,000 and 100,000 MkLinux users. A significant number of the installed MkLinux systems are being used in mission-critical applications.

During the early years, most MkLinux development occurred either at Apple or at The Open Group Research Institute in Grenoble, France. MkLinux Developer Release 1 (DR1) was released in early 1996.

MkLinux is a project begun by the OSF Research Institute (now Silicomp RI) and Apple Computer to port Linux, a freely distributed UNIX-like operating system, to a variety of Power Macintosh platforms running on top of OSF Research Institute’s implementation of the Mach microkernel.

Later that year, DR2 was released, incorporating numerous bug fixes. The Linux server was updated to the 2.0.x source base shortly thereafter. At about the same time, (December, 1996) PCI machines were supported and DR2.1 was completed and incorporated into Apple’s “Reference Release”. DR2.1 was released a few months later. With the exception of shared library support and support for 603e machines, very little changed until the appearance of the G3 PowerMacs in late 1997. Support for these machines trickled into the source base over the course of a few months, and pre-DR3, as it was then known, was frozen about March of 1998. While Apple’s quality assurance people tested the disk, the world moved on without it. As a result, a substantial number of bug fixes didn’t make it into the DR3 release.

By the time DR3 was released, at least three additional PowerBook models were partially supported (1400, 2400, and G3 series), and numerous major causes of crashes had been eliminated. At this point, a number of developers had made various fixes to PowerBook support, but they weren’t all in the same kernel.

At that point, at the request of Gilbert Coville, I sent out a request for patches and changes. The GENERIC kernels were born. Several developers joined me in setting up a CVS server for sources so that developers from around the world could easily coordinate their development efforts and maintain a single source tree.

Since the DR3 release, MkLinux has made significant advances in multiple Ethernet support, IDE support, floppy support, and overall stability. Literally hundreds of bug fixes and patches have been submitted in the past few months, and MkLinux is in a stronger position than ever to grow and improve for years to come.

Beginning in the summer of 1998, development work on MkLinux transitioned from Apple and OSF to a community-led effort.


MkLinux DR3 cdimage 648MB
md5sum: e9b4b07649e9fd7e74431a8267b96784
MkLinux DR3 7.18MB.src.tgz
md5sum: ad36bf17f2856ba7a980574b40b3c6e0
DR3 osfmk.export 379KB.tgz
md5sum: d11f1b9c38ccb9df2fc9112109a8afe5
DR3 osfmk 4.6MB.src.tgz
md5sum: e4e914d9f849f77fb3746be02ccde1df
DR3 tools 174KB.tgz
md5sum: d2e9fe89c6bd61097b5de18cfdee66f8

MkLinux MAINDISK 669MB.img
md5sum: a33137a038bbc84a7348a4746fe9f825
MkLinux MAINDISK-OLD 673MB.img
md5sum: 4ef456439841c13ac71f6a6c0d550b7d




Web site:
Origin: Germany
Category: Embedded, Mobile, Others
Desktop environment: GUI
Architecture: x86, PowerPC
Based on: µnOS
Media: Install
The last version | Released: 1.2 | October 22, 2006

Symobi (“System for mobile applications”) – a modern and mobile OS. It is based on the µnOS operating system which incorporates the Sphere microkernel. Symobi offers a complete graphical OS environment with services, a graphical user interface, standard programs, and drivers. The operating system is designed for the use in embedded and mobile systems, but is also suitable for other purposes.

Symobi is platform independent by architecture. Hence, it can be deployed on all modern processor architectures. Nevertheless, there is some work to do to really port Symobi to a new hardware platform. But this work is easy to do since only platform specific mechanisms (e.g. MMU) have to be implemented. There are no architectural changes to be made and there is no higher level programming work to do. As a result, Symobi can be ported to a new platform within weeks and to another processor model of an already supported platform within days. This basic ability of Symobi is liked a lot by our customers since it allows them to choose the hardware they really want and need for their application instead of having to choose a hardware fitting the RTOS used.

Valuable Abilities:
– real-time
– small size/footprint
– high provable stability/reliability
– simplicity
– high performance
– small, efficient API
– embeddable

Modern Features:
– multi-core/multi-processor support
– multi-platform
– client/server architecture
– isolated hardware driver architecture
– light-weight multithreading & multitasking
– strongly protected process spaces
– wide-range scalability

Supported Hardware:
– x386 / IA32
– ARM / XScale
– PowerPC


Symobi 1.2 Wave Live Demo i386
md5sum: f8e3aa7d8a6d38eb3240942a90d7b46c

Symobi 1.2 PowerPC Live Demo
md5sum: 0c426f9d8bfd3fe9eabc532c4b92edf3

Symobi 1.2 VMware Image Live Demo
md5sum: 35d9e6fb9acaa136b92c4a58b5ab963f




Web site: (not active)
Origin: USA
Category: Desktop
Desktop environment: Workplace Shell (WPS)
Architecture: x86, PowerPC
Based on: Independent
Wikipedia: OS/2
Media: Install
The last version | Released: 4.52 | December 2001

OS/2 – a proprietary operating system, started in 1985 by IBM and Microsoft with a name of “CP/DOS”. Originally, OS/2 was expected to gradually replace DOS and Windows.

In the summer of 1990, Microsoft announced Windows 3.0 and it became a monster hit. The relationship between IBM and Microsoft was already strained, and further development of OS/2 was left entirely to IBM. Microsoft went on to develop NT, enhance Windows, and produce Windows 95.

Eventually, IBM figured out what was wrong and fixed it. OS/2 2.0 and 2.1 used 386 memory management, ran almost all DOS programs, and ran most Windows applications as well. IBM now supports clone computers, and has largely abandoned its PS/2 Microchannel family for the same PCI, ISA, IDE, SVGA architecture everyone else uses.

In the fall of 1994, IBM released Warp (OS/2 3.0) and made its last big marketing push for OS/2. IBM had a product out ten months before Windows 95 would be released. OS/2 was technically a better system than Windows 95 would be, with real program integrity, priorities, and server-quality I/O. None of this was discussed in any of the IBM ads or announcements. Instead, IBM concentrated on a “one button connection to the Internet” through IBM’s expensive public network. It would be six months before IBM released a version of Warp for corporate and campus use (with LAN support) and IBM never succeeded in capturing market share for Warp among home computer users.

Application programs could not interfere with themselves or with each other. The system could natively use larger amounts of memory. Yet the system maintained the command language and file structure of DOS.

Each OS/2 program runs in its own address space. It is common to talk about the old 16-bit programs and the newer 32-bit programs, but OS/2 does not separate the two or treat them differently. More accurately, OS/2 assumes that each of its applications may have a mixture of 16-bit and 32-bit pieces. OS/2 is itself a hybrid system with mixtures of both types of code.

OS/2 recognizes when a program has been constructed using the old 16-bit tools (producing variable sized segments) or with the new 32-bit tools (providing 4K pages). The different EXE file structure changes the way that the program is loaded into memory. Once they start running, however, all modules get the same services and all are assumed to have both 16 and 32-bit components.

Native OS/2 programs open files, request storage, or load programs by calling standard system routines. These routines are packaged in the same sort of Dynamic Link Libraries (DLLs) that are used in Windows. There are 16-bit and 32-bit libraries with versions of all the standard system services, and a program can choose which to call.

The Workplace Shell (WPS) was introduced in OS/2 2.0. WPS is an object-oriented shell allowing the user to perform traditional computing tasks such as accessing files, printers, launching legacy programs, and advanced object oriented tasks using built-in and third-party application objects that extended the shell in an integrated fashion not available on any other mainstream operating system.

The last version of OS/2 4.52 was released in 2001.

The project was re-branded to ArcaOS and is under development by Arca Noae.


OS/2 3.0 Warp i386 383MB.iso
md5sum: 290f78744f5343e3bf05a331a8e0e45f
OS/2 4 Warp trial 333MB.iso
md5sum: debd1d8e3ab5e9a940e4458b9a5d6955
OS/2 4 Warp interactive demo for Win31/Win95 84MB.iso
md5sum: 95cbf702a31541e7ad20bc5e2d32bcb4




Web site:
Origin: USA
Category: Rescue
Desktop environment: CLI
Architecture: x86, x86_64, ARMHF, PowerPC
Based on: Debian
Wikipedia: Finnix
Media: Live CD
The last version | Released: active | 2021
Zobacz po polsku Zobacz po polsku: Finnix

Finnix – a small, text based rescue CD based on Debian GNU/Linux, targeted to system administrators. Finnix works in Live mode, but it can be installed on your computer’s hard drive. The Live system can be started from a CD, USB flash drive and via the network (PXE).

Finnix includes tools for disk partitioning, network traffic monitoring, boot record repair and installation of other operating systems.

Finnix is built on Debian from the testing branch and is available for i386, amd64, armhf and powerpc machines.

The Finnix Live image also includes the FreeDOS system.

The project was started in 1999, with its first public release in March 2000, making it one of the oldest LiveCDs (predated by DemoLinux and immediately preceded by the Linuxcare Bootable Toolbox).
The project developer is Ryan Finnie.

After 5 years of break, in May 14, 2020 a new version of Finnix 120 released.


Finnix 120 amd64 470MB.iso

Finnix 111 i386/amd64 163MB.iso
md5sum: f111ff8eee915f508ade13b934d47ce6
Finnix 111 ARMHF 111MB.iso
md5sum: f111ffa290ab46ad193fdbbb2952a785
Finnix 111 PowerPC 158MB.iso
md5sum: f111ff0864d2796d788a98785ecb7589




Web site:
Origin: UK
Category: Desktop
Desktop environment: GUI
Architecture: x86, ARM, PA-RISC, MIPS, PowerPC, SPARC
Based on: Independent
Wikipedia: Inferno
Media: Install
The last version | Released: 4 | March 28, 2015

Inferno – an operating system designed for building distributed and networked systems on a wide variety of devices and platforms. Inferno was based on the experience gained with Plan 9 from Bell Labs, and currently being developed by Vita Nuova. Applications for this system are written in the Limbo language. The name of the system and some related programs (including Styx, Limbo) come from the Dante’s Divine Comedy.

Inferno can run as a user application on top of an existing operating system or as a stand alone operating system. Most of the popular operating systems and processor architectures are supported:
– Host Operating Systems
– Windows NT/2000/XP
– Irix
– Linux
– MacOS X
– FreeBSD
– Solaris
– Plan 9

Inferno applications are written in Limbo®, a modern, safe, modular, concurrent programming language with C-like syntax. It is more powerful than C but considerably easier to understand and debug than C++ or Java. It is easy to express the concurrency in the physical world directly in Limbo’s syntax. Any Inferno application will run identically on all Inferno platforms.

High level security is an important part of the Inferno system. By using one standard protocol for all network communication, security can be focused on one point and provided at a system level. Inferno offers full support for authenticated, encrypted connections using a certificate based user identification scheme and variety of algorithms.

Inferno 4 was released in 2005 as free software.

Founded in March 2000, Vita Nuova Holdings Ltd is an operating systems and application development company specializing in technologies for distributed applications on network devices and embedded systems.


Inferno 20150328 Unix-like systems (FreeBSD, Linux, MacOS X, Plan 9) 71MB.tgz
md5sum: 1b3b406dcaa9d7919e933dd192d53a39

Inferno Windows 2000, XP, and 7
md5sum: 728b515bc6d866a24bed9b573965ee90

Inferno Mac OSX 386 3,7MB.tgz
md5sum: 83a10dc646f421dead3d59d63bc64ba8

Inferno source code




Web site: (not active)
Origin: Russia
Category: Desktop, Server
Desktop environment: KDE, GNOME
Architecture: x86, x86_64, PowerPC
Based on: Fedora
Wikipedia (RU): ASPLinux
Media: Install
The last version | Released: 14 | November 26, 2008

ASPLinux (Application Service Provider Linux) – a Russian distribution of the Linux operating system. It is based on the RPM packages, and it is fully compatible with Fedora distribution. Russian language support in this distribution works out of the box. Previously, the location was maintained for almost all Cyrillic codings: KOI8-R, KOI8-U, CP1251, ISO 8859-5, UTF-8. Starting from version 12, the team of designers departed from supporting many Cyrillic codings, leaving only UTF-8, and also resigned from the company’s installer, replacing it with Anaconda.

Up to version 9, ASPLinux was based on the Red Hat system. All next versions are based on Fedora distribution.

ASPLinux is easiest to install and use, 100% RedHat compatible Linux distribution. Full featured graphical and text mode installation program includes unique partitioning tool ASPDiskManager allowing to repartition your hard drive during installation without data loss. In order to simplify multibooting procedure we bundle ASPLinux with powerful graphical bootmanager ASPLoader. ASPLinux provides best available Asian and European languages localization. It bundles the best available Linux applications making it suitable for both home/office and server use. ASPLinux includes several graphical user environments such as KDE, GNOME and others to make your work with it a pleasure.

ASPLinux can be installed on a computer with at least i686 CPU, at least 128 Mb RAM, a CD-ROM drive for installation from a CD-ROM, a VGA-compatible
video-board and monitor.

ASPLinux editions:
– Deluxe – 2 DVDs with the system and source texts of the program (the widest set of programs), 3 printed instructions, 90 days of technical support;
– Standard – 2 DVDs with the system and source texts of the program, 2 printed instructions, 60 days of technical support;
– LiveMedia Edition – 1 DVD with the system, 1 printed manual, 30 days of technical support;
– Express – 1 DVD with system, 30 days of technical support;
– Greenhorn – LiveCD-distribution variant (in the latest version of LiveDVD), 10 days of technical support;
– ASPLinux Server.

ASPLinux is a business unit of SWsoft, a multinational software development company with headquarter in Singapore and offices in USA and Europe. ASPLinux contacts: Moscow, Russia.


ASPLinux 11.2 DVD 3.56GB.iso
md5sum: daa246178eb61599b8a6a0858194a0a2




Web site:
Origin: Switzerland
Category: Desktop
Desktop environment: TUI (text user interface)
Architecture: x86, Ceres, Xilinx Spartan, SPARC, PowerPC, RIOS, MIPS
Based on: Independent
Wikipedia: Oberon
Media: Install
The last version | Released: V5 | 2013 (?)

Oberon – a single-user, multi-tasking system that runs on bare hardware or on top of a host operating system. Oberon is also the name of a programming language in the Pascal/Modula tradition.

The Oberon project was started at the Swiss Federal Institute of Technology in Zürich (ETHZ) in 1985 by Niklaus Wirth and Jürg Gutknecht. Although the project was originally targeted towards in-house hardware, the language and system have now been ported to many computer platforms. Oberon is also a name of a modern integrated software environment.

In 1991, Jürg Gutknecht and his group continued the development towards the ETH Oberon System. The goal was to exploit the inherent potential and features of Oberon to a much larger degree, upgrade the system by a concept of composable and persistent objects, complement the textual user interface by a graphical companion and provide support for the ubiquitous network. In 1995, the first official Oberon System 3 release was finished. Since then, the system has been constantly improved and extended. In 1997, the Release 2.2 including a large palette of applications was published together with a comprehensive hypertext-based documentation. In March 2000, a new release was ready and the system was renamed “ETH Oberon System”.

The original Oberon system is a single-threaded, single-user, co-operative multi-tasking operating system that runs on bare hardware or on top of a hosted operating system as a single-window application. The ETH Oberon System is an extended version that has intrinsic support for persistent objects and for building graphical user interfaces. It presents itself as a hierarchy of modules, many of which export one or several powerful abstract data types. Application modules simply reuse these data types and do not have to care about their implementation at all.

ETH Oberon System highlights:
– Advanced Textual User Interface
– Integrated object support in the kernel
– Object Autonomy and Persistence
– Extensibility by Software Bus Technology
– Fully Hierarchical Composability
– Generalized MVC Scheme
– Powerful GUI Framework Gadgets
– Self-Contained Documents
– Extensibility on Different Levels

The ETH Oberon System package includes several interesting tools and applications. Many of them were developed as productivity tools by ETH assistants and students.

The Oberon system is available free of charge and no registration is required for downloading the material. The source code is available under a BSD-like License.

The source of the Oberon screenshot is Wikipedia; uploader: SomPost; under BSDU License.




Web site:
Category: Desktop
Desktop environment: Window Maker
Architecture: PowerPC
Based on: Darwin
Media: Live
The last version | Released: | July 17, 2015

PureDarwin – a community project to make Darwin more usable (some people think of it as the informal successor to OpenDarwin).
Darwin is the Open Source operating system from Apple that forms the basis for macOS.

The goal of the PureDarwin project is to make Darwin more usable for open source enthusiasts and developers by providing documentation and by enabling them to retrieve, understand, modify, build, and distribute Darwin.

UseD components are specifically released by Apple for use with Darwin, as well as other Open Source components (collectively called “upstream code”). Specifically, it means that we do not use any components from Mac OS X. It also means that we try to stay as close as possible to the “outside world” as in Mac OS X (e.g., regarding the choice of compilers, options, etc.). It does not mean, however, that we do not modify and add to the upstream code, to the extent that the respective licenses allow.




Web site: (not active)
Origin: USA
Category: Desktop
Desktop environment:
Architecture: PowerPC
Based on: BSD
Media: Install
The last version | Released: 7.2.1 | July 16, 2004

OpenDarwin – a freely available, multi-platform Berkeley Software Distribution (BSD) / Mach 3.0 kernel-based UNIX-like operating system.

The goal of the OpenDarwin project, founded in April 2002, is to create an independent branch of the Darwin operating system that increases collaboration between Apple developers and the open source community. Apple benefits from the project because development in OpenDarwin is often incorporated into Darwin releases; and the open source community benefits since it is given complete control over its own operating system.

The OpenDarwin developers use a version control system called Concurrent Versions System (CVS to manage changes to the OpenDarwin source code. Many of the OpenDarwin developers are Apple employees, whereas others are not. It should be noted that the OpenDarwin project is fully independent of Apple, and has complete control over it’s own code, though they generally try to stay compatible with Apple’s own software.

Like most modern operating systems, OpenDarwin employs a built-in kernel debugger to help the developers find kernel bugs.

The goal of the OpenDarwin project is to provide resources for open source developers to interact and produce products for Apple’s Mac OS X. One of the key aspects of the project is to enable interested Mac OS X developers to be able to retrieve, modify, build, and distribute operating system changes.

The project has a Core Team , similar to the other various BSD projects. We are currently seeking contributors for all aspects of the project, and additions to the Core Team will be chosen from the most active contributors. One of the initial Core Team’s first action items is to establish the rules for how future Core Team and project members will be selected.

OpenDarwin core team members:
– Rob Braun – Founder of (a now defunct darwin information site), maintainer of xinetd , and contributing author to the UNIX System Administration Handbook.
– Kevin Van Vechten – The Darwin team at Apple.
– Torrey T. Lyons – A committer on the XFree86 Project, Torrey is the founder of the XonX Project. He is a scientist at Mission Research Corporation, Los Angeles.


No download is available