I was concerned enough that our "/" fs is read-only, with symlinks for everything interesting down into /tmp/etc instead. The rcS script made the initial set from a bunch of template files.
It, of course, was an embedded device that happened to be based on Linux, not some sort of "embedded Linux" device where J. Random Developer would expect to function happily. Last I heard, the worst of the NAND flash devices was on the order of 10^3-10^5 writes, not 10^6. -- Jim -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sameer Naik Sent: Monday, April 12, 2010 12:03 PM To: BusyBox Developer List Subject: NAND Write operations Hi, This may not be the right place to ask this question, but i only ask this because i believe most of the developers on this list work primarily with embedded systems. So here goes it. Normally on a linux system network configuration related files like resolv.conf and ifcfg-eth*, etc are stored in the /etc folder. These files are normally updated at boot or precisely when the network is configured. NAND memory have a ~100K write cycles before which write could start failing. This number is rather very large, hypothetically even if the network is configured 10 times a day the flash is good for around 27 years (100000 / (365 * 10)). Secondly, considerable amount of fragmentation could occur due to small updates on the file system I may be getting a little paranoid here, but how much is this of cencern on a production system. Regards ~Sameer _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
