FTR, I would strongly advise against that, see https://github.com/martinpitt/umockdev/issues/110#issuecomment-736224503 . You want the tests to work independently on the hardware it's running on, so that you can run it on e.g. standard autopkgtest infra.
You could create /sys/firmware/efi/efivars/ tarballs of a bunch of real systems with the properties that you want, keep them in the tests, and unpack these in your test cases. You most probably just need a few of them, so you can strip them down or possibly create them individually as files, but a full tarball might be the quickest start. ** Bug watch added: github.com/martinpitt/umockdev/issues #110 https://github.com/martinpitt/umockdev/issues/110 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906320 Title: fake-device-wrapper should bind-mount efivars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1906320/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
