Follow Slashdot stories on Twitter

 


Forgot your password?
Close
typodupeerror
×
BSD Operating Systems

BSDi's Software Divisions Acquired by Wind River 80

Posted by AilleCat from the two-flavors-that-taste-great-together dept.
big knife writes: "Check here for the official press release." Wind River is the company that puts out vxWorks, the embedded OS that runs our great Arrowpoint Web Content Switch we have here at OSDN. Evidently, BSDi will become iXsystems, dealing with BSD product solutions, and hardware (essentially a beefed up Telenet Systems). The status of FreeBSD and their commitment to Open Source, and FreeBSD in specific is mentioned, definitely a good thing.
This discussion has been archived. No new comments can be posted.

BSDi's Software Divisions acquired by Wind River More

BSDi's Software Divisions acquired by Wind River

Comments Filter:
  • The commitment to Open Source at Wind River is quite serious. Fixes, patches, and improvements to GCC submitted to the FSF are an ever increasing event. Furthermore, the BSD relationship is quite prevalent as many wind river developers have cut their teeth on BSD while attending UC Berkeley. (Wind River is headquartered in Alameda just 20 minutes south of Berkeley).

  • Re:It may be the best for WRS (Score:1)

    by Anonymous Coward
    Folks, why can't you understand this simple fact: FreeBSD is NOT LIKE pSOS, because it's not owned by any company.

    Therefore, you CANNOT buy it out or close it's source - it's just impossible. You can choose not to contribute your changes to the community - that's fine, it's your work, and you have the right to earn on it (unlike with GPL'd s/w ;).

    So, for me the only possible negative impact that this event could have on FreeBSD is that the former BSDi division could be stopped from contributing to FreeBSD codebase as part of their work. Pity, but we can live with it.

    Andrzej Bialecki
    FreeBSD developer

  • But are they welcome at the OSS party? (Score:2)

    by Anonymous Coward
    This article [linuxdevices.com] about Wind River's acquisition of BSDi includes an interesting developer-preference graph which shows how VxWorks peaked and how embedded Linux has shot up from nowhere. The article also includes some quotes from two of Wind River's VPs and its founder (Jerry Fiddler) about Wind River's attitude regarding open source software and linux. Together, these make it quite clear what Wind River is up to, and why they felt compelled to buy their way into the open source / UNIX movement.

    The article concludes with the question . . . "Wind River has made it clear that they plan to support -- and hope to gain the support of -- the BSD open source developer community. But the question remains -- how warmly will FreeBSD developers welcome the potential dominance of BSD UNIX by the world's leading proprietary embedded OS vendor?"

  • What it comes down to is that BSDi is Telenet Systems plus some change and Windriver is BSDi plus some change. Or, put another way, if Telenet Systems had changed its name to iXsystems, and Wind River had directly acquired BSDI, we would be at pretty much the same point.

  • winpoet was bought from another company... even so, the alternative, enternet 300, is ten times worse!!!

    --
    And Justice for None [geocities.com]
  • Depends on what criteria you're using for fitness, but for sheer performance, Alteon kicks Arrowpoint's butt. Their AD4 has been quite flexible enough to run my company's global websites.
  • As far as I understand vxWorks is basically the industry leader in RTOS's,


    In the same way that Microsoft is the leader in desktop OSs: they sell the most. For an RTOS with some more advanced features, see INTEGRITY [ghs.com]. I think it's nifty anyhow.

    Things like that may be what BSDi is needed for in WR's portfolio. BSD has features like memory protection and services other than the traditional Real Time scheduling. Are more devices moving to 'good enough time' scheduling that a unix provides?

  • Re:But are they welcome at the OSS party? (Score:4)

    by FFFish ( 7567 ) on Wednesday April 04, 2001 @04:34PM (#314647) Homepage
    I daresay Linux in the embedded market is taking off exactly as quickly as it merits.

    There are better solutions than Linux, peeps. Take the blinders off, and see how wide and varied the world is!


    --
  • Will they kill Pico?

    No. They couldn't even if they wanted to.

    Warner Losh
    FreeBSD Core

  • Wind River isn't infallible... ::grin:: (Score:5)

    by hatless ( 8275 ) on Wednesday April 04, 2001 @01:26PM (#314649)
    Wind River's products aren't all good. They're also responsible for WinPOET, the horrid PPP-over-Ethernet client most residential DSL customers live with. It's got memory leaks--bad ones--and has had them for a few versions straight. Use it, and you'd be led to think PPPoE is a terrible technology with a lot of overhead. The installer is pretty big and involved, too.

    What's even stranger is that this comes from an embedded-systems software company. You'd think they'd be well-positioned to pull off a PPPoE implementation at least as small and stable as some of the (downright tiny) Linux ones. Setting aside the kernel modules now available, there are things like rt-pppoe, a userspace client that manages to chug along merrily in a few dozen kilobytes of RAM.
  • For anyone interested, it seems Slackware will remain with the old BSDi company (which will become iXsystems).
  • No, Slackware was supported under BSDi the same way they (and FreeBSD) were under Walnut Creek. It seems Wind River was interested only in BSD related things, so Slackware stays with iXsystems/BSDi.
  • This does not have anything to do with FreeBSD since it exists as a seperate entity maintained by volunteers.

    Is this good for FreeBSD or BSD in general? Only time will tell.

    Wind River is much larger than BSDi it just may have the corporate muscle *BSD needs to increase its market share.
    I have never worked with Wind river but so I'll just wait and see.

    There's a strange guy here that keeps posting FreeBSD is dead. Most of us are just ignoring you. Can you please explain how does this merger kills FreeBSD?

    FreeBSD is public domain just like linux.
    Can you take over and buy linux? HA!

    BSDi/WalnutCreek was a company doing "FreeBSD" work not vise versa. Now there's Windriver/BSDi/WalnutCreek doing FreeBSD work.

    I don't know about you guys but I think FreeBSD is getting more and more popular these days.
  • this is true, i've used both --- "enternet" is why I got a dsl-router
  • Hell yeah! It's the only Linux distro left that doesn't load your harddrive up with cruft and pieces of lint. It's the only distro not made by committee. If you want the most Unix-like of Linuces, it's the only way to go.

    Of course, if you can't find your ass without a GUI, then definitely stay away :-)
  • Oh damn! What am I going to do? I've got a subscription to both FreeBSD *and* Slackware! I hope they don't ship me blank CDs.

    If BSD is dead, then what's running this compp p&8 K nb! .. .. . . [end transmission]
  • I have been working with VxWorks for the past year.
    You pay through the nose to get any tiny little bit of functionality beyond the barest essentials, the development envorionment sucks (constant crashes, horrible IDE performance), the OS claims to be POSIX compliant but isn't, and support is absolutely TERRIBLE. They have blown us off several times when we needed problems solved and questions answered.
    The three reasons for using VxWorks today are:
    1) Hard real time. And if you can stand latency of a couple hundred ns, Solaris 8 or IRIX can fulfill your needs.
    2) Experienced workforce. In the embedded arena, there are many experienced VxWorks developers. If your team is composed of such people, VxWorks may become a good choice when you need your product out the door in a hurry.
    3) Availability of various software components and drivers. Many vendors create drivers and modules (e.g. net protocols) for VxWorks first and often exclusively. The quality of these products is often mediocre, however one still pays through the nose for them as there is no other solution.
    WRS' monopoly may have been fraying at the edges (embedded Linux offerings and others such as QNX are beginning to show a following), however, the technological advantage these competitors are displaying may be erased by this move (the BSDi acquisition). At long last, WRS will have a Real Operating System which will show all those haughty bastards with their Protected and Virtual Memory, POSIX compliance and OSS tools who's the boss.
    I'd be absolutely thrilled to work with BSD instead of VxWorks (FreeBSD is my workstation OS of choice), but I fear this may well seal the fate of other companies such as QSSL and Be, which are true innovators and do not have the financial clout to push their competitors out by buying them (or equivalent solutions) out.
  • Although have mixed feelings about this....
    Specially when the BSDi itself JUST acquired WC....

    But windriver is a much bigger, and well known company, so if Hubbard agreed, then it must be good for FreeBSD ...

    (Hopefully) :(

  • Last i've heard...
  • Arrowpoint was purchased by Cisco who is now producing the Arrowpoint Swiches as Cisco Content Services Switches. Arrowpoint made their CLI almost identical to IOS (I assume in the hope that they'd be purchased). Cisco is phasing out their localdirector and distributed director products in favor of the Arrowpoints which do the job of both, and do it far better.

    The Cisco (nee Arrowpoint) switches are slowly being "Ciscoized" over the next few software releases. The OS code is being changed to be more similar to IOS.

    The Cisco CSS are (in my opinion) the best switches of their type on the market followed (REALLY closely) by Radware. These are both ASIC based switches with a central processing unit. They're fast due to the ASICs and flexible due to the CPU. The CPU makes the inital switching decision and hands the TCP flow over to the ASICs for switching.

    The other options in this market space are either slow PC based systems (f5 which are BSDi based and Coyote Point which are Linux based) or inflexible ASIC based systems (Alteon, etc).
  • I'll second that. Wind River has gotten better, but they're still in a "what can free software do for us" rather than "how can we use free software to help our customers and everyone else?"

    They use GCC extensively as their cross-compiler, but are not great contributors to GCC development.

  • I think quite some space in the database could be saved by crosslinking the following comments: 1 [slashdot.org], 2 [slashdot.org], 3 [slashdot.org], 4 [slashdot.org], 5 [slashdot.org], 6 [slashdot.org]. 7 [slashdot.org], 8 [slashdot.org], 9 [slashdot.org], a [slashdot.org], b [slashdot.org], c [slashdot.org], d [slashdot.org].
    They're all the same. Sir, thank you for your intelligent opion, I really appreciate it but posting it just once would have been enough. Thank you.

  • I have been using and contributing to BSD since 1983 and FreeBSD since 1994. I have absolutely no wish for FreeBSD to gain market share in embedded devices or any other area. There are plenty of other systems in those areas and if that was what I wanted that's what I'd use. What we need is a greater diversity of approaches, rather than everything converging on what's currently successful.

    As Dennis Ritchie might say, if you want QNX you know where to find it.

  • I expect that key developers would leave and restart elsewhere; after a period of chaos, consensus would build behind the biggest grouping of core commiters who agreed to re-form as the new entity.

    Now if they managed to crash a plane with most of those commiters, they might get somewhere.

    Boss of nothin. Big deal.
    Son, go get daddy's hard plastic eyes.

  • The same can be said for Wind River.
  • Don't mention the OT-3. I mentioned it once, but I think we got away with it.
  • I work with VxWorks on a daily basis as part of my job, and I'm not sure why people think this is a good thing? Wind River is *anything* but an Open Source company in their business model:

    Strict licenses which must be renewed annually for access to tech support, bugfixes and updates (we're talking about tens of thousands of dollars here).

    Mediocre tech support for smaller customers (unless, of course, you are willing to pay for them to send out one of their consultants).

    A draconian closed-source policy that, among other things, forces customers to pay exhorbitant fees for read-only access to source code. Right-to-modify licenses are even more exhorbitant.

    And the Tornado tools are supported on any OS you like... as long as that OS is Windows NT or Solaris 2.x.

    Okay fine, WRS isnt Microsoft. But the enemy of your enemy is *not* necessarily your friend.

    :Michael
  • How do you pronounce it? Presumably just like "uniX systems" but without the un.
  • If Wind River is going to "integrate" FreeBSD the same way they "integrated" PSOS, then you can kiss it goodbye.

    The BSD license allows for proprietary modules built on top of open software. When people at my workplace refer to "Microsoft embedded", they mean Wind River.

    Embrace, extend, extinguish.

    Go to their web site [windriver.com] you'll see PSOS listed as a product. Then call them up and try to buy it without buying VxWorks.

    Good luck!

  • FreeBSD was not in business to start with.
  • They can't kill PicoBSD; after all, it's maintained by volunteers.

    Remember, they can't buy FreeBSD itself. They can employ several developers, they can provide the main FTP site, but they can't kill any part of FreeBSD any more than Red Hat could kill Linux.

  • Re:Future of FreeBSD (Score:3)

    by agshekeloh ( 67349 ) on Wednesday April 04, 2001 @01:30PM (#314671) Homepage
    Just as any one company cannot kill Linux, no one company can kill FreeBSD. BSDi does not own FreeBSD -- nobody owns FreeBSD. While it would suck big-time if they fired their FreeBSD developers, it wouldn't take more than a day for each of them to find a new job developing FreeBSD.

    Wind River could kill BSD/OS. But by the time they do that, I suspect that the really cool stuff will have already been assimilated into FreeBSD. That process is well under way now.

    If Wind River stopped selling FreeBSD CDs, how long do you think it would be until the FreeBSD Foundation picked up the slack? Or until Jordan Hubbard found a new employer who would do it for them?
  • the system architect who settled on VxWorks up and left when he realised we were screwed


    Wuss. Be a man, admit your mistake, and clean it up, that's what I say. That's why I am working on my plans to to migrate my project.
  • In what sense? In the "completely ironic and false" sense, the "Bill Clintonesque 'Define the word is' sense"? The "I don't know what I'm talking about but I like to hear my own voice" sense? The "I'm a /. troll" sense? Or the "WindRiver AstroTurf" sense?

    In my own experience (see my other comment in this thread) WRS has had terrible support, been generally clueless, and provided little or no value added to the world.

  • A VxWorks User... (Score:4)

    by wowbagger ( 69688 ) on Wednesday April 04, 2001 @06:41PM (#314674) Homepage Journal
    I have the misfortune to have specified VxWorks for a project I am designing. I am sorry, but I trust Wind River about as far as I can throw them.

    First, full disclosure. My project isn't the typical embedded project - it's large, it runs the X windows system, it uses TCL/TK, it has a good-sized hard disk. This is not exactly what VxWorks is targeting, and many of my problems stem from that. For a small project, it's probably good.

    OK, now for the dirt.

    1) I have NEVER, NOT ONCE, gotten any significant help on a problem from Wind River. This does not mean that they didn't try, but in the end every problem I ran into I ended up solving myself. For instance, when I was first building the system, I built it to load from IDE hard disk. I found out, after weeks of wasted effort and several calls back and forth to Wind River that the networking stack was disabled if you weren't booting from the network, unless you turned on an option that was not documented.

    2) We purchased the RtX server that Wind River sells. It turns out the X server won't work with the latest version of VxWorks. The version of VxWorks it does work with does not support DNS nor DHCP.

    3) The IDE driver doesn't use DMA, and the system does not understand partitions. I had to write the code to parse the partition table of the hard disk. And the lack of DMA sucks when you are trying to log a large amount of data to the hard disk.

    4) The VxWorks file system is DOS. They have a hack to support long file names, but that hack isn't VFAT. So, you cannot simultainously have long file names and compatiblility with any other OS.

    5) When we signed up with Wind River, we asked them as to when and if they were going to support development using Linux as a host. Since they already support Solaris, this SHOULDN'T be rocket science. We were told "within 6 months". That was two years ago. Guess what.

    6) The DOS file system has bugs where it tries to free() a static buffer. I don't have the source, I cannot fix the bug. RMS has a good point here.

    7) The X server only supports 256 color mode. The server is derived from XFree, but since XFree isn't under GPL, Wind River doesn't distribute the source. Therefor, I cannot build it to support TrueColor. I cannot change the keysyms (which would be damn useful since I have keys that a standard X server doesn't have.)

    8) On the StrongArm platform, they claim to support that chip, but they don't enable the on-chip cache, nor do they give you a good place to do so. Therefor, the chip runs at half speed.

    9) Their implementation of the TCP stack has bugs. They pass your driver a buffer you are to place the packet into, but they don't tell you that because of a bug in the driver, you have to place the packet at bufferstart+2.

    10) Their debugger does not run reliably on a network with a lot of traffic.

    Given my experiences with Wind River, I don't feel warm and fuzzy about their purchase of ANYTHING. As soon as I can convince management (and that won't be long) I will be porting my project over to Linux.
  • Tech: What kind of system is that?

    Admin: That's an ick systems box.

    Tech: Well if you don't like it, why don't you return it?
  • I guess at least BSDi wasn't bought by WindOws.
    I wish they'd pick up the company that makes the LVM tools too. It'd be cool to be able to run with softupdates, vinum, GFS, and the LVM tools.
  • I wonder how many of these problems stem from running on Windows?

  • yes, it's quite obvious why WindRiver is doing this: it's because they've quickly seen their market share shrinking because of Embedded Linux. developers love that they have all the source code to their embedded OS right there if they need it, and this is a big plus.

    Linux in the embedded market isn't taking off as quickly as it should however, and that's mostly because of the GPL. a lot of embedded hardware companies make hardware that's somewhat similar to the competition (especially networking markets outside of the network "core"), and software is their value-add. the problem, of course, is if they must provide the code to that value-add software, it doesn't give them an edge up on the competition for long. i have heard this concern from some companies, especially some of the larger ones (such as Cisco), and it's a very valid concern.

    of course BSD doesn't have the same GPL restrictions, and i believe that's why WindRiver is so interested. they can offer the same source-code level support as Embedded Linux without that nasty GPL restriction being passed on to their customers. as a result, it's a pretty easy sell against Embedded Linux. of course it's probably not as good for the industry as a whole (i still have a sneaking suspicion that industry-wide code sharing is good in the long run), but it does keep the Ciscos of the world happy.

    at any rate, VxWorks is an excellent operating system, and i think WindRiver will do a great job with BSDi. whether or not it will benefit the free software community remains to be seen, but it'll definitely help their bottom line.

    - j

  • But, as was asked when Walnut Creek/BSDI merged to form BSDi.....

    What will be the outcome for FreeBSD? Or PicoBSD?

    The intention may be good, but the execution is the thing.

  • What if they maim it and leave its disfigured body on the floor, next to pSOS and ISI?

  • As opposed to the present value of VA linux or RedHat vs their past value?

    How about the cancelled IPO's of Turbo/SuSE/Linuxcare?

    Looks like it is hard to find a way to make money when your primary product is given away free.

    Not to mention that making money in pure software isn't easy....unless you are microsoft.
  • Even though PicoBSD is a stripped FreeBSD....and "freeBSD will continue as before", PicoBSD is most like the space WindRiver is normally associated with.

    Will they kill Pico?
  • I hope not.

    It would be rather stupid of Wind River to kill off their only credible chance to play in the new market of $0.00 per unit for an embedded system that PicoBSD/FreeBSD (net and openBSD) and embedded linux represents.

    Wind River can still make money by adding value, and selling their development tools. They will just have to abandon the idea of getting $1.98 per unit sold. The only question is: Can Wind River let go of their per unit license for their code?
  • I thought that the job of Chief Evangelist already belonged to another Hubbard...
  • The ZDNet article [zdnet.com] talks about how Linux fans are defending the GNU GPL license over the BSD license.
  • the question was "how does linux/unix work with java. The answer was that java works well with all kinds of OS's.
  • With all the BSD enthusiats chiming in with "this ought to be great for *BSD", take a look at some fairly recent history with pSOS.

    pSOS is an embedded kernel (and all the various add-ons), formerly written and sold by "Integrated Systems, Inc" (ISI). A little over a year ago, Wind River purchased ISI. Only a couple months after the aquisition, they announced that pSOS would be discontinued. Maybe there's another explaination, but it appears that they purchased ISI to bury the competitive pSOS kernel.

    Only several months before this happened, I had started a little embedded project where I work, and we decided to purchase a kernel and TCP/IP stack. I spent about a week checking out the various vendors, and I investigated pSOS quite a bit, since some of our customers had some very successful products based on it. I also took a good look at Linux. I really wanted to use linux, but the truth is that it requires quite a lot of memory and a 32 bit chip, and I was hoping to stay with a 16 bit chip and smaller memory. Still, I started out with an absolute requirement that the vendor provide source code. ISI never provided (normal) customers with source, and Wind River is about as closed as closed source gets. I ultimately went with US Software [ussw.com], who provide source and have a product targeted at smaller systems. ATI Nucleus [accelerate...nology.com] was a close second choice. I utlimately obtained both vendor's API reference manuals, and USSW's were more down-to-earth (provided a much better conceptual model of what their code was doing) and they were easier to use. USSW's TCP/IP stack comes with two interfaces, the usual sockets interface we all know and love, and their own very light weight interface. If you use the light weight one, you can compile without sockets (saves about 12k code space). I needed to add a tiny feature to the light weight one, and within 1 day I was able to read through the TCP/IP stack source and understand it enough to add the thing I needed with good confidence I was doing it well. I made a similar addition to their kernel, in the space of about one day. With these small changes to customize their interfaces to my needs, I got my code running in only a few weeks, and I was able to produce a 16-bit x86 (real mode, yuk) executable image that was about 50k that included their multitasking kernel, tcp/ip stack, and my old single-task app converted to nicely run multi-threaded to serve multiple concurrent sessions, all running on very low cost hardware, AMD's Net186 Eval Board [amd.com]. Having the source code for whatever kernel you're using in an embedded project is a major advantage. Don't ever let those slimey salesmen tell you otherwise!

    Wind River (and the former ISI) are closed source. They put a lot of effort into sales and marketing, and they put quite a bit of effort into trying to convince me that it wasn't an advantage to have source code. Fortunately where I work the management is pretty sensible and doesn't presume to be able to evaluate kernels and network stacks. When it became obvious I'd never select them due to being closed source, they made a couple attempts to directly communicate with my managers, which raised a couple questions, but they trusted my judgement that having source code was critically important.

    I know of a similar group that had started a project based on the Netsilicon chip [netsilicon.com], which at the time was only supported by pSOS from ISI. Netsilicon provided source for their device drivers, but the pSOS kernel and stack were closed source. Well, there were a lot of really unhappy campers when Wind River bought ISI and announced they would bury pSOS, and Netsilicon and their customers were certainly not amused. Getting stuck with an obsolete object-only library that has a bug really sucks.

    So before anyone gets really excited about the great things Wind River might do for BSDi, take a little look back at the not-so-distant history where they purchased ISI and then almost immediately announced the death of ISI's core product, pSOS... with what appears (from my limited point of view) as an utter disregard for the installed pSOS customer base.

    An remember, these guys are closed source proprietary software. They spout all sorts of marketiod language about "total cost of ownership", "industry leading [insert word]", blah, blah, blah. They make some pretty impressive product offerings, yet there is no shortage of horror stories of someone who hit bugs or needed to add a feature and was absolutely helpless without the source code. I saw a good example of one of those stories above, and I hope it gets moderated up to 5 (though PHB's wouldn't ever read slashdot), having the source code can make all the difference between spending a day or two customizing/bug fixing and spending weeks of frustration on the phone and ultimately working around it somehow.

  • Wind River is committed to making proprietary extensions to Open Source code and then licensing it for big $$$. Wind River is committed to spreading FUD about the GPL in order to combat Open Source RTOS companies (http://slashdot.org/articles/01/02/22/0250200.sht ml). This is definitely a bad development for BSDi.
  • To see a company specialising in embedded systems embrace BSD like this is incredibly good news. Why? Because no matter how many servers there are, there will be 1000 times more embedded devices. This is the current battleground, and I would love to see FreeBSD steal some major marketshare in this arena.......

    That, and a constant, reliable source of funding for the FreeBSD project will ensure its dominance (flames anyone?) in the Open Source arena........

    God damn, its feel good to be a FreeBSD zealot right now. :)
  • You either try to gain market share in all areas at once (as Linux is doing), or you work on one industry at a time. FreeBSD serves as an excellent server platform due to its speed, and reliability. It only makes sense to take its strengths into the embedded arena, where speed and reliability are 2 crucial requirements.....

    I was not trying to say that FreeBSD should concentrate on embedded devices ONLY, just that it was an excellent direction to go towards. It will increase the diversity of the OS, and ultimately, recognition.

    In todays world, marketshare equates to mindshare.

  • This is real simple.

    An analogy. Imagine that the FSF and Linus Torvalds jointly decide that any futher development they make towards GNU software and the Linux kernel will be proprietary. Forget that they wouldn't ever do that, just realize that because they own the copyright they could. But sitting on your desk is a CD of your Linux distribution of choice. It contains all the source code, and that version of the code is under a free license. You could take all that source code and continue developing it yourself. It would not die, as long as someone was willing to keep it going.

    The same is true for FreeBSD. WindRiver could say that all further development they make to FreeBSD will be proprietary. But sitting on the desks of all the FreeBSD developers is a CD containing all the source code to FreeBSD, and that particular version of the source code is covered by a free license. They would simply take that source code and continue their project unhindered.

    And you can believe that if WindRiver turns out to be a bad host, the FreeBSD developers will do exactly that; WindRiver can't prevent them from taking their toys and going to play somewhere else.
  • Do you realize that you post this *EXACT* post every single time there is a BSD article? Crawl back under your rock and stop spreading FUD.

    Matt
  • Are you sure? Wasn't slackware spun off into a separate company when BSDi bought Walnut Creek?

    --

  • I suppose this means slashdot is dead too... seeing as how they were aquired by Andover and then OSDN... being bought isn't being killed... I use BSD and linux... open source OS'es are damn hard to kill, because they have loyal fans willing to carry on even if the funding and support stops... FreeBSD rocks my UNIX world... it's faster, more stable, and runs on machines with less than 128 megs of RAM... heck even /. had a post on that recently
    #set prompt = $user.$group @ `hostname -s`#
    root.wheel @ reality#
  • If anyone is interested... I will give you some ballpark pricing info on Tornado. It ain't cheap.

    We were looking into doing some development on the ARM. We were going to look at Tornado. We were going to get the Tornado 2.0 for all simulators and Tornado 2.0 for ARM.

    The development tools for Tornado was $13,500 plus $2,295 for a single runtime licence. The ARM cost was $7,015 for development and $3,505. That brings our grand total to $28,050.

    Also - that does not include the per seed licence royalties that you would need to pay to WindRiver for every machine that you embedded the code in. I don't know what this cost per licence is - again I heard that it ain't cheap.

  • Also - I forgot to mention that this cost is based on a per project basis. If you have another project that requires the same tools that you already have then thats just too bad. You must relicence the tools.
  • Whats worse, having all that legalese in there, or the company that gets sued because it isn't?

  • So, what happened to pSOS ??


    --
  • Windows is simply the development environment, along with Solaris (I think). The memory leaks come from bad code which has nothing to do with Windows. The tools are basically wrappers around the typical GNU stuff (gcc,gdb,etc.). Not everything can be blamed on Microsoft.

  • But I still wish this was an April Fool's joke. I mean c'mon 'iXsystems'?? How 'krad' does that sound.
    --
  • Slashdot actually does okay under the load considering that they actually use those things. I was actually surprised to hear them boast about the arrowpoints at all after their less than spectacular performance [slashdot.org] with them before, both in the load handling and the resulting customer service they received (the "Great DDoS" episode right about the time they switched toexodus).


    Fist Prost

    "We're talking about a planet of helpdesks."
  • If Wind River is going to "integrate" FreeBSD the same way they "integrated" PSOS, then you can kiss it goodbye.

    The FreeBSD Project exists as a separate entity from BSDi and Wind River. It is not going away. This is not "Wind River gained control over FreeBSD"; this is "Wind River gained control over a company that was doing FreeBSD work".

  • I don't think there's enough information to be either optimistic or pessimistic.

    BSDi has working with the FreeBSD Project quite closely, disclosing code which is being incorporated into FreeBSD 5.0. Now BSDi is under new management. What will be the new management's take on this? Will they leave this untouched? Will they make changes here? Good or bad? How much can they affect the FreeBSD Project?

    There's not much to do but sit and wait.

  • More info... (Score:4)

    by Autonomous Crowhard ( 205058 ) on Wednesday April 04, 2001 @01:11PM (#314704)
    Here [wrs.com] is the Wind River press release about the BSDi aquisition.Here [wrs.com]is the FAQ about the aquisition. The quote that probably is most important to the Slashdot community is:
    Q. What is Wind Rivers philosophy on open source technology?
    A. Wind River has always used open source technology. In fact, Wind River was the first licensee of the BSD network stack. The company supports the open source community and is committed to maintaining, distributing, and supporting FreeBSD. To spearhead that effort, BSDis Chairman of the Board Dr. Marshall Kirk McKusick, Vice President Open Source Technology & Chief Evangelist Jordan Hubbard, and Chief Technology Architect Michael Karels will join Wind River. Hubbard will continue to be responsible for the development and promotion of the FreeBSD OS as the release engineer for all FreeBSD products.

    Wind River feels that FreeBSD is an open source OS based on a rich heritage and solid technical foundation and offers great technology and sensible licensing terms to its community. With FreeBSD, the open source and business communities can drive the individual and industry standards for a UNIX-based OS.

    For additional info, here are the Yahoo [yahoo.com] and Reutuers [yahoo.com] articles. This aquisition is combined with Wind River's purchase [wrs.com] of Eonic Systems,a developer of high-performance software solutions for real-time embedded DSP application.

  • Do I smell an Apple IP lawsuit in the air?
  • This document contains "forward-looking" statements that involve risks and uncertainties that could cause actual results or outcomes to differ materially from those contemplated by the forward-looking statements. For this purpose, any statements contained in this press release that are not statements of historical fact may be deemed to be forward-looking statements. Words such as "believes," "anticipates," "plans," "expects," "will," "would," "look forward," and similar expressions are intended to identify forward-looking statements. There are a number of important factors that could cause the results of Wind River or Bids to differ materially from those indicated by these forward-looking statements, including, among others, risks detailed in Wind Rivers most recent Form 10-K and other reports filed with the Securities and Exchange Commission. Additional factors that could cause or contribute to such differences include, but are not limited to, risks relating to the consummation of the contemplated acquisition transaction, including the risk that stockholder approval might not be obtained in a timely manner, or at all. In addition, statements in this press release relating to the expected benefits of the contemplated acquisition transaction are subject to risks relating to the timing and successful integration of the technologies of Wind River and BSDi, retention of key personnel, the ability to maintain or expand existing relationships between BSDi and its customers, unanticipated expenditures, changing relationships with customers and suppliers and other factors.

    Have things really got to the point where you have to give a lawyer a living by adding this sort of bullshit to the end of a press release?

  • This is probably more of a Good Thing (tm) for BSD than a Bad Thing. The Wind Rivers has always been a great company to deal with (I have worked quite a bit with vxWorks) and they will be able to scrounge up interest in BSD (which is much needed). As far as I understand vxWorks is basically the industry leader in RTOS's, so it's a company that will be around for quite awhile and gives BSD some security.
  • pSOS was the main competitor to VxWorks, until Wind River bought it. They let it sit for a year or two, then decided to kill it off. At the Embedded Systems Conference last fall I bitched about this in the Wind River booth, the guy said they were reconsidering that decision. Later investigation shows pSOS is still alive.

    But.

    I don't see anyone using it anymore. And if I were starting a new project I don't think I'd choose an OS when the sole reason the vendor is behind it 100% is to make it easier to insert the knife.

  • vxWorks, the embedded OS that runs our great Arrowpoint Web Content Switch we have here at OSDN

    If there's one endorsement you'd think companies wouldn't want, it's to be known as part of the system that serves Slashdot. It's baffling to me how that a systems company could be so oblivious to the performance of the flagship site in its web content division. Doesn't VA realize how bad it makes them look?

    Unsettling MOTD at my ISP.

  • Wind River's committment to Open Source if iffy (Score:3)

    by n7lyg ( 219105 ) on Wednesday April 04, 2001 @01:27PM (#314710)
    I cannot help but be worried about the Wind River purchase. At least, when BSDI purchased Walnut Creek, there was the feeling that they at least had some connection to the Open Source community through the shared BSD heiritage. Now, Wind River has absolutely no committment to Open Source, since the entire premise of the company is selling proprietary software. Also, they have a very bad track record with previous acquisitionns (rememer pSOS and ISI?) Even though they have Hubbard and Karels and McKusick as talking heads saying good things, exactly how long will the good feelings last? According to the article on Yahoo!, the reason WRS did this was to try to force more people to use their proprietary tools, not to promote openness.
  • Although I thought that the BSDI merger was okay, I'm not so sure about this latest merger is a good thing for FreeBSD. That said, it's important to remember that *all* walnut creek was doing was distribution for FreeBSD, like Infomagic does for the Linux distributions. BSDI and now Wind River are just the company pressing the official CD, and running the ftp servers. If things don't go well, I suspect the FreeBSD team will go shop around for a company more reponsive to the goals of the FreeBSD development team. Like Linux, no company *owns* FreeBSD. It's a community driven software project like the Linux Kernel (although different licensing of course.) Anyway time will tell.
  • FreeBSD went out of business and was taken over by BSDI who sell another troubled OS I know this guy is just a troll, but it shows how little they know of the subject matter. FreeBSD went out of buisness? it isn't EVEN a buisness!! Arghh! Good trolls at least get the facts straight!
  • I think your questions are very well answered in the press release, BSDi code will continue to be merged into FreeBSD as before. I am hoping this is not just a statement to keep us from flaming them to death, but it makes sense
  • " It's a community driven software project like the Linux Kernel (although different licensing of course.) Anyway time will tell." not exactly. whereas for linux, you can send in patches to the kernel, you can't do so with bsd. *bsd is maintained by a group of people and not the community.

    --
    Tres_Status
  • Just ask pSOS customers what the future of pSOS became when Wind River bought ISI... --Blair

  • I can confirm most of these points. Wind River can't support the system it's currently selling; how on earth do they expect to be able to support a whole new OS when they're sacking half the BSDi staff?

    As an aside, the system architect who settled on VxWorks up and left when he realised we were screwed, and we're now looking at moving to Linux for future versions, on the basis that we'll get way more support for zero cost. Go figure.

  • I was just on the Wind River conference call for investors/mediapeople/etc and a 'personal investor' asked "What are the plans to make FreeBSD support javascript?" I just thought some of you could use a laugh. =)
  • I'm highly concerned about this purchase. In my opinion, as a regular BSDi customer, I don't want them to change in the slightest. They offer the best/most knowledgeable/fastest customer service I've seen. Their sales staff are extremely knowledgeable, their tech support staff is quick and clued. And just when I thought I've found the perfect server vendor...
  • Keep in mind, pSOS and VxWorks were virtually identical in functionality after years of competing against each other for the same business. It doesn't make sense in the long run to cover the same market with 2 identical products, right? FreeBSD as an open-source unix is significantly different than VxWorks, so it makes sense to put ongoing effort into both, and that's what will happen.

Slashdot Top Deals

A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson

Close