Hi there,
This is not exactly an specific ARM platform question, but I believe is of interest to
the community,
and I use an ARM platform anyway (ebsa285) where these ideas are put into practice.
My question: what would be the best file system for an embedded platform that uses
most of the fs as
read-only, but needs write access for a few of state files? right now, the application
runs on
boot-up from an IDE, but if the users shut the box the "hard way", i.e., turn power
off, fs gets
messed up, as expected. It mostly comes back on the next boot-up after fsck, but it
has also happened
that the odd hard drive has died on us. It's not the way to go anyway.
We've played with JFFS, but the memory overheads for the database are massive. I am
aware of Cramfs, but
not familiar with it. We've been playing also with ramdisks, and it works, but if it
not unmounted on shutdown,
the state information that needs to be saved up, is obviously lost.
Has anybody out there faced a similar situation? any thoughts welcome. I am happy to
keep trying all the
available options.
TIA
Jaime
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
