ndex477
Well-Known Member
Here's my situation, I use a Linux distro on a daily basis and i have a Hisense Sero 7 Pro tablet. My Sero 7 won't mount in Linux as it's MTP(Have yet to find a way to mount it) so i mount the tab using Windows 7.
Today i noticed that there is a file in my download folder named "file_contexts". Here is what part of it looks like:
#line 1 "external/sepolicy/file_contexts" ########################################### # Root / ubject_r:rootfs:s0 # Data files /adb_keys ubject_r:rootfs:s0 /default.prop ubject_r:rootfs:s0 /fstab\..* ubject_r:rootfs:s0 /init\..* ubject_r:rootfs:s0 /res(/.*)? ubject_r:rootfs:s0 /ueventd\..* ubject_r:rootfs:s0 # Executables /charger ubject_r:rootfs:s0 /init ubject_r:rootfs:s0 /sbin(/.*)? ubject_r:rootfs:s0 # Empty directories /lost\+found ubject_r:rootfs:s0 /proc ubject_r:rootfs:s0 # SELinux policy files /file_contexts ubject_r:rootfs:s0 /property_contexts ubject_r:rootfs:s0 /seapp_contexts ubject_r:rootfs:s0 /sepolicy ubject_r:rootfs:s0 ########################## # Devices # /dev(/.*)? ubject_r:device:s0 /dev/akm8973.* ubject_r:akm_device:s0 /dev/accelerometer ubject_r:accelerometer_device:s0 /dev/alarm ubject_r:alarm_device:s0 /dev/android_adb.* ubject_r:adb_device:s0 /dev/ashmem ubject_r:ashmem_device:s0 /dev/audio.* ubject_r:audio_device:s0 /dev/binder ubject_r:binder_device:s0 /dev/block(/.*)? ubject_r:block_device:s0
Where could this file have come from? I use a USB hub for multiple devices but i don't think that caused it. The file even contains info about my GPS magnetic sensor(in bold). Any response is greatly appreciated.
Today i noticed that there is a file in my download folder named "file_contexts". Here is what part of it looks like:
#line 1 "external/sepolicy/file_contexts" ########################################### # Root / ubject_r:rootfs:s0 # Data files /adb_keys ubject_r:rootfs:s0 /default.prop ubject_r:rootfs:s0 /fstab\..* ubject_r:rootfs:s0 /init\..* ubject_r:rootfs:s0 /res(/.*)? ubject_r:rootfs:s0 /ueventd\..* ubject_r:rootfs:s0 # Executables /charger ubject_r:rootfs:s0 /init ubject_r:rootfs:s0 /sbin(/.*)? ubject_r:rootfs:s0 # Empty directories /lost\+found ubject_r:rootfs:s0 /proc ubject_r:rootfs:s0 # SELinux policy files /file_contexts ubject_r:rootfs:s0 /property_contexts ubject_r:rootfs:s0 /seapp_contexts ubject_r:rootfs:s0 /sepolicy ubject_r:rootfs:s0 ########################## # Devices # /dev(/.*)? ubject_r:device:s0 /dev/akm8973.* ubject_r:akm_device:s0 /dev/accelerometer ubject_r:accelerometer_device:s0 /dev/alarm ubject_r:alarm_device:s0 /dev/android_adb.* ubject_r:adb_device:s0 /dev/ashmem ubject_r:ashmem_device:s0 /dev/audio.* ubject_r:audio_device:s0 /dev/binder ubject_r:binder_device:s0 /dev/block(/.*)? ubject_r:block_device:s0
Where could this file have come from? I use a USB hub for multiple devices but i don't think that caused it. The file even contains info about my GPS magnetic sensor(in bold). Any response is greatly appreciated.