T

vasilito 79d00e2372 viewer: hex-edit mode with byte-level edit cursor (Phase 28)

tlcview now supports in-place byte-level editing in Hex view:

  F4 (Text -> Hex), F2 (Hex -> HexEdit) toggles between read-only
  hex view and an editable overlay. HexEdit mode draws an extra-
  bright cursor over the *active nibble* (H or L) so the user
  always knows which digit the next keystroke will replace.

Nibble pipeline (mirror of MC's mcedit hex cursor):
  - type 'a'..'f' or '0'..'9': stash the high nibble and advance
    to the low nibble; the byte is NOT yet written
  - second nibble: combine with stashed high, write the byte,
    advance the cursor by 1, reset to high nibble
  - arrow keys: H/L toggle (Right/Left), row navigation (Up/Down),
    page jump (PgUp/PgDn)
  - F10/Esc/Ctrl-Q on a dirty buffer opens the
    'Save before quit? (Y/N/Esc)' prompt; Y saves, N discards,
    Esc cancels and stays in HexEdit

Byte storage:
  - Inline and Compressed sources (the default for files < 1 MiB
    and all .gz/.bz2) are mutated in place via the new
    FileSource::write_byte(offset, value) helper.
  - FileSource::save_to(path) persists the buffer byte-exact.
  - Chunked sources (≥ 1 MiB plain files) refuse to enter
    HexEdit — caller gets a silent no-op. The new
    SourceError::NotMutable variant carries the diagnostic.

Header / footer:
  - mode label changes from 'Hex' to 'HexEdit' in the header
  - footer shows 'Nibble H' or 'Nibble L' (which digit is next)
  - '[+]' marker appears after the mode label when the buffer
    has unsaved edits

8 new tests cover: F2 enter, nibble commit + cursor advance,
dirty F10 opens prompt, clean F10 closes, Y/N/Esc prompt
resolution, Chunked refusal, arrow-key nibble toggling.

Total: 1172 tests passing, 0 failing.

2026-06-20 23:32:54 +03:00

.cargo

…

.gitlab

…

assets

…

bin

…

config

…

docs

…

gparted-git

…

local

…

podman

…

prefix

…

recipes

…

scripts

…

sources

…

src

…

.codex

…

.config

…

.gitignore

…

.gitignore_override

…

AGENTS.md

…

build.sh

…

Cargo.lock

…

Cargo.toml

…

CHANGELOG.md

…

CONTRIBUTING.md

…

flake.lock

…

flake.nix

…

HARDWARE.md

…

LICENSE

…

Makefile

…

native_bootstrap.sh

…

podman_bootstrap.sh

…

qemu-boot2.png

…

qemu-boot3.png

…

qemu-boot3.ppm

…

qemu-boot4.png

…

qemu-boot-screenshot.png

…

README.md

…

redbear.ipxe

…

rust-toolchain.toml

…

README.md

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.sh is the canonical entry point. Bare make all works but bypasses the .config checking and REDBEAR_ALLOW_PROTECTED_FETCH=1 gates that build-redbear.sh enforces. See AGENTS.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.

Languages

C 43.9%

C++ 23.5%

Makefile 7.3%

Python 3.7%

JavaScript 3.4%

Other 17.1%

README.md Unescape Escape

Red Bear OS

What is Red Bear OS?

Quick Start

Prerequisites

Build & Run

Public Scripts

Config Targets

Current Status

How It Works

Documentation

Contributing

License

README.md