AROS – Discovering and Understanding a Modern Amiga-Like Operating System 

Article 1: What Is AROS? 

If you have followed our previous Amiga course, you already know that the Amiga was much more than just a computer. Its operating system introduced concepts that were remarkably advanced for its time: multitasking, shared libraries, devices, handlers, message ports and a highly modular system architecture. But what if we wanted to recreate these ideas on modern and different hardware? This is where AROS comes in. AROS stands for: AROS Research Operating System It is a free and open-source operating system inspired by the architecture and programming interfaces of AmigaOS. But AROS is not simply an Amiga emulator. It is an operating system in its own right. 

1. From AmigaOS to AROS 

In our Amiga course, we learned that AmigaOS consists of several layers. 

A simplified view looks like this: 

Applications 
↓ 
Libraries, Devices and Datatypes 
↓ 
Exec 
↓ 
Hardware 

This modular architecture was one of the great strengths of AmigaOS. Programs could communicate with the operating system through well-defined interfaces rather than having to control everything directly. AROS follows many of the same ideas. 

Its developers created implementations of familiar Amiga concepts such as:
Exec-style multitasking
AmigaDOS-style file handling
libraries
devices
handlers
datatypes
message ports
command-line tools
graphical applications

For an experienced Amiga user, many parts of AROS therefore feel surprisingly familiar.

2. AROS Is Not AmigaOS 

This distinction is important. AROS is not the original AmigaOS source code. Instead, it is an independent open-source implementation of an AmigaOS-like operating system. The goal was to reproduce important concepts and APIs while allowing the system to run on hardware far beyond the original Amiga computers. This gives AROS an interesting position in the Amiga world. It preserves many Amiga concepts while also allowing developers to experiment with them. 

3. AROS Is Not an Emulator 

This is probably one of the most important things for beginners to understand. Programs such as UAE emulate Amiga hardware. 

An emulator attempts to reproduce components such as: 
Motorola 68000-series CPUs
Amiga chipset behaviour
memory architecture
custom chips
peripherals

AROS takes a different approach. AROS itself is an operating system. Depending on the version and platform, it can run on different processor architectures and environments. 

So the basic distinction is: 

Emulator:
Recreates Amiga hardware
Runs AmigaOS inside the emulated machine
Recreates classic hardware behaviour
Focuses on hardware compatibility

Aros:
Implements an operating system
Is itself the OS
Can target different hardware architectures
Focuses strongly on the AmigaOS-style software architecture

4. Familiar Ideas from AmigaOS 

If you have completed our Amiga course, you already know many of the concepts required to understand AROS. 

For example, we previously looked at: 

Exec 

The core of the Amiga operating system responsible for important functions such as multitasking, memory management and message passing. 

Libraries 

Reusable collections of operating-system functions that applications can open and use. 

Devices 

Software interfaces for communicating with hardware or hardware-like services. 

Handlers 

Components that provide DOS-level services such as filesystems and logical devices. 

Datatypes 

A system that allows applications to handle different data formats through standardized interfaces. 

Shell 

The command-line environment for controlling the operating system. All of these ideas are extremely useful when learning AROS. That is why our earlier Amiga course provides such a good foundation. 

5. AROS and the Amiga Philosophy One reason 

AROS is interesting is that it preserves much of the philosophy behind AmigaOS. Traditional Amiga systems were designed around small, specialized components. Instead of building everything into one enormous program, the operating system provides services that programs can use. 

For example, an application might: 
open a library,
call functions from that library,
communicate with other tasks using messages,
access hardware through a device,
load a file through a datatype.

This modular approach is deeply connected to the Amiga architecture. AROS continues many of these concepts. As we explore the system, we will repeatedly discover ideas that should already look familiar. 

6. The AROS Desktop 

Classic Amiga users are familiar with Workbench. AROS normally provides its own desktop environment called Wanderer. Conceptually, Wanderer performs a similar role. 

