
It is also worth noting that the ' by-name' (or ' by-num') entry can exist in fstab files as shown in this example taken from device/asus/flo/fstab.flo: dev/block/platform/msm_sdcc\.1/by-name/ssd u:object_r:modem_block_device:s0 dev/block/platform/msm_sdcc\.1/by-name/fsg u:object_r:modem_block_device:s0 dev/block/platform/msm_sdcc\.1/by-name/modemst u:object_r:modem_block_device:s0 dev/block/mmcblk0 u:object_r:root_block_device:s0 dev/block/platform/msm_sdcc\.1/by-name/m9kefs u:object_r:efs_block_device:s0 This is resolved by ueventd as explained in the following commit: These are example entries from device/asus/flo/sepolicy/file_contexts, note the ' by-name' entry. data/app-asec(/.*)? u:object_r:asec_image_file:s0


mnt/asec/+/res\.zip u:object_r:asec_public_file:s0 system/bin/run-as - u:object_r:runas_exec:s0 system/bin/sh - u:object_r:shell_exec:s0 dev/socket/dumpstate u:object_r:dumpstate_socket:s0 dev/socket/dnsproxyd u:object_r:dnsproxyd_socket:s0 dev/socket/adbd u:object_r:adbd_socket:s0 dev/adf-overlay-engine*\.* u:object_r:graphics_device:s0 dev/adf-interface*\.* u:object_r:graphics_device:s0 dev/accelerometer u:object_r:sensors_device:s0

It is used by the file labeling commands such as restorecon. This file is used to associate default contexts to files for file systems that support extended file attributes. This section details the Android policy configuration file formats with worked examples.
