Systems · Information Technology · Software
Real-time operating systems: the software that cannot be late
An anti-lock brake controller that is a little late is not slow; it is wrong. A vast, mostly invisible category of computing lives under that rule, and it runs on operating systems almost nobody has heard of.
From the book The Operating System: Supervisor, Kernel, GhostChapters 30, 31 and 32. Read the full book free as a PDF.
Predictable, not fast
A real-time operating system is not a fast one; it is a predictable one. The guarantee on offer is not "quick" but "by this deadline, always" - a scheduler whose worst-case latency can be bounded and proven in advance. Ordinary Linux and Windows configurations optimize throughput and fairness on average and make no hard deadline guarantees: a disk error storm or a memory compaction can delay a task. A flight-control computer or an infusion pump does not care about the average. It cares that the response never, ever misses. The engineering consequence is a different culture: smaller kernels, static analysis, certification evidence, release cycles measured in years. In these markets the operating system is a safety component, and safety components are proven, not patched.
VxWorks and the road to Mars
The archetype is VxWorks, created by Wind River, a company founded in a Berkeley garage in 1981. VxWorks became the industry's leading RTOS, certified across hundreds of safety projects to standards such as DO-178C for aviation and ISO 26262 for cars. Its most famous workplace is not on Earth: NASA's Curiosity and Perseverance rovers both drive across Mars on it.

The lineage's most instructive hour came on an earlier rover. In July 1997, days after Mars Pathfinder landed, the spacecraft began resetting itself unpredictably. Engineers on Earth reproduced the fault on a replica and traced it to priority inversion: a low-priority weather task, holding the data bus's lock, was blocking a high-priority bus task while medium-priority tasks ran instead, so the highest-priority work missed its deadline and the watchdog reset the machine. The fix - enabling priority inheritance, a mechanism already present in VxWorks but switched off in that build - was uploaded to a spacecraft 190 million kilometres away, and the mission was saved by what amounted to a one-line change in scheduling policy. The pathology was not in any instrument. It was in the invisible rules about whose turn it was.
Certification as the product
The real-time world has its own economy. Its customers do not buy downloads; they buy certification evidence, long-term support and the certainty that the vendor will still answer the phone in fifteen years. An avionics programme chooses an RTOS at design start and lives with it for forty years, through the airframe's entire production and service life. Prices are small per unit and enormous in aggregate, because the units are planes, trains, infusion pumps and robots - machines whose failure modes are measured in bodies. Around the car industry, the AUTOSAR standard plays a parallel role, fixing interfaces so that applications can be developed independently of the hardware beneath them.
QNX and the hundred-computer car
A modern car is not a machine with a computer; it is dozens of computers with wheels. QNX, one of the best-known automotive operating systems, was born in 1980 in Kanata, Ontario, where Dan Dodge and Gordon Bell founded Quantum Software Systems; their product was called QUNIX until a polite letter from AT&T's trademark lawyers persuaded them to shorten it. QNX is a microkernel: the kernel does almost nothing but pass messages and schedule, while drivers and file systems run as ordinary processes outside it. A crashed driver is a process to restart, not a machine to reboot.
Its route to ubiquity ran through BlackBerry, which bought QNX in 2010 as its own phone business crested. The phone failed; the kernel thrived. By BlackBerry's fiscal 2026 results, QNX software was embedded in more than 275 million vehicles, with a design-win backlog of around 950 million dollars, which BlackBerry defines as estimated future royalty revenue from vehicle programmes it has won. The operating-system question that Microsoft and Nokia fought over in phones is being refought, quietly, in every car company on earth, with the difference that here a scheduling mistake can kill.
The embedded long tail
Beyond cars and spacecraft stretches the true mass of the industry. Routers run Linux or FreeBSD; televisions run Tizen and webOS; cash machines ran Windows XP for years past its 2014 retirement because recertifying a fleet cost more than extended support. At the bottom of the scale sit kernels a few thousand lines long: FreeRTOS, created by Richard Barry in 2003 and taken under Amazon's stewardship in 2017 under the permissive MIT licence, and the Linux Foundation's Zephyr. Small controllers may run a compact operating system or bare-metal firmware without one; microcontroller shipment counts do not measure operating-system installations.
The frontier is proof. In 2009 the seL4 microkernel became the first general-purpose kernel with a machine-checked functional-correctness proof - its code mathematically demonstrated to implement its specification. DARPA's HACMS programme then built seL4-based flight software and turned a red team loose on it; the red team could not break in, while the stock baseline fell. And in April 2021 the commons reached Mars: the Ingenuity helicopter made the first powered flight on another world running Linux and NASA's open-source F Prime framework on a phone-class processor. This embedded world is where the industry's next architecture is being prototyped - as it was in 1969, on a spare PDP-7.
Quick answers
What is an RTOS used for?
Anywhere a late answer is a wrong answer: anti-lock brakes, flight control, infusion pumps, industrial robots, spacecraft. VxWorks and QNX are the market's flagship systems; FreeRTOS and Zephyr cover the smallest devices.
Is Linux a real-time operating system?
Ordinary Linux configurations give no hard deadline guarantees. The kernel supports a real-time preemption option (PREEMPT_RT), and the latency you get still depends on the hardware, the kernel configuration and the software above it. Linux flew on the Ingenuity Mars helicopter as a deliberate technology demonstration, and certified safety work often goes to VxWorks, QNX and their peers.
What operating system do cars use?
Several. QNX is widely used for safety-critical and dashboard systems (BlackBerry reports it in more than 275 million vehicles), alongside AUTOSAR-based firmware on small controllers, automotive Linux, and Android Automotive for screens.
Sources
- Wikipedia, "Wind River Systems", and Wind River VxWorks product pages
- Mike Jones (recounting David Wilner's account), "What really happened on Mars Rover Pathfinder", RISKS Digest 19(49), December 1997
- Wikipedia, "QNX", and BlackBerry QNX company materials
- BlackBerry Limited, Q4 fiscal 2026 results, SEC Form 8-K exhibit
- NASA JPL, "Meet the Open-Source Software Powering NASA's Ingenuity Mars Helicopter"
- AWS Open Source Blog, "Announcing FreeRTOS kernel v10" and AWS stewardship
- DARPA, High-Assurance Cyber Military Systems (HACMS) case study
