Open Kreyren opened 8 months ago
and i guess using the table declaration (https://github.com/nix-community/disko/blob/master/example/legacy-table.nix) would be more manageable as it can declare exactly on which sector to have what compared to the current that sets size = "512M"
?
whats the error? the legacy table is deprecated and lacks a lot of features. gpt table can also set start and end instead of size, size is just an alias for end = "+${size}"
whats the error? the legacy table is deprecated and lacks a lot of features. gpt table can also set start and end instead of size, size is just an alias for end = "+${size}" -- @Lassulus (https://github.com/nix-community/disko/issues/490#issuecomment-1873938795)
I didn't try to run it yet, because i felt like i didn't know what i was doing and am unsure how to set it up so that it does encryption in a sane way with disko tbh
gpt table can also set start and end instead of size, size is just an alias for end = "+${size}"
Can that be declared in sectors? expected is sector size of 1 * 512 = 512 bytes
I feel like i get more control over the partitioning by using sectors, but unsure
yeah the start, stop and size parameters of gpt also support sectors. just specify them without a suffix. Weil if you want to specify the password interactively just don't specify a keyFile/passwordFIle and you should be asked interactively. Best way to figure out problems is to try it out
I figured out this configuration, but i feel like i don't know what am I doing..
See the
###!
for intent, i am not sure how to declare the encryption as the projected usecase is to boot into a recovery that automatically applies the nixos configuration on the disk and reboots for like this "absolute" purity where the whole system gets wiped and OS re-installed.