diff options
| author | Samuel Dionne-Riel <samuel@dionne-riel.com> | 2021-04-23 23:20:49 -0400 |
|---|---|---|
| committer | Samuel Dionne-Riel <samuel@dionne-riel.com> | 2021-04-24 14:49:05 -0400 |
| commit | ba666011a64aee55c78c9cb4b0e7c272479d9a2e (patch) | |
| tree | dc3a71596ed68cf7ba25e78043a55bdeac52d5e3 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 9b18a78c739a2a43c3ed386a4a9c52e4f7360650 (diff) | |
make-disk-image: Account for reserved disk space
This is a bit of a thorny issue. See, the actual `diskSize` variable is
for the *total* disk size, not for the filesystem!
The automatic numbers are meant to compute the *filesystem* required
space. So we have to add any other reserved space!
We have different requirements for reserved space. E.g. there could be
none (when it's actually a filesystem image). There could also be 1MiB
for alignment for an MBR image, legacy+gpt needs 2MiB, then GPT with an
ESP ("bootSize") needs to take the boot partition and GPT size into
account too!
Though luckily(?) for this latter situation we can cheat! As noted in the
change, `bootSize` is NOT the boot partition size. It is actually the
offset where the target filesystem starts.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions