Android udev /dev 设备节点权限

/*************************************************************************
 *                  Android udev /dev 设备节点权限
 * 说明：
 *     现在的Linux系统设备节点权限一般都是通过动态配置，之前一直没找到具体
 * 在哪里配置的说明，这次在看参考书的时候发现ueventd.rc就是用来做这件事的。
 *
 *                                   2016-5-14 深圳 南山平山村 曾剑锋
 ************************************************************************/

一、参考文档：
    Embedded Android
        https://www.google.co.id/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&ved=0ahUKEwiWwcrbqtjMAhWDppQKHdhjBroQFgg5MAQ&url=http%3A%2F%2Fwww.staroceans.org%2Fkernel-and-driver%2F%255BEmbedded.Android(2013.3)%255D.Karim.Yaghmour.pdf&usg=AFQjCNHe5Ey14egLQXgmOpP-PGN510ALgA

二、原文：
    .　页码：
    . 内容：
    udev events
    As I explained earlier, access to devices in Linux is done through nodes within the /dev directory. In the old days, Linux distributions would ship with thousands of entries in that directory to accommodate all possible device configurations. Eventually, though, a few schemes were proposed to make the creation of such nodes dynamic. For some time now, the system in use has been udev, which relies on runtime events generated by the kernel every time hardware is added or removed from the system.  In most Linux distributions, the handling of udev hotplug events is done by the udevd daemon. In Android, these events are handled by the ueventd daemon built as part of Android’s init and accessed through a symbolic link from /sbin/ueventd to /init. To know which entries to create in /dev, ueventd relies on the /ueventd.rc and /ueventd.<device_name>.rc files.

三、总结：
    之前遇到需要修改权限之类的事情，一般都是在init.rc中进行修改，那时候觉得挺奇怪的，因为一般会有专门给设备节点设置权限的文件，那里明显不是，但也没找到准确的地方，现在终于找到依据了。