vasilito
1dcdc5d39d
Adds the 9th tab in the multi-view system: Process, reading process state and memory from /proc/[pid]/stat on Linux hosts. Last major top-like view, complementing hardware tabs (Storage/Network/Sensors) with software state. New module process.rs (215 lines, 9 unit tests): - ProcessInfo: pid, comm, state, ppid, utime, stime, priority, nice, num_threads, vsize_kb, rss_kb - parse_stat_line() handles (comm) with spaces like (Web Content) via last-')' extraction (per man 5 proc format) - Field indices: state=0, ppid=1, utime=11, stime=12, priority=15, nice=16, num_threads=17, vsize=20, rss=21 - read_comm() fallback for parens-parsing failures - ProcInfo::read() scans /proc, sorts by RSS desc, truncates to 50 - format_memory_kb() with binary unit suffix Updated app.rs: - New field processes: ProcInfo, refreshed every 13th tick (6.5 sec). 13-tick modulus coprime with all (3,4,5,7,11). - TabId::Process variant (9th tab) - TabId::next() cycles PerCpu → System → Info → Motherboard → Battery → Sensors → Network → Storage → Process → PerCpu Updated render.rs: - New render_process_panel() with PID/STATE/PRIO/NI/THR/RSS/VIRT/COMM columns. Comm truncated to 20 chars. Sort by RSS desc (top-like). - render_tab_bar() for 9 tabs with hotkey 1-9 - render_once dumps Process panel for headless verification Updated main.rs: - mod process; declaration - New dispatch arm TabId::Process => render_process_panel - Hotkey 9 jumps to Process tab - render_process_panel added to imports Linux host smoke test (596 processes, top 50): - opencode 3.7 GiB, thunderbird 2.1 GiB, plasmashell 517 MiB - kwin_wayland shows PRIO=-2 (real-time scheduling) - Total RSS: 17.5 GiB Unit tests: 43/43 pass (5 bench + 12 sensor + 7 network + 10 storage + 9 process). Cross-compile SHA256: 2c30f86dce574f173efdcf8eb588f83abd8f0bdf2c5a2678452dd0e6a244dbf2. Docs: improvement plan §37, CONSOLE-TO-KDE §3.3.2 v1.13, RATATUI-APP-PATTERNS §13.14 + §14 (19 modules, 43 tests).
Red Bear OS
A microkernel operating system written in Rust, derived from Redox OS
What is Red Bear OS?
Red Bear OS is a general-purpose, Unix-like operating system with a microkernel architecture, written in Rust. It is a full fork of Redox OS, frozen at release 0.1.0, with added hardware support, filesystem drivers, and a KDE Plasma desktop path.
Goals:
- AMD & Intel parity — first-class support for both platforms on bare metal
- KDE Plasma desktop — Wayland-based desktop environment via the KWin compositor
- Hardware GPU acceleration — AMD GPU (amdgpu) and Intel GPU drivers via
redox-drm - Modern subsystems — USB, Wi‑Fi, Bluetooth, ext4, GRUB, D-Bus
- Offline-first builds — reproducible from archived, BLAKE3-verified sources
Quick Start
Prerequisites
Linux x86_64 host with Rust nightly, QEMU, nasm, and standard build tools.
See the Redox Build Guide for full setup.
Build & Run
# Clone
git clone https://gitea.redbearos.org/vasilito/RedBear-OS.git
cd RedBear-OS
# Recommended: use the Red Bear wrapper
./local/scripts/build-redbear.sh redbear-mini # Text-only target
./local/scripts/build-redbear.sh redbear-full # Desktop-capable target
# Boot in QEMU with the resulting image
make qemu
Build script:
local/scripts/build-redbear.shis the canonical entry point. Baremake allworks but bypasses the.configchecking andREDBEAR_ALLOW_PROTECTED_FETCH=1gates thatbuild-redbear.shenforces. SeeAGENTS.md§ Build Commands for full details.
Public Scripts
| Script | Purpose |
|---|---|
local/scripts/build-redbear.sh |
Canonical build wrapper for redbear-mini/full/grub |
scripts/run.sh |
Build and run in QEMU (-b to build, -c <config> for target) |
scripts/build-iso.sh |
Build a live ISO for bare-metal boot |
scripts/build-all-isos.sh |
Build all live ISO targets |
scripts/network-boot.sh |
PXE network boot helper |
scripts/dual-boot.sh |
Dual-boot installation helper |
Config Targets
| Target | Type | Description |
|---|---|---|
redbear-full |
Desktop | Wayland + KDE + GPU drivers + D-Bus services |
redbear-mini |
Console | Text-only recovery / install target |
redbear-grub |
Console | Text-only with GRUB boot manager |
Current Status
Red Bear OS boots to a login prompt in QEMU with working wired networking, D-Bus system bus, hardware detection daemons, and filesystem support (RedoxFS, ext4, FAT).
| Area | Status |
|---|---|
| Boot (ACPI/x2APIC/SMP) | ✅ Bare-metal proven |
| Userspace drivers (PCI, storage, net) | ✅ Working in QEMU |
| D-Bus system bus + services | ✅ Working (login1, PolicyKit, UDisks, UPower) |
| ext4 / FAT filesystems | ✅ Compiles, installer-wired |
| POSIX gaps (relibc) | 🚧 Bounded Wayland-facing support |
| DRM/KMS display drivers | 🚧 AMD + Intel compile; HW validation pending |
| Wayland compositor | 🚧 Bounded proof; Qt6/KF6 clients crash at init |
| KDE Plasma desktop | 🔄 In progress (Qt6/KF6 compile; KWin/QML blocked) |
| Wi‑Fi / Bluetooth | 📋 Planned (architected, implementation pending) |
How It Works
Red Bear OS uses a userspace driver model — all drivers run as unprivileged daemons:
Kernel (microkernel)
└── schemes: memory, irq, event, pipe, debug
└── Driver daemons (userspace)
├── pcid → PCI enumeration
├── e1000d → Intel ethernet
├── xhcid → USB controller
└── vesad → Display framebuffer
The kernel provides minimal services (memory, interrupts, IPC). Everything else — filesystems, networking, graphics, input — runs in userspace.
Documentation
- Implementation Plan — roadmap and execution model
- Desktop Path Plan — kernel → DRM → Mesa → Wayland → KDE
- D-Bus Integration — session bus architecture
- USB Plan — USB stack design
- Wi‑Fi Plan — wireless architecture
- Bluetooth Plan — BT stack design
- Documentation Index — full doc map
Contributing
Red Bear OS uses a full fork model. Upstream Redox sources are frozen and archived. All custom work lives in local/:
local/
├── patches/ # Durable changes to upstream source trees
├── recipes/ # Custom packages (drivers, GPU, system)
├── docs/ # Integration and planning docs
└── scripts/ # Build, test, and release tooling
We welcome contributions made with or without AI assistance — we care about quality, not how the code was produced.
License
MIT — same as upstream Redox OS.