vasilito
0080fac138
The cub AUR→RBPKGBUILD→recipe.toml conversion pipeline (located at local/recipes/system/cub/source/) was assessed end-to-end against 12 representative real-world PKGBUILDs: - libevdev (simple meson) - fd-find (cargo) - libpciaccess 0.18.1 (meson) - fmt (cmake) - wlroots-git (git source, complex deps) - libpciaccess 0.19 (extra/-style, meson + ninja) - ffmpeg (configure + options) - mesa 24.3 (git+url + multi-source + pkgver()) - gzip (configure + git source + check) - zlib (simple C, configure) - openssl (pkgbase split package) - glib2 (complex deps, real-world) The assessment found 8 critical bugs that would prevent cub from producing working Red Bear recipes for any real Arch package. 7 of the 8 bugs were fixed in the previous commit (7c5b1f36e); the 8th (custom-template recipes lack DYNAMIC_INIT and cookbook_apply_patches boilerplate) is deferred as a cookbook-integration concern. This commit adds two artifacts of the assessment: 1. local/docs/cub-assessment-and-improvement-plan.md (508 lines, ~28KB): the complete assessment document. Sections: - Executive summary (architecture decision + 8-bug verdict) - What cub does well (10+ working cases) - The 8 bugs (location, severity, root cause, fix) - Test methodology - Test cases by category (A: conversion success, B: dep mapping, C: source URL, D: build template, E: edge cases, F: validation) - Forward improvement plan (16 items in 4 tiers) - Appendix A: cub architecture map (CLI + 17 modules) - Appendix B: RBPKGBUILD format spec - Appendix C: Generated recipe format vs. real Red Bear recipe 2. local/recipes/system/cub/source/cub-assessment/: a 12-PKGBUILD integration test harness. A standalone binary that exercises the conversion pipeline on each PKGBUILD and reports status, warnings, action_items, recipe validity (TOML), and the first 30 lines of the generated recipe. Used to verify the bug fixes in7c5b1f36e— all 12 cases convert successfully post-fix, including the previously-erroring mesa 24.3 (which now produces a valid recipe with a multi-source warning). The test harness lives next to the cub source (cub-assessment/) and has its own Cargo.toml with [workspace] empty so it doesn't join the cub workspace. Build/run with: cd local/recipes/system/cub/source cargo run --manifest-path cub-assessment/Cargo.toml The harness is intended for use by future cub maintainers to catch regressions. It's not wired into CI yet — that would be a separate task.
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, with added hardware support, filesystem drivers, and a KDE Plasma desktop path. The current development branch is 0.2.3 and the current Red Bear OS version is 0.2.3 (same as the branch name).
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
# Build and run the desktop target in QEMU
./scripts/run.sh --build
# Build a live ISO for bare metal
./scripts/build-iso.sh redbear-full
# Build the text-only recovery target
./scripts/run.sh --build --config redbear-mini
Repository Hosting
The canonical Red Bear OS Git server is Gitea at
https://gitea.redbearos.org/vasilito/RedBear-OS.git. GitHub is not a Red Bear OS source of
truth and must not be used for pushes, issues, releases, or project coordination.
Public Scripts
| Script | Purpose |
|---|---|
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/
├── sources/ # Red Bear source forks (git repos, directly editable)
├── 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.