MINIX 3

MINIX 3

Minix 3 running X11 with twm as Window Manager.
Developer Andrew S. Tanenbaum
Written in C
OS family Unix-like
Working state Current
Source model Open source
Latest release 3.3.0 (16 September 2014 (2014-09-16)) [±][1]
Platforms i386 (IA-32) architecture, ARM architecture
Kernel type Microkernel
Default user interface ash
License BSD license
Official website www.minix3.org

MINIX 3 is a project to create a small, highly reliable, and functional Unix-like operating system. It is published under a BSD license and is a successor project to the earlier MINIX 1 and MINIX 2 operating systems.

The main goal of the project is for the system to be fault-tolerant by detecting and repairing its own faults on the fly, without user intervention. The main uses of the operating system are envisaged to be embedded systems and education.[2]

MINIX 3 currently supports IA-32 and ARM architecture systems. It is also possible to run MINIX under emulators or virtual machines, such as Bochs,[3][4] VMware Workstation,[5] Microsoft Virtual PC,[6] Oracle VirtualBox,[7] and QEMU. Ports to the ARM[8] and PowerPC[9] architectures are in development.

The distribution comes on a live CD and also can be downloaded as a USB stick image.[10] The latest release is "3.4.0rc2-373b793.iso.bz2" (28 January 2016).

Goals of the project

Structure of monolithic kernel and microkernel-based operating systems, respectively

Reflecting on the nature of monolithic kernel based systems, where a driver (which has, according to MINIX creator Tanenbaum, approximately 3–7 times as many bugs as a usual program)[11] can bring down the whole system,[12] MINIX 3 aims to create an operating system that is a "reliable, self-healing, multiserver UNIX clone".[13]

In order to achieve that, the code running in kernel must be minimal, with the file server, process server, and each device driver running as separate user-mode processes. Each driver is carefully monitored by a part of the system known as the reincarnation server. If a driver fails to respond to pings from the reincarnation server, it is shut down and replaced by a fresh copy of the driver.

In a monolithic system, a bug in a driver can easily crash the whole kernel, something that is much less likely to occur in MINIX 3.[14]

History

MINIX 3 versions[15]
Version Release date Description
3.1.0 2005-10-24
  • The first release of MINIX 3 (Book Release).
3.1.2a 2006-05-29
  • New Packman package manager.
  • Fixed an installation issue with auto-partitioning disks.
3.1.3 2007-04-13
3.1.3a 2007-06-08
  • Bug fixes.
3.1.4 2009-06-09
3.1.5 2009-11-05
  • Improvements performance
  • Shared memory
  • setitimer function
  • ISO 9660 file system
  • Open Sound System
  • Trap NULL accesses now, for user convenience
  • Improved signal handling
  • Better support for debuggers (ptrace improvements, etc.)
  • Network card autodetection (for supported PCI cards), improved network configuration
3.1.6 2010-02-08
  • New Network drivers: Atheros L2, Intel E1000, Realtek 8169, DEC Tulip
  • PipeFS - removed pipe handling from filesystem drivers
  • HGFS - support for mounting VMware shared folders as file system
  • VFS: supplemental group support and sticky bit support
  • Floating-point unit support
  • System Event Framework (SEF)
  • Experimental APIC support
3.1.7 2010-06-16
  • Userspace scheduling and a scheduling server[16]
  • Proper support for multiple Ethernet cards of the same type
  • Boot monitor allows loading images > 16 MB
  • Buildsystem support for building MINIX with GCC
  • Support for the cp1251 and koi8-u charsets
3.1.8 2010-10-04
3.2.0 2012-02-29
  • Porting GNU Debugger to MINIX 3 and implementing core dumping support
  • FUSE Support with experimental NTFS-3G file system
  • Gradual replacement of MINIX userland with NetBSD userland
  • Replacing the default compiler ACK with Clang (GCC is also supported)
  • Switch to ELF and NetBSD libc libraries
  • Pkgsrc Upstreaming and Application Porting
  • Asynchronous virtual filesystem (VFS) server.
  • Replacing the MINIX bootloader with NetBSD bootloader
  • NCQ support in the AHCI driver
