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.

Merge branch 'v082-monred' into v082-integration

Federico Pereira8d291b006159
diff --cc CHANGELOG.md
index 3679892,462f3fe..1813fbe
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -56,53 -14,37 +56,84 @@@ of the matching [GitHub release](https:
### Added
+- **Design study: an immutable LordOS with A/B system images** ([docs/IMMUTABLE.md](docs/IMMUTABLE.md)).
+ It compares dm-verity system partitions, fs-verity, composefs, OSTree, A/B root partitions and
+ btrfs snapshots against Debian 13, the Store, the Raspberry Pi 5 and LordOS's threat model, and
+ recommends a separate, optional edition: a read-only `/usr` verified by dm-verity in two slots,
+ one signed boot image per version, automatic fallback to the previous version when an update
+ doesn't start, and `/etc` and the home folders kept on their own partition. The classic edition,
+ `install.sh` and in-place updates stay as they are; there is no conversion of existing systems.
+- **Experimental build of that design** (`tools/immutable/`, not part of the regular ISO or
+ Raspberry Pi image): a disk image for UEFI virtual machines with the A/B layout, a signed
+ update into the other slot, and a scripted demonstration in which a deliberately broken version
+ fails three times and the machine returns to the previous version on its own. Its payload is a
+ minimal Debian 13, not the LordOS desktop yet; the rest of the plan moves to later versions.
+- **New wallpapers.** Eleven original LordOS wallpapers in three categories: **Signature** (Crystal
+ Crown, Eternal Dawn, Royal Flow, Royal Waves, Violet Horizon), **Lumo** (Celestial, Aurora) and
+ **Cosmos** (Event Horizon, Infinite Galaxy, Solar Odyssey, Stellar Voyage), created by iPERFEX
+ with an AI image generator. Settings → Wallpaper now lists every wallpaper grouped by category,
+ with the previous four gradients as "Gradients". They are installed once in
+ `/usr/share/backgrounds/lordos/` as high-quality JPEG (about 4 MB in total) with small thumbnails
+ for the pickers, and a higher-resolution version added later is used automatically on the
+ screens that need it.
+
+### Changed
+
+- **New default wallpaper:** new users start on **Celestial**; anyone who already chose a wallpaper
+ keeps it. The login screen (and the remote login page) now shows **Crystal Crown**.
+- The Control Center shows the current wallpaper and three from the collection; the rest are in
+ Settings → Wallpaper (**Change Wallpaper…**).
+- **Suggested for your computer.** Store → Discover now starts with packages for the hardware
+ LordOS finds in the computer, each with the reason it appears ("We detected a printer from HP
+ connected by USB"): the guest tools of a VMware or QEMU virtual machine, the proprietary graphics
+ driver for an NVIDIA card (labeled as not free software, never preselected, with what changes:
+ DKMS, Secure Boot key enrollment, older cards, and that the free nouveau driver stays the
+ default), vendor drivers for USB printers and scanners, driverless USB printing (`ipp-usb`),
+ the Raspberry Pi 5's board tools, and the firmware package a Wi-Fi, Bluetooth, network or
+ graphics device asked for and didn't find. One click shows the usual plan and installs through
+ the package engine; "Don't suggest again" hides a card for good. When something new is
+ suggested, the Store's Discover item shows a count and one notification says so. For a
+ VirtualBox virtual machine the card explains that its guest utilities aren't part of Debian 13.
+ Detection only reads the kernel's hardware files; nothing is sent anywhere. The rules are data
+ (`assets/store/suggestions.json`); see [docs/PACKAGES.md](docs/PACKAGES.md).
+
+### Fixed
+
+- **Package lists after enabling a component.** Adding a component (such as `non-free-firmware`)
+ or a source whose signed release file hadn't changed upstream left the package list as it was
+ ("already up to date"); the index is now rebuilt whenever the set of lists it is built from
+ changes.
+ - **Allow or block each destination inside Monitor's app rows.** Open an app in Monitor → Network
+ and every name it reached (or address, when the system resolver gave no name) has its own
+ allow/block switch, showing what the app's rules decide for it right now and why ("By the rule
+ \*.example.com", "Follows this app's default", "Blocked by this app's restrictions"). A click
+ writes, flips or removes the rule for exactly that name, the same rule Settings → Privacy →
+ Network rules by app shows, and `lord-netperm` applies it at once. Long lists show eight and
+ "N more…"; rows keep their place while the list is open
+ ([docs/MONITOR.md](docs/MONITOR.md#per-destination-switches-082)).
+ - **Traffic history.** The Network tab's chart now zooms out from the live minute to 1 hour,
+ 24 hours, 7 days and 30 days, steps back and forward one window at a time and has **Now**; with
+ an app selected its own chart follows the same window, and the summary lists the apps that moved
+ the most in it. Your session records bytes received and sent per minute (7 days) and per hour
+ (30 days), for the computer and for each of your apps, in a small file in your home folder
+ (`~/.local/state/lordos/net-history.bin`): never an address, a name or a country. Settings →
+ Privacy → Monitor has **Keep a traffic history** (on) and **Clear History**
+ ([docs/MONITOR.md](docs/MONITOR.md#traffic-history-082)).
+
+ ### Changed
+
+ - **The map's moving dots cost about half as much.** lord-server now repaints several small
+ rectangles per frame instead of the one box around every change, skips clipped parts of the
+ interface outside them, and copies only those rectangles to the screen; the dots are small
+ ready-made images. With Monitor's map animating, the animation's share of lord-server's CPU went
+ from 2.9 to 1.6 points of one core (VM 119, CPU compositing), and every partial repaint of the
+ desktop gets cheaper the same way. Blurred surfaces (the menu bar, the Dock) are still repainted
+ whole when anything touches them, as in 0.8.1 ([docs/MONITOR.md](docs/MONITOR.md#082-several-damaged-rectangles-vm-119)).
+
+ ### Not included
+
+ - **City names on the map.** Debian 13 only ships country-level IP databases (`geoip-database`) and
+ LordOS's own is country-level too, so labels stay countries; no large download was added.
## [0.8.1-beta] - 2026-10-19
diff --cc assets/locales/en/monitor.json
index 85e75da,b20d645..ffad2e3
--- a/assets/locales/en/monitor.json
+++ b/assets/locales/en/monitor.json
@@@ -218,44 -218,29 +218,69 @@@
"proc.noCmdline": "(none: a kernel thread or a process that cleared it)",
"proc.tab.stats": "Statistics",
"proc.tab.files": "Open files and ports",
+ "temp.col": "Temperature",
+ "temp.noSensor": "No sensor",
+ "temp.resting": "Resting",
+ "temp.noSensorHint": "This disk has no temperature sensor the system can read (memory cards, virtual disks and many USB adapters don’t).",
+ "temp.restingHint": "The disk is resting: it is read again as soon as it is used, so it can stay spun down.",
+ "temp.limitOwn": "Limit {max} °C, reported by the drive",
+ "temp.limitDefault": "Limit {max} °C (the drive does not report its own)",
+ "temp.title": "Temperature · {name}",
+ "temp.sensor.nvme": "NVMe sensor",
+ "temp.sensor.drivetemp": "SATA sensor",
+ "health.col": "Health",
+ "health.title": "Health (SMART)",
+ "health.ok": "OK",
+ "health.warning": "Check",
+ "health.failing": "Failing",
+ "health.unknown": "No data",
+ "health.none": "No SMART",
+ "health.noneHint": "This kind of disk does not report its health (memory cards, virtual disks).",
+ "health.waiting": "Reading the disk’s health…",
+ "health.standby": "The disk is resting: its health is read the next time it is used.",
+ "health.errorHint": "The disk did not answer SMART (it may not have it, or be behind a USB adapter that blocks it).",
+ "health.hint.ok": "The disk reports no problems.",
+ "health.hint.warning": "There are signs of wear: open it in Disks to see why, and keep a backup.",
+ "health.hint.failing": "The disk says it will fail soon. Copy your data now.",
+ "health.hint.unknown": "The disk answered, but without enough data.",
+ "health.openDisks": "Open in Disks",
+ "health.hours": "Powered on",
+ "health.hoursUnit": "h",
+ "health.wear": "SSD wear",
+ "health.basic": "Basic reading. Install smartmontools in Disks for the full report and self-tests.",
+ "diskAlert.toggle": "Notify me when a disk gets too hot or its health gets worse",
+ "diskAlert.hotTitle": "{name} is too hot",
+ "diskAlert.critTitle": "{name} is at a critical temperature",
+ "diskAlert.hotBody": "{dev} is at {temp} °C (limit {max} °C). Check the airflow around it.",
+ "diskAlert.open": "Open Monitor",
+ "diskAlert.checkTitle": "{name} needs a check",
+ "diskAlert.checkBody": "{dev} shows signs of wear. Make sure you have a backup.",
+ "diskAlert.failTitle": "{name} is failing",
+ "diskAlert.failBody": "{dev} reports that it will fail soon. Copy your data now.",
- "health.idle": "Not read yet: a spinning disk is read the next time it is in use, so a resting disk is not woken up. With smartmontools it is read without waking it."
++ "health.idle": "Not read yet: a spinning disk is read the next time it is in use, so a resting disk is not woken up. With smartmontools it is read without waking it.",
+ "hist.live": "60 s",
+ "hist.1h": "1 h",
+ "hist.24h": "24 h",
+ "hist.7d": "7 d",
+ "hist.30d": "30 d",
+ "hist.per.1h": "per minute",
+ "hist.per.24h": "every 15 min",
+ "hist.per.7d": "per hour",
+ "hist.per.30d": "every 6 h",
+ "hist.unavailable": "The traffic history is not available in this session.",
+ "hist.off": "The traffic history is off (Settings → Privacy → Monitor).",
+ "hist.none": "Nothing was recorded in this period.",
+ "hist.topApps": "Most traffic · {range}",
+ "net.moreDomains": {
+ "one": "{count} more…",
+ "other": "{count} more…"
+ },
+ "net.fewer": "Show fewer",
+ "net.domainRestricted": "Blocked by this app's restrictions",
+ "net.domainByDefault": "Follows this app's default",
+ "net.domainByRule": "By the rule {rule}",
+ "privacy.history": "Keep a traffic history",
+ "privacy.historyHint": "Bytes received and sent per minute for 7 days and per hour for 30 days, for the computer and for each app. Never addresses, names or countries. Kept only in your home folder.",
+ "privacy.clear": "Clear History",
+ "privacy.cleared": "History cleared"
}
diff --cc assets/locales/es/monitor.json
index e1afc46,ea5d2bf..06baeb1
--- a/assets/locales/es/monitor.json
+++ b/assets/locales/es/monitor.json
@@@ -218,44 -218,29 +218,69 @@@
"proc.noCmdline": "(ninguna: un hilo del núcleo o un proceso que la borró)",
"proc.tab.stats": "Estadísticas",
"proc.tab.files": "Archivos y puertos abiertos",
+ "temp.col": "Temperatura",
+ "temp.noSensor": "Sin sensor",
+ "temp.resting": "En reposo",
+ "temp.noSensorHint": "Este disco no tiene un sensor de temperatura que el sistema pueda leer (las tarjetas de memoria, los discos virtuales y muchos adaptadores USB no lo tienen).",
+ "temp.restingHint": "El disco está en reposo: se vuelve a leer en cuanto se use, así puede seguir detenido.",
+ "temp.limitOwn": "Límite {max} °C, informado por el disco",
+ "temp.limitDefault": "Límite {max} °C (el disco no informa el suyo)",
+ "temp.title": "Temperatura · {name}",
+ "temp.sensor.nvme": "sensor NVMe",
+ "temp.sensor.drivetemp": "sensor SATA",
+ "health.col": "Salud",
+ "health.title": "Salud (SMART)",
+ "health.ok": "Bien",
+ "health.warning": "Revisar",
+ "health.failing": "Fallando",
+ "health.unknown": "Sin datos",
+ "health.none": "Sin SMART",
+ "health.noneHint": "Este tipo de disco no informa su salud (tarjetas de memoria, discos virtuales).",
+ "health.waiting": "Leyendo la salud del disco…",
+ "health.standby": "El disco está en reposo: su salud se lee la próxima vez que se use.",
+ "health.errorHint": "El disco no respondió SMART (puede no tenerlo, o estar detrás de un adaptador USB que lo bloquea).",
+ "health.hint.ok": "El disco no informa problemas.",
+ "health.hint.warning": "Hay señales de desgaste: abrilo en Discos para ver por qué y tené una copia de seguridad.",
+ "health.hint.failing": "El disco dice que va a fallar pronto. Copiá tus datos ya.",
+ "health.hint.unknown": "El disco respondió, pero sin datos suficientes.",
+ "health.openDisks": "Abrir en Discos",
+ "health.hours": "Encendido",
+ "health.hoursUnit": "h",
+ "health.wear": "Desgaste del SSD",
+ "health.basic": "Lectura básica. Instalá smartmontools en Discos para el informe completo y las autopruebas.",
+ "diskAlert.toggle": "Avisarme cuando un disco se caliente demasiado o empeore su salud",
+ "diskAlert.hotTitle": "{name} está muy caliente",
+ "diskAlert.critTitle": "{name} está a una temperatura crítica",
+ "diskAlert.hotBody": "{dev} está a {temp} °C (límite {max} °C). Revisá la ventilación a su alrededor.",
+ "diskAlert.open": "Abrir Monitor",
+ "diskAlert.checkTitle": "{name} necesita revisión",
+ "diskAlert.checkBody": "{dev} muestra señales de desgaste. Asegurate de tener una copia de seguridad.",
+ "diskAlert.failTitle": "{name} está fallando",
+ "diskAlert.failBody": "{dev} informa que va a fallar pronto. Copiá tus datos ya.",
- "health.idle": "Todavía sin leer: un disco giratorio se lee la próxima vez que se use, para no despertarlo si está en reposo. Con smartmontools se lee sin despertarlo."
++ "health.idle": "Todavía sin leer: un disco giratorio se lee la próxima vez que se use, para no despertarlo si está en reposo. Con smartmontools se lee sin despertarlo.",
+ "hist.live": "60 s",
+ "hist.1h": "1 h",
+ "hist.24h": "24 h",
+ "hist.7d": "7 d",
+ "hist.30d": "30 d",
+ "hist.per.1h": "por minuto",
+ "hist.per.24h": "cada 15 min",
+ "hist.per.7d": "por hora",
+ "hist.per.30d": "cada 6 h",
+ "hist.unavailable": "El historial de tráfico no está disponible en esta sesión.",
+ "hist.off": "El historial de tráfico está apagado (Ajustes → Privacidad → Monitor).",
+ "hist.none": "No se registró nada en este período.",
+ "hist.topApps": "Más tráfico · {range}",
+ "net.moreDomains": {
+ "one": "{count} más…",
+ "other": "{count} más…"
+ },
+ "net.fewer": "Mostrar menos",
+ "net.domainRestricted": "Bloqueado por las restricciones de esta app",
+ "net.domainByDefault": "Sigue lo predeterminado de esta app",
+ "net.domainByRule": "Por la regla {rule}",
+ "privacy.history": "Guardar un historial de tráfico",
+ "privacy.historyHint": "Bytes recibidos y enviados por minuto durante 7 días y por hora durante 30 días, del equipo y de cada app. Nunca direcciones, nombres ni países. Se guarda solo en tu carpeta personal.",
+ "privacy.clear": "Borrar historial",
+ "privacy.cleared": "Historial borrado"
}
diff --cc assets/locales/pt/monitor.json
index 6121b49,d7eeb36..3d88081
--- a/assets/locales/pt/monitor.json
+++ b/assets/locales/pt/monitor.json
@@@ -218,44 -218,29 +218,69 @@@
"proc.noCmdline": "(nenhuma: uma thread do núcleo ou um processo que a apagou)",
"proc.tab.stats": "Estatísticas",
"proc.tab.files": "Arquivos e portas abertos",
+ "temp.col": "Temperatura",
+ "temp.noSensor": "Sem sensor",
+ "temp.resting": "Em repouso",
+ "temp.noSensorHint": "Este disco não tem um sensor de temperatura que o sistema possa ler (cartões de memória, discos virtuais e muitos adaptadores USB não têm).",
+ "temp.restingHint": "O disco está em repouso: volta a ser lido assim que for usado, para que possa continuar parado.",
+ "temp.limitOwn": "Limite {max} °C, informado pelo disco",
+ "temp.limitDefault": "Limite {max} °C (o disco não informa o seu)",
+ "temp.title": "Temperatura · {name}",
+ "temp.sensor.nvme": "sensor NVMe",
+ "temp.sensor.drivetemp": "sensor SATA",
+ "health.col": "Saúde",
+ "health.title": "Saúde (SMART)",
+ "health.ok": "OK",
+ "health.warning": "Verificar",
+ "health.failing": "Falhando",
+ "health.unknown": "Sem dados",
+ "health.none": "Sem SMART",
+ "health.noneHint": "Este tipo de disco não informa sua saúde (cartões de memória, discos virtuais).",
+ "health.waiting": "Lendo a saúde do disco…",
+ "health.standby": "O disco está em repouso: sua saúde é lida na próxima vez que for usado.",
+ "health.errorHint": "O disco não respondeu SMART (pode não ter, ou estar atrás de um adaptador USB que o bloqueia).",
+ "health.hint.ok": "O disco não informa problemas.",
+ "health.hint.warning": "Há sinais de desgaste: abra-o em Discos para ver por quê e mantenha um backup.",
+ "health.hint.failing": "O disco diz que vai falhar em breve. Copie seus dados agora.",
+ "health.hint.unknown": "O disco respondeu, mas sem dados suficientes.",
+ "health.openDisks": "Abrir em Discos",
+ "health.hours": "Ligado",
+ "health.hoursUnit": "h",
+ "health.wear": "Desgaste do SSD",
+ "health.basic": "Leitura básica. Instale o smartmontools em Discos para o relatório completo e os autotestes.",
+ "diskAlert.toggle": "Avisar quando um disco esquentar demais ou sua saúde piorar",
+ "diskAlert.hotTitle": "{name} está quente demais",
+ "diskAlert.critTitle": "{name} está a uma temperatura crítica",
+ "diskAlert.hotBody": "{dev} está a {temp} °C (limite {max} °C). Verifique a ventilação ao redor.",
+ "diskAlert.open": "Abrir Monitor",
+ "diskAlert.checkTitle": "{name} precisa de verificação",
+ "diskAlert.checkBody": "{dev} mostra sinais de desgaste. Garanta que você tem um backup.",
+ "diskAlert.failTitle": "{name} está falhando",
+ "diskAlert.failBody": "{dev} informa que vai falhar em breve. Copie seus dados agora.",
- "health.idle": "Ainda não lido: um disco giratório é lido na próxima vez que for usado, para não acordá-lo em repouso. Com o smartmontools é lido sem acordá-lo."
++ "health.idle": "Ainda não lido: um disco giratório é lido na próxima vez que for usado, para não acordá-lo em repouso. Com o smartmontools é lido sem acordá-lo.",
+ "hist.live": "60 s",
+ "hist.1h": "1 h",
+ "hist.24h": "24 h",
+ "hist.7d": "7 d",
+ "hist.30d": "30 d",
+ "hist.per.1h": "por minuto",
+ "hist.per.24h": "a cada 15 min",
+ "hist.per.7d": "por hora",
+ "hist.per.30d": "a cada 6 h",
+ "hist.unavailable": "O histórico de tráfego não está disponível nesta sessão.",
+ "hist.off": "O histórico de tráfego está desligado (Ajustes → Privacidade → Monitor).",
+ "hist.none": "Nada foi registrado neste período.",
+ "hist.topApps": "Mais tráfego · {range}",
+ "net.moreDomains": {
+ "one": "mais {count}…",
+ "other": "mais {count}…"
+ },
+ "net.fewer": "Mostrar menos",
+ "net.domainRestricted": "Bloqueado pelas restrições deste app",
+ "net.domainByDefault": "Segue o padrão deste app",
+ "net.domainByRule": "Pela regra {rule}",
+ "privacy.history": "Manter um histórico de tráfego",
+ "privacy.historyHint": "Bytes recebidos e enviados por minuto durante 7 dias e por hora durante 30 dias, do computador e de cada app. Nunca endereços, nomes ou países. Fica só na sua pasta pessoal.",
+ "privacy.clear": "Apagar histórico",
+ "privacy.cleared": "Histórico apagado"
}
diff --cc docs/MONITOR.md
index 240ec53,03a7f6a..80fe1ba
--- a/docs/MONITOR.md
+++ b/docs/MONITOR.md
@@@ -7,10 -7,10 +7,11 @@@ a big number and a live area chart, a r
The Network tab takes the shape of a per-app network monitor (apps on the left, map in the middle, summary on
the right).
-Phase 1 was read-only. Since then the Network tab holds per-app firewall rules (Phase 2), in
-0.8.1 the Processes tab can stop a process and show its details ("Process actions"), and in 0.8.2
-each destination of an app has its own allow/block switch and the traffic chart reaches back 30
-days ("Traffic history"). There are no alerts.
+Phase 1 was read-only. Since then the Network tab holds per-app firewall rules (Phase 2) and, in
- 0.8.1, the Processes tab can stop a process and show its details ("Process actions"). In 0.8.2 the
- Disks tab shows each disk's temperature and health, and the session can notify when a disk gets too
- hot or less healthy ("Disk temperature and health"). There is no saved history.
++0.8.1, the Processes tab can stop a process and show its details ("Process actions"). In 0.8.2
++each destination of an app has its own allow/block switch, the traffic chart reaches back 30 days
++("Traffic history"), the Disks tab shows each disk's temperature and health, and the session can
++notify when a disk gets too hot or less healthy ("Disk temperature and health").
## Tabs
@@@ -235,12 -286,10 +346,13 @@@ bottom of the tab (`settings.monitor.di
```
apps/monitor/ index.jsx (tabs), Network.jsx (Network), MapView.jsx (map), Chart.jsx,
- TrafficChart.jsx (mirrored sent/received chart), draw.js (pixels),
+ TrafficChart.jsx (mirrored sent/received chart), History.jsx (zoom and
+ history windows), draw.js (pixels),
icons.jsx, Privacy.jsx, countries.js (generated)
apps/monitor/Processes.jsx the Processes tab, its context menu, the stop sheet and Get Info
+apps/monitor/DisksTab.jsx the Disks tab: rates, temperature and health per disk, the chosen disk's cards
+sdk/smart.js, sdk/smartparse.js SMART summaries and smartctl's JSON → one model (Disks app too)
+sdk/diskwatch.js notices when a disk gets too hot or less healthy
sdk/monitor.js useMonitor(), stores monitorSamples / monitorProcesses / monitorConnections /
monitorDetail; monitor.watchProcess(), monitor.stopProcess()
server/src/ui/js_monitor.c lord.monitor (read-only, validated API)
@@@ -271,15 -321,12 +385,18 @@@ tests/mmdb_test.c, tests/map_bench.c
| `detail(pid, st)` | Get Info: the process the thread describes once per second (`0, 0`: none) |
| `detailInfo()` | its latest details, or `null` if there is nothing new; `{ pid, gone: true }` once it ended |
| `signal(pid, st, 'TERM' \| 'KILL')` | stops one of the user's own processes: `null`, or an error code (`proc.gone`, `proc.protected…`, `proc.notOwn`, `proc.denied`) |
+| `watchDisks(on)` | (0.8.2) with the Monitor closed, the thread wakes every 30 s and reads only the disk sensors |
+| `diskTemps()` | (0.8.2) `{ t, disks: [{ name, model, rota, sensor, temp, tempT, tempMax, tempCrit, tempIdle, awake }] }` or `null` if nothing new; it does not keep the 4 Hz sampling alive |
+
+Each disk in `sample().disk.disks` carries the same fields (`sensor`: `"nvme"`, `"drivetemp"` or
+`null`; `temp` in °C or `null`; `tempT`: when it was read; `tempIdle`: a spinning disk at rest, not
+read; `awake`: I/O in the last minute).
+ | `history({ from, step, n, app })` | the traffic history in `n` buckets (see "Traffic history"), or `null` |
+ | `historyEnable(on)` / `historyClear()` | the "Keep a traffic history" setting; deletes the history |
No function takes paths or commands: the only arguments are booleans, a language code (letters,
- digits, `-` and `_`, up to 15), a PID with its start time (integers) and `'TERM'` or `'KILL'`.
+ digits, `-` and `_`, up to 15), a PID with its start time (integers), `'TERM'` or `'KILL'`, and the
+ history's integers and app id (`[A-Za-z0-9._:@+~/-]`, up to 127).
`lord-server` runs nothing for the Monitor.
### Sampling without slowing the screen
diff --cc docs/VM-SETUP.md
index 99fc798,e7eae0a..d236a08
--- a/docs/VM-SETUP.md
+++ b/docs/VM-SETUP.md
@@@ -1143,56 -1143,30 +1143,83 @@@ folder `~/LordOS-monred`, installed int
- The session language, theme and accent were changed for the screenshots and restored from
`~/.config-lordos-backup-monred` afterwards.
+## Step 29 — 0.8.2: immutable (A/B) prototype (VM 122 `lordos-sandbox`, October 19)
+
+See `IMMUTABLE.md`, "The prototype". On VM 122 (172.17.0.56), in its own folder `~/LordOS-inmut3`
+(only `tools/immutable/`) and the work folder `/var/tmp/lordos-immutable` (base tree, images,
+throwaway test key). The test images boot in **QEMU inside the VM** (nested KVM, OVMF): the VM's own
+disk, boot, network and LordOS installation were not touched.
+
+- **Installed** (`apt-get install --no-install-recommends`): `debootstrap`, `systemd-repart`,
+ `systemd-ukify`, `systemd-boot-efi`, `systemd-boot-tools`, `cryptsetup-bin`, `erofs-utils`,
+ `qemu-system-x86`, `ovmf`, `gpg`, `gpg-agent`, `gpgv`, `libcryptsetup12`, `mtools`,
+ `dosfstools` (and their dependencies). `systemd-boot` itself and dracut were installed only inside
+ the image's chroot, never on the VM (dracut would replace the VM's initramfs-tools).
+- **Run:** `sudo tools/immutable/build.sh all` and `sudo tools/immutable/demo.py` (as root: `lord`
+ is not in the `kvm` group, and it was not added). The demo's HTTP server listens on port 8642
+ only while it runs; QEMU uses user-mode networking.
+- **Left behind:** the packages above and `/var/tmp/lordos-immutable` (~5 GB; delete it to free the
+ space). Nothing else changed.
+## Step 29 — New wallpapers (VM 123 `lordos-monitor`, October 19)
+
+Tree in `~/LordOS-wp`, built there (`make -C server -j4`, `make -C server test`: 23 passed,
+3 skipped). Nothing was installed with apt.
+
+- **Deployment, temporary:** `/usr/local/lib/lordos` was copied to `lordos.wp123-bak`, the new
+ `lord-server`, `lord-sessiond`, `lord-vault`, `lord-maild`, the themes and `assets/` were installed
+ over it, and the collection went to `/usr/share/backgrounds/lordos` with the
+ `assets/wallpapers` link, as the package does. Afterwards the backup was copied back, the files
+ that only the new build had were removed (`diff -rq` against the backup: identical), and
+ `/usr/share/backgrounds/lordos` was deleted.
+- **New user:** `~/.config/lordos/settings.json` was replaced by `{"language": "en"}` for the
+ screenshots (Celestial by default, then Crystal Crown and light mode chosen in Settings) and
+ restored from its backup (`wallpaper: "sunset"` again).
+- **Login screen:** the session from before the deploy was ended and `/run/lordos/autologin-done`
+ removed to show the greeter and then autologin again; `/etc/lordos/session.conf` wasn't changed.
+- **Screenshots** with `screendump` from the Proxmox host, the pointer with
+ `lord-qmp-input.py 123 1280 800`. eth0 and the VM's network weren't touched.
+## Step 29 — Disk temperatures and SMART with smartmontools (VM 119 `lordos-spot`, October 19)
+
+See `MONITOR.md` ("Disk temperature and health") and `SYSTEM.md` ("SMART with smartmontools").
+
+- **Deploy:** the `v082-disks` tree built in `~/LordOS-dt082`; only `lord-server`, the themes and
+ `assets/locales` were installed in `/usr/lib/lordos`, after a backup
+ (`/var/tmp/disktemp082-backup/lordos-before.tgz`), and put back from it afterwards.
+- **Test user:** `disktest` ("Disk Test", in the `sudo` group, a test-only password), created so the
+ login screen could be used without touching `lord`'s password; removed afterwards
+ (`userdel -r disktest`).
+- **`drivetemp`** was loaded by hand (`modprobe drivetemp`) to check that QEMU's SATA disk gets no
+ sensor (it has neither SCT nor attribute 194); unloaded afterwards.
+- **smartmontools** was installed twice from the Disks app's "Install smartmontools" (the package
+ engine's `pkg-install`), as the feature does, and purged afterwards (`apt-get purge
+ smartmontools`), so the next test starts from "not installed" again. Before that, the fixtures in
+ `server/tests/smart/` were captured with a `smartctl` unpacked into `/tmp/smx` (`apt-get download`
+ + `dpkg -x`, never installed).
+- Nothing else changed: no Proxmox setting, no network setting.
+ ## Step 29 — Monitor → Network: per-destination switches, traffic history, several damaged rectangles (VM 119 `lordos-spot`, October 19)
+
+ See `MONITOR.md` ("Per-destination switches", "Traffic history", "0.8.2: several damaged
+ rectangles"). On VM 119 (172.17.0.54), built in its own folders (`~/LordOS-monred`, plus
+ `~/LordOS-before` from `origin/main` and instrumented copies for the measurements), all deleted at
+ the end.
+
+ - **Installed:** `linux-perf` (`apt-get install --no-install-recommends linux-perf`), to find where
+ `lord-server` spends CPU while the map animates (`perf record -g -t <main thread>`). It stays
+ installed.
+ - **Deployed for the test, then restored:** `/usr/lib/lordos` (the session's `lord-server`, the
+ theme bundles, `assets`, and for the per-app history `lord-netperm` from the same tree, since the
+ installed one predates the 0.8.1 traffic accounting) was saved in `/var/backups/lordos-monred-bak`
+ and put back at the end (file list and contents compared with `diff -r`; the backup was then
+ deleted). `lord-netperm.service` was restarted with the original binary.
+ - **Session:** `/etc/lordos/session.conf` with `AUTOLOGIN=lord` (it didn't exist; removed at the
+ end) and `/run/lordos/autologin-done` removed before each `systemctl restart lordos`, to start a
+ fresh session with each build. The language (English), Appearance mode and Reduce motion were
+ changed for the screenshots and measurements, and `settings.json` and `firewall.json` were
+ restored from a copy; the history file the test wrote (`~/.local/state/lordos`) was deleted. The
+ VM ends at the login screen.
+ - **Traffic:** `curl --limit-rate 40k` loops to Debian mirrors in ten countries from the SSH
+ session (stopped at the end), and Firefox ESR (already on the VM) opening a few sites and one
+ download (`~/Downloads/ls-lR.gz`, deleted).
+ - **Screenshots** with `screendump` from the Proxmox host; pointer and keys with
+ `lord-qmp-input.py 119 1280 800` and `qm monitor 119` `sendkey`.
+ - Nothing in the network configuration was touched (`eth0` keeps 172.17.0.54).
diff --cc server/Makefile
index 02ed672,d84d20d..0947e8a
--- a/server/Makefile
+++ b/server/Makefile
@@@ -48,9 -48,9 +48,9 @@@ QJS_OBJ := $(patsubst %,build/qjs/%.o,q
# .lpk app isolation, permissions and signing (src/sec, see docs/PRIVACY.md and docs/SIGNING.md)
# Monitor: metrics, connections and the country of an IP (src/monitor, see docs/MONITOR.md)
- MON_SRC := src/monitor/mon.c src/monitor/disktemp.c src/monitor/conn.c src/monitor/procctl.c src/monitor/proc_admin.c src/monitor/mmdb.c src/monitor/map.c src/ui/js_monitor.c
-MON_SRC := src/monitor/mon.c src/monitor/nethist.c src/monitor/netrec.c src/monitor/conn.c src/monitor/procctl.c src/monitor/proc_admin.c src/monitor/mmdb.c src/monitor/map.c src/ui/js_monitor.c
++MON_SRC := src/monitor/mon.c src/monitor/disktemp.c src/monitor/nethist.c src/monitor/netrec.c src/monitor/conn.c src/monitor/procctl.c src/monitor/proc_admin.c src/monitor/mmdb.c src/monitor/map.c src/ui/js_monitor.c
# Media (src/media, docs/MEDIA.md): only the lord-server side. Only lord-media links FFmpeg.
-MEDIA_SRC := src/media/media.c src/media/mview.c src/media/capture.c src/media/annot.c src/media/maudio.c src/media/mpulse.c src/media/proto.c src/ui/js_media.c
+MEDIA_SRC := src/media/media.c src/media/hwdec.c src/media/mview.c src/media/capture.c src/media/annot.c src/media/maudio.c src/media/mpulse.c src/media/proto.c src/ui/js_media.c
SEC_SRC := src/sec/json.c src/sec/sign.c src/sec/pkgstate.c src/sec/perms.c src/sec/cgroup.c src/sec/sandbox.c src/sec/brokersrv.c src/sec/brokercam.c src/sec/brokerkr.c src/sec/restrict.c src/sec/appid.c src/sec/pwguard.c
# App mode: lord-server --app <id> runs an .lpk app as an isolated Wayland client (src/app)
APP_SRC := src/app/appclient.c src/app/appspawn.c src/ui/js_broker.c src/ui/js_brokercam.c
@@@ -307,9 -307,15 +307,15 @@@ build/map-bench: tests/map_bench.c src/
# Monitor process actions (src/monitor/procctl.c): the protected list, stat parsing, a signal that
# refuses a stale start time (PID reuse), TERM/KILL on a child, and the Get Info JSON
test: build/procctl-test
-build/procctl-test: tests/procctl_test.c src/monitor/procctl.c src/monitor/procctl.h src/monitor/mon.c src/monitor/conn.c src/monitor/mmdb.c src/pkg/xz.c build/obj/ui/stb.o
- $(CC) $(CPPFLAGS) $(CFLAGS) $(WARN) -std=c11 -o $@ tests/procctl_test.c src/monitor/procctl.c src/monitor/mon.c src/monitor/conn.c src/monitor/mmdb.c src/pkg/xz.c build/obj/ui/stb.o -lm -lpthread
+build/procctl-test: tests/procctl_test.c src/monitor/procctl.c src/monitor/procctl.h src/monitor/mon.c src/monitor/disktemp.c src/monitor/conn.c src/monitor/mmdb.c src/pkg/xz.c build/obj/ui/stb.o
+ $(CC) $(CPPFLAGS) $(CFLAGS) $(WARN) -std=c11 -o $@ tests/procctl_test.c src/monitor/procctl.c src/monitor/mon.c src/monitor/disktemp.c src/monitor/conn.c src/monitor/mmdb.c src/pkg/xz.c build/obj/ui/stb.o -lm -lpthread
./$@ || { rm -f $@; exit 1; }
+ # the Monitor's traffic history file: totals, 7-day/30-day rotation, cut and damaged files, Clear
+ test: build/nethist-test
+ build/nethist-test: tests/nethist_test.c src/monitor/nethist.c src/monitor/nethist.h
+ @mkdir -p build
+ $(CC) $(CPPFLAGS) $(CFLAGS) $(WARN) -std=c11 -o $@ tests/nethist_test.c src/monitor/nethist.c -lm
+ ./$@ || { rm -f $@; exit 1; }
# canvas.c rows: SIMD (NEON on aarch64) against C, bit for bit, and how long each one takes
# UI engine (docs/DESIGN.md "Engine notes"): ellipsis in LTR/RTL/Arabic/Thai/emoji, per-side borders,
# per-corner radii, logical edges, transforms and hit testing; `build/engine-test bench` times a 2000-row
diff --cc server/src/ui/js_monitor.c
index c308e5a,edb7284..74c75c9
--- a/server/src/ui/js_monitor.c
+++ b/server/src/ui/js_monitor.c
@@@ -19,9 -19,11 +19,14 @@@
* an error code (proc.gone, proc.protected…, proc.notOwn, proc.denied).
* Other users' processes go through the root helper (proc-signal,
* administrators only; sdk/monitor.js).
+ * watchDisks(on) disk temperatures with the Monitor closed (every 30 s; sdk/diskwatch.js)
+ * diskTemps() the latest { t, disks: [{ name, model, sensor, temp, tempMax, … }] } or
+ * null if nothing new; it does not keep the 4 Hz sampling awake
+ * historyEnable(on) Settings → Privacy → Monitor → "Keep a traffic history" (0.8.2)
+ * history({ from, step, n, app }) bytes per bucket from the history file (monitor/nethist.c):
+ * { res, oldest, now, rx: [n], tx: [n], top: [[app, rx, tx]] } or null;
+ * from/step in Unix seconds, n ≤ 1500, app an app id or null (the machine)
+ * historyClear() deletes the history; true if it is gone
*/
#include "js_monitor.h"
#include "../monitor/mon.h"
@@@ -390,8 -453,9 +467,11 @@@ static const JSCFunctionListEntry monit
JS_CFUNC_DEF("detail", 2, f_detail),
JS_CFUNC_DEF("detailInfo", 0, f_detail_info),
JS_CFUNC_DEF("signal", 3, f_signal),
+ JS_CFUNC_DEF("watchDisks", 1, f_watch_disks),
+ JS_CFUNC_DEF("diskTemps", 0, f_disk_temps),
+ JS_CFUNC_DEF("historyEnable", 1, f_history_enable),
+ JS_CFUNC_DEF("history", 1, f_history),
+ JS_CFUNC_DEF("historyClear", 0, f_history_clear),
};
void js_monitor_register(JSContext *c, JSValue lord, const char *assets_dir) {