Hi, Am 9. August 2024 22:08:09 MESZ schrieb Pascal Hambourg <pas...@plouf.fr.eu.org>: >On 09/08/2024 at 17:05, Philip Hands wrote: > >> 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.
@phil: is there a reason, why you do not use this built-in feature, but instead invent the wheel again? Maybe you were just not aware of this? >> 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. +1 for considering this being a corner case, which does not need to be supported by the default recipes. >> 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. Holger -- Sent from /e/ OS on Fairphone3
