Fsaos

Fsaos

Web site: github.com/farlepet/fsaos
Origin: USA
Category: Desktop
Desktop environment: CLI
Architecture: x86
Based on: Independent ?
Wikipedia:
Media: Live
The last version | Released: ? | August 8, 2014

Fsaos (Fairly Simple Assembly Operating System) – an operating system created purely for hobby and education purposes.

It is mostly written in Assembly and released under the MIT License.

The project founder is Peter Farley.

Download

Fsaos x86 485KB.iso
md5sum: 20de75f18ab08497af843331245cd766
Fsaos source code 89KB.zip
md5sum: 1874dc55b57a6d1542db1205b1185d62

 

OpenStep

OpenStep

Web site: gnustep.org/resources/OpenStepSpec/OpenStepSpec.html
Origin: USA
Category: Desktop
Desktop environment:
Architecture: IA-32, PA-RISC, SPARC
Based on: UNIX
Wikipedia: OpenStep
Media: Install
The last version | Released: ? | ?

OpenStep – an object-oriented operating system that uses any modern operating system as its core. Mainly created by NeXT. NeXT Computer Inc, and Sun Microsystems Inc. teamed up in late 1993 to push a free object layer API based on the NeXTSTEP object system. This agreement evolved into the OpenStep specification which was published by NeXT in a first draft back in summer 1994.

There is a distinction between OpenStep, which is an API specification, and OPENSTEP (capitalized) which is a specific implementation of OpenStep developed by NeXT. Although it was originally created on a Unix-based Mach kernel (just like the NeXTSTEP core), OPENSTEP versions were also available on Solaris and Microsoft Windows NT. Therefore, OPENSTEP libraries (which were supplied with the OPENSTEP system) are actually a subset of the original OpenStep specification.

Download

No download is available.
md5sum:

 

NeXTSTEP

NeXTSTEP

Web site: (not active)
Origin: USA
Category: Desktop
Desktop environment:
Architecture: Intel x86, Motorola 68000, SPARC, PA-RISC
Based on: UNIX
Wikipedia: NeXTSTEP
Media: Install
The last version | Released: 4.2 Pre-release 2 | September 1997

NeXTSTEP – an object-oriented, multitasking operating system created by NeXT Computer, Inc. a company founded in 1985 by Apple Computer co-founder Steve Jobs.

This system was created on the base of Mach microkernel and BSD Unix system code. NeXTStep was oriented to work in a graphical environment. It had a very well-prepared, intuitive user interface, based on object-oriented architecture, quite different from both the most popular then Microsoft Windows 3.1 and Mac OS. The visualization engine was based on Postscript, which on one hand made it very demanding in terms of hardware (considerable demand for memory) and on other hand an ideal solution for industrial and designer workstations.

NeXTSTEP 1.0 was released 18 September 1989 after a couple of hits in 1986, and last Release 3.3 in early 1995, and previously worked only on the Motorola 68000 CPU family (especially the original black boxes) and the generic IBM compatible x86/Intel, Sun SPARC , and HP PA-RISC. About the time 3.2 releases NeXT teamed up with Sun Microsystems to develop OpenStep, cross-platform implementation of the standard (for Sun Solaris, Microsoft Windows, and NeXT Mach kernel version) based on NEXTSTEP 3.2.

In February 1997, after the purchase of NeXT by Apple, it became the source of the popular operating systems macOS, iOS, watchOS, and tvOS.

The NeXTSTEP screenshot’s author: Gürkan Sengün; source: Wikipedia; License: GNU GPL.

Download

No download is available.
md5sum:

 

Overclockix

Overclockix

Web site: overclockix.com (not active)
Origin: USA
Category: Desktop
Desktop environment: GNOME, KDE
Architecture: x86, x86_64
Based on: Debian
Wikipedia:
Media: Live CD
The last version | Released: 7.8.0 | June 1, 2015

Overclockix – a Debian based Linux distribution for hardware tuning, stress-testing, and overclocking.

The first versions of Overclockix were based on Knoppix and were created by Arkaine23 in 2003. It was under active development between 2033 and 2005.

