|
I'm developing an embedded Linux (it is almost over now). What I'm struggling with is the system goes unstable by cutting power source frequently and it does not boot anymore. It even does not perform The system just has a XFCE with a fixed Qt App autoloaded to display some charts. My question is that how commercial embedded Linux distros (like Wifi AP's management Linux, ...) avoid this problem? Do you have any idea? | |||||
feedback
|
|
Most do one of two things: They either run the main filesystem read-only and have a separate area for storage of data that is mounted read-write, or They have the main filesystem compressed in a file which gets expanded into a ramdisk at bootup time. This means that the filesystem is always in the same state whatever happens. There is only the small configuration storage area to worry about, and that can have a filesystem that doesn't worry too much about power loss. Another tip is to disable all caching on the storage partition so all changes are immediately written to disk. | |||
feedback
|
|
Yes, generally speaking, they don't. When it comes down to it, everyone probably has failed embedded devices - whether it is network gear, ip devices or other. Simply put, build your application as best as you can - as a developer, that is all you can do. Try to make your application as robust as possible - put error checking at the highest/every level. So for example, if you have a configuration file that is needed and your application can not run without, put a beep/feedback if it isn't found - let the user know. The next level really comes from your hardware manufacturer - redundancy or robustness is key, and again, make sure the hardware vendor follows the above ideas such as error checking/verbose feedback so that if something fails, people know why/what did it. I have not gone in to that much detail, but I hope this helps and points you in the right direction. | |||
feedback
|
