NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[natemcnutty]

Originally Posted by T_D_H

same issue as before, switching to recover method, and going to test on my brand new TP2 with diff sdcard, 2 at once = greater testing

I've got a rhod500 as well, and this setup works great. It is already rooted as well, so don't have to worry about that

[[ACL]]

Originally Posted by natemcnutty

I've got a rhod500 as well, and this setup works great. It is already rooted as well, so don't have to worry about that

hey nate.. i didnt test this at all but i did implement the sdcard loop wait for the recovery. pain in the ass to restore and lose the modules .. so im still trying to master mind a way around that.

[natemcnutty]

Originally Posted by [ACL]

hey nate.. i didnt test this at all but i did implement the sdcard loop wait for the recovery. pain in the ass to restore and lose the modules .. so im still trying to master mind a way around that.

What about something like this?

tar -cvzf /cache/modules.tgz /data/modules/
/bin/flash_eraseall /dev/mtd/mtd3 > /dev/null
/bin/mount -t yaffs2 /dev/block/mtdblock3 /data > /dev/null
tar -xzf /cache/modules.tgz -C /data

[[ACL]]

Originally Posted by natemcnutty

What about something like this?

tar -cvzf /cache/modules.tgz /data/modules/
/bin/flash_eraseall /dev/mtd/mtd3 > /dev/null
/bin/mount -t yaffs2 /dev/block/mtdblock3 /data > /dev/null
tar -xzf /cache/modules.tgz -C /data

i ran my first test yesterday to restructure the modules path. I tried to port over sqsh4 so i can try the other method but the patch is too massive. So ill try to night with yaffs2 instead. If it works, then we will just do as you said and copy them over to system and mount looping them. This way we can wipe data all we want and not loose anything. Only thing we need to make sure is that people wipe their old modules or else system will just baloon up.

Also because the recovery is only 8mb, we will only have room for 1 extra kernel in there.. ohh well.. better than nothing

[natemcnutty]

Originally Posted by [ACL]

i ran my first test yesterday to restructure the modules path. I tried to port over sqsh4 so i can try the other method but the patch is too massive. So ill try to night with yaffs2 instead. If it works, then we will just do as you said and copy them over to system and mount looping them. This way we can wipe data all we want and not loose anything. Only thing we need to make sure is that people wipe their old modules or else system will just baloon up.

Also because the recovery is only 8mb, we will only have room for 1 extra kernel in there.. ohh well.. better than nothing

Couple of easy fixes there. We can make recovery 16 MB or something larger if you'd like. It can come from cache or from data.

For modules, I think very very few people will be wanting to hold onto their old kernel once they upgrade, but if they do, we could require a sd card for that. Just move them into a tgz on the sd card using the old uname as the name so that the kernel can grab its appropriate modules

[natemcnutty]

Originally Posted by [ACL]

hey nate.. i didnt test this at all but i did implement the sdcard loop wait for the recovery. pain in the ass to restore and lose the modules .. so im still trying to master mind a way around that.

By the way, tested the sdcard loop just now. Works perfectly. I have some more cleanup that I'd like to do in init, so can you look through this patch and let me know what you think?

Edit: I changed the sdcard partition thing to be more efficient, removed some unnecessary stuff like the install-seq.sh portion, moved /tmp to /cache instead of /data/tmpcache, and removed the auto-mount sections for the mtdparts since we specify them in Tinboot.

[[ACL]]

Originally Posted by natemcnutty

By the way, tested the sdcard loop just now. Works perfectly. I have some more cleanup that I'd like to do in init, so can you look through this patch and let me know what you think?

Edit: I changed the sdcard partition thing to be more efficient, removed some unnecessary stuff like the install-seq.sh portion, moved /tmp to /cache instead of /data/tmpcache, and removed the auto-mount sections for the mtdparts since we specify them in Tinboot.

This part is confusing

-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

edit: all the other changes are really good. good house keeping . Lets figure this part out "+mount /cache /tmp" before commiting. Everything else will be fine. Did you test it yet?

[natemcnutty]

Originally Posted by [ACL]

This part is confusing

-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...

[[ACL]]

Originally Posted by natemcnutty

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...

time for a pig build ? leave it out for now, and if this is needed by android we can add it to the rc. This wya we dont have to rebuild the initrd to get this to work.

[natemcnutty]

Originally Posted by [ACL]

time for a pig build ? leave it out for now, and if this is needed by android we can add it to the rc. This wya we dont have to rebuild the initrd to get this to work.

Then should we do the same with shared_prefs? Also, in the latest build, did anyone else lose root? I see su there, but it isn't working.

Edit: Weird, I had to download busybox to get Titanium Backup working, but then ES File Explorer won't let me root explore... Guess I need to start fresh again.