Wind River Partners With Red Hat On Embedded Linux
An anonymous reader writes "According to LinuxDevices: 'Calling embedded Linux and VxWorks 'the standards in device software development,' Wind River today announced a dual operating system strategy that adds a newly developed embedded Linux distribution -- Red Hat Embedded Linux -- alongside its proprietary VxWorks real-time operating system.'"
First they "acquired" Slackware. And then sold it off/gave it away after doing nothing with it. Then they "acquired" BSD and have done little with it. Now they have linked up with RedHat for embedded Linux tools?
When WindRiver Systems (WRS) came in several years ago to give a presentation on their strategies for Tornado and VxWorks products we were disappointed. After two hours of the pain and agony of learning nothing we didn't already know, we asked "where's the beef"? (old expression, but I think you "get it") They told us their entire strategy was to become a $1BILLION company inside of a year. Some strategy, eh?
Our experience is that WRS provides marginal support on the VxWorks products, and have made a mess of their licensing systems and servers (that track tools use and enforce their payment structures). Let's hope WRS doesn't take away from the strength of the Open Source community, the tools development it undertakes, and the great support it gives...
Here are the things that WR ships when you go to use VxWorks for your embedded system project:
Components Included
Development tools:
TORNADO Integrated Development Environment
GNU and DIAB C/C++ Compilers
WIND VIEW system analyzer
SNiFF+ PRO code visualization tool
Full VxSim
TORNADO BSP DEVELOPER'S KIT
Runtime Components:
VxWorks embedded RTOS
TrueFFS flash file system
VxFusion
VxVMI
VxMP
So, how far does Linux have to come to match these tools?
Try using ext2 et al on a flash file system.
You only get 100,000 writes on an flash chip. You need a strategy for minimizing writes. No general purpose file system made for a hard disk is going to do that optimally.
In any event, the type of glitch they had on the rover wasn't an obvious file system bug. It was more one of those confluence of supposedly normally handleable events that in concert with each other make for a bad situation.