Quote:
Originally Posted by ndno
Yeah, I didn't mean to say it will fix the restarts/SOD. Just thought it will may have better data integrity using a native ext2 partition than a data.img mounted on a FAT32 partition; I'm just speculating... 
Yeah, it's not really "hacking" skills. I called it hacking because that's what I'm doing, hacking away at the scripts and stuff until it works.
arrrghhh, if you find a good Windows tool that can create Linux EXT2 partitions (EXT4 for GBX0A), let's us know. I didn't know such tools existed so that's why I said a Linux distro is required. I guess I should do some more googling; I just tend to like Linux more so I didn't bother searching.
I didn't realize that neopeek was already doing this; I have never used neopeek. So I guess neopeek is more complicated to set up than the haret builds we have here 
Again, I'm just doing this as an experiment for learning purposes so unless there are a lot of PROs for switching to native EXT2 partitions on a SD card, people should just stick to the way haret builds are set up in this forum. Besides, the NAND project is very close (if not yet) to completing and it uses native EXT2 partitions on a faster NAND interface so people should wait for that |
Agreed on the NAND comments.
I would not agree with ext4 for GB - the reason being is journaled file systems should NOT be used on SD cards - unless you use a very specific type of mount, I believe the mount option is noatime. Either way, be very, VERY careful when using a journaled FS on a SD card - I would just avoid that altogether.
Neopeek builds are definitely harder to use, no question
.
The tool I heard people were using was calling MiniPartitionTool or something to that effect...