ba666011a6
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. |
||
---|---|---|
.. | ||
make-options-doc | ||
test-driver | ||
build-vms.nix | ||
eval-config.nix | ||
from-env.nix | ||
make-channel.nix | ||
make-disk-image.nix | ||
make-ext4-fs.nix | ||
make-iso9660-image.nix | ||
make-iso9660-image.sh | ||
make-squashfs.nix | ||
make-system-tarball.nix | ||
make-system-tarball.sh | ||
qemu-flags.nix | ||
testing-python.nix | ||
utils.nix |