aboutsummaryrefslogtreecommitdiff
path: root/ubi-utils/tests/README.udev
diff options
context:
space:
mode:
Diffstat (limited to 'ubi-utils/tests/README.udev')
-rw-r--r--ubi-utils/tests/README.udev10
1 files changed, 8 insertions, 2 deletions
diff --git a/ubi-utils/tests/README.udev b/ubi-utils/tests/README.udev
index 6c12277..06e71d3 100644
--- a/ubi-utils/tests/README.udev
+++ b/ubi-utils/tests/README.udev
@@ -15,5 +15,11 @@ In our Ubuntu distribution we put that to new file:
/etc/udev/rules.d/50-local.rules
Another possibility is to call udevsettle utility in libubi after the volume
-has been created See src/libubi.c - the call is there but is commented out.
-This is anyway an ugly hack, but works, although makes the tests slower.
+has been created See src/libubi.c - the call is compiled in only if
+UDEV_SETTLE_HACK is defined. This is anyway an ugly hack, but works, although
+makes the tests slower. Suggestions are welcome.
+
+So, if you have udevsettel unility in your system, you do not have to do
+anyting, and the tests should work, because we compile libubi with
+UDEV_SETTLE_HACK. Otherwise, you should remove -D UDEV_SETTLE_HACK
+from the makefile and pre-create UBI device nodes.