It gives the user a graphical environment for working with: 
disks
directories
files
applications
system tools
preferences

When you first start AROS, Wanderer is therefore one of the first parts of the system you will encounter. For an Amiga user, the idea is familiar, even though the implementation and appearance are different. We will explore Wanderer in detail in a later article. 

7. The Shell Is Still Important 

As we discovered in the Amiga course, the Shell provides another way of looking at the operating system. The same is true with AROS.

Through the AROS Shell we can explore: 
directories
assigns
commands
devices
system files
scripts
environment variables
command arguments

This will eventually allow us to look beneath Wanderer and understand how AROS is organized internally. Our previous knowledge of the Amiga Shell and AmigaDOS will therefore become particularly valuable. 

8. Thinking in Amiga Terms 

One of the easiest ways to learn AROS is to constantly compare it with what we already know. 

Amiga Concept: Workbench, Amiga Shell, Exec, Libraries, Devices, Handlers, Assigns, Startup Scripts
Aros concept: Wanderer, AROS shell, Exec-compatible architecture, Libraries, Devices, Handlers, Datatypes, Assigns, Startup Scripts

This does not mean that everything behaves exactly like it does on a classic Amiga. But the conceptual similarities give Amiga users a major advantage when exploring AROS. 

9. Why Learn AROS? 

AROS is particularly interesting because it provides another way to study the ideas behind the Amiga operating system. 

With AROS we can investigate questions such as: 
How can AmigaOS concepts be implemented on other hardware?
Which ideas from AmigaOS are still useful today?
How does an Amiga-like operating system organize its components?
How compatible can an independently developed operating system become?
How can applications be written for such a system?

AROS therefore gives us something more than another desktop environment. It gives us a platform for exploring the architecture and philosophy of AmigaOS from a new perspective. 

10. What We Will Explore in This Course 

This new course will gradually move from everyday use toward the internal architecture of AROS. We will look at topics including: Using AROS We will explore Wanderer, disks, drawers, files, preferences and basic system configuration. The AROS Shell We will learn commands, assigns, paths, scripts and other command-line concepts. 

AROS Under the Hood Later we will investigate: 
Exec
tasks
processes
libraries
devices
handlers
message ports
datatypes
system directories
startup mechanisms

AROS vs. AmigaOS Throughout the course we will compare the two systems. This will help us understand where AROS follows traditional AmigaOS concepts and where it takes a different approach. AROS Programming Finally, we can go deeper and look at how programs interact with AROS itself. Because we already explored Amiga programming in the previous course, we will be able to compare the programming models directly. 

11. From the Amiga to AROS 

Our previous course started with the Amiga hardware and gradually worked its way upward. 

We learned about: 

Hardware → Exec → AmigaOS → Shell → Applications → Programming 

With AROS we can now approach the subject from another direction. The original Amiga taught us where these concepts came from. AROS will show us how many of these concepts can live on beyond the original Amiga hardware. That makes AROS a natural next step in our journey. Conclusion AROS is an independent open-source operating system inspired by the architecture and APIs of AmigaOS. 

It preserves many familiar concepts: 
multitasking
libraries
devices
handlers
datatypes
assigns
Shell commands
message-based communication
a lightweight and modular system design

But it is not simply AmigaOS running inside an emulator. AROS takes many ideas from the Amiga operating-system architecture and implements them in an independent system capable of targeting different environments and hardware platforms. For anyone who has followed our Amiga course, this makes AROS especially interesting. We already understand the language. Now we can explore a different implementation of many of the same ideas. Coming Next Article 

2: AROS for Amiga Users – What Is Familiar and What Is Different? 

In the next article, we can make the connection to the previous Amiga course even stronger by comparing AmigaOS and AROS side by side: Workbench vs. Wanderer, system directories, assigns, Shell, libraries, devices, startup sequence and the general structure of both operating systems.