3.2.1 2013-02-21
3.3.0 2014-09-16
  • ARM architecture support (cross-compilable)
  • Support for the mmap() I/O mechanism. Allows for shared dynamic libraries and lower memory footprint.
  • New input infrastructure: input server and keyboard driver separated from TTY
  • VND: vnode disk (loopback) block driver
  • LLVM Bitcode build of the system
  • Import of LLVM / clang in the sources
  • Unified block cache shared by FSes and VM
  • Improved NetBSD compatibility (utilities, calls, types (lots of 64-bit), toolchain, codebase, and packages)
  • C type for messages. Cleaner. Bigger.
  • Improved driver modularity: UDS separate from PFS, PTY from TTY, one controller per at_wini instance, LOG removed from boot image.
  • Packages are now dynamically linked
  •   Book Release
  •   Old release
  •   Current stable release
  •   Current development release

MINIX 3 was publicly announced on 24 October 2005 by Andrew Tanenbaum during his keynote speech on top of the ACM Symposium Operating Systems Principles conference. Although it still serves as an example for the new edition of Tanenbaum and Woodhull's textbook, it is comprehensively redesigned to be "usable as a serious system on resource-limited and embedded computers and for applications requiring high reliability."

Reliability in MINIX 3

One of the main goals of MINIX 3 is reliability. Below, some of the more important principles that enhance MINIX 3's reliability are discussed.

Reduce kernel size

Monolithic operating systems such as Linux and FreeBSD and hybrids like Windows have millions of lines of kernel code. In contrast, MINIX 3 has about 6,000 lines of executable kernel code,[17] which can make problems easier to find in the code.

Cage the bugs

In monolithic kernels, device drivers reside in the kernel itself. This means that when a new peripheral is installed, unknown, untrusted code is inserted in the kernel. A single bad line of code in a driver can bring down the system.

In MINIX 3, each device driver is a separate user-mode process. Drivers cannot execute privileged instructions, change the page tables, perform arbitrary input/output (I/O), or write to absolute memory. They have to make kernel calls for these services and the kernel checks each call for authority.

Limit drivers' memory access

In monolithic kernels, a driver can write to any word of memory and thus accidentally trash user programs.

In MINIX 3, when a user expects data from, for example, the file system, it builds a descriptor telling who has access and at what addresses. It then passes an index to this descriptor to the file system, which may pass it to a driver. The file system or driver then asks the kernel to write via the descriptor, making it impossible for them to write to addresses outside the buffer.

Survive bad pointers

Dereferencing a bad pointer within a driver will crash the driver process, but will have no effect on the system as a whole. The reincarnation server will restart the crashed driver automatically. For some drivers (e.g., disk and network) recovery is transparent to user processes. For others (e.g., audio and printer), the user may notice. In monolithic kernels, dereferencing a bad pointer in a driver normally leads to a system crash.

Tame infinite loops

If a driver gets into an infinite loop, the scheduler will gradually lower its priority until it becomes idle. Eventually the reincarnation server will see that it is not responding to status requests, so it will kill and restart the looping driver. In a monolithic kernel, a looping driver could hang the system.

Limit damage from buffer overflows

MINIX 3 uses fixed-length messages for internal communication, which eliminates certain buffer overflows and buffer management problems. Also, many exploits work by overrunning a buffer to trick the program into returning from a function call using an overwritten stack return address pointing into attacker controlled memory, usually the overrun buffer itself. In MINIX 3, this attack is mitigated because instruction and data space are split and only code in (read-only) instruction space can be executed, commonly known as Data Execution Prevention. However attacks which rely on running legitimately executable memory in a malicious way (return-to-libc, return-oriented programming) are not prevented by this mitigation.

Restrict access to kernel functions

