| 9 Mar 2024 |
 void | how did disko handled start/end before? it seems I need to enter exact start/ends to get continuity. | 10:35:50 |
| void | for instance, does end="16G-1" work with sgdisk? | 10:36:08 |
| void | dont want to find out what 2^4*2^20-1 is. | 10:36:44 |
| void | previously I can have my way by just end="16G" and it would work, hm. | 10:37:27 |
 @palo:xaos.space | Is use priority and size now. works fine for me. | 10:38:26 |
| @palo:xaos.space | I also liked the partition array better, but the partition labels havn't been uniq back than, now they are. But I don't know what the intention was. What I'm missing is a Options overview, like man configuration.nix. At the moment I look in the source code. | 10:41:15 |
| void | yeah but the exact start/end values are always important for recovery in case something goes bad. | 10:45:29 |
| void | no disko dev recovers data from bad disks I guess these days. | 10:45:53 |
| void | I think this is sgdisk's --new param ambiguity including the end sector. | 11:02:31 |
| void | what a bummer. | 11:02:35 |
| void | --align-end
When possible, align the end points of partitions to one less than a multiple of the alignment value. When both start and end points are aligned, partitions should be multiples of the alignment value in size, which is necessary for some partition encryption tools to function correctly. This option applies to all partitions created after this option on the command line. Note that this alignment is not always possible; for instance, if the free space at the end of a disk is less than the alignment value, with the current final partition being aligned, and if sgdisk is asked to create a partition in that space, then it will not be end-aligned.
| 11:33:53 |
| void | ok start & size is better I guess with --align-end. | 11:34:10 |
| void | not sure how it worked before though. | 11:34:28 |
 lassulus | yeah, generation an options manpage for disko is still a complicated topic, since everything is kinda recursive it's hard to use the old doc genrators for that. Also the old list based approach was kind of lacking in the referencing and updating part, like if you add a partition in between everything has to shift a bit.
and yes, size is the new recommended way, start is usually 0, which means the next available space in sgdisk, which should be reproducible if you run the same script multiple times. so partitions usually only need size. you can use priority if you want certain partitions to be in front of others, but so far this didn;t made any difference in any bootloader. porting table partitions to gpt partitions is sadly not a straight forward thing, since the latter alwas have a label and before it was optional. | 11:39:35 |
| lassulus | * yeah, generation of options manpages for disko is still a complicated topic, since everything is kinda recursive it's hard to use the old doc genrators for that. Also the old list based approach was kind of lacking in the referencing and updating part, like if you add a partition in between everything has to shift a bit.
and yes, size is the new recommended way, start is usually 0, which means the next available space in sgdisk, which should be reproducible if you run the same script multiple times. so partitions usually only need size. you can use priority if you want certain partitions to be in front of others, but so far this didn;t made any difference in any bootloader. porting table partitions to gpt partitions is sadly not a straight forward thing, since the latter alwas have a label and before it was optional. | 11:39:54 |
| lassulus | this all ties in, into making the create part of every type idempotent, so running the createScript multiple times should just add stuff where it can and we should be able to run this on every nixos-rebuild switch | 11:41:26 |
| lassulus | opt-in in the beginning ofc | 11:41:49 |
| lassulus | but not every feature from the old table type got ported to the new gpt type, like msdos tables. but I have no usecase for them, if someone needs them (and is not happy with the weird gpt-hybrid thingie) please message me and we can implement a new type in tandem (meaning you do it and I tell you how :)) | 11:49:57 |
| void | how do I set bootable = true; now? | 11:52:47 |
| void | or better, is there a migration guide ;P | 11:52:59 |
| lassulus | bootable = true didn't have any effect on gpt partitions before actually | 11:55:24 |
| lassulus | ah migration guide would be very cool, but sadly I haven't written one yet | 11:55:54 |
| lassulus | maybe we should start a pad and just get it done? but the knowledge is very scattered in my memory | 11:57:19 |
| void | I usually use a wiki when it happens, write everything I know atm, then restructure & fill the gaps. | 12:00:31 |
| lassulus | like my ideal idea was to generate a migration script, but I never finished it and then I realized that everybody was still using the legacy tables and so I wrote the deprecation notice first | 12:02:58 |
| void | is there a checkpoint/milestone in time where you tell users to say hey you can migrate now? | 12:08:09 |
| void | Im hesistating atm. | 12:08:22 |
| lassulus | Well you should have migrated sooner :D | 12:11:22 |
| lassulus | But it's not fully automatic yet. So the migration pain is yours until I build the migration script | 12:12:11 |
| lassulus | But not sure it will ever be done | 12:12:21 |
