AMIGA-os

The Commodore Amiga was released in 1985, and was among the first (and certainly most successful) home computers to feature a microkernel operating system. The Amiga's kernel, exec.library, was small but capable, providing fast pre-emptive multitasking on similar hardware to the cooperatively-multitasked Apple Macintosh, and an advanced dynamic linking system that allowed for easy expansion

XENIX

Xenix is a version of the Unix operating system, licensed by Microsoft from AT&T in the late 1970s. The Santa Cruz Operation (SCO) later acquired exclusive rights to the software, and eventually began distributing it as SCO UNIX.

Trusted Xenix was a variant developed by Trusted Information Systems which incorporated the Bell-LaPadula model of multilevel security, and had a multilevel secure interface for the STU-III secure communications device (that is, an STU-III connection would only be made available to applications running at the same privilege level as the key loaded in the STU-III). It was evaluated by formal methods and achieved a B2 security rating under the NSA's Trusted Computer System Evaluation Criteria—the second highest rating ever achieved by an evaluated operating system. Version 2.0 was released in January 1991, version 3.0 in April 1992, and version 4.0 in September 1993. It was still in use at least as of 1995.

EXOKERNEL

An exokernel is a type of kernel that does not abstract hardware into theoretical models. Instead it allocates physical hardware resources, such as processor time, memory pages, and disk blocks, to different programs. A program running on an exokernel can link to a library operating system that uses the exokernel to simulate the abstractions of a well-known OS, or it can develop application-specific abstractions for better performance

NANO KERNEL

A nanokernel delegates virtually all services — including even the most basic ones like interrupt controllers or the timer — to device drivers to make the kernel memory requirement even smaller than a traditional microkernel

HYBRID KERNEL

Hybrid kernels are essentially a compromise between the monolithic kernel approach and the microkernel system. This implies running some services (such as the network stack or the filesystem) in kernel space to reduce the performance overhead[citation needed] of a traditional microkernel, but still running kernel code (such as device drivers) as servers in user space

MICRO KERNEL

The microkernel approach consists of defining a simple abstraction over the hardware, with a set of primitives or system calls to implement minimal OS services such as memory management, multitasking, and inter-process communication. Other services, including those normally provided by the kernel such as networking, are implemented in user-space programs, referred to as servers. Microkernels are easier to maintain than monolithic kernels, but the large number of system calls and context switches might slow down the system because they typically generate more overhead than plain function calls.

A microkernel allows the implementation of the remaining part of the operating system as a normal application program written in a high-level language, and the use of different operating systems on top of the same unchanged kernel. It is also possible to dynamically switch among operating systems and to have more than one active simultaneously

MONOLITHIC KERNEL

In a monolithic kernel, all OS services run along with the main kernel thread, thus also residing in the same memory area. This approach provides rich and powerful hardware access. Some developers, such as UNIX developer Ken Thompson, maintain that monolithic systems are easier to design and implement than other solutions.[citation needed] The main disadvantages of monolithic kernels are the dependencies between system components - a bug in a device driver might crash the entire system - and the fact that large kernels can become very difficult to maintain.