Am 13.02.20 um 14:03 schrieb Trent W. Buck: > Michael Biebl wrote: >> Am 13.02.20 um 13:29 schrieb Trent W. Buck: >>> Packages like udisks2 run "udevadm trigger" in their postinsts. >>> When building a Debian Live image, if /proc is mounted in the chroot, all >>> is well. >>> When building a Debian Live image, if /proc is NOT mounted in the chroot, >>> udevadm gives annoying errors, and the whole build crashes. >>> >>> Without /proc: >>> >>> root@DESKTOP-P00TKMM:/# udevadm trigger >>> Failed to scan devices: No such file or directory >> >> This means, /sys is missing, not proc afaics. > > Thanks for the prompt reply. > > My tests show /proc alone is enough to enable the existing "do nothing" code. > Giving a longer excerpt from from boring-full-transcript.txt.xz: > > 78root@DESKTOP-P00TKMM:/# udevadm trigger > Failed to scan devices: No such file or directory
You should only get this error message if /sys is not mounted. I assume your chroot has neither /sys nor /proc mounted. systemd-udevd.service has ConditionPathIsReadWrite=/sys You could try to convince upstream to add a similar check to "udevadm trigger"
signature.asc
Description: OpenPGP digital signature
