>Either mke2fs directly on the MTD device, or use resize2fs to enlarge >the filesystem to fill the full MTD device. Or make sure the large >image is a sparse file, then it needs less disk space. I suppose I was thinking that I will want the ability to download/install files as necessary and use the available space on the partition so that is why I was wanting access to all 256MB in the flash. >It's only now that I understand what you actually want. Sorry about that. I'll take more time next time to clarify clearly what I am attempting to understand and implement. >BTW, be careful with ext2 on flash, you really want it mounted >noatime,nodiratime or otherwise every file access will update the atime >information and cause needles wear on the flash block that contains the >atime for that particular file. Ok. Thanks for the advice. I've noticed with jffs2, that after doing either tftp transfers or simple power downs, that I can see jffs2 messages scroll by about empty flash found and then, eventually, it seems to corrupt the area where init is for busybox and won't boot. That is what I am most worried about. Is this what you use (jffs2) and is there any way to be sure that something like that doesn't happen in the field? -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
