Follow TV Tropes


Useful Notes / Operating System

Go To

"The box said that I needed to have Windows 98 or better... so I installed Linux."
Anonymous about Linux

Before a computer can do much, it'll need some software to provide basic system services. This is basically what an operating system (or OS for short) does; it manages devices and memory, keeps applications from stepping on each other's toes, and provides an Application Programming Interface (sometimes many APIs) for applications to use.


In the early days of computing, computers didn't have operating systems; you programmed them directly in Binary Bits and Bytes and on some really old machines (including ENIAC, the first practical electronic computer, and IBM's old card-counting machines), you didn't have program memory at all — you had to rewire them on a device not unlike an old-time telephone switchboard. Starting in the early 1960s, the advent of time sharing, the basis of multitasking, led to huge advances in what computers were capable of and following after the first modern OSes date from this era. Later, when microcomputers became common, they had much smaller operating systems of their own, such as CP/M, Apple DOS, ProDOS and MS-DOS; since microcomputers didn't have special hardware to manage and protect memory, most of the time a microcomputer OS simply wrapped the machine's ROM libraries with disk I/O functions, something that was especially true on the Apple ][ and the IBM Personal Computer. As computers got more powerful and cheaper, richer feature sets such as preemptive multitasking and tons of APIs and libraries were added.


At the OS Core: The Kernel

OSes are built around a central program known as the kernel. Generally speaking, the kernel manages hardware and provides services for other programs to use. Kernels are often supplemented with device drivers, which help the kernel use the hardware, and servers, which implement specific services like a network stack. To provide reliability, most modern OSes use at least two levels of access. Everything that runs in the same memory space as the kernel runs in kernel space. Everything outside of that is user space, or userland. If a user space program wants to access hardware, they have to make system calls to the kernel who validates the call and grants the request. Some of the modern OSes, especially those with hybrid kernels, also provide a third access level for the service tasks, which is also unavailable for applications, but is distinct from the kernel space to improve the system stability.

OSes usually organize the kernel, drivers, and services in one of three ways:

  • Monolithic: All device drivers and services are run in kernel space. The Linux kernel is an example. This offers the most performance, since device drivers and server run with the kernel. However, if any of those crash, they can crash the OS too.
  • Microkernel: Only the kernel and very basic services run in kernel space, the rest is in user space. MINIX is an example. As device drivers and servers are outside of kernel space, it makes the system very reliable. If a driver or server dies, the kernel can revive it without the user knowing. However, in general microkernels impose a greater performance impact due to the extra overhead needed for these drivers, servers, and user apps to communicate with each other.
  • Advertisement:
  • Hybrid: The kernel runs along with device drivers and servers, but they're not as tightly coupled. This is where the third security level becomes handy, as the drivers and servers are usually ran there. This takes the best of both paradigms. Windows and macOS use hybrid kernels.

General features of OSes

Modern OSes provide the following features:
  • Access to hardware and system resources: The OS grants permission for user space programs to use hardware if they need to and have permission to do so.
  • Multitasking and scheduling: As the processor can only handle so many applications at once and applications may be in various states of execution, the OS handles scheduling those applications on the processor.
  • Memory Management: Programs need to have separate memory spaces in order to not collide with each other. The OS is responsible for creating these separate memory spaces and making sure one application doesn't modify data in another application's memory space, unless the appropriate action is taken.
  • Security: The OS provides the means to create user accounts and enforce access levels. This helps restrict who has access to read from, write to, or execute files or other resources.

Notable operating systems

  • OSes with their own pages
  • Disk Operating System (DOS): A DOS-based system provides basic memory and hardware management services. They can only launch one application at a time, originally straight from a floppy disk. Because of this, they cannot support multiple users or have multiple applications running. Drivers and so-called "memory resident" programs can stay in memory, but the application has support them directly. For example, if you install a Microsoft mouse driver, applications have to know what a "Microsoft Mouse" is; mouse support isn't automatic. Note that while a characteristic of a DOS-based system is the command line interface, not all command line interface based systems are DOS based. UNIX for example is primarily command line driven, but it supports multiple programs and users.
  • AmigaOS: The OS that shipped with the Commodore Amiga and later. It offered graphical, windowed, pre-emptive multitasking before its competitors and had such a powerful media-based API that it was the go-to OS for multimedia computers from the late 80s to early 90s. Has an open-source rewrite named AROS, in a similar vein to what Linux and GNU are collectively for UNIX.
  • OS/2: This OS is notable for being a joint effort between Microsoft and IBM, at first. IBM, wanting to reign control over the PC standard started creating systems that were anything but PCs. After Windows 3.0 took off, Microsoft broke the deal, but had to support OS/2 per contract. To which IBM gleefully advertised it could run MS-DOS and Windows applications (to a varying degree of reliability). It never really took off, being limited to the IBM fleet sales and some specialist niches,note  but it found use in ATMs and mass transit ticket kiosks.
  • NeXTSTEP: Developed by the NeXT Corporation in 1989, which was founded by Steve Jobs after he resigned from Apple. Based off UNIX and BSD, its goals was to be as programmer friendly as possible, offering an array of powerful interfaces. Systems using NeXTSTEP created the first world wide web server, among other things. It was later released as the open source OpenSTEP and became the basis of Mac OSX.
  • BeOS: An OS that started development in the early 90s by Be Inc. for use on the BeBox. Noted for being developed from the ground up with multimedia in mind and received praise for being very responsive, even when the system was completely taxed. It never really took off, since it was facing against the deeply entrenched Windows and macOS. Interestingly, it had a chance at reaching higher levels of success as it was one of the candidate operating systems that Apple considered purchasing and using as a modern replacement for its increasingly obsolete classic Mac OS, but Be founder Jean-Louis Gassée (who, much like Steve Jobs, once worked for Apple) offered Apple a ridiculously inflated price for the company. Apple then decided to end the negotiations with Be, and eventually decided to purchase NeXT, the company that Steve Jobs had founded after his departure from Apple, bringing him back into Apple and using NeXT's operating system NeXTSTEP as the basis for what became Mac OS X.
  • zOS: A mainframe OS designed by IBM, it is the lineal descendant of the "mainline" operating system (OS/360) for IBM mainframes dating back to 1964; making it the oldest OS in continual widespread use. Designed for maximum uptime, maximum throughput (at the expense of interactivity), and bullet-proof backwards compatability; the epitome of a "mission critical" OS. Due to a strong virtualization push, IBM often offers it as a way to host multiple AIX or Linux servers on the same hardware.

See also