Am 13.02.20 um 13:29 schrieb Trent W. Buck:
> Package: udev
> Version: 241-7~deb10u3
> Severity: wishlist
> File: /sbin/udevadm
> 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.
> With /proc:
>     root@DESKTOP-P00TKMM:/# udevadm trigger
>     Running in chroot, ignoring request.
>     root@DESKTOP-P00TKMM:/# udevadm control --help
>     Running in chroot, ignoring request.
> Without /proc:
>     root@DESKTOP-P00TKMM:/# udevadm trigger
>     Failed to scan devices: No such file or directory

This means, /sys is missing, not proc afaics.

>     root@DESKTOP-P00TKMM:/# udevadm control --reload
>     root@DESKTOP-P00TKMM:/# echo $?
>     1
> Can you please make udevadm do something like this?
>     printf("/proc is missing or empty.\n")
>     printf("Probably running in a chroot, ignoring request.\n")
>     exit(0)
> It sounds like best current practice is for postinsts to ignore ALL
> errors[0], which (I think) is worse, because udevadm can be smarter
> than the postinst about what is a "real" error.

I guess you'd have to convince upstream that this is a good idea to add
such a check.

Once upstream has such a patch, we can cherry-pick it.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to