| 12 Jun 2024 |
 maralorn | * Now it says "disk-nixos-zeus-system-vault (crypted-root-fs)" much more informative. | 20:13:12 |
| 15 Jun 2024 |
|  linj joined the room. | 13:51:37 |
| 16 Jun 2024 |
| maralorn | How relevant is it to explicitly set a priority field? | 22:02:49 |
| maralorn | * How relevant is it to explicitly set a priority field in the gpt type? | 22:15:22 |
| 17 Jun 2024 |
 hexa | I think it affects the ordering? | 00:00:43 |
| hexa | https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md | 00:01:38 |
| maralorn | Yeah, the question is whether the ordering matters. I assume that since disko mounts by label the order is completely irrelevant for mounting and only needed for partitioning. So theoretically it doesn’t even have to be deterministic. | 09:01:10 |
| maralorn | I mean if it is important to me that swap definitely is after efi I can annotate it, but if I don’t care I can just use whatever disko comes up with, don’t I? | 09:02:19 |
 lassulus | yes | 09:30:24 |
| lassulus | it sometimes matters for the ef02 partition if you do legacy booting on gpt | 09:30:39 |
| lassulus | but on my machines even that didn't matter | 09:30:49 |
| maralorn | How does disko disambiguate if two partitions have the same priority? I assume it’s then basically depending on the order Nix does attrsToList? | 22:18:16 |
| lassulus | Probably alphabetical | 22:45:12 |
| 21 Jun 2024 |
|  TheDragon joined the room. | 12:57:42 |
|  @linus:schreibt.jetzt left the room. | 14:06:32 |
| 22 Jun 2024 |
|  nyanbinary 🏳️⚧️ joined the room. | 01:25:42 |
| maralorn | lassulus: What made you decide to use partlabels for partition discovery? Isn’t that a bit dangerous because of possible naming collisions? | 07:48:16 |
| lassulus | fs labels are dependant on the filesystem. partition numbering is different for each backend and less flexible when updating the table | 07:49:26 |
| lassulus | but yeah, there is risk of conflicts if you apply the same config to different disks | 07:50:19 |
| lassulus | but with partlabels, the device can also be specified by an environment variable. this was not possible with the old numbering | 07:50:54 |
| maralorn | So, you are saying there is a risk, but there is no better option? | 07:55:09 |
| lassulus | yes :D | 07:57:57 |
| lassulus | maybe we can add the device to the default partlabel | 07:58:26 |
| maralorn | Well, I guess it’s fine to declare this the users responsibility. | 08:17:31 |
| maralorn | Although maybe disko could at least detect if multiple partitions on the same system are named the same. | 08:18:17 |
| maralorn | Of course that doesn’t protect against collissions with random disks on the system which have no mount instructions. | 08:19:00 |
| maralorn | e.g. an old disk with previous system after a migration. | 08:19:24 |
| maralorn | * e.g. an old disk with the previous system after a migration to a new disk. | 08:19:47 |
| maralorn | Hm, that actually doesn’t sound super far-fetched. 😄 | 08:20:09 |
|  Anna Aurora joined the room. | 12:59:54 |
