What is the difference between OS and RTOS?

Answer 1

Linux and RTOS are two distinct concepts.

Linux is the name given to a specific operating system.

An RTOS (Real-Time Operating System) is a specially designed TYPE of Operating System. Where a 'normal' Operating Systems schedule resources/processing time to programs when they are available to the system, whereas an RTOS specializes in allowing programs to run in 'real time', meaning they are able to respond to changes (typically from an external source) as close to instantly as possible.

Typically, you would find an RTOS in situations where the computer has to react instantly to changes, such as an industrial control system or systems that monitor and control the power grid. If the operating system prevented the program from responding in a timely fashion, the program would be worthless.

Real-time Operating Systems are typically very small, optimized systems, whereas a standard OS is very large, feature-laden and has thousands of different features that run at once.

There IS a pared-down version of Linux known as "RTLinux" which falls into the category of an RTOS, but it's not the version of Linux most people are used to seeing. It's very purpose-build, optimized and fast, unusable by anyone but system designers who can work with such an OS.

Answer 2

A real-time operating system is intended for systems that need to tightly control responsiveness and performance. With an RTOS you can prioritize operations such that the most critical areas of the application get control of the processor exactly when they need it. All other lower priority operations are paused. An RTOS also gives you all of the other advantages of an OS: * a consistent coding platform * a rich set of APIs to save coding time and errors * processor housekeeping functions * hardware abstraction
RTOS stands for real-time operating system, versus the general-computing operating system (OS). The key difference between general-computing operating systems and real-time operating systems is the need for " deterministic " timing behavior in the real-time operating systems. Formally, "deterministic" timing means that operating system services consume only known and expected amounts of time. In theory, these service times could be expressed as mathematical formulas. These formulas must be strictly algebraic and not include any random timing components. Random elements in service times could cause random delays in application software and could then make the application randomly miss real-time deadlines – a scenario clearly unacceptable for a real-time embedded system. Many non-real-time operating systems also provide similar kernel services. General-computing non-real-time operating systems are often quite non-deterministic. Their services can inject random delays into application software and thus cause slow responsiveness of an application at unexpected times. If you ask the developer of a non-real-time operating system for the algebraic formula describing the timing behavior of one of its services (such as sending a message from task to task), you will invariably not get an algebraic formula. Instead the developer of the non-real-time operating system (such as Windows, Unix or Linux) will just give you a puzzled look. Deterministic timing behavior was simply not a design goal for these general-computing operating systems. On the other hand, real-time operating systems often go a step beyond basic determinism. For most kernel services, these operating systems offer constant load-independent timing: In other words, the algebraic formula is as simple as: T(message_send) = constant , irrespective of the length of the message to be sent, or other factors such as the numbers of tasks and queues and messages being managed by the RTOS. Many RTOS proponents argue that a real-time operating system must not use virtual memory concepts, because paging mechanics prevent a deterministic response. While this is a frequently supported argument, it should be noted that the term "real-time operating system" and determinism in this context covers a very wide meaning, and vendors of many different operating systems apply these terms with varied meaning. When selecting an operating system for a specific task, the real-time attribute alone is an insufficient criterion, therefore. Deterministic behavior and deterministic latencies have value only if the response lies within the boundaries of the physics of the process that is to be controlled. For example, controlling a combustion engine in a racing car has different real-time requirements to the problem of filling a 1,000,000 litre water tank through a 2" pipe. Real-time operating systems are often uses in embedded solutions, that is, computing platforms that are within another device. Examples for embedded systems include combustion engine controllers or washing machine controllers and many others. Desktop PC and other general-purpose computers are not embedded systems. While real-time operating systems are typically designed for and used with embedded systems, the two aspects are essentially distinct, and have different requirements. A real-time operating system for embedded system addresses both sets of requirements.