Later, machines came with libraries of support code which were linked to the user's program to assist in operations such as input and output. It is these that is the genesis of the modern-day operating system. However, machines still ran a single job at a time; at Cambridge University in England the job queue was at one time a washing line from which tapes were hung with clothes pegs. The color of the pegs indicated the priority of the job.
The conceptual bridge between the precise description of an operating system and the colloquial definition is the tendency to bundle widely, or generally, used utilities and applications (such as text editors or file managers) with the basic OS for the sake of convenience; as OSes progressed, a larger selection of 'second class' OS software came to be included, such that now, an OS without a graphical user interface or various file viewers is often considered not to be a true or complete OS.
The broader categories of systems and application software are discussed in the computer software article.
Early operating systems were very diverse, with each vendor producing one or more operating systems specific to their particular hardware. Every operating system, even from the same vendor, could have radically different models of commands, operating procedures, and such facilities as debugging aids. Typically, each time the manufacture brought out a new machine, there would be a new operating system. This state of affairs continued until the 1960s when IBM developed the S/360 series of machines; although there were enormous performance differences across the range, all the machines ran essentially the same operating system, OS/360. (A brief but illuminating and very wise account of the development of OS/360 is in Fred Brooks, The The Mythical Man-Month).
OS/360 evolved to become successively MFT, MVT, SVS, MVS, MVS/XA, MVS/ESA, OS/390 and z/OS, that includes the UNIX kernel as well as a huge amount of new functions required by modern mission-critical[?] applications running on the zSeries mainframes. It is worth mentioning, that IBM maintained full compatibility with the past, so that programs developed in the sixties can still run under z/OS with no change. Although z/OS runs UNIX applications, it is called a proprietary OS, in opposition to an Open System. If you use the non-UNIX interfaces, unique to z/OS, your program is not easily portable on a non-z/OS operating system. To read more about z/OS, UNIX, LINUX and other OS on zSeries, go to http://www.ibm.com/servers/eserver/zseries/os/.
The UNIX operating system was developed at AT&T. Because it was essentially free in early editions, easily obtainable, and easily modified, it exemplified the idea of a operating system that was conceptually the same across various hardware platforms.
The development of microprocessors made inexpensive computing available for the small business and hobbyist, which in turn led to the widespread use of interchangeable hardware components using a common interconnection (such as the S-100, SS-50, Apple II, ISA, and PCI buses), and an increasing need for 'standard' operating systems to control them. The most important of the early OSes on these machines was CP/M-80 for the 8080 / 8085 / Z-80 CPUs. It was based on several Digital Research Corporation operating systems, mostly for the PDP-11 architecture. MS-DOS (or PC-DOS when supplied by IBM) was based originally on CP/M-80. Each of these machines had a small boot program in ROM which loaded the OS itself from disk. The BIOS on the IBM-PC class machines was an extension of this idea and has accreted more features and functions in the 20 years since the first IBM-PC was introduced in 1981.
The decreasing cost of display equipment and processors made it practical to provide graphical use interfaces for many operating systems, such as the generic X Window System that is provided with many UNIX systems, or other graphical systems such as Microsoft Windows, the Radio Shack Color Computer's OS-9 Level II, Apple's Mac OS, or even IBM's OS/2. The original GUI was developed at Xerox Palo Alto Research Center in the early '70s (the Alto computer system) and imitated by many vendors.
Operating systems provide a set of functions needed and used by most applications, and provide the necessary linkages to control the computer's hardware. Without an operating system, each program would have to have drivers for your video card, sound card, hard drive, etc...
someone help me here on the history; this is just vague rambling; what about mini and mainframe history, development of Mach kernel, etc., and the other gaps I'm leaving?
A useful and readable (albeit somewhat opinionated) book dealing with operating system history is Neal Stephenson's In the Beginning ... was the Command Line (1999)
Search Encyclopedia
|
Featured Article
|