feat(t495s): upstream T495 hardware, BTRFS disko, English deploy docs #20

Merged

rutger.putter merged 2 commits from bram.buijs/DAWO-NixOS:feat/t495s-btrfs into main

2026-06-18 12:53:33 +00:00

bram.buijs commented

2026-06-18 12:12:10 +00:00

Collaborator

References #10. Supersedes #14.

Reworks the T495s client (#14) onto the agreed shape.

Hardware module imports the upstream nixos-hardware lenovo-thinkpad-t495
profile instead of a hand-rolled one. The initrd module list is taken from a
real nixos-generate-config on the device; replace it with nixos-facter
on-device (input already present).
Disko switched ext4 -> BTRFS single-nvme-luks (ADR-0005), the standard image
layout; the ext4 profile is removed. One layout to maintain.
docs/deploy.md rewritten in English: nixos-anywhere for the initial install,
deploy-rs for updates of a running device, and a short fleet note.

Refs #10, supersedes #14. A fresh BTRFS install on the physical T495s to follow as
proof (screenshot or deploy output as a comment).

Question: OK to standardise on BTRFS single-nvme-luks for all clients and drop
the ext4 profile?

References #10. Supersedes #14. Reworks the T495s client (#14) onto the agreed shape. - Hardware module imports the upstream `nixos-hardware` lenovo-thinkpad-t495 profile instead of a hand-rolled one. The initrd module list is taken from a real `nixos-generate-config` on the device; replace it with nixos-facter on-device (input already present). - Disko switched ext4 -> BTRFS `single-nvme-luks` (ADR-0005), the standard image layout; the ext4 profile is removed. One layout to maintain. - `docs/deploy.md` rewritten in English: nixos-anywhere for the initial install, deploy-rs for updates of a running device, and a short fleet note. Refs #10, supersedes #14. A fresh BTRFS install on the physical T495s to follow as proof (screenshot or deploy output as a comment). Question: OK to standardise on BTRFS `single-nvme-luks` for all clients and drop the ext4 profile?

bram.buijs added 2 commits

2026-06-18 12:12:10 +00:00

feat: Lenovo T495s reference client + in-place-upgrade disko 9c4fc8ac9e

Add an AMD ThinkPad T495s reference client next to the existing hp-elitebook, plus an ext4-cryptroot disko variant (nvme-luks-ext4) that matches an existing install so a host can switch to this config without a wipe (single-nvme-luks stays the full-wipe path), reusing the lanzaboote keys. docs/deploy.md covers provisioning with nixos-anywhere and updates via deploy-rs.

feat(t495s): use upstream T495 hardware, BTRFS disko, English docs daed6f81a1

Address the #14 review:
- import the upstream nixos-hardware lenovo-thinkpad-t495 profile instead of
  hand-listing common-cpu-amd/gpu-amd/pc-laptop/ssd.
- switch the host to the existing BTRFS single-nvme-luks disko profile and drop
  the ext4 layout (avoids future inode limits, matches the base image).
- rewrite docs/deploy.md and the host comments in English per CONTRIBUTING.

Ref: #10

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

bram.buijs referenced this pull request

2026-06-18 12:23:09 +00:00

feat: add Lenovo T495s reference client + in-place-upgrade disko #14