Bug#929891: Error message about udev rules not found
Hi, On 02/06/2019 20:39, Dark Penguin wrote: > 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. > --- Thanks for the report. This will be fixed in the next release. For the record: The issue comes from the '-a' (AND) operator of the command 'test', that is not very strict: in 'test condition1 -a condition2', condition2 is evaluated even if condition1 is false. Using 'test condition1 && test condition2' (with &&, the AND operator of the shell, more strict) will solve this. quidame signature.asc Description: OpenPGP digital signature
Bug#929891: Error message about udev rules not found
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
