User:Ale2323dev/Theia OS

From OSDev Wiki
< User:Ale2323dev(Redirected from Theia OS)
Jump to navigation Jump to search

Theia OS

Theia OS is an independent, proprietary operating system developed from scratch. It is built around a custom kernel known as the Theia NT Kernel, with its own system architecture, kernel services, and application programming interfaces.

The project aims to develop a general-purpose operating system with an independent architecture and software ecosystem. Its design combines concepts associated with monolithic and microkernel operating systems while maintaining its own architectural identity.

Theia OS is not based on Linux, Unix, or POSIX, nor is it intended to be a reimplementation of Microsoft Windows. Instead, it follows an independent development direction, drawing inspiration from existing operating systems in areas such as usability, system organization, and the long-term desktop experience.

Development is organized into numbered milestones, progressing from boot infrastructure and fundamental kernel facilities toward memory management, scheduling, system interfaces, persistent storage, and native application support.

Project overview

Property Description
Name Theia OS
Kernel Theia NT Kernel
Kernel architecture Hybrid
Primary implementation languages C and NASM assembly
Current processor target x86 (32-bit)
Development model From-scratch operating system development
Operating system category General-purpose operating system (long-term goal)
Source availability Proprietary; source code is not publicly distributed
Development status Active development
Current development version 0.18

Project goals and philosophy

Theia OS is intended to become a general-purpose operating system rather than remain limited to a basic kernel or experimental boot environment.

Its development follows an incremental approach in which fundamental operating system facilities are established before higher-level functionality is introduced.

The project emphasizes the following principles:

  • An independent kernel and system architecture.
  • Clearly defined responsibilities between kernel components.
  • Dedicated system interfaces.
  • Controlled access to operating system resources.
  • Memory management and address-space isolation.
  • A structured task and resource-management model.
  • Persistent storage and a dedicated filesystem.
  • Native application support.
  • A graphical user interface and desktop environment.
  • Long-term portability across different processor architectures and hardware platforms.

These principles describe the project's architectural direction. They do not imply that every listed facility is already implemented.

Design independence

Theia OS is not a Linux distribution, Unix-like operating system, or POSIX-based system.

It is also not a Windows clone or a reimplementation of Windows internals.

Windows is one of the inspirations behind some of Theia OS's long-term usability objectives, particularly the goal of providing a practical general-purpose desktop operating system with native applications, system utilities, and developer interfaces.

However, Theia OS maintains its own kernel, system interfaces, architecture, and development roadmap.

Kernel architecture

The core of Theia OS is the Theia NT Kernel.

The kernel follows a hybrid architectural approach, combining selected characteristics associated with monolithic and microkernel designs.

The architectural objective is to balance performance, centralized kernel functionality, and separation of responsibilities.

Monolithic-kernel characteristics provide a foundation for efficient execution of core operating system services, while microkernel-inspired principles influence the organization and separation of system responsibilities.

The hybrid designation describes the project's architectural direction. It does not imply that Theia OS directly implements another operating system's kernel architecture.

Kernel implementation

The kernel is primarily written in freestanding C, with NASM assembly used for processor-specific and low-level operations.

Freestanding C allows kernel development without depending on a hosted operating system runtime or a conventional application environment.

Assembly is used where direct interaction with processor mechanisms is required.

The current development target is the 32-bit x86 architecture.

System architecture

Theia OS is designed around distinct system components and interfaces. The objective is to establish clear boundaries between kernel functionality, operating system services, and application-facing facilities.

The principal architectural concepts include the Theia NT Kernel, the System API, the Standway API, and a planned Hardware Abstraction Layer.

Theia NT Kernel

The Theia NT Kernel provides the core execution environment of the operating system.

Its responsibilities include the fundamental mechanisms required by higher-level system components, such as memory management, task management, processor interaction, and controlled access to kernel services.

Kernel functionality is introduced through successive development milestones rather than implemented as a single feature set.

System API

The System API is designed as the principal interface through which applications access operating system services.

It separates application-facing operations from the underlying system-call mechanism.

Applications are not intended to depend directly on individual kernel system calls. Instead, the System API provides the designated interface for requesting operating system functionality.

This separation establishes a defined contract between applications and the operating system while allowing the underlying kernel implementation to evolve.

The System API is being developed as part of version 0.18.

Standway API

The Standway API is an application-facing interface intended to provide a higher-level programming environment for native applications.

It is designed to operate above the System API rather than duplicate the kernel's system-call interface.

Its purpose is to provide application developers with a more convenient and consistent interface while keeping low-level operating system interactions within the designated system layer.

Standway is planned as a subsequent development milestone following the initial System API foundation.

Hardware Abstraction Layer

