AOS Design Guide The AOS project is a very large and complex
system. Often the system is built in an ad-hoc manner with
little or no design beforehand, frequently with the attitude
that it will be cleaned This design methodology typically
produces a system with only partial functionality. This also
involves a lot of writing and re-writing the same code. It is
usually also the case that "I'll do it later" never eventuates.
This page lists some of the design choices involved when
building SOS to allow you to better understand the difficulties
before they occur. You are free borrow or ignore as much or as
little of this information as you like. This is only a guide,
and any SOS project you want to produce is fine. Data Structures
and Subsystems While designing SOS you will need to consider a
number of different subsystems and data structures, and how they
Some systems you will need to consider include: - A task/thread
startup protocol - File system access - Console access - A VFS-
like layer - [Virtual] Memory -