pages / replacements
Architecture & replacements
What each system is planned to use, and which components may be changed later.
01 / primary project
RaskenOS
Initial target: keep the original MINIX design and utilities while validating an experimental x86-64 port. These are planned components, not a confirmed working build.
- kernel
- MINIX 3-derived microkernel → native x86-64 target
- system services
- MINIX PM, VFS, VM, RS, SCHED and user-space drivers
- c library
- MINIX / NetBSD-derived libc
- shell
- Almquist shell (ash)
- init
- Original MINIX init
- filesystems
- MFS and ext2
- bootloader
- Existing MINIX-compatible boot path initially
- toolchain
- Preserve the experimental port's existing compiler, linker and build scripts initially
- packages
- pkgin + pkgsrc initially → custom C package manager later
- installer
- MINIX setup initially → custom C + ncurses installer later
- smp
- Reported two-core experiment; verification pending
No changes to the original MINIX component choices are planned until the 64-bit foundation has been tested.
02 / secondary project
Rasken Linux
A separate TTY-focused Linux distribution concept. This architecture is planned, and development is on hold.
- kernel
- Regular upstream Linux → carefully debloated configuration
- init
- systemd / separate init → BusyBox init
- core tools
- GNU coreutils → BusyBox utilities
- shell
- Bash → dash
- c library
- glibc
- compiler
- GCC
- bootloader
- GRUB, BIOS and UEFI targets
- filesystem
- ext4
- packages
- Custom C binary package manager; optional source ports
- installer
- Offline ISO with a C + ncurses text installer
- interface
- TTY-only base installation
This is a design plan, not an announcement of available packages or installation media.
