Slashdot Mirror


Wind River Announces It Likes Linux After All

onecrazyfoo writes "Wind River is going to start supporting Linux in the embedded market. Pretty big news from the largest company in the embedded tools market. What makes it even more interesting is the fact that they have been very anti-Linux and outspoken about it in the past. You can read more about their announcement at LinuxDevices.com." I'm guessing this has come about because of recent changes in the company.

13 of 218 comments (clear)

  1. Pfft by Rosco+P.+Coltrane · · Score: 5, Interesting

    They're just doing like LynuxWorks former Lynx with their Blue Cat Linux. I have a strong suspicion that WindRiver just wants to profit from some of the Linux hype, given that, apart from the price, quite frankly, their OS and tool suites are just way better than any embedded Linux suite I've ever seen/worked on/worked with.

    It's just another company trying to jump on the Linux bandwagon. Nothing to see here folks ...

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:Pfft by Anonymous Coward · · Score: 1, Interesting
      quite frankly, their OS and tool suites are just way better than any embedded Linux suite I've ever seen/worked on/worked with

      Speaking as the only person in my previous company who could make Tornado work, I'd rather eat my liver than touch it again. And let's not even talk about Tornado AE, wherein fixing its unbelievably broken implementation allowed me only to discover its unbelievably broken design.

      But anyway, I imagine that Wind River is jumping on Linux simply because their VxWorks AE kernel is a total dead end. The only surprise is that it took them this long to capitulate. If my guess is right, expect to see support for AE dwindle rapidly after this announcement.

      The embedded market is no longer the same as the RTOS market. The old VxWorks 5.4 RTOS kernel doesn't have any memory protection, and that's a deal-breaker these days for any embedded system that doesn't require RTOS-level determinism. In response, Wind River cobbled together VxWorks AE, which is the sorriest excuse for a protected-memory OS you'll ever see.

      Its "protection domain" scheme doesn't operate like any reasonable VM paradigm. An example: (1) You cannot create a protection domain that contains a running process. (2) But the only way to create a process inside a protection domain is to spawn out of a process that's running inside the protection domain. Yes, those two statements are contradictory. Yes, there is a way around it. Yes, that loophole is the only way to use the product.

      Conceivably, they've fixed this since I used it. But that's just one of many indications that the product was half-baked from conception -- they probably just asked their in-house RTOS people to engineer a VM system. I could give worse examples but I'm skating too close to a lawsuit as it is.

      Tellingly, VxWorks AE was originally supposed to be VxWorks 6.0. They changed it to AE after realizing that no one using 5.4 would ever upgrade. Not that they could -- VxWorks AE requires the completely non-backwards-compatible Tornado AE. Oops.


      +++ATH0

  2. We should *not* consider this a good thing... by pla · · Score: 5, Interesting

    From the comments so far, I will presume most Slashdotters have no experience with WindRiver.

    Exercising great restraint to avoid writing anything they would likely sue me for (such as a factual tale of my experience dealing with them for over two years), I would just like to point out that we should not, in any way, consider this "good" news.

    Aside from their "quality" tools (the fixing of which I can thank for giving me a reason to learn Tcl), expect to hear about a GPL violation within a few weeks. And if they handle that accusation like they handle their customers' bug reports, well, good ol' Darl may start sounding fairly reasonable to deal with.

    1. Re:We should *not* consider this a good thing... by sasami · · Score: 3, Interesting

      Aside from their "quality" tools (the fixing of which I can thank for giving me a reason to learn Tcl)

      You too, huh?

      I guess every VxWorks shop gets to have this lovely learning experience.

      ---
      Dum de dum.

      --
      Freedom is not the license to do what we like, it is the power to do what we ought.
  3. Formerly with FreeBSD Wind river? by agent+dero · · Score: 3, Interesting

    This is an actual question, wasn't Wind River one of the major contributors to the fantastic development work done on FreeBSD?

    If so, how could this be _bad_ for linux in any way shape or form? Even if you don't like the company, linux-heads should wake up and realize, any company that's investing in linux and open source is GOOD, look how far FreeBSD has come from 386/BSD and FreeBSD 2.x

    --
    Error 407 - No creative sig found
  4. Re:Well well well... by NanoGator · · Score: 5, Interesting

    "it lets people change their minds when it becomes clear they can't fight the future."

    Can't fight the future, or did Linux finally reach maturity? There's a big difference between fighting it kicking and screaming and simply not being able to use it because there's things it wasn't able to do.

    Don't assume that everybody who avoids Linux is an idiot.

    --
    "Derp de derp."
  5. but, host tools? by cycle · · Score: 3, Interesting

    Whenever I'm building something on VxWorks, I'm mainly cursing about having to work from a Win or Sun machine. No Tornado for Linux. I would be really, really pleased if they would just release a host-tools-suite for Linux. That would make building stuff for VxWorks a much more pleasant experience. Jumping straight to "embedded linux" support sounds a little like jumping the gun, actually. They've spent 20 years developing VxWorks, it seems to me the most natural and useful Linux support would be to release a Linux-native development kit for it.

    1. Re:but, host tools? by The+Vulture · · Score: 2, Interesting

      I wish that WindRiver would release their host-tools for Linux also.

      The project that I'm working on now, was previously done on Solaris, but the Solaris machines (Ultra 5's) are starting to show their age.

      I'd love to be able to build under Linux. One thing that I have thought of doing is getting the gcc source from WindRiver for the version of Tornado that I'm using, and build my own MIPS cross-compiler/binutils for Linux (I don't really need the GUI, since we use a Makefile that's not geneated from the tools).

      -- Joe

    2. Re:but, host tools? by k8to · · Score: 3, Interesting

      Back when I was at Windriver, me and another guy over in tech support tried to get Tornado over to Linux, but while we were attempting it, management was deciding to deprecate the other UNIX builds and was busy creating dependencies on the registry and MFC. At the time X libs weren't generally reentrant which was a blocker.

      We got sidetracked and the build stagnated and we never did that final 20%. It would have been so easy with just one person doing it full time. ..

      --
      -josh
  6. Re:Well well well... by Skyshadow · · Score: 2, Interesting
    Can't fight the future, or did Linux finally reach maturity? There's a big difference between fighting it kicking and screaming and simply not being able to use it because there's things it wasn't able to do.

    Given their attitude and the fact that this was relatively recently, I'd say "fighting it kicking and screaming" is a much better representation than "waiting for functionality".

    And I would argue that anyone who does not see the *potential* of Linux, both in terms of technology development and the bottom line, is an idiot. What I mean here are the folks who, despite the staggering amount of evidence and press to the contrary, still think of Linux and OSS software as some sort of quaint ameature effort. The head of my division is one of these guys -- we've taken to calling him "executivus obsoletus". The Wind River folks, at least the ones I talked to, were the same sorts.

    --
    Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
  7. Going the way of Sun? by Brett+Glass · · Score: 3, Interesting

    Sun did a similar thing: it embraced Linux, even though doing so was to feed and support something which was cannibalizing its core business. It is now regretting that decision. Will Wind River? Alas, I suspect so. Wind River has nothing to gain by supporting Linux.

  8. Anti-Linux stance? by k8to · · Score: 4, Interesting

    Maybe I didn't read the right articles, but I saw some belief that the GPL kernel might not mix well with the embedded world, and a perception of Linux being embraced by competitors, which caused them to try the other route: BSD.

    I didn't see any kind of "Linux is no good" message coming from WRS. Maybe I missed some clueless sales-drone speeches?

    The people you see making the pro-linux statements today: especially Fiddler, were making similar noises around the time I left, back in 1999. The attitude hasn't fundamentally changed, they just tried other avenues and they didn't work.

    WRS has long had an idiology that the runtime is not the important piece, but that the tools are where the major development value is. This stems from the origin of the company as a tools provider for VRTX. As a result, they've supported multiple runtimes over the course of the company, at times runtimes provided by alternate vendors. Thus, the Linux thing isn't new.

    What might be new is that the general open source movement is providing more and more sophisticated developer tools for free, such that their custom-packaging of GCC and gui project manager/debugger/etc aren't worth the boatload of cash they're used to charging for it.

    --
    -josh
  9. Using *NIX Wind River products by Anonymous Coward · · Score: 1, Interesting

    Remember that they first told customers they could not use GPL because of licensing, and they're now embracing the very same technology.

    At the same time, they have dropped the technology they told customers should use at the drop of a hat, leaving customers cold in the dark.

    I would be very, very careful if you plan to use their tools; The Tools You Depend On may also disappear on a moment's notice and no longer be available tomorrow.
    Why become dependent on them if there are excellent, free, alternatives?