summaryrefslogtreecommitdiff
path: root/tests/test-admin-deploy-none.sh
Commit message (Collapse)AuthorAgeFilesLines
* Update FSF license notices to use URL instead of addressJoseph Marrero2021-12-071-3/+1
|
* *: rename master to main in tests & examplesTimothée Ravier2021-05-071-2/+2
|
* lib/deploy: Also install HMAC file into /bootJonathan Lebon2019-10-291-0/+1
| | | | | | | | | | | | To allow for FIPS mode, we need to also install the HMAC file from `/usr/lib/modules` to `/boot` alongside the kernel image where the `fips` dracut module will find it. For details, see: https://github.com/coreos/fedora-coreos-tracker/issues/302 Note I didn't include the file in the boot checksum since it's itself a checksum of the kernel, so we don't really gain much here other than potentially causing an unnecessary bootcsum bump.
* tests/test-admin-deploy-none: Split grub.cfg directory and file creationRobert Fairley2019-04-241-1/+2
| | | | | | | | | Split the creation of the directory containing grub.cfg, and the creation of the file, so that a failure in the mkdir command will fail the test and not attempt the touch command. Closes: #1831 Approved by: jlebon
* tests/test-admin-deploy-none: Update comment for #1774 statusRobert Fairley2019-04-241-2/+2
| | | | | Closes: #1831 Approved by: jlebon
* Add sysroot.bootloader repo config keyRobert Fairley2019-03-011-0/+52
The sysroot.bootloader key configures the bootloader that OSTree uses when deploying a sysroot. Having this key allows specifying behavior not to use the default bootloader backend code, which is preferable when creating a first deployment from the sysroot (#1774). As of now, the key can take the values "auto" or "none". If the key is not given, the value defaults to "auto". "auto" causes _ostree_sysroot_query_bootloader() to be used when writing a new deployment, which is the original behavior that dynamically detects which bootloader to use. "none" avoids querying the bootloader dynamically. The BLS config fragments are still written to sysroot/boot/loader/entries for use by higher-level software. More values can be supported in future to specify a single bootloader, different behavior for the bootloader code, or a list of bootloaders to try. Resolves: #1774 Closes: #1814 Approved by: jlebon