Results 74 comments of Ben Alex

I've found the same issue occurs with a colon (`:`) in a filename. It is also being substituted with a period (`.`), making GitHub Releases unsuitable for hosting Arch Linux...

Thanks @MariusVolkhart. Just one request, can you please add a reference to the use of the `thirdparty` directory to the "License" section of `README.md`?

Your reply prompted me to remember that I'm using a standard `booster.yaml` across all servers which includes: ```yaml network: dhcp: on ``` Commenting out the `network`, then `/usr/lib/booster/regenerate_images` and `reboot`...

I adapted your `PKGBUILD` to use `source=(git+https://github.com/anatol/booster#branch=issue-155)` which resulted in `booster-git-0.8.r1.gd30b272-1-x86_64.pkg.tar.zst`. It did not resolve the issue. Disabling the `network` continued to work around the issue.

@anatol can I suggest updating the `issue-155` branch with [recent commits](https://github.com/anatol/booster/compare/issue-155...master) and then I give it another try? I am concerned about the apparent regression of the network not starting...

Using the latest `issue-155` branch with the `booster.yaml` shown earlier, the server which does not use Clevis booted with the following debug log: ``` [ 0.000000] Command line: initrd=\intel-ucode.img initrd=\booster-linux.img...

Hi @anatol. Sorry for the delay; it has been a very busy week! I built `booster-git-0.8.r7.g4d4fba1-1-x86_64.pkg.tar.zst` with a DHCP enabled `booster.yaml` and the following represents the final screen shot before...

Arch Linux's latest `booster` is 0.8-1 and this was the release that prompted the issue. Did you want me to try `booster-git` against `master` (given we have an `issue-155` branch)?

I built `booster-git-0.8.r15.g546af2d-1-x86_64.pkg.tar.zst` with the same `booster.yaml` as earlier. I found rebooting results in different network messages on each occasion, although none complete the boot by unlocking via Clevis. Here...

I built `booster-git-0.8.r17.g2cd47d3-1-x86_64.pkg.tar.zst` (noting the prior DHCP library was fetched) and still see different results on each boot. Here are final screen shots from two boots: ![image](https://user-images.githubusercontent.com/718596/180355436-3cfe703c-8921-4dd6-b914-ca17fc0c638f.png) ![image](https://user-images.githubusercontent.com/718596/180355461-ef202dca-e1db-42a0-ada8-39a31f3ec041.png) Note the...