This papering over serious problems reminds me of Windows reboot syndrome.
In Windows you can set a service to take action on:
* First failure
* Second failure
* Subsequent failure
Possible actions:
* Take No Action (default)
* Restart the Service
* Run a Program
* Restart the Computer
There's also a class of Windows services viz. "Critical System Services" e.g. lsass.exe, smss.exe, etc.
If you change their in-use resources, you have to restart the system.
How to idendify them: enum
RM_APP_TYPE is set to
RmCriticial in
RM_PROCESS_INFO structure.
Of course they're different from Windows Critical Error i.e. BSOD. Reaction to BSOD is modifiable through registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
If you look at Android and Cell phones - they are operating without issues, and car companies are leaving QNX for Android.
"without issues" is another name for "lost advanced civilisations". it doesn't exist.
The story of Patriot Missile Failure, arithmetic errors and 24 bit fixed point register:
http://www-users.math.umn.edu/~arnold//disasters/patriot.html | UMN.edu
I wanted to talk to folks that did embedded systems for projects like NASA and other mission critical aspects that might be beyond the scope of Linux and FreeBSD.
When it comes to "Embedded System", electronics is the most important topic.
IMO. Frankly, '
FreeBSD vs Linux' and/or
(systemd)?"bad":"good"; etc is rather off-topic.
I'm not talking about raspbian-enabled Pi, sitting on the table, running ^C/^V-ed code.
Final words:
IMO, electronics 101 is essential to embedded systems. Here's two paper-books (my favourite!).
First item has a new edition, I don't have it, but I think 2nd edition is good enough!
1. The Art of Electronics 2nd Edition (Horowitz, 1989)
2. Digital Logic and Computer Design (Mano, 1979)