When booting a Grml system with the toram boot option, this causes the booted system to end up with an incomplete rootfs from grml-terminalserver's perspective. As we noticed today during a troubleshooting session the generated configuration fails hard from several different angles (dummy entries in generated configs, missing syslinux *.c32 files, un-replaced variables like %SQUASHFS_NAME% or so).
We either manage to fix this by handling this in grml-terminalserver's code, or we check for this situation and fail hard to avoid surprises for the user.
When booting a Grml system with the
toramboot option, this causes the booted system to end up with an incomplete rootfs from grml-terminalserver's perspective. As we noticed today during a troubleshooting session the generated configuration fails hard from several different angles (dummy entries in generated configs, missing syslinux*.c32files, un-replaced variables like%SQUASHFS_NAME%or so).We either manage to fix this by handling this in grml-terminalserver's code, or we check for this situation and fail hard to avoid surprises for the user.
/cc @jkirk