Package: bilibop-rules Version: 0.5.6 After installing bilibop, even without enabling lockfs, I see this error message during the boot process:
--- Begin: Running /scripts/local-bottom ... Warning: bilibop-lockfs: Nothing to do. ls: /root/etc/udev/rules.d/70-persistent-cd.rules: No such file or directory ls: /root/etc/udev/rules.d/70-persistent-net.rules: No such file or directory done. --- With lockfs enabled, it is still there: --- Begin: Running /scripts/local-bottom ... Warning: bilibop-lockfs: Locking files. Begin: bilibop-lockfs: Setting up overlay branches ... done. Success: bilibop-lockfs: Root filesystem is now locked (soft policy). Warning: bilibop-lockfs: Modifying temporary static filesystem table (fstab). ls: /root/etc/udev/rules.d/70-persistent-cd.rules: No such file or directory ls: /root/etc/udev/rules.d/70-persistent-net.rules: No such file or directory done. --- This is reproducible on Debian Buster amd64, and I saw it on Raspbian Stretch with bilibop 0.5.6 from Debian Buster armhf. I don't see any negative consequence of this, other than making the user scared a little, but it is still an error message meant to be noticed. Maybe it will help find other bugs. :) -- darkpenguin