Device drivers obtain kernel services (such as copying data to users' address spaces) by making kernel calls. The MINIX 3 kernel has a bit map for each driver specifying which calls it is authorized to make. In monolithic kernels, every driver can call every kernel function, authorized or not.

Restrict access to I/O ports

The kernel also maintains a table telling which I/O ports each driver may access. As a result, a driver can only touch its own I/O ports. In monolithic kernels, a buggy driver can access I/O ports belonging to another device.

Restrict communication with OS components

Not every driver and server needs to communicate with every other driver and server. Accordingly, a per-process bit map determines which destinations each process may send to.

Reincarnate dead or sick drivers

A special process, called the reincarnation server, periodically pings each device driver. If the driver dies or fails to respond correctly to pings, the reincarnation server automatically replaces it with a fresh copy. The detection and replacement of non-functioning drivers is automatic, without any user action required. This feature does not work for disk drivers at present, but in the next release the system will be able to recover even disk drivers, which will be shadowed in random-access memory (RAM). Driver recovery does not affect running processes.

Integrate interrupts and messages

When an interrupt occurs, it is converted at a low level to a notification sent to the appropriate driver. If the driver is waiting for a message, it gets the interrupt immediately; otherwise it gets the notification the next time it does a RECEIVE to get a message. This scheme eliminates nested interrupts and makes driver programming easier.

Architecture

The Architecture of MINIX 3

As can be seen, at the bottom level is the microkernel, which is about 4,000 lines of code (mostly in C, plus a small amount of assembly language). It handles interrupts, scheduling, and message passing. It also supports an API of about 30 kernel calls that authorized servers and drivers can make. User programs cannot make these calls. Instead, they can issue POSIX system calls which send messages to the servers. The kernel calls perform functions such as setting interrupts and copying data between address spaces.

At the next level up, there are the device drivers, each one running as a separate user-mode process. Each one controls some I/O device, such as a disk or printer. The drivers do not have access to the I/O port space and cannot issue I/O instructions directly. Instead, they must make kernel calls giving a list of I/O ports to write to and the values to be written. While there is a small amount of overhead in doing this (typically 500 ns), this scheme makes it possible for the kernel to check authorization, so that, for example, the audio driver cannot write on the disk.

At the next level there are the servers. This is where nearly all the operating system functionality is located. User processes obtain file service, for example, by sending messages to the file server to open, close, read, and write files. In turn, the file server gets disk I/O performed by sending messages to the disk driver, which actually controls the disk.

One of the key servers is the reincarnation server. Its job is to poll all the other servers and drivers to check on their health periodically. If a component fails to respond correctly, or exits or gets into an infinite loop, the reincarnation server (which is the parent process of the drivers and servers) kills the faulty component and replaces it with a fresh copy. In this way the system is automatically made self-healing without interfering with running programs.

Currently the reincarnation server, the process server, and the microkernel are part of the trusted computing base. If any of them fail, the system crashes. Nevertheless, reducing the trusted computing base from 3-5 million lines of code found in Linux and Windows systems to about 20,000 lines greatly enhances system reliability .

Differences between MINIX 3 and prior versions

Main article: MINIX
Diagram of the relationships between several Unix-like systems

MINIX 1, 1.5, and 2 were developed as tools to help people learn about the design of operating systems.

MINIX 1.0, released in 1987, was 12,000 lines of C and some x86 assembly language. Source code of the kernel, memory manager, and file system of MINIX 1.0 are printed in the book. Tanenbaum originally developed MINIX for compatibility with the IBM PC and IBM PC/AT microcomputers available at the time.

MINIX 1.5, released in 1991, included support for MicroChannel IBM PS/2 systems and was also ported to the Motorola 68000 and SPARC architectures, supporting the Atari ST, Commodore Amiga, Apple Macintosh and Sun Microsystems SPARCstation computer platforms. A version of MINIX running as a user process under SunOS was also available.

MINIX 2.0, released in 1997, was only available for the x86 and Solaris-hosted SPARC architectures. Minix-vmd was created by two Vrije Universiteit researchers, and added virtual memory and support for the X Window System.

MINIX 3 does the same, and provides a modern operating system with many newer tools and many Unix applications.[18] Prof. Tanenbaum once said:

“ Please be aware that MINIX 3 is not your grandfather's MINIX ... MINIX 1 was written as an educational tool ... MINIX 3 is that plus a start at building a highly reliable, self-healing, bloat-free operating system ... MINIX 1 and MINIX 3 are related in the same way as Windows 3.1 and Windows XP are: same first name.[13] ”

There have also been many improvements in the structure of the kernel since MINIX 2 was released, making the operating system more reliable.[19] MINIX version 3.1.5 was released 5 Nov 2009. It contains X11, Emacs, vi, cc, GCC, Perl, Python, Almquist shell, Bash, Z shell, FTP client, SSH client, Telnet client, Pine, and over 400 other common Unix utility programs. With the addition of X11, this version marks the transition away from a text-only system. Another feature of this version, which will be improved in future ones, is the ability of the system to withstand device driver crashes, and in many cases having them automatically replaced without affecting running processes. In this way, MINIX is self-healing and can be used in applications demanding high reliability.

MINIX 3.2.0 was released in February 2012. This version has many new features, including the Clang compiler, experimental symmetric multiprocessing support, procfs and ext2fs filesystem support, and GDB. Several parts of NetBSD have also been integrated in the release, including the bootloader, libc and various utilities and other libraries.[20]

MINIX 3.3.0 was released in September 2014. This release is the first version to support the ARM architecture in addition to x86. It also supports a NetBSD userland, with thousands of NetBSD packages running right out of the box.

See also

References

  1. ↑ "MINIX Releases". Retrieved 16 September 2014.
  2. ↑ [Posted October 24, 2005 by corbet] (2005-10-24). "Minix 3 hits the net". Lwn.net. Retrieved 2014-05-01.
  3. ↑ "Getting Started with Minix on Bochs on Mac OS". Woodhull.com. Retrieved 2014-05-01.
  4. ↑ "OSNews.com". OSNews.com. Retrieved 2014-05-01.
  5. ↑ "Minix under VMWare Installation How-To". Patrick.wagstrom.net. Retrieved 2014-05-01.
  6. ↑ "Minix on Virtual PC: first look". Woodhull.com. Retrieved 2014-05-01.
  7. ↑ "Minix 3 on Virtual box". inopinion.org.
  8. ↑ "minix3.org". minix3.org. Retrieved 2014-05-01.
  9. ↑ Ingmar Alting. "A port of the MINIX OS to the PowerPC platform" (PDF).
  10. ↑ "Minix3". Minix3. Retrieved 2014-05-01.
  11. ↑ Tanenbaum, Andy (2006-09-25). "Introduction to MINIX 3". OSnew. OSnews. Retrieved 2008-07-04. From Rebirth section: "Various studies have shown that software broadly contains something like 6-16 bugs per 1000 lines of code and that device drivers have 3-7 times as many bugs as the rest of the operating system. When combined with the fact that 70% of a typical operating system consists of device drivers, it is clear that device drivers are a big source of trouble. For Windows XP, 85% of the crashes are due to bugs in device drivers. Obviously, to make OSes reliable, something has to be done to deal with buggy device drivers. Building a reliable system despite the inevitable bugs in device drivers was the original driving force behind MINIX 3."
  12. ↑ "CSAIL Calendar: CSAIL Event Calendar". Csail.mit.edu. Retrieved 2014-05-01.
  13. 1 2 "Tanenbaum-Torvalds debate, Part II". Cs.vu.nl. 2006-05-12. Retrieved 2014-05-01.
  14. ↑ Archived July 1, 2006, at the Wayback Machine.
  15. ↑ "MinixReleases - Minix Wiki". Wiki.minix3.org. Retrieved 2014-05-01.
  16. ↑ Björn Patrick Swift. "Individual Programming Assignment User Mode Scheduling in MINIX 3" (PDF). Minix3.org.
  17. ↑ "The MINIX 3 Operating System". minix3.org. Archived from the original on 2012-01-20.
  18. ↑ "FAQ - Minix Wiki". Minix3.org. 2013-11-09. Retrieved 2014-05-01.
  19. ↑ Archived April 17, 2006, at the Wayback Machine.
  20. ↑ "MINIX Releases". wiki.minix3.org. Retrieved 29 February 2012.

Further reading

Wikibooks has a book on the topic of: Minix 3
Wikimedia Commons has media related to Minix.
This article is issued from Wikipedia - version of the 12/4/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.