[ Mike Gabriel, 2022-02-24 ] > The underlying causes of this is that we append "-- ipappend 2" to the > kernel cmdline when doing the PXE boot into the Debian Installer. This > kernel boot cmdline is generated by /usr/sbin/debian-edu-pxeinstall (and was > necessary in older times). Right. 'ipappend' is used by PXELINUX, but for 'bullseye' we switched to iPXE to be compliant with the re-written LTSP. > What happens with this "-- ipappend 2" bit of the kernel cmdline is that it > gets added (during the installation process) to the GRUB_CMDLINE_LINUX > variable in /etc/default/grub: > > GRUB_CMDLINE_LINUX="ipappend 2" PXELINUX evaluates 'ipappend 2' and adds BOOTIF=<hardware-address-of-boot-interface> to the kernel command line, allowing the initrd program to determine from which interface the system booted. Obviously, iPXE doesn't understand 'ipappend'. I'm just wondering if there are other side-effects. > So, the booting systems finds a "2" in the kernel boot cmdline after the > system has been installed via PXE and this "2" is interpreted as runlevel 2 > by systemd (PID 1). While PXE installations have always been tested during development (and also at release and point release days), the 'Minimal' profile has been chosen for this test case to save time. As there's no GUI, this bug got away undetected. It might be a good idea to choose 'Workstation' for future tests. Wolfgang
Attachment:
signature.asc
Description: PGP signature