| 28 Jun 2024 |
 magic_rb | i wanted to ask: on systems with a MBR parttable i keep getting the warning about it being deprecated and from what i read on the github page of disko, the path forward is to switch to GPT, but i have at least one system where that is impossible and multiple where switching it right now would be very very impractical. Is MBR supported some other way or are you just deprecating support for it completely? | 06:26:53 |
 lassulus | Mostly dropping completly. There are hybrid tables in GPT. And I haven't seen a usecase where they don't work | 07:05:41 |
| magic_rb | In reply to @lassulus:lassul.us
Mostly dropping completly. There are hybrid tables in GPT. And I haven't seen a usecase where they don't work On my ereader the gpt parttable collides with where uboot needs to be, can it be moved somehow? Uboot needs to be at 1k offset from the start of the sd and takes up 3MB roughly | 07:13:11 |
| lassulus | hmm, maybe, but I don't think disko has support for that right now | 07:26:28 |
 Mic92 | lassulus: I just live-migrated a system with incremental disko format and it worked! | 09:24:29 |
| Mic92 | In reply to @magic_rb:matrix.redalder.org
i wanted to ask: on systems with a MBR parttable i keep getting the warning about it being deprecated and from what i read on the github page of disko, the path forward is to switch to GPT, but i have at least one system where that is impossible and multiple where switching it right now would be very very impractical. Is MBR supported some other way or are you just deprecating support for it completely? I would say it's a bit about expectation management, we won't implement new features for these old stuff and we added the warning to get most people to migrate. But realistically there are enough systems with it still out there that we won't remove it any time soon. | 09:27:02 |
| lassulus | brave | 09:28:57 |
