Bug 6631

Summary: Several /dev/* (mostly mem system) devices have too minimal permissions
Product: [Build System, Metadata & Runtime] BSPs Reporter: yocto
Component: bsps-runtimeAssignee: Alejandro Hernandez <alejandro.hernandez>
Status: RESOLVED OBSOLETE QA Contact:
Severity: normal    
Priority: Medium CC: boon.leong.ong, sgw, yp.kernel.watcher, yp.watcher
Version: 1.4.5   
Target Milestone: 1.7   
Hardware: Other   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description yocto 2014-08-14 16:07:47 UTC
ENVIRONMENT

Galileo hardware
clanton-full bitbaker image

REPRODUCE

$ ls -ld /dev/zero # or random, urandom, full, null
crw-rw---- 1 root root 1, 5 Aug 14 18:05 /dev/zero

SOLUTION

--- etc.orig/mdev.conf
+++ etc/mdev.conf
@@ -1,3 +1,9 @@
 (sd[a-z])([0-9]+) 0:0 0660 *(/usr/bin/automount.sh)
 mmcblk([0-9]+)([a-z]+[0-9]+) 0:0 0660 *(/usr/bin/automount.sh)
-
+zero      root:root 0666
+random    root:root 0666
+urandom   root:root 0666
+full      root:root 0666
+null      root:root 0666
+zero      root:root 0666
+rtc0      root:root 0664
Comment 1 Saul Wold 2014-09-23 22:27:44 UTC
This issue is actually contained with in the meta-clanton layer for the Galileo board.  You suggested fix below is correct. The Galileo BSP is still based on the 1.4.x release which is now supported by the community, but in fact does not have support for mdev, it was added by the meta-clanton layer as mentioned.

Upon investigating new releases 1.5 and beyond, mdev is being supported directly by busybox, but was missing the /dev/rtc entry, so that will be added in 1.7

Since the layer is outside the control of the Yocto Project, I am going to close this bug at this time, feel free to discuss this directly on the Galileo community page.