R/W Flash = Eventual Burnout?

[javamatte]

I'll preface this by letting you know I develop on 8-bit micros, so I'm familiar enough with Flash memory to be dangerous, but by no means an expert!

I am eagerly awaiting the delivery of my Zaurus SL-5500, and from what I've read about OZ, I think that's what I want to flash on there.  I am a little concerned, however, that making the ROM (Flash) area writable AND putting config/log files that get written and rewritten constantly there can't be a good idea.

Has anyone had OZ on there Z for a long time?  Has anyone run into Flash burnout problems?  Am I being insanely paranoid, since it would take the average user at least a couple of years to exceed a million writes on most config files (100 / day for 3+ years *grin*).

Thanks for any feedback, I would love to load the OZ rom, I just don't want to end up with a designer techie paperweight.

-javamatte

[lardman]

Log files are written to the tmpfs which is RAM based and dynamically sized iirc.

Config files don't tend to be written that often; plus jffs offers wear leveling and the write life is something like 100k cycles iirc.

I wouldn't worry too much.


Si