Skip to content

kuma v0.19.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Aug 01:33
v0.19.0
7014327

Added

  • kuma install can name the sizes it used to decide for you. --esp 1G and --boot 4G set how big the EFI system partition and /boot are, and the interview asks for both with the defaults shown, so a person who does not care presses enter twice. The shape does not move: still three partitions, the root still takes what is left, and encryption still changes what the root holds rather than the disk. A size below what its partition is for is refused with the reason rather than a number (256M for the ESP, 1G for /boot), and the swapfile questions are measured against what the named sizes left over, so a disk that fits the defaults can be too small for what was asked, and the refusal says so with the arithmetic. The dry run prints the resolved sizes in its layout, the JSON surface carries them the same way, and the command it hands over keeps the flags it was given. Naming nothing changes nothing: the defaults are the sizes every kuma machine has been installed with so far.

Static x86_64 binary, no runtime dependencies.

$ curl -LO https://github.com/Letdown2491/kuma-linux/releases/download/v0.19.0/kuma-x86_64-unknown-linux-musl
$ chmod +x kuma-x86_64-unknown-linux-musl && sudo mv kuma-x86_64-unknown-linux-musl /usr/local/bin/kuma

Verify it came from this workflow:

$ cosign verify-blob \
    --bundle kuma-x86_64-unknown-linux-musl.bundle \
    --certificate-identity-regexp '^https://github.com/Letdown2491/kuma-linux/' \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    kuma-x86_64-unknown-linux-musl

Built from 701432742e9a92c47338aeb353215be1f1b11fa7.

Assets 8
Loading