mirror of
https://git.launchpad.net/livecd-rootfs
synced 2025-02-12 22:07:10 +00:00
ed1844eda1
kdump-tools uses ucf for config file management and naively modifying the config file meant for the target system directly will cause the file hash to not get updated in the ucf database. This will then cause later modifications to fail because "there's nothing to do". Although actually doing the modification to the ucf database is messy. Let's just modify the file in the live layer to get the behavior we want there.
28 lines
1.2 KiB
Bash
Executable File
28 lines
1.2 KiB
Bash
Executable File
#!/bin/bash -ex
|
|
|
|
# We install kdump-tools in the minimal layer but it's enabled by default.
|
|
# 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.
|
|
|
|
case ${PASS} in
|
|
ubuntu-server-minimal.ubuntu-server.installer.*)
|
|
;;
|
|
*)
|
|
exit 0
|
|
;;
|
|
esac
|
|
|
|
sed -i 's/USE_KDUMP=1/USE_KDUMP=0/' /etc/default/kdump-tools
|