summaryrefslogtreecommitdiffstats
path: root/templates/boot/generic-grub-tftp.jinja2
diff options
context:
space:
mode:
authorJan-Simon Moeller <jsmoeller@linuxfoundation.org>2023-01-19 23:50:09 +0100
committerJan-Simon Moeller <jsmoeller@linuxfoundation.org>2023-01-20 02:18:53 +0100
commit7ea2e8f50109841416cfb4a3e95f49ca781b623d (patch)
tree30e185983851cb92a8a9b4d7e84c87ad8ef177ba /templates/boot/generic-grub-tftp.jinja2
parent5dd81edf53ff9c2d636a8cef46784cfc2a2fdde8 (diff)
Change the mask to the systemd-network-generator.service
It is not systemd-networkd that does bite use here, it is the systemd-network-generator.service that will interfere with our settings. This is triggered by the ip=dhcp setting on the kernel cmdline and even the removed wired.network file will not prevent his from interfering and taking the network interface down and up for another dhcp run. Question is ... WHY ?!: The interface IS already configured. Connmand can be configured to ignore it and does actually ignore or at least not take it down. Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org> Change-Id: I2872ddfbc97e26ae84fcc3640a9129c28691557c
Diffstat (limited to 'templates/boot/generic-grub-tftp.jinja2')
-rw-r--r--templates/boot/generic-grub-tftp.jinja22
1 files changed, 1 insertions, 1 deletions
diff --git a/templates/boot/generic-grub-tftp.jinja2 b/templates/boot/generic-grub-tftp.jinja2
index 7c02040..192abd0 100644
--- a/templates/boot/generic-grub-tftp.jinja2
+++ b/templates/boot/generic-grub-tftp.jinja2
@@ -9,7 +9,7 @@ protocols:
# context allows specific values to be overridden or included
context:
- extra_kernel_args: initrd={{ initrd }} systemd.mask=systemd-networkd.service
+ extra_kernel_args: initrd={{ initrd }} systemd.mask=systemd-network-generator.service
{%- endif %}
{% endblock %}
{%- block boot %}