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.
C cdebiandesktop-environmentebpffirewalllandlocklinuxlinux-distributionopen-sourceprivacyquickjsraspberry-pi-5reactsecuritywaylandwayland-compositor
docs/PAPER.md regenerated from the paper (automatic default apps: Settings -> Default Apps shows the app a file opens with when no choice is set)
Federico Pereira0890d84b82bf
diff --git a/docs/PAPER.md b/docs/PAPER.mdindex ada3b99..dd7f5fc 100644--- a/docs/PAPER.md+++ b/docs/PAPER.md@@ -136,7 +136,7 @@ LordOS speaks to several Debian services over their own protocols with its own c- **Network (`lord-netd`).** The network belongs to the system, not to a session. `lord-sessiond` starts `lord-netd` at boot with a fixed path and no arguments, so the machine has an address before anyone logs in. It runs only the closed `net-*` actions: its own DHCP client and netlink code, Wi-Fi through Debian's `wpa_supplicant`, WireGuard through LordOS's own netlink code, OpenVPN, IPsec/IKEv2 through strongSwan's `charon` driven over VICI with LordOS's own client, and optionally OpenConnect, PPTP and Fortinet-compatible tunnels. It talks only to the sessions' root helpers, over a socket that accepts only uid 0.- **Fans (`lord-fand`).** A root service that reads the CPU temperature every 2 s and writes fan duty from a profile, from early boot. It drives only fans its own scan found: the Raspberry Pi 5 fan header and allow-listed motherboard controllers. Laptop, GPU and unknown fans are never written. On stop, or after a crash, it restores the original kernel settings. It runs no programs, has no network, no capabilities and no device nodes.-- **Hardware settings.** Displays (modes from KMS with EDID names, a 15-second "keep these settings?" revert, per-display persistence, rotation, Night Light), Bluetooth through BlueZ, battery and power profiles, idle and lid handling, date and time, notifications for Linux apps and default apps. Changes arrive as kernel uevents and D-Bus signals; nothing polls. On a Raspberry Pi 5, Settings → Board firmware shows and updates the bootloader in the board's EEPROM through two closed admin actions (0.8.4.1).+- **Hardware settings.** Displays (modes from KMS with EDID names, a 15-second "keep these settings?" revert, per-display persistence, rotation, Night Light), Bluetooth through BlueZ, battery and power profiles, idle and lid handling, date and time, notifications for Linux apps and default apps (in 0.8.6, in development: when you haven't chosen one, a file opens with the system's default or the first installed app that declares its type, shown as "Automatic"). Changes arrive as kernel uevents and D-Bus signals; nothing polls. On a Raspberry Pi 5, Settings → Board firmware shows and updates the bootloader in the board's EEPROM through two closed admin actions (0.8.4.1).- **Updates.** Installed systems update in place from LordOS's signed APT repository on lordos.org, from Store → Updates or with `apt`; changes that are more than new files run as numbered, idempotent migrations (0.8.1). The Store's package engine follows apt's priorities (`/etc/apt/preferences.d`, 0.8.5), so on the Raspberry Pi image "Update all" chooses the same versions as `apt` and the pinned kernel stays blocked, and it accepts sources written as `Architectures: amd64,arm64` as apt does. The update from 0.8.4.1 or 0.8.4 to 0.8.5 runs no migration; it was tested with the release package built as 0.8.5~rc2 on a VMware machine on 0.8.4.1 and a Raspberry Pi 5 on 0.8.4, both with `apt`, then a restart.### Source files