On 05/11/2026 at 12:51, Alper Nebi Yasak wrote:
On 2026-11-05 10:28 +03:00, Pascal Hambourg wrote:
On 04/11/2026 at 19:26, Alper Nebi Yasak wrote:
I think I had a libdebian-installer MR that would add amd64/cros
and arm64/cros to archdetect, which partman-auto would want?
For reference:
<https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/6>
I guess yes, it would allow to ship recipes for this subarch. But it may
affect other d-i packages which use archdetect. What is the current
reported subarchitecture on ChromeOS platforms ?
They are not EFI, so it defaults to "amd64/generic" or "arm64/generic" IIRC.
Kibi expresses concern about grub-installer in a MR comment. Currently
it is disabled on arm*/non-efi and x86/mac, and tries to install grub-pc
on x86/non-efi. The "generic" subarchitecture is not explicitly used, so
a new ChromeOS subarchitecture would not be handled differently. IIUC
grub-installer should be disabled on x86/cros. This is trivial to do.
The MR adds recipes for armhf, are there any ChromeOS machines with this
architecture ?
Yes, but we can't boot d-i through this boot method on those due to size
limits (8/16/32 MiB depending on board) on the bootable image size.
We can sometimes chainload e.g. U-Boot from these partitions but I don't
know how to detect the board as running ChromeOS bootloader in those cases,
so not a concern for now.
IIUC your MR adds the ChromeOS subarchitecture for armhf too. So how
should it be dealt with ?
[3] https://salsa.debian.org/installer-team/partman-cros/-/merge_requests/2
Never clearing the flag seems a bit extreme. What about using the same
logic as in partman-efi to preserve unused existing ESPs instead ?
I'm not sure the analysis is correct there, I have to test things again.
I remember installing to a USB disk without messing up ChromeOS on the
eMMC. Maybe they chose "Do not use" on existing partitions expecting it
to be like the ESP case? IIRC I thought it makes no sense to mark a CrOS
partition as "Do not use" except to indicate it should stop being one.
OK, but partman-auto marks all partitions "do not use" before starting
automatic partitioning.
Ah. In that case switching to the ESP logic makes sense.
I suspect that this change was submitted in reaction to partman-auto
behaviour. In that case simpler options may be considered:
- In partman-auto, do no mark ChromeOS partitions "do not use".
- In partman-cros/update.d, restore method=cros if method is empty and
method-old (saved by partman-auto) = cros.