In init.mt8163.rc:
on fs
write /proc/bootprof "INIT:Mount_START"
mount_all /fstab.mt8163
setprop ro.crypto.state unencrypted
#change partition permission
exec /system/etc/partition_permission.sh
#change partition permissions
exec /system/bin/chmod 0640 /dev/block/platform/mtk-msdc.0/by-name/boot
...
In dmesg:
[ 7.570313] .(3)[1111:init]init: command 'setprop ro.crypto.state unencrypted' action=fs status=0 (/init.mt8163.rc:71)
[ 7.570358] .(3)[1111:init]init: argv[0]= exec
[ 7.570375] .(3)[1111:init]init: argv[1]= /system/etc/partition_permission.sh
then no further message is printed.
lxc log says:
NOTICE lxc_start - start.c:post_start:1447 - '/init' started with pid '1111'
...
DEBUG lxc_start - start.c:signal_handler:342 - container init process exited
DEBUG lxc_start - start.c:__lxc_start:1392 - unknown exit status for init: 9
DEBUG lxc_start - start.c:__lxc_start:1397 - Pushing physical nics back to host namespace
DEBUG lxc_start - start.c:__lxc_start:1400 - Tearing down virtual network devices used by container
INFO lxc_error - error.c:lxc_error_set_and_log:55 - child <1111> ended on signal (9)
So I placed a 'exit 0' inside that script, and it quits with 0 as expected, but then init still quits at the next exec command. Probably means permission to chown/chmod those block devices is not granted.