It was re-born in 2011 by mbentley and developed until 2015.
The live system’s base has been changed from Knoppix to Debian with GNOME desktop as default.

Download

Overclockix LTSP21 i386 670MB.iso
md5sum: 7d441acd37a4019e3973835d0905de37

 

Monoppix

Monoppix

Web site: monoppix.com (not active)
Origin: USA
Category: Desktop
Desktop environment: KDE
Architecture: x86
Based on: Knoppix
Wikipedia:
Media: Live CD
The last version | Released: 1.1.8.0 | August 22, 2005

Monoppix – a Live CD Linux distribution, based on Knoppix, which showcasing and spreading Mono technology which is a free .NET framework implementation to Linux/Unix operating systems.

It is a live system so it works without installing it on your hard drive – it runs completely off the CD and RAM.

The live CD features:
– Mono runtime environment, compiler and class libraries
– Monodevelop – Mono enabled IDE
– XSP – ASP.NET web server
– GTK# – for desktop applications (sample included)
– MySQL database server
– Quickstarts and Mono walkthroughs and tutorials

Download

Monoppix 1.1.8.0 i386 491MB.iso
md5sum: e8c59b7583925369ff94f1be889d3af1

 

SunOS

null

Web site: oracle.com/us/sun/index.html (not active)
Origin: USA
Category: Server
Desktop environment: CLI
Architecture: 386i, Sun, SPARC
Based on: BSD
Wikipedia: SusOS
Media: Install
The last version | Released: 4.1.4 | November 1994

SunOS – a UNIX based OS derived from BSD, created by Sun Microsystems. Initially released in 1982, it was the standard OS on Sun Machines at that time. Platforms supported by this OS were the Motorola 68000, the Sun 386i, and the SPARC.

Sun-1’s were the very first models ever produced by Sun. The earliest ran Unisoft V7 UNIX; SunOS 1.x was introduced later. According to some sources, fewer than 200 Sun-1’s were ever produced; they are certainly rare. The switch from Motorola 68000’s to 68010’s occurred during the Sun-1’s reign. Some models are reported to have 3Mbit Ethernet taps as well as 10Mbit.
68000-based Sun-1’s are not supported by SunOS. The last version of SunOS to support Sun-1’s may be the same as the last version to support Sun-2’s, since the 100U CPU boards are the same part.

Sun-2’s were introduced in the early 1980’s and were Sun’s first major commercial success. While not as popular or as common as the later Sun-3’s, they did well and there are still quite a few in circulation in the home/collector-used market.
All Sun-2’s are based on the Motorola 68010 and run SunOS. The last version of SunOS to support Sun-2’s was 4.0.3. Early Sun-2’s were Multibus; later models were VME, which Sun continued to use through the Sun-3 era and well into the Sun-4 line.

Sun switched to using the Motorola 68020 with the introduction of the Sun-3’s. A few later models had 68030’s, but by that time Sun was already moving toward SPARC processors. All models either have a 68881 or 68882 FPU installed stock or at least have a socket for one. All models which are not in pizza box chassis are VMEbus. Two out of three pizza box models have a “P4” connector which can take a framebuffer; the exception is the 3/50.
Support for Sun-3’s was introduced in SunOS 3.0. The last version of SunOS to support Sun-3’s was 4.1.1U1.
During the Sun-3 era, Sun introduced the handy practice of putting the model number on the Sun badge on the front of the chassis.
There are two different kernel architectures in the Sun-3 model line. All 68020-based models are “sun3” architecture; 68030-based models (the 3/80 and 3/4xx) are “sun3x” architecture.

The Sun 386i models, based on the Intel 80386 processor, were introduced when 80386-based IBM PC/AT clones were starting to become widespread. Intel had finally produced a chip sufficiently capable (32-bit, among other things) to allow porting SunOS, and using an Intel processor and an ISA bus offered the ability to run MS-DOS applications without speed-draining emulation. Unfortunately, they were a dismal failure.
Support for Sun-386i’s was introduced in SunOS 4.0. The 386i SunOS releases came from Sun’s East Coast division, so 386i SunOS was not identical to the standard version with the same number. The last released version of SunOS to support Sun-386i’s was 4.0.2; there are a few copies of 4.0.3Beta (with OpenLook 2.0) floating around.

