From: Bill Pittman <bill.pitt...@ni.com> /dev/mdev.seq exists to synchronize concurrently running instances of mdev and to ensure that they execute in the proper order. Without this synchronization, it is possible to have inconsistent mount points, to leak device nodes, or to have a node erroneously removed in rapid hotplug scenarios.
Enable the use of mdev.seq by creating an empty /dev/mdev.seq at boot. Signed-off-by: Richard Tollerton <rich.toller...@ni.com> Signed-off-by: Ben Shelton <ben.shel...@ni.com> --- meta/recipes-core/busybox/files/mdev | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-core/busybox/files/mdev b/meta/recipes-core/busybox/files/mdev index f7ed1f3..c4447ef 100755 --- a/meta/recipes-core/busybox/files/mdev +++ b/meta/recipes-core/busybox/files/mdev @@ -4,5 +4,6 @@ mount -t tmpfs tmpfs /dev -o size=64k,mode=0755 mkdir /dev/pts /dev/shm chmod 777 /dev/shm mount -t devpts devpts /dev/pts +touch /dev/mdev.seq echo "/sbin/mdev" > /proc/sys/kernel/hotplug mdev -s -- 2.0.2 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
