Unnamed repository
e0e6dde32f
In the commit 63205a4dc4c400f75571869d87682c0cdb475830, there was introduced a change in the decision logic of the 20-zipl-kernel.install script. Specifically, whether the Boot Loader Specification (BLS) is used. Instead of just checking the existence of the /sbin/new-kernel-pkg file, the existence of the /boot/loader/entries directory is also checked. More thorough testing revealed that the above commit covers only the case when a new kernel is added. However, the remaining cases should also be covered. That means the case when a rescue kernel is added and the case when some kernel is removed. Resolves: #1778243 Fixes: #1755899 Signed-off-by: Jan Hlavac <jhlavac@redhat.com> |
||
|---|---|---|
| .gitignore | ||
| 20-zipl-kernel.install | ||
| 52-zipl-rescue.install | ||
| 91-zipl.install | ||
| ccw_init | ||
| ccw.udev | ||
| dasd.udev | ||
| dasdconf.sh | ||
| device_cio_free | ||
| device_cio_free.service | ||
| normalize_dasd_arg | ||
| s390-tools-zipl-blscfg-rpm-nvr-sort.patch | ||
| s390-tools-zipl-invert-script-options.patch | ||
| s390utils.spec | ||
| sources | ||
| zfcp.udev | ||
| zfcpconf.sh | ||