Support for Sun-4’s was introduced in SunOS 4.0, although there was a special variant of SunOS 3.2 for Sun-4’s which was shipped with some very early units. Since this product line is still current, it is still in general supported by SunOS, which has mutated to become part of Solaris. Support for some earlier models has been dropped, and some later models require at least 4.0.3c, 4.1.1, or Solaris 2.x.

SunOS took a shift starting with version 5.0, which changed its base from BSD to Unix System V Release 4, and became Solaris. The last release under the SunOS name was Version 4.1.4, released in November 1994.

Download

No download is available.
md5sum:

 

Evolution Makeiso

Evolution Makeiso

Web site: evolutionlinux.com (not active)
Origin: USA
Category: Desktop
Desktop environment: CLI
Architecture: x86_64
Based on: Arch Linux
Wikipedia:
Media: Live CD
The last version | Released: 2015.11.01 | November 1, 2015

Evolution Makeiso – a live media based on Arch Linux, created by Makeiso script.

The goal of Makeios is to create an easy to use method of duplicating an existing Arch install for installation on new hardware. Makeiso will create a live iso containing all the info to recreate your Arch install, within a GUI environment.

The Makeiso script will create a live ISO that will include an all new net-based, guided manual CLI installer.

The newly created live ISO will install an up to date duplicate of your Arch install, or alternatively install a new Arch “base only” system.

Download

Evolution Makeiso 2015.11.01 amd64 572MB.iso
md5sum: 50dba50a0e104d0f04bb00bbb0d4ec66

 

GNOSIS

null

Web site: cis.upenn.edu/~KeyKOS/Gnosis/Gnosis.html (not active)
Origin: USA
Category: Server
Desktop environment: CLI
Architecture: IBM ?
Based on: Independent
Wikipedia: GNOSIS
Media: Install
The last version | Released: ? | ?

GNOSIS (Great New Operating System In the Sky) – an example of a completely different kind of operating system. Gnosis was developed by TYMSHARE as a proprietary control program and it also developed proprietary application packages to run on it. GNOSIS was based on the research of Norman Hardy, Dale E. Jordan, Bill Frantz, Charlie Landau, Jay Jonekait, et al. McDonnell Douglas bought Tymshare, Inc. and then sold it in 1984 to Key Logic.

Programs under Gnosis are built out of protection domains with firewalls between them. Domains are small, simple, and cheap.
Domains communicate through doors in the firewalls, called capabilities. Capabilities are a simple, uniform, efficient means of representing authority.

There are several significant factors which make it possible.

* First, and foremost, the Gnosis concept of distinct domains without implicit interactions between them results in simpler programs. Because of this, we have had to spend a great deal of time designing the interfaces between these domains to insure that adequate function exists in each; but perhaps even that is a benefit since we will know exactly how the system goes together. The basic design of Gnosis will ensure that no compromises to the design occur during the implementation.

* Second, because individual components are completely isolated from each other, except for the prescribed interfaces, it is a simple matter to implement each domain independently of the remainder of the operating system. Very little scaffolding is required. We went to install the CMS editor in Gnosis and noted all of the things we thought ought to be there as co-requisites, things like a command language to call the editor, a file system, a loader, catalog facilities, and so on. To our surprise, we discovered that we didn’t need any of those facilities. We could just connect the editor directly to the terminal handler and test it. This made development go much quicker.

* Third, we have been able to coexist with, and take advantage of, CMS during the early going. We expect to use CMS services for quite some while for compiling programs and so forth. Thus our “critical mass” of code is very much smaller that it would otherwise be.

