I might as well add my two-bits in.
High quality NAND usually guarantees 100,000 program-and-erase cycles, using 100% of the blocks in the NAND. Reference: http://www.eng.utah.edu/~cs3992/2009/NAND_Flash_prop.pdf
So lets say this is the case, 100,000 write and erase cycles for the entire NAND.
Lets say five new firmware updates per year, 5 erase and program cycles. Down to 99,995 for the first year. Lets say you write temporarily to your home directory once every hour, every day for a year. With linux, this causes a read-write-erase in the same physical location on a device. That area of blocks, say 20 blocks, gets written to. 100,000 - (8,760 + 5) = 91,235
Year 1: 91,235
Year 2: 82,470
Year 3: 73,705
Year 4: 64,940
...
Year 11: 3,585 cycles left.
That's with nothing else going on, like programming packages, updates, tests, bumps, bangs, bruises.
11 years seems like a long time until you get there.
High quality NAND usually guarantees 100,000 program-and-erase cycles, using 100% of the blocks in the NAND. Reference: http://www.eng.utah.edu/~cs3992/2009/NAND_Flash_prop.pdf
So lets say this is the case, 100,000 write and erase cycles for the entire NAND.
Lets say five new firmware updates per year, 5 erase and program cycles. Down to 99,995 for the first year. Lets say you write temporarily to your home directory once every hour, every day for a year. With linux, this causes a read-write-erase in the same physical location on a device. That area of blocks, say 20 blocks, gets written to. 100,000 - (8,760 + 5) = 91,235
Year 1: 91,235
Year 2: 82,470
Year 3: 73,705
Year 4: 64,940
...
Year 11: 3,585 cycles left.
That's with nothing else going on, like programming packages, updates, tests, bumps, bangs, bruises.
11 years seems like a long time until you get there.
