feat: add Lenovo T495s reference client + in-place-upgrade disko #14
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Discussion
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Help Wanted
Status
Need More Info
Prio - Hoog
Prio - Laag
Prio - Middel
styling
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MinBZK/DAWO-NixOS!14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "bram.buijs/DAWO-NixOS:pr-t495s"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds, as discussed in #10:
modules/hardware/lenovo-t495s.nix, AMD ThinkPad T495s hardware module(initrd modules from an on-device
nixos-generate-config; replace withnixos-facteronce it boots)modules/hosts/profiles/disko/nvme-luks-ext4.nix, ext4-cryptroot layout thatmatches an existing install, for in-place migration without a wipe
(
single-nvme-luksstays the full-wipe path)modules/hosts/clients/dawo-t495s.nix, the host, wired throughprofiles-dawo-generic, with a commented opt-in block for the hardeningmodules; lanzaboote secure boot reusing the existing
/var/lib/sbctlkeys sothe signed chain and TPM2 unlock keep working
docs/deploy.md, provisioning with nixos-anywhere and updates via deploy-rsNote: this drops the
.forgejoCI workflow that was in my branch, it'smirror-specific, not for upstream.
Evaluates green.
Build/deploy proof to follow: verifying on a Lenovo T495s before merge.
Deploy.md looks good, but let's keep it English as per the CONTRIBUTING.md.
The T495 from Lenovo already has a upstream config here. Could you include it?
Is there a specific reason you're implementing ext4 while we already have a disko profile with BTRFS and will prevent any inode issues in the future?
Superseded by #20, which reworks this onto upstream nixos-hardware for the T495 and a BTRFS single-nvme-luks disko layout, with English deploy docs. Closing this one in favour of #20.
Pull request closed