mirror of
https://github.com/systemd/systemd.git
synced 2026-06-24 08:47:49 +00:00
33bb855f3a
Currently the partition list is ordered like this: First come the partitions that exist as definition files (could be pre-existing partitions or could be new ones), then come the pre-existing partitions that aren't matched to a definition file. This ordering is visible to the user when we print our partition table, and it doesn't really make sense from a UX perspective: Partition tables are usually either presented in order of the partition indices, or in order of the partition offsets. Arguably the latter would be nicer here, since the visualization below is already ordered by physical offsets. So reorder the list after we assigned the new partitions to their respective free areas, according to the physical offset (or, for partitions to newly create, the order that we will allocate them in). Another potential upside of this is that we could rely on the partition order in the code now more, too. To ensure it keeps working, also add a test in the integration tests for it. Screenshot before: <img width="2853" height="686" alt="Screenshot From 2026-06-05 00-58-07" src="https://github.com/user-attachments/assets/7f24b527-7d79-49c4-916b-52faa892d4eb" /> Screenshot after: <img width="2853" height="686" alt="Screenshot From 2026-06-05 00-58-16" src="https://github.com/user-attachments/assets/4505ec5e-cab4-4ac1-95f0-b5af3991509e" />