A Hardware Abstraction Layer (HAL) is part of the long-term architecture.

Its purpose is to separate hardware- and platform-dependent operations from components that can be shared across different hardware environments.

A dedicated abstraction layer can reduce the amount of platform-specific logic required throughout the operating system and provide a more structured foundation for supporting additional hardware configurations.

The HAL is a planned architectural component. It should not be confused with a fully implemented cross-platform hardware interface.

Boot process

The boot process is one of the earliest foundations established by Theia OS.

The project includes its own boot infrastructure rather than relying on an external bootloader as its permanent boot architecture.

The current development work targets the BIOS boot path on x86 hardware.

The boot infrastructure is responsible for establishing the initial execution environment and transferring control to the operating system's kernel components.

Boot development is organized into stages, with additional initialization and platform support introduced as the architecture evolves.

UEFI support and broader platform compatibility are separate development concerns and should not be assumed to be available merely because the BIOS boot path exists.

Initialization system

The initialization system is a distinct part of Theia OS architecture.

Its foundations were introduced during the early development milestones, before the functional console milestone.

The Init component is intended to coordinate the initialization of system components during the boot process.

Its role is part of the broader organization of the operating system and its startup sequence.

The initialization infrastructure is developed alongside the kernel and other fundamental system components.

Console environment

Theia OS includes a text-mode console used during early system development.

The console provides an interactive environment for issuing commands and observing operating system information.

Its development began with the Console Foundation milestone and progressed toward functional console capabilities.

The console also serves as an important development interface because it provides a visible way to validate system initialization and kernel functionality through the normal boot process.

The console is intended to evolve as the operating system gains additional system services and application support.

A future graphical environment is part of the project's long-term objectives.

Memory management

Memory management is one of the foundational areas of Theia OS development.

The project introduces memory-management functionality incrementally, establishing the facilities required for increasingly sophisticated kernel and user-mode execution.

The development direction includes:

  • Physical memory management.
  • Virtual memory management.
  • Memory allocation.
  • Memory-region management.
  • Address-space isolation.
  • Controlled memory access between system components.

These facilities provide the foundation for task execution and the separation of application memory from kernel memory.

Memory management is treated as an operating system responsibility rather than merely an application-level allocation mechanism.

The development of memory facilities precedes the introduction of a complete native application environment.

Task and resource management

Theia OS is being developed with structured task and resource-management facilities.

Task management provides the foundation for executing and coordinating independent units of work within the operating system.

The architecture also includes managed kernel resources, allowing system objects to be accessed through controlled interfaces rather than exposing their internal implementation directly to applications.

These facilities are part of the broader effort to establish a structured execution environment.

The scheduler foundation was introduced in version 0.17.

Further development of task and resource management is associated with the evolution of the system-call infrastructure and application environment.

Inter-process communication

Inter-process communication (IPC) is part of the system architecture.

IPC provides mechanisms through which independent tasks can exchange information and coordinate operations.

Theia OS development considers communication and resource ownership as related architectural concerns.

The objective is to establish controlled communication mechanisms that integrate with task management and the operating system's resource-management facilities.

IPC is part of the broader system-services architecture.

Timer and kernel time facilities

Timer functionality and kernel timekeeping are separate milestones in the development of Theia OS.

The Timer Foundation milestone established the initial foundation for timer functionality.

The subsequent Kernel Time milestone introduced the next stage of kernel timing facilities.

These capabilities provide important foundations for time-dependent kernel operations and the coordination of system activities.

Storage and filesystem

Persistent storage is part of the long-term design of Theia OS.

The project plans to introduce a dedicated filesystem rather than relying indefinitely on temporary memory-based storage.

The filesystem is intended to provide persistent data storage and a foundation for the future application environment.

Filesystem development is scheduled after the initial system-call and application-interface foundations.

The filesystem and its associated storage facilities are separate development concerns. A complete native application environment depends on the availability of the necessary storage and program-loading infrastructure.

Application environment

A native application environment is a major long-term objective of Theia OS.

The application model is intended to provide a structured way to load, execute, manage, and terminate programs running outside the kernel's privileged execution environment.

The planned application architecture is based on the operating system's own system interfaces rather than direct application access to kernel internals.

The development of application support depends on several preceding foundations:

  • A functioning system-call mechanism.
  • A defined System API.
  • User-mode execution facilities.
  • Memory isolation.
  • Task and resource management.
  • Persistent storage and filesystem support.
  • An executable loading mechanism.

The project roadmap places the beginning of formal program support after the preceding system-interface and filesystem development milestones.

Standway and application development

Standway is intended to provide the application-facing programming interface for native software.

It is designed to simplify application development while preserving the separation between applications and the kernel.

