API Documentation
The public Crimson kernel API docs are generated from the RADPx-OS repository with Doxygen.
Experimental Operating System
RADPx OS
RADPx OS is the Crimson 0.2.0 experimental package line for the POSIX-inspired kernel, x86 VM image track, embedded board ports, future SoC targets, and RADPx .radpm package metadata.
Version: Crimson 0.2.0
Suite: experimental
Build: RadBuild os.radix
Current x86: 0.2.0 beta 1
Current Crimson x86 Release
The current x86_64 GRUB release bundles include the bootable ISO, ext4 root filesystem image, FAT image, checksums, and helper scripts where available.
RADPx OS 0.2.0 beta 1Versioned GitHub Release for Crimson x86 terminal, smoke-test, RADCompositor images, and RADpm packages.
x86_64 Interactive Terminal BundleFramebuffer login shell profile with Vim tiny, ncurses metadata, ISO, ext4, and FAT images.
x86_64 Smoke Terminal BundleAutologin/autotest terminal profile for scripted VM checks.
x86_64 RADCompositor BundleSlint/RADCompositor profile with Vim tiny, ISO, ext4, and FAT images.
Build With RadBuild
RadBuild 0.2.1 owns the canonical x86_64 GRUB VM image builds. Crimson currently publishes separate terminal and RADCompositor/Slint profiles, both under the experimental suite.
radbuild build os --settings settings.json --json-eventsCrimson VM Profiles
The terminal profile boots directly to the framebuffer login prompt and rash. The window-manager profile packages the Slint-backed RADCompositor path for UI stabilization.
radbuild build os --settings settings.terminal.json --json-events
radbuild build os --settings settings.wm.json --json-eventsRoot Filesystem
rkconfig controls the generated hostname, initial root password, terminal scale, and ext4 size. The image stages Unix-style directories including /bin, /dev, /etc, /home/root, /lib, /mnt, /usr, /tmp, and /var/log.
RADPx kernel modules use .rko; future RADPx shared objects use .rso.
RADPx Package Repository
RadicalPackages hosts RADPx .radpm metadata and release archives beside Debian packages. In this release line, RadBuild is the installer: it resolves package metadata and stages package archives into generated root filesystems.
Common OS images should select packagegroups first, then add explicit packages only when needed. Packagegroups keep terminal, desktop, networking, and SDK selections reproducible while still letting RadBuild report missing dependencies without silently changing a project.
radix-terminal-baseCore terminal image set with RADLib, ncurses, and Vim tiny.
radix-desktop-baseRADCompositor/RADLib UI image set for the window-manager profile.
radix-networkingNetwork, DNS resolver, time sync, and timezone packages.
radix-dev-sdkDevelopment/sysroot package set for RADPx terminal application ports.
radix-coreCore RADPx userspace layout and boot support metadata.
radix-ncursesRADPx ncurses/tinfo shared runtime, .rso libraries, static archives, and terminal UI headers.
radix-vim-tinyTiny upstream Vim port metadata, RADPx defaults, and Vim license for terminal images.
radlibRADLib aggregate metadata for future RADPx userspace and service packages.
radlib-runtimeRADLib runtime package metadata for generated RADPx root filesystems.
radlib-uiRADLib UI and Slint-facing metadata for RADPx OS builds.
radix-networkRADPx network service package metadata.
radix-dns-resolverDNS resolver service package metadata.
radix-time-syncNTP/time synchronization service package metadata.
radix-tzdataTimezone data package metadata.
Create an Image From Scratch
Install RadBuild, create a RADPx project from a packaged template, use menuconfig to select packagegroups and runtime settings, then run the emitted VM script.
sudo apt install radbuild
radbuild project create ~/radix-work --non-interactive --template radix-os-terminal --project-name radix-terminal
cd ~/radix-work/radix-terminal
radbuild menuconfig --settings settings.json
radbuild build os --settings settings.json --json-events
./artifacts/radix/x86_64-grub-terminal/run-radix-vm.sh