Quote:
Originally Posted by makkonen
I've got commit access to the rootfs, so I can push it upstream... but I'd like to get the rest of the issues sorted before I do. (Perhaps I'm a little too proud of my generally clean commits.  )
if you connect with adb during the bootanimation, chown to 1002 (or 1002:1002) works... I don't know at which point that change is made, and if it's sometime while the init script is running (in which case we can just change the order). Moving the bit about dbus.conf down to the bottom of the file might've worked for me last night -- or I might've just missed the error message and forgot to delete the cache folder, so I just thought it worked. I was a bit tired. |
I Can take a look at it when I get home I don't have my TP with me right now. Maybe you're right the order might make a difference. But I don't know if the order is important or not. Maybe busybox is just being stupid when running the script vs adb via bash/sh
On babijoee's initial fix commit it gives a error on his too. Its odd because it should be able to change the owner to 1002 with out that user being known. I do it on my linux/ubuntu system all the time, i have a script that patches the squashfs perms before i make a new one and i don't have users 1003 1004 etc