View Single Post
  #2000 (permalink)  
Old 03-22-2011, 01:30 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:
Originally Posted by [ACL] View Post
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
__________________
Reply With Quote