API Documentation
The public Crimson kernel API docs are generated from the RADPx-OS repository with Doxygen.
RADPx OS is the Crimson 0.1.5 experimental package line for the POSIX-inspired kernel, the x86 VM image track (framebuffer terminal plus a Slint multi-window desktop shell whose Terminal, File Explorer, and Text Editor windows now run as separate userland processes over the compositor), embedded board ports, future SoC targets, and RADPx .radpm package metadata.
The current x86_64 GRUB release bundles include the bootable ISO, ext4 root filesystem image, FAT image, checksums, and helper scripts where available.
The public Crimson kernel API docs are generated from the RADPx-OS repository with Doxygen.
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-eventsThe terminal profile boots directly to the framebuffer login prompt and rash. The window-manager profile boots the Slint-backed RADCompositor desktop shell — a gradient dock with an app launcher plus movable, resizable Terminal, File Explorer, and Text Editor windows, all rendered by dynamic Slint in the freestanding kernel.
radbuild build os --settings settings.terminal.json --json-events
radbuild build os --settings settings.wm.json --json-eventsrkconfig 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.
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.
radpx-terminal-baseCore terminal image set with RADLib, ncurses, and Vim tiny.
radpx-desktop-baseRADCompositor/RADLib UI image set for the window-manager profile.
radpx-networkingNetwork, DNS resolver, time sync, and timezone packages.
radpx-dev-sdkDevelopment/sysroot package set for RADPx terminal application ports.
radpx-coreCore RADPx userspace layout and boot support metadata.
radpx-ncursesRADPx ncurses/tinfo shared runtime, .rso libraries, static archives, and terminal UI headers.
radpx-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.
radpx-networkRADPx network service package metadata.
radpx-dns-resolverDNS resolver service package metadata.
radpx-time-syncNTP/time synchronization service package metadata.
radpx-tzdataTimezone data package metadata.
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 ~/radpx-work --non-interactive --template radpx-os-terminal --project-name radpx-terminal
cd ~/radpx-work/radpx-terminal
radbuild menuconfig --settings settings.json
radbuild build os --settings settings.json --json-events
./artifacts/radpx/x86_64-grub-terminal/run-radpx-vm.sh