BookTracker
Still Fresh
- Joined
- Oct 14, 2008
- Messages
- 21
BigTruck said:Yes, that would work fine, but that means you'd be wasting space on the SD card. Every time a package in the firmware is updated, the new package would be installed on the SD card. That's what I meant by never updating the NAND. 256MB at most (more or less depending on compression) isn't really that huge of a deal considering how cheap 16GB SD cards are now, but nonetheless it's still a waste of space.AndIn^.^ said:guys it probably works like this:
nand - libfile.bla
sd-nothing
when u set the union(insert your SD),
sd gets libfile.bla
lets say libfile.bla2 comes out,
it should overwrite the libfile.bla, which really means that it copies libfile.bla2 to the sd card, and leaves libfile.bla on the nand.
so like everyone said, with the sd you got your system, without it... out-of-the-box pandora.
so in other words, i suppose if u got 2 files with the same name, the one on the sd would be favored.
(so lets say if you insert another sd card, and want latest verions, you would have to update again. but is that a problem? )
this is how i think it would work(how ti usually does, i guess...), correct me if wrong.
i would consider it a safe choice, besides what we want is functionality i think. and libs are usually small.
plus every version beyond the one following the out of the box one, would be updated normally(on top of the version inside the SD card). so its not tooooo much a waste, for a functional reality right?
like said before sd cards are a given, and that would protect 'the original functionality' of the out of the box version, so you can mess with your anyway you want. ^^
cheers
Last edited by a moderator: