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:

 

Mxchg

Mxchg

Web site: mxchg.com (not active)
Origin: ?
Category: Multimedia
Desktop environment: KDE
Architecture: x86
Based on: Knoppix
Wikipedia:
Media: Live CD
The last version | Released: 001 | March 7, 2007

Mxchg – a based on Knoppix live CD which lets you try, without installing, the Music Exchange software.

It is “Your Fresh New Music Centre” and also allows artists to “Distribute music to their fans directly. The Media Exchange is ‘open source’, and all the source code is included on the CD”.

It allows:
– to share musical collections
– play and organize music
– tag music
– automatically remove duplicate songs
– automatically download music from some artists.

Download

Mxchg 001 i386 265MB.iso
md5sum: 6f3bc3b102340c2beb1b1717277ae613

 

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:

 

NicEDesktop

NicEDesktop

Web site: havoc9.com/nice/ (not active)
Origin: ?
Category: Desktop
Desktop environment: Xfce
Architecture: x86
Based on: Debian
Wikipedia:
Media: Live CD
The last version | Released: 1.0 | August 10 (?) 2007

NicEDesktop – a Debian based Linux distribution which works in live mode.

It comes with many programs for both recreational and administrative purposes. Its main goals are to be useful and entertaining while maintaining user-friendliness, as well as to provide a “complete” temporary operating system for any PC user.

NicEDesktop uses Xfce desktop environment as default.
The latest version 1.0 is based on Debian “Lenny”.

The live user is: ‘root’; with ‘toor’ password.
To start Xfce desktop type: startdesk

Download

NicEDesktop 1.0 i386 617MB.iso
md5sum: d2d5472d10c4d4ed38b4bd8880cc199b

 

2.11BSD

null

Web site: github.com/RetroBSD/2.11BSD
Origin: ?
Category: Server
Desktop environment: CLI
Architecture: x86
Based on: 4.3BSD
Wikipedia:
Media: Install
The last version | Released: 2.11 | November 1994

2.11BSD – a BSD operating system based on and comes with several missing pieces that came after the 4.3BSD-Tahoe. 2.11BSD CSRG was the last edition of the DEC PDP-11 line system. This release is maintained Steven Schultz with a series patchlevel. It is the release of 4.4BSD-Lite, and requires the original UNIX license.

The system hasn’t been fit onto a non-separate I&D or machine without a floating point processor in a long time. Lots of overlay schemes need to be worked out; the floating point simulator in the kernel hasn’t been tested; sendmail won’t run on a non-separate machine, so bin/mail and ucb/Mail have to auto-configure not to use sendmail; csh is overlaid now even on a separate I&D machine, /lib/cpp is pushing the limit to handle all the #define’ing that is required to compile the kernel.

Due to the amount of software ported from 4.3BSD (and the Internet) he number of PORT directories has been cut down in order to fit the distribution on two 1600bpi tapes. Many of the sources not included are available from INTERNET archive sites, others will have to be acquired from a friendly 4.3BSD site.

Credits: Cyrus Rahman, of Duke University; Steven Schultz, of Contel Federal Systems; Keith Bostic; Casey Leedom.

Download

2.11BSD-pl195 i386 27MB.tar
md5sum: fae5078f664069a383013325d290960a

 

Multi Distro LiveCD

Multi Distro LiveCD

Web site: multidistro.tlm-project.org (not active)
Origin: ?
Category: Desktop
Desktop environment: Enlightenment, JWM, KDE
Architecture: x86
Based on: R.I.P.
Wikipedia:
Media: Live CD
The last version | Released: 2.5 | February 22, 2006

Multi Distro LiveCD – a LiveCD that contains 9 different mini Linux distributions, all executable when you start the PC without installing them on a hard disk.

The Live CD features following distributions: Slax, GeexBOX, DamnSmallLinux, INSERT, RIP, Mpentoo, Olive, Grafpup, Limp, and a memory checker is included in a single 700 Mb CD.

The project founder is Sandu Ionut.

Download

Multi Distro LiveCD 2.5 i386 714MB.iso
md5sum: 9daad899256a84470ea10e8ba4d59dc3

 

KeyKOS

null

Web site: cap-lore.com/CapTheory/KK/
Origin: USA
Category: Microkernel, Others
Desktop environment: CLI
Architecture: IBM S/370, IBM Mainframe
Based on: GNOSIS
Wikipedia: KeyKOS
Media: Install
The last version | Released: ? | ?

KeyKOS – an operating environment for S/370 computers which provides a high level of security, reliability, performance, and productivity. It allows emulation of other environments such as VM, MVS, and POSIX.

When Tymshare started work on KeyKOS in the early 1970s, there were solid business requirements justifying the project. With the price of main storage dropping, applications were too tightly bound to disk storage. Because Tymshare’s systems were accessed from around the world, continuous operation was a requirement. Existing systems were prone to failure from many causes, both hardware and software. They did not recover from these failures gracefully. These systems required significant operator intervention in both normal operation and during recovery. They did not provide the security needed to allow competing organizations to share programs and data in a controlled manner where it made economic and social sense.

Because of these deficiencies, Tymshare decided its best option was to build a system of its own. This system had a number of design goals including: high security, high reliability, economical processing of high transaction volumes, and enhanced productivity for managers, programmers, users, operators, and hardware.

