Quote:
Originally Posted by [ACL]
This part is confusing
Code:
-mkdir -p -m 0777 /data/tmpcache
-mkdir -p -m 0771 /data/shared_prefs
+if [ ! -d /data/shared_prefs ] ; then
+ mkdir -p -m 0771 /data/shared_prefs
+fi
chmod 0771 /data/shared_prefs
chown 1000:1000 /data/shared_prefs
ln -s /data/shared_prefs /shared_prefs
-ln -s /data/tmpcache /tmp
+mount /cache /tmp
Does the link /shared_prefs need to exisit?
Also what is stored on /tmp? ifs its true tmp i wonder if we can scrap it
Keep in mind that recovery needs some of this so we need to make sure we arent getting in the way. recovery uses cache lot for its logs and stuff.
I see this on the rc mkdir /data/local/tmp 0771 shell shell . so how many tempts do we really need ..lol |
Yeah, so here's how I understand some of this.
shared_prefs is for sharing preferences between standard user and root user in some applications. Not sure if this is some legacy backwards compatibility thing or what.
The ln -s will create a link at /shared_prefs and it doesn't have to exist like a mount does.
The /tmp was already being stored on /data, and I just moved it over to /cache. I have a feeling that /tmp is used by programs that don't support or may not be aware of /cache. In any case, I figured we could leave that one alone but move it to /cache to clean up our /data partition. No point in backing that up when we backup the data partition.
Edit: Well, I just read that /data/local/tmp is what things like the market use to download APK's to. I'm beginning to think maybe /tmp is something we did on XDAndroid...