NixOS + Framework | 225 Members | |
| Discussing NixOS in the context of the Framework laptop | 50 Servers |
| Sender | Message | Time |
|---|---|---|
| 10 May 2026 | ||
| Albert Larsan and i will have similar output here (except for partitions 3 and 4, which we were told to ignore): two partitions for our system | 16:27:21 | |
| one for our ESP, the other that is a single luks container | 16:27:48 | |
| Yep, except that I have LVM between luks and btrfs | 16:28:13 | |
presumably for $REASONS :) | 16:28:24 | |
| (and a huge ESP) | 16:28:28 | |
| advantage of lvm is to modify the partition size in the future? | 16:29:00 | |
| * (and a huge ESP for Lanzaboote and dual-boot) | 16:29:04 | |
| Albert Larsan: p4 is windows? | 16:30:22 | |
| I don’t really remember, might be qubes or kicksecure. | 16:31:23 | |
| IMO, on a single disk system, there's no reason to put lvm between the luks container and your fs of choice | 16:31:36 | |
| Windows lives on an 250G extension card | 16:31:55 | |
| well, assuming that you're using a single filesystem like btrfs | 16:32:03 | |
| so there is no benefit of using LVM here? | 16:32:38 | |
| not where albert has used it, IMO | 16:32:55 | |
| does the NixOS install CD sets this up? | 16:33:48 | |
| uh, no clue | 16:33:59 | |
| what you're looking at was actually manually partitioned back in the day | 16:35:11 | |
| Having swap also crypted in the same luks container is the main benefit for me (ignoring swap files). | 16:37:10 | |
well, yeah. /swap for me is just a btrfs subvolume and my swap space is a swap file conveniently at /swap/file | 16:37:33 | |
| disko configuration that i wrote recently but haven't used to reformat my in-use disk (because i haven't bothered migrating) is:
| 16:38:46 | |
| Also, moving stuff by adding a pv to lvm and removing the old pv is also nice (although I never used it). (you can also do this using btrfs native multi-disk support) | 16:39:12 | |
this is how i'll be migrating this machine's disk to a new disk, with the above disko configuration. | 16:41:08 | |
| I have another impermanance setup, where I move the root submodule to a subfolder (for crash recovery), and delete the ones that are too old. | 16:42:41 | |
| my impermanence module (referenced in the above config) just sets up the i'd be interested in seeing your crash recovery setup. | 16:47:42 | |
| * my impermanence module (referenced in the above config) just sets up the i'd be interested in seeing your crash recovery setup. | 16:48:11 | |
| * my impermanence module (referenced in the above config) just sets up the i'd be interested in seeing your crash recovery setup. | 16:48:22 | |
| or do you simply mean that instead of deleting the root subvol on boot (like i do currently), you create another snapshot of it | 16:50:58 | |
| I have this version (https://git.sr.ht/~albertlarsan68/dotfiles/tree/main/item/nixos/scripts/root-reset.sh) that snapshots the root before rolling it back (with a failed attempt at preserving nested subvolumes). It runs after hibernation resume and before mounting sysroot. .The modern version (for the new machines) is at https://git.sr.ht/~albertlarsan68/dotfiles/tree/flake-parts/item/nixos-modules/impermanence/rollback.sh and literrally mvs the /root submodule to a dated folder, then deletes old versions. | 16:52:53 | |
| The modern version does properly save nested submodules | 16:53:46 | |
| got it | 16:55:18 | |