Skip to content

LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.

docs/PAPER.md regenerated from the paper (the hidden blurred window rule checked on the rebased build; the x86 PC reference and hardware video decoding moved to 0.8.7)

Federico Pereira2c537b476390
diff --git a/docs/PAPER.md b/docs/PAPER.md
index f07ab50..ada3b99 100644
--- a/docs/PAPER.md
+++ b/docs/PAPER.md
@@ -646,7 +646,7 @@ The Raspberry Pi 5 is the only supported board. Results on a real board (16 GB,
### 7.5 Modern PCs
-There are no measurements on real PCs in the repository yet. The ISO is tested on virtual machines (UEFI and BIOS); testing on a real AMD machine from the live USB is planned. LordBench (0.8.6) is designed to measure memory and CPU at idle, boot time, frame times, video and app start in a repeatable way, and community hardware reports (0.8.7) to collect them from real machines (`docs/BENCHMARK.md`). In development for 0.8.6 (unreleased; the latest release is 0.8.5-beta), its first part is built: a sandboxed `lord-bench` helper that measures the CPU, memory, the GPU offscreen, storage and a sustained load, stops near the temperature limit or when the processor throttles, and records the conditions of each run, shown in System Information → Performance as "×N" of reference machines; it also measures software video decoding and the remote desktop's encoders, the desktop's frame times and the time from a pointer move to the screen, alone and under a low-priority load, and boot time over several restarts; it also runs from a terminal (`lordos-sysreport bench`). Also in development, it times LordOS's own interface work with the engine's real code (the layout and paint of a fixed full-HD desktop scene, and the shaping of paragraphs in Latin, Arabic, Devanagari, Thai and Chinese with fonts built into the helper, which opens no files; on the reference virtual machine 37 frames per second on one core and 40 with the paint threads, 619 shaping runs per second on one core and 3,595 on eight; on the Raspberry Pi 5, in two quick runs, 39 and 45 frames per second and 630 and 2,520 shaping runs per second on one and four cores), compared with a reference only when it was measured with the same LordOS version, and `lord-bench` checks its own sandbox before any work: six things it must not be able to do (open a local socket or a network connection, run a program, start a process, create a file, read a system file) were all refused on that machine, and a run where one gets through is marked unstable. On a Raspberry Pi it watches the board's firmware during the whole run: the under-voltage alarm, the only flag the LordOS Pi kernel exposes, the firmware's full throttling flags where an older kernel has them, and 80 °C, where the firmware starts slowing the processor down, which stops a peak test as throttled; System Information's Raspberry Pi section reads the same alarm and flags and leaves out what the kernel doesn't show. This was tested on simulated system files and on the Pi 5, where the alarm is present and reads 0 with the official power supply; an actual under-voltage was not provoked. The references are a virtual machine and a Raspberry Pi 5 (§7.4); hardware video decoding and a real PC reference are not built yet.
+There are no measurements on real PCs in the repository yet. The ISO is tested on virtual machines (UEFI and BIOS); testing on a real AMD machine from the live USB is planned. LordBench (0.8.6) is designed to measure memory and CPU at idle, boot time, frame times, video and app start in a repeatable way, and community hardware reports (0.8.7) to collect them from real machines (`docs/BENCHMARK.md`). In development for 0.8.6 (unreleased; the latest release is 0.8.5-beta), its first part is built: a sandboxed `lord-bench` helper that measures the CPU, memory, the GPU offscreen, storage and a sustained load, stops near the temperature limit or when the processor throttles, and records the conditions of each run, shown in System Information → Performance as "×N" of reference machines; it also measures software video decoding and the remote desktop's encoders, the desktop's frame times and the time from a pointer move to the screen, alone and under a low-priority load, and boot time over several restarts; it also runs from a terminal (`lordos-sysreport bench`). Also in development, it times LordOS's own interface work with the engine's real code (the layout and paint of a fixed full-HD desktop scene, and the shaping of paragraphs in Latin, Arabic, Devanagari, Thai and Chinese with fonts built into the helper, which opens no files; on the reference virtual machine 37 frames per second on one core and 40 with the paint threads, 619 shaping runs per second on one core and 3,595 on eight; on the Raspberry Pi 5, in two quick runs, 39 and 45 frames per second and 630 and 2,520 shaping runs per second on one and four cores), compared with a reference only when it was measured with the same LordOS version, and `lord-bench` checks its own sandbox before any work: six things it must not be able to do (open a local socket or a network connection, run a program, start a process, create a file, read a system file) were all refused on that machine, and a run where one gets through is marked unstable. On a Raspberry Pi it watches the board's firmware during the whole run: the under-voltage alarm, the only flag the LordOS Pi kernel exposes, the firmware's full throttling flags where an older kernel has them, and 80 °C, where the firmware starts slowing the processor down, which stops a peak test as throttled; System Information's Raspberry Pi section reads the same alarm and flags and leaves out what the kernel doesn't show. This was tested on simulated system files and on the Pi 5, where the alarm is present and reads 0 with the official power supply; an actual under-voltage was not provoked. The references are a virtual machine and a Raspberry Pi 5 (§7.4); hardware video decoding and a real PC reference are not built yet and moved to 0.8.7.
### Source files
@@ -743,7 +743,7 @@ make -C server test-full # adds the helpers, the sandbox and the HarfBuzz comp
- **Terminal and text:** the VT emulator, OpenType shaping against HarfBuzz, Unicode bidi against the official test file, input methods, Thai word breaking against libthai.
- **Security:** the sandbox (app, network, helper), signing (NIST and RFC 8032 vectors), package state, archive path rules against malicious archives, `lord.fs` protections, the firewall rules (with 20,000 JSON mutations and 30,000 random operations against a linear reference), the DNS reader (200,000 random packets), the kernel-map compiler (480,000 connections), and the kernel integration test (18 of 18 on a VM).
- **Parsers:** mail, MIME, HTML sanitizer, iCalendar, vCard and XML (30,953 checks with mutation fuzzing), the vault format, importers, QR, CBOR, D-Bus marshalling, the country database reader, journal, TZif and IPP.
-- **Engine and hardware:** layout and painting, NEON vs. C, the touchpad driver with recorded gestures, fans on fake sysfs trees, display arrangement, sound, and the WebAssembly specification suite. Since 0.8.6 (in development; the latest release is 0.8.5 Beta), every frame of random scenes, and of a Monitor scene with a translucent, blurred Terminal minimized into the Dock, is compared with a full repaint through a copy of the compositor's damage and double-buffer bookkeeping; that comparison found and fixed seven partial-repaint errors, and the same check on a running desktop on a virtual machine (the 0.8.2 scene, 22 minimize and restore cycles, 54 comparisons per run, before and after, with one damaged box and with several) found no stale area.
+- **Engine and hardware:** layout and painting, NEON vs. C, the touchpad driver with recorded gestures, fans on fake sysfs trees, display arrangement, sound, and the WebAssembly specification suite. Since 0.8.6 (in development; the latest release is 0.8.5 Beta), every frame of random scenes, and of a Monitor scene with a translucent, blurred Terminal minimized into the Dock, is compared with a full repaint through a copy of the compositor's damage and double-buffer bookkeeping; that comparison found and fixed seven partial-repaint errors, and the same check on a running desktop on a virtual machine (the 0.8.2 scene, 22 minimize and restore cycles, 54 comparisons per run, before and after, with one damaged box and with several) found no stale area. A blurred window hidden whole behind an opaque one is no longer repainted with every change near it: a translucent Terminal behind Monitor's moving map made each frame repaint 46 % of the screen, now 11–15 % with one damaged box and 3–4 % with several on that virtual machine, checked the same way with no stale area.
- **System Information (0.8.5):** the collector over five fake machines (an AMD desktop, an Intel laptop, an Nvidia desktop, a Raspberry Pi 5, a virtual machine) filled with serial numbers, UUIDs, MAC addresses and names that must not reach a report (none does, 460 checks), the SMBIOS memory reader against crafted and malformed tables, and the Checks and Sandbox Probe evaluation (56 checks).
On the final ISO build: `make -C server test` reported 23 passed, 0 failed, 1 skipped (bidi data not installed).