2024-09-11 11:21:27 -07:00
|
|
|
#!/bin/bash -ex
|
|
|
|
|
|
|
|
# We install kdump-tools in the minimal layer but it's enabled by default.
|
2024-09-17 11:25:13 -07:00
|
|
|
# subiquity/curtin will later decide to either keep it enabled or disable it
|
|
|
|
# in the target system, but let's ensure it's disabled in the live layer.
|
|
|
|
# We do this by manually modifying /etc/default/kdump-tools to use USE_KDUMP=0.
|
|
|
|
# Without this, kdump-tools is still technically disabled since it requires both:
|
|
|
|
# 1. crashkernel on the kernel command line
|
|
|
|
# 2. USE_KDUMP=1 in /etc/default/kdump-tools
|
|
|
|
# and the kernel command line in the live layer doesn't have the crashkernel
|
|
|
|
# parameter in the kernel command line, but this semi-disabled state isn't
|
|
|
|
# ideal. So let's be doubly sure and set USE_KDUMP=0.
|
|
|
|
#
|
|
|
|
# Note that kdump-tools relies on ucf for configuration file management. So
|
|
|
|
# while we could modify the value in the minimal layer, doing so in a way that
|
|
|
|
# doesn't make future dpkg-reconfigures hard is a huge hassle. You also have
|
|
|
|
# to make sure to do the same steps to every layer it may get included.
|
2024-09-11 11:21:27 -07:00
|
|
|
|
|
|
|
case ${PASS} in
|
2024-09-17 11:25:13 -07:00
|
|
|
ubuntu-server-minimal.ubuntu-server.installer.*)
|
2024-09-11 11:21:27 -07:00
|
|
|
;;
|
|
|
|
*)
|
|
|
|
exit 0
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
|
|
|
|
sed -i 's/USE_KDUMP=1/USE_KDUMP=0/' /etc/default/kdump-tools
|