On 09/08/2024 at 17:05, Philip Hands wrote:
While we're changing things, could we distinguish between LVM recipes
and non-LVM ones?
What would be the differences between LVM and non-LVM recipes ?
I do not see how to do this only in recipes, except by adding a dummy
partition with $lvmignore{ } or $defaultignore{ } and a minimum size
bigger than any storage capacity so that the recipe is rejected, which
is clearly a hack. A cleaner way would be that partman-auto and
partman-auto-lvm look for built-in recipes in different locations.
I tend to install servers with something like the multi recipe, except
instead of devoting the bulk of the disk to /home I instead leave it
unallocated (which I do by allocating a spare volume, with keep set to
avoid wasting time formatting it, and I then remove in the late script).
That then gives the flexibility of easily adding volumes or extending
them, as needed by the system.
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.
The other thing I tend to when using multiple partitions is allocate
1.5GB to /boot so that there's enough room for a grml image for use in
conjunction with the grml-rescueboot package.
Isn't this a niche use case ? My understanding was that guided
partitioning was primarily intended for general purpose use cases.
Would it be worth making the upper limit for /boot be 1.5G, and using a
scaling factor (if possible) that will only use that much for disks
larger than 1TB, say, as then its a small enough proportion to be no
loss even if people don't use it for grml.
It is at least possible. The PRIORITY value in recipes represents a
"scaling factor", in a rather convoluted way.
