Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

(jcwren) Re: (bunchas): why i may have to leave perl...

by jcwren (Prior)
on Nov 10, 2000 at 00:15 UTC ( #40803=note: print w/replies, xml ) Need Help??

in reply to RE (tilly) (6): why i may have to leave perl...
in thread why i may have to leave perl...

I agree that Linux will probably become more and more viable for smaller platforms, in the future. This can really only achieved by better modularization of various components. Most embedded OS kernels are highly modularized, down to 'Do you want threads or not', or 'Does the PPP include auto-dialing' levels.

This is where Linux is behind, at the moment. BlueCat and etLinux are steps in the right direction. And believe me, I would *love* to run an embedded Linux kernel on this project. I have no qualms about developing under it. But this is where these kernels excel, is that they've become very tuned over the years. LynxOS (from LynuxWorks) claims that a minimal (non-TCP stacked) kernel can run in 33K. I built a minimal BlueCat kernel, and it wouldn't boot in 2MB (kernel went through signon, but somewhere near the last step, it just has a seizure, and doesn't indicate why. Feeding it more memory solved the problem.)

You're also correct that I can buy service contracts through third party shops. However, the cost of this option is moderately comparable to the recurring support contracts that Microware, WindRiver and others charge. If you are talking to a customer, it's easier to tell them that "Yes, we get the OS, support, and licenses, etc all from the same company.", rather than "Well, we go here for this, there for that, another over yonder to do something else." Customers, as a rule, like cohesive solutions.

There are several dozen embedded OS vendors in the market (Kadak, Treck, Microware, WindRiver, pSOS, many more). All have different capabilities, marketing strageties, and cost/performance curves. Some will inevitably go out of business. One could argue that if the embedded Linux distro that you're dependent on stops being supported, you're in a similiar (but not as bad) situation. My solution has been in the past to write into the contract that we get full rights to any products we buy, should the company go out of business. We had to cancel one contract with an OS vendor at the last minute because of a failure to agree to escrowing it. Linux, of course, really doesn't have this problem, but if you're reliant on the support for the distro, you have to figure out what it takes to port to some other release, and how customized the kernel and everything is. There are less hassles, legally, involved, but it's a time sink any time you have to deal with this crud.

I consider it unlikely that many of the larger OS vendors will go out of business anytime soon. One of the reasons for that is platform diversity. Linux runs on far fewer platforms (at the moment) than OS/9 does, for example. Also, the knowledge base built into those companies, as far as embedded systems goes, is phenominal. I would have to speculate that most shops that are supporting embedded Linux have a smaller knowledge base regarding embedded system support (not skills, tho) than Microware does (who's been doing this for over 15 years).

So no, I'm not going to bet against Linux in any way imaginable. I'm disappointed, if anything, that we won't be using it on this project. But I'm not betting on Microware, WindRiver, or pSOS blowing away anytime soon, either.


e-mail jcwren
  • Comment on (jcwren) Re: (bunchas): why i may have to leave perl...

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://40803]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2020-03-28 14:59 GMT
Find Nodes?
    Voting Booth?
    To "Disagree to disagree" means to:

    Results (167 votes). Check out past polls.