Migrated 8 more recipes to external patches:
kdecoration (Plasma 6.6.5)
kf6-kcmutils (KF6 6.26.0)
kf6-kdeclarative (KF6 6.26.0)
kf6-kwayland (Plasma 6.6.5)
kf6-notifyconfig (KF6 6.26.0)
kirigami (KF6 6.26.0)
konsole (v24.08.3)
kwin (Plasma 6.6.5)
Regenerated kf6-kcoreaddons and kf6-knotifications
patches — the originals were generated with the
`diff --label='local/recipes/kde/.../source-pristine'`
form (relative-to-cwd paths) which `git apply --check`
in the cookbook source dir couldn't resolve. The
regenerated patches use the bare `a/CMakeLists.txt`
label form which `git apply` resolves against the
current directory (i.e. ${COOKBOOK_SOURCE}).
All 24 KF6 + Plasma + Konsole + Kirigami + KDecoration
patches now verified to apply cleanly via
`git apply --check` from inside each recipe's
source-pristine/.
Migration status: 24/24 KF6 + 6/6 KDE/Plasma + 2/15
unclassified (breeze, kde-cli-tools, kf6-kded6,
kglobalacceld, plasma-desktop, plasma-workspace are
NO-OPs — the ecm_install_po_files_as_qm call is absent
from upstream 6.26.0; cleanup-kf6-noop-seds.sh will
delete their sed chains in a follow-up commit). sddm is
git-sourced (no tarball) and was migrated earlier via
the inline drop-x11.py approach.
.gitignore:
Added local/recipes/**/source-pristine/ so the
migration pristine snapshots don't pollute git
status. The pristine dirs are ephemeral working
state used by migrate-kf6-seds-direct.sh; the
upstream tarball can re-extract them on demand.
local/scripts/migrate-kf6-seds-direct.sh:
Added 14 new recipes to the migration list
(breeze, kde-cli-tools, kdecoration, kf6-kcmutils,
kf6-kdeclarative, kf6-kded6, kf6-kwayland,
kf6-notifyconfig, kglobalacceld, kirigami, konsole,
kwin, plasma-desktop, plasma-workspace). Recipes
without a pristine/ snapshot are reported as FAIL
(with the message 'missing pristine or source dir')
rather than being silently skipped, so the user
can see exactly which recipes still need a
`repo fetch` round-trip.
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.