Future application-development facilities may include dedicated APIs, development tools, utilities, and specialized interfaces for particular application categories.

These facilities belong to the planned application ecosystem and should not be interpreted as a currently available development platform.

Processor architecture and portability

The current Theia OS development target is 32-bit x86.

Long-term architectural goals include support for additional processor architectures and hardware platforms.

Potential architectural targets include:

  • x86-64.
  • ARM and AArch64.
  • RISC-V.
  • Other processor architectures where appropriate.

Supporting additional architectures requires more than recompiling the existing kernel.

Each architecture requires appropriate processor initialization, exception and interrupt handling, memory-management integration, calling conventions, system-call entry mechanisms, and compatible compiler and assembler toolchains.

Hardware platforms may also require different initialization procedures, timers, interrupt controllers, and device support.

The planned Hardware Abstraction Layer is intended to contribute to this portability effort, together with architecture-specific components.

Multi-architecture support is a long-term objective. The current x86 implementation does not imply that the other architectures are already supported.

Development history and roadmap

Theia OS development is organized into numbered milestones. Each milestone establishes a specific foundation or introduces a significant expansion of the operating system.

The development process progresses from initial boot infrastructure and kernel foundations toward memory management, console functionality, scheduling, system interfaces, persistent storage, and native application support.

Development milestones

Version Milestone Description
0.1 Proof of Boot Establish the initial boot foundation.
0.2 Kernel Foundation Establish the fundamental kernel infrastructure.
0.3 Init Foundation Establish the foundations of the Init component.
0.4 Console Foundation Establish the initial console infrastructure.
0.5 Functional Console Introduce functional console capabilities.
0.6 Timer Foundation Establish the foundations of timer functionality.
0.7 Kernel Time Establish kernel timing facilities.
0.8 Memory Foundation Establish the initial memory-management infrastructure.
0.9 Memory Region Manager Introduce memory-region management.
0.10 Memory Allocator Foundation Establish the kernel memory allocator foundation.
0.12 Input Foundation Establish the console input infrastructure.
0.13 Console Expansion Expand console functionality.
0.14 Console Expansion Continue the expansion of console functionality.
0.15 Basic Closed Reach the Basic Closed development milestone.
0.16 Allocator Complete & Complete Shutdown Complete the designated memory allocator and shutdown milestones.
0.17 Scheduler Foundation Establish the scheduler foundation.
0.18 Syscalls Foundation Establish the system-call infrastructure and begin the System API foundation.

Note: Version 0.11 was skipped due to a numbering mistake. It does not represent a separate development milestone.

The table summarizes the principal development milestones. Additional maintenance, correction, and development commits may exist between milestone commits without representing separate version milestones.

Version 0.18 — Syscalls Foundation

Version 0.18 focuses on establishing the system-call infrastructure and the foundation of the System API.

The development of this version is divided into multiple stages.

The first stage has been completed, while the overall version remains in progress.

The completion of the first stage does not mean that the entire System API or all planned system services are finished.

Further development is required before version 0.18 can be considered complete.

Version 0.19 — Standway Foundation

Version 0.19 is planned to establish the foundation of the Standway application-facing API.

Standway is designed to operate above the System API, providing a higher-level interface for application development.

This milestone follows the initial system-interface work established in version 0.18.

Version 0.20 — Filesystem Foundation

Version 0.20 is planned to begin the foundation of the native filesystem.

Persistent storage is an important requirement for the future application environment and general-purpose operation of Theia OS.

Filesystem development is a separate milestone from the system-call and application-interface foundations.

Version 0.24 — Program Foundation

Version 0.24 is designated as the Program Foundation milestone.

Its purpose is to begin the formal foundation for native program support.

This stage follows the preceding work on system interfaces, application-facing APIs, and filesystem infrastructure.

The milestone represents the transition from establishing fundamental operating system services toward supporting native programs as a defined part of the system architecture.

Development status

Theia OS remains under active development.

The project has progressed beyond its initial boot and console foundations and has established successive memory-management, input, scheduling, and system-interface milestones.

Version 0.18 is currently in progress. Its first development stage has been completed, while additional work remains before the overall milestone can be considered complete.

The project has not yet reached its long-term general-purpose desktop objectives.

Native application support, the complete filesystem, the graphical environment, and broad multi-architecture compatibility remain future development goals.

Development status should therefore be evaluated according to individual milestones rather than treating the long-term architecture as an already completed operating system.

Releases and documentation

Public project information and documentation are maintained separately from the proprietary implementation.

The public repository contains documentation and project information. It does not provide the operating system's private source code or internal implementation materials.

Development releases are intended to document significant milestones and provide publicly distributed system images where applicable.

Pre-releases may represent incomplete development stages and should not be considered stable releases.

See also