Package: partman-auto


Date: Thu, 15 Aug 2024 00:47:22 +0200
From: "Diederik de Haas" <didi.deb...@cknow.org>
To: "Pascal Hambourg" <pas...@plouf.fr.eu.org>, <1076...@bugs.debian.org>, 
"Philip Hands" <p...@hands.com>, "Holger Wansing" <hwans...@mailbox.org>
Cc: José Ángel Pastrana <japp.deb...@gmail.com>, "Vagrant Cascadian" 
<vagr...@debian.org>
Subject: Re: Bug#1076952: [RFD] partman-auto: Update guided partitioning size 
limits for current and future needs


On Fri Aug 9, 2024 at 10:08 PM CEST, Pascal Hambourg wrote:
> Guided partitioning with LVM already provides a feature to reserve space 
> in the VG. Maybe it could be extended to guided partitioning with plain 
> partitions.

I'm not 100% sure if this fits into this subject/discussion, but ...

On ARM devices it would be very useful if the first 16MB would be
(automatically) reserved.
The U-Boot bootloader is normally put in the first part of the boot
device and for Rockchip based devices that can extend to the 16MB
'mark'. AFAIK bootloaders for other SoCs are before that.

If you use the current recipes you end up with an unbootable system as
the U-Boot bootloader get overwritten with the / (root) partition and
the data on it.
There should be a bug for it, but I didn't manage to find it.

Right now, the instruction is to choose manual partitioning and create
a 16MB partition ([1] says 32MB, but it should be 16MB [2]) and then the
normal partitions and after that you could remove that partition again.
And if you type in 16MB, then you need to 'hope' that it is actually
16MB and not something (a bit) smaller.
I like to think that I'm more advanced then most users and I found it
quite difficult to do.

So it would be very helpful if the recipe(s) for ARM devices would
reserve the first 16MB automatically with plain partitioning.

[1] https://wiki.pine64.org/wiki/ROCK64_Software_Releases#Debian
[2] https://opensource.rock-chips.com/wiki_Partitions



-- 
Holger Wansing <hwans...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Reply via email to