KeyKOS provides persistent virtual address spaces where programs may keep data. The system caches frequently referenced data in main storage. When several processes are accessing the same data, for example the CMS “S” disk, the data blocks involved are likely to already in main storage, improving access times. Only one copy will be maintained in main storage, improving storage utilization. Persistent virtual storage allows the kernel to globally optimize disk arm movement and rotational latency. The KeyKOS implementation also provides complete separation of physical and logical DASD management. No unprivileged program is aware of the type or configuration of real DASD in the system.

KeyKOS has a system-wide checkpoint which periodically saves the state of the entire system. If a system outage occurs, the system will restart from the last checkpoint with all data and processes in a consistent state as of that checkpoint. The KeyTXF transaction processing system will recover database updates to the point of failure. Should a CPU fail, the DASD can be shared with or switched to a backup CPU to quickly restore service by restarting from the last checkpoint.

Data mirroring stores multiple copies of data for reliability and performance. The KeyKOS system continues to operate if a mirrored disk fails. When the disk is repaired, or a replacement disk is formatted and brought online, the mirrored data is automatically restored to that disk. Performance is enhanced by having several paths to a particular piece of data. The full function of the system is available in essentially any S/370 computer language. A standard invocation protocol permits high level languages to invoke low level function and low level languages to invoke high level function, enhancing the usefulness of all languages.

The KeyKOS system is designed for unattended operation. The only common operator functions are mounting tapes and servicing the printer.

The KeyKOS system is designed for continuous operation. Full system backup dumps may be taken while the system is running. When a dump has completed, the backup tapes contain an image of all data and processes in the system at a consistent instant of time. avoiding inconsistency in the data. These “tape checkpoints” are conceptually independent of the physical DASD type or configuration. They may be restored to different physical devices if necessary.

KeyKOS/370 runs on System/370-compatible single processor CPUs. It currently supports 3330, 3350, and 3380 count key data format disks and 3370 FBA format disks. System software includes the context switcher and two command systems.

Copyright © 1985, 1987, 1988, 1990 Key Logic. All rights reserved.
Permission to reproduce and redistribute this document in paper or electronic form is hereby granted, provided that this copyright notice remains intact.

KeyKOS is a predecessor of the EROS and its successors are CapROS and Coyotos operating systems.

Download

No download is available.
md5sum:

 

CompactBSD

null

Web site: compactbsd.sourceforge.net
Origin: ?
Category: Embedded
Desktop environment: CLI
Architecture: x86
Based on: OpenBSD
Wikipedia:
Media: Live
The last version | Released: 0.1.0 | August 22, 2002

CompactBSD – a set of tools that allow you to compress OpenBSD onto a small (32MB) compact flash card for use in small embedded servers. CompactBSD can be used to power wireless hot spots, which is what FatPort uses it for.

CompactBSD offers the easiest way to get OpenBSD up and running on Compact Flash-based systems such as the FatPointOEM. In order to use the ZComax 200mW PCMCIA wireless card in your FatPointOEM box, you will need to add a patch to the OpenBSD 3.1 kernel.

CompactBSD runs on an i386-class box running OpenBSD3.1, it also requires that Python 2.1.2 be installed.

The project developer is Ken Simpson.

Download

CompactBSD 0.1.0 i386 348KB.tgz
md5sum: 2b4457d09216c8122385d0dde15df831

 

DAZOS

DAZOS

Web site: sourceforge.net/projects/anitaos2/
Origin: ?
Category: Desktop
Desktop environment: IceWM
Architecture: x86
Based on: Puppy Linux
Wikipedia:
Media: Live CD
The last version | Released: ? | December 30, 2013

DAZOS – a Linux distribution based on Puppy Linux and targeted to old machines.

This distro is following a minimalism approach and will try where possible to use self-contained programs and is using Lucid Puppy Barebones 5.25 RETRO for its base suitable for old hardware and slightly newer.

Has the added advantage of allowing the install of Ubuntu .deb packages.
Has 2.6.30.5 kernel.
SDL Libraries included now.

Download

DAZOS i386 141MB.iso
md5sum: c24c1d15d288220e4549fbb6436c4f3a

 

emBSD

null

Web site: www.embsd.org
Origin: ?
Category: Firewall
Desktop environment: CLI
Architecture: x86
Based on: OpenBSD
Wikipedia:
Media: Live
The last version | Released: 1.1 | May 2001

emBSD – a stripped down version of OpenBSD. The concept for emBSD is a small foot print operating system for x86 (or other) hardware to use as little hard disk space as possible yet provide a fully functional Routing Firewall. The main driving force behind this concept is to not use a hard disk drive at all, but use off the shelf Compact Flash cards.

emBSD is a very small system designed for specific purposes. emBSD is not currently a server base OS. It is simply made to filter, control, and forward traffic within your organization. The kernel has been optimized specifically for handling large flows of traffic as well as providing extra interfaces for migrating to IPv6. An optimal emBSD system will not have moving disks inside to potentially fail. Solid-state disks are employed on the majority of our critical machines.

The project developers are Ken Rice and Truman Boyes.

Download

emBSD 1.1 i386 16.2MB.zip
md5sum: fc75b7206ed25b07eb8447e30ee73a2f