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-disks' into v082-integration

Federico Pereira9c2fc9a3589b
diff --cc CHANGELOG.md
index aee61fc,972ec4e..a1a82a2
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -8,82 -8,36 +8,108 @@@ suffix (`-beta`) and are published on G
of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases), generated by
`tools/release/release-notes.sh` (see [docs/RELEASING.md](docs/RELEASING.md)).
+ ## [0.8.2] - Unreleased
+
+ ### Added
+
+ - **Monitor → Disks: each disk's temperature and health.** The Disks tab now shows every physical
+ disk's live temperature, read from the kernel without root: NVMe and M.2 drives through the nvme
+ driver's own sensor (also on a Raspberry Pi 5 with an M.2 HAT), SATA disks through the `drivetemp`
+ module, which the `lordos` package now loads at boot. Memory cards, virtual disks and adapters
+ without a sensor say "No sensor", never a made-up value. The chosen disk gets a 30-minute
+ temperature chart with the drive's own limits when it reports them, and an OK / Check / Failing
+ light from a cached SMART summary, with "Open in Disks". Spinning disks are only read while they
+ are in use, so a resting disk is never woken up
+ ([docs/MONITOR.md](docs/MONITOR.md#disk-temperature-and-health-082)).
+ - **Disks: the full SMART report with smartmontools.** The first time, the health card offers to
+ install Debian's smartmontools through the Store's package engine (an administrator). Then it
+ shows the overall health and why in plain words, temperature and limits, SSD wear (% of its rated
+ life used), power-on hours and cycles, reallocated and pending sectors, every attribute with a plain
+ name, the NVMe health log, the error log, the disk's own temperature history, and short and long
+ self-tests with progress and results. USB disks behind adapters that pass SMART through work too.
+ `smartctl` runs only through four new closed, validated root helper actions (`smart-info`,
+ `smart-health`, `smart-test`, `smart-abort`) on real whole disks, at a fixed path, with JSON output
+ ([docs/SYSTEM.md](docs/SYSTEM.md#smart-with-smartmontools-082)).
+ - **Notifications when a disk gets too hot or its health gets worse**, at most once per disk every
+ 30 minutes for heat, and only when the health is worse than last seen. On by default, with a switch
+ in Monitor → Disks.
+
## [Unreleased]
+## [0.8.2] - Unreleased
+
### 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…**).
+
+## [0.8.1-beta] - 2026-10-19
+
+A maintenance and polish release on top of 0.8.0-beta, and the first one that installed systems
+can update to in place: from here on, new versions arrive through **Store → Updates** (or `apt`)
+from a signed LordOS repository, with no reinstall. It also brings a Dock you arrange yourself,
+remote login over SSH from Settings, Restart and Shut Down in the crown menu, process actions and
+complete traffic accounting in Monitor, Bluetooth on the Raspberry Pi 5, and fixes for typing lag
+and black windows on the GPU path and for legacy BIOS boot in virtual machines.
+
+### Added
+
+- **A Dock you arrange yourself.** Drag any app (a LordOS app, an installed package or a Linux
+ app such as Firefox) from the app launcher onto the Dock and it lands where you drop it; drag icons
+ along the Dock to reorder them (the neighbours slide aside); drag one away and hold it for a
+ moment to remove it with a "poof", or use **Keep in Dock** / **Remove from Dock** in the menus.
+ Files stays first and the Trash last (it shows when it is full, opens in Files, takes files
+ dropped from Files and empties after a confirmation); Files, Settings and the app launcher can't
+ be removed. The Dock's menu starts with quick actions: an app's own (Settings' sections, Files'
+ folders, Mail's New Message, Monitor's tabs) or a Linux app's desktop actions from its `.desktop`
+ file. Settings → Desktop & Dock → **Reset Dock to defaults** puts the theme's apps back. The
+ Classic theme's taskbar works the same way, with a drop line. The arrangement from 0.8.0 is
+ migrated on first login ([docs/DOCK.md](docs/DOCK.md#customizing-the-dock-081)).
+- **Update LordOS from the Store, without reinstalling.** Store → Updates now shows "LordOS
+ <version> is available" with the release notes and an Update button, next to Debian's updates;
+ files, settings and accounts are kept, and a "Restart required" notice appears when the new
+ version (or a new kernel) is installed. It works the same on the ISO install, the Raspberry Pi
+ image, Debian with `install.sh` and servers, and `sudo apt update && sudo apt upgrade` does the
+ same. An optional daily check (on by default, never installs anything) notifies when something
+ new is available ([docs/UPDATES.md](docs/UPDATES.md)).
+- **Settings → Sharing → Remote login (SSH).** A new switch, off by default on every install,
+ turns the standard SSH server on and off for good (`systemctl enable --now` / `disable --now`).
+ The first time, it installs `openssh-server` through the package engine (the Store's path). The
+ page shows `ssh <user>@<address>` for this computer and its ED25519 host key fingerprint, and
+ lets you allow all users or only administrators. Root never logs in (`PermitRootLogin no` in a
+ drop-in shipped by the `lordos` package). The Raspberry Pi image's `ssh` switch file keeps
+ working and shows up as on ([docs/REMOTE.md](docs/REMOTE.md#remote-login-ssh)).
+- **Restart… and Shut Down… in the crown menu** (and behind a Power button in the Classic theme's
+ start menu); before, they were only on the login screen. Each opens a confirmation that does it
+ by itself after 60 seconds unless cancelled, lists the apps still open and warns when other users
+ are logged in. The session asks `lord-sessiond`, which only accepts those two words: any user may
+ do it alone, and only an administrator while other users have sessions open
+ ([docs/SESSIONS.md](docs/SESSIONS.md#restart-and-shut-down-from-a-session)).
- **Monitor → Processes: stop a process and Get Info.** Select a row and use the new Stop and
Info buttons, the right-click menu, a double click, ❖/Ctrl+I or Delete. Stop asks first, with
**Quit** (SIGTERM), **Force Quit** (SIGKILL) and Cancel. Your own processes are signalled by the
diff --cc docs/VM-SETUP.md
index 7b8218e,2af2ce7..99fc798
--- a/docs/VM-SETUP.md
+++ b/docs/VM-SETUP.md
@@@ -1143,38 -1143,21 +1143,56 @@@ 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.