vasilito
6870429b21
Migrate the libdrm recipe from the tar+patches shape (redox.patch + four P1-P4 patches from local/patches/libdrm/) to a Local source pointing at the new Red Bear fork at local/sources/libdrm/. The fork is based on upstream libdrm 2.4.125 (https://gitlab.freedesktop.org/mesa/libdrm) and already has the full redox.patch series applied in-tree. The P1-P4 patch files referenced from the previous recipe (P1-drm-ioctl-bridge, P2-drm-get-pci-info, P3-drm-get-version-driver-name, P4-drmGetDeviceFromDevId-redox) were already merged into redox.patch and no longer existed in local/patches/. Consolidating everything into a single in-tree fork is the durable form per the FULL FORK PRINCIPLE. The fork's redox divergence covers: - include/drm/drm.h: include <sys/ioctl.h> on __redox__ instead of <sys/ioccom.h> - xf86drm.h: Redox-aware ioctl type definitions - xf86drm.c: major()/minor()/makedev() macros from musl for __redox__, open_memstream fallback path (returns NULL with diagnostic on __redox__), redox_drm_write_all helper, and the drmOpen / drmGetDeviceFromDevId / etc. rewrites that dispatch through scheme: paths on Redox - xf86drmMode.c: Redox shim for drmModeGetResources / drmModeGetConnector / etc. and the mode probing path - xf86drm_redox.h: new header providing the Redox-side helper API (open scheme:, drm fd adaptation, dev_t packing) used by xf86drm.c Recipe changes: - source: tar + patches list -> Local { path = '../../../../local/sources/libdrm' } (the recipe lives under both recipes/wip/x11/libdrm and recipes/libs/libdrm symlinks into local/recipes/libs/libdrm; the four-.. path resolves correctly from both locations to local/sources/libdrm). - version: bumped to 0.2.3 (Red Bear fork tracking upstream 2.4.125). - description: marked v6.0 2026 Red Bear fork. - removed: redox.patch and source/ / source.tar / target/ artifacts under the recipe directory; they are no longer referenced and the fork is the single source of truth. Verified: ./target/release/repo cook libdrm (with REDBEAR_ALLOW_PROTECTED_FETCH=1) builds successfully and publishes libdrm 0.2.3 to repo/x86_64-unknown-redox/ with the fork's commit identifier pinned.
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
# 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.