Unnamed repository
5229fe4f01
The kernel-install script created unconditionally a $BOOT_DIR_ABS directory that was used by the sd-boot bootloader. The kernel-install plugins checked the existence of that directory to decide whether the BLS snippets would be created in the path expected by sd-boot or the one expected by zipl. But the $BOOT_DIR_ABS contains the machine ID that's set in the environment variable $KERNEL_INSTALL_MACHINE_ID. If there's no machine ID set, then the $BOOT_DIR_ABS is set to a temporary directory that's removed after all the kernel-install plugins exit. The $KERNEL_INSTALL_MACHINE_ID isn't set for example when kernel-install is executed in a container since there won't be an /etc/machine-id file. This causes 20-zipl-kernel.install script to wrongly remove the /tmp directory. So if $KERNEL_INSTALL_MACHINE_ID isn't set, just exit the script since the BLS snippets can't be installed anyways since their filename also contain the machine ID. Also, don't attempt to remove $BOOT_DIR_ABS because kernel-install doesn't create this directory anymore and instead is created only when sd-boot is installed. |
||
---|---|---|
.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 |