I ended up doing something a little different, I add the folders I needed to a list of dirs that get created in (TARGET_ROOT_OUT)/ or some variable like that, short-term mem loss. Anyways it was in an Android.mk file in system/core/ I believe and when I went to build it said something about grandfathered modules, so I added those to a file (like it said not to do
) in build/core if I remember correctly, and it built with the directories in place with the correct perms as I added in system/core/include/private/android_*.h (I can't remember the whole name), sweet.
I did brunch, I still haven't figured out those boot tools ,
Now I gotta figure out mounting, I tried changing the mountpoint for the sdcard in vold.fstab but it didn't mount on boot (not in 'mount' or 'df') I can do that manually for testing out glibc based daemons, I have problems with sockets and some to run, Apache2 works, rpcbind works, and a few others but not postgresql or nfs-common, the two I really want, I wonder if a program can connect to a db on another host?). Editing /etc/fstab is easy to do, I gotta figure out these little differences from Debian that I am familiar with. This is not normal thats for sure, its like they micro managed all the permissions and different partitions/mountpoints.