Package: bilibop-lockfs Version: 0.5.6
Steps to reproduce: # apt-get install bilibop --no-install-recommends Now, add a single line to the bottom of /etc/bilibop/bilibop.conf : BILIBOP_LOCKFS_WHITELIST=/anything It does not matter if this directory exists or not. Now do an "update-initramfs -u -k all", and reboot. You won't be able to boot, because all mounts except "/" will fail, giving you an emergency shell. Attempting to mount one of them manually (by "mount /mydir") gives me the following result: /sbin/mount.lockfs: 1: eval: net.ifnames=0: not found This is apparently a part of my kernel command line. Here it is, just in case: # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=64e67ea6-1627-4258-9c70-8bcc120daf86 ro console=tty1 console=ttyS0 ipv6.disable=1 net.ifnames=0 consoleblank=0 lockfs This is reproducible on Debian Buster amd64 and Raspbian Stretch with bilibop 0.5.6 from Debian Buster armhf. Other lines in bilibop.conf work fine, only the "whitelist" one seems to break things. However, whitelisting other mounts or marking them "noauto" in /etc/fstab seems to help, despite the option itself being the source of the problem. %) -- darkpenguin