* Fourth, the basic design of Gnosis allows us to write most of the operating system as user code, which means we will be able to eliminate a lot of duplication of effort in terms of testing tools, etc. The system will also be much simpler because all of the details of the hardware are masked in the kernel. Consequently no domain programmer need ever deal with them, which makes the domains simpler, and also greatly reduces the impact of any hardware changes. We have tended to follow the advice of Fred Brooks in the Mythical Man-month, where he suggests “be prepared to throw the first one away.” We have implemented each domain with the simplest possible algorithms in order to test the design. Later we will have to discard many of these domains and rewrite them with high performance algorithms which obey the same interface specifications. Most of these first attempt domains can be implemented In a matter of days.

* Last, but certainly not least, we have a relatively high technology “office of the future” system called AUGMENT which we are using to keep all of our design notes as well as our user documentation. The use of this system,will save us a significant amount of labor as we develop a user community over the next several years.

The combination of these facilities has made it possible for us to implement a great deal of function very quickly. As Norm mentioned earlier, we have only just started running our first domains recently. Yet we expect to be able to have a significant online database application operational within a year.

Download

No download is available.
md5sum:

 

HPBSD

null

Web site: flux.utah.edu/~mike/hpbsd/hpbsd.html
Origin: USA
Category: Server
Desktop environment: CLI
Architecture: HP 9000
Based on: 4.3BSD
Wikipedia:
Media: Install
The last version | Released: 2.0 | April 1993

HPBSD – a port of 4.3BSD UNIX operating system for the HP9000 300, 400, 700 and 800 series machines done by Systems Programming Group at the University of Utah, developed between 1987 and 1993.

The goal was to replace the HP-UX (System V derivative) with BSD environments on HP machines in Utah CS department, in order to improve compatibility with Vaxen who worked on BSD and Sun workstations that ran on SunOS. Port was completed in a month, thanks to an older BSD port for HP 9000/200. Trait that was HPBSD tell any binary compatibility with HP-UX-TV. I went to support the HP 9000 HPBSD was later inserted into the main tree BSD code, and appeared in 4.3BSD-Reno.

The current version, HPBSD 2.0, is still largely based on 4.3bsd but has the 4.4bsd filesystem and networking kernel code and utilities as well as the ANSI-compliant C library. This version was “released” in April 1993. Improvements has been limited to bug fixes and support for new hp700 CPUs that we have. It is still the desktop operating system of choice inside the Flux and Avalanche research groups.

HPBSD is based on the 4.3 release of BSD from CSRG at Berkeley with additions from 4.4bsd and numerous local modifications. It still looks and feels pretty much like a 4.3 system, but configuring and building software packages is more 4.4bsd-like.

Supported Hardware: HP300/400 (68k based) and HP700/800 (PA-RISC based).
Since HPBSD contains AT&T and HP proprietary code it is not freely available.

The project founder is Mike Hibler.

Download

No download is available.
md5sum:

 

386BSD

null

  • Web site: 386bsd.org
  • Origin: USA
  • Category: Server
  • Desktop environment: CLI
  • Architecture: x86
  • Based on: UNIX
  • Wikipedia: 386BSD
  • Media: Install
  • The last version | Released: 2.0 | August 2016

386BSD – a derived from 4.3BSD, the first open source Berkeley UNIX operating system. It was the progenitor of Linux, iOS, and Android. Beginning with “A Modest Proposal” in 1989, 386BSD broke from proprietary systems by having publicly accessible code and documentation.

386BSD Release 0.0 was distributed in 1993 in tandem to the popular “Porting Unix to the 386” article series published in Dr. Dobb’s Journal.
Release 0.1 quickly followed, enhanced with contributions throughout the globe.

386BSD Release 1.0, aka Jolix, was a break from earlier Berkeley UNIX systems through use of a modular architecture. 386BSD Release 2.0 built upon the modular framework to create self-healing components. Each release introduced novel mechanisms from role-based security to polymorphic protocols.

386BSD.org provides the opportunity to interact with the original source, articles and supporting materials, and a live demo of 386BSD Release 2.0.

386BSD is a mother of free BSD systems today, such as: BSD/386, NetBSD, FreeBSD, BSD/OS, Darwin, OpenBSD and others.

The project authors are Lynne and William Jolitz.