Zum Inhalt der Seite gehen


At this point it's really a disgrace how #nixos never manages to generate correct hardware configurations if you do even the most basic configurations following the wiki.

I really think stuff like disk encryption must not be a hassle for instance. And nixOS effectively not properly supporting it really annoys me.
Dieser Beitrag wurde bearbeitet. (4 Wochen her)
disk encryption works for me with both luks and zfs encryption.
it works, but it's not recognised by the generate-hardware script even tho that should imho just work given my understanding of the purpose of said script.
it should really find and add the current open luks device. That shouldn't be to hard to implement if I am honest.
well, it seems to be harder than I thought. We can enumerate the files under /dev/mapper/ and skip control but from there I have no idea how to get to the disk itself. You could run cryptsetup status <name> but that doesn't honor the disk/by-uuid it was mounted from but just uses the resolved symlink.
can you get the uuid knowing the symlink?
The /dev/mapper/ symlink points to /dev/dm-0. Somehow cryptsetup knows from where the device is mounted and then you would need to find the dev/by-uuid for that device. All a bit hacky....
I'd probably maybe take a look at what lsblk is doing to figure that out ...