Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
BSD Operating Systems

Sun vs. OpenBSD? 279

An anonymous reader writes "CNet has an article up about OpenBSD trying to get documentation for Sun's UltraSparc-III processor. Basically Sun is giving them a bit of run around....There is some documentation available for the processor, but not enough to get things to boot."
This discussion has been archived. No new comments can be posted.

Sun vs. OpenBSD?

Comments Filter:
  • Not surprising (Score:2, Interesting)

    by Anonymous Coward
    And why exactly should Sun open up the specs for competition that prices its products at $0 without at least getting a headstart with Solaris?
    • It has traditionally been a selling point for Sun that there technologies are based on open specifications, reducing the risk of a vendor lock-in.
    • Re:Not surprising (Score:2, Insightful)

      by Anonymous Coward
      Because if you'd bother to actually *READ* the article about this you'd see that they have already provided the Linux team with enough information to get it running, but won't give the OpenBSD team the info that they need.

      Keeping a step ahead of opensource with Solaris isn't an issue.
      • Re:Not surprising (Score:5, Interesting)

        by mike_the_kid ( 58164 ) on Thursday December 05, 2002 @10:39AM (#4818062) Journal
        The linux team apparently approached sun to show them the specs, Sun said "sign an NDA or no deal." Linux team signs, code goes under the GPL.

        OpenBSD team approaches sun, Sun said "sign an NDA or no deal", OpenBSD says no, thats against the spirit of our project and the BSD license.

        The interesting thing is that here the code is being used in an open source project (linux), but OpenBSD will not make use of it, because they respect the intent of the GPL.
        • Re:Not surprising (Score:5, Insightful)

          by jbolden ( 176878 ) on Thursday December 05, 2002 @11:10AM (#4818232) Homepage
          GPL code can't be taken into a commercial product. Sun may not be as worried about GPL code as BSD code. IBM for example could take information from BSD code and wrap right into AIX without disclosure. That isn't true for GPL code.

          Further nobody actually knows what the Linux guys got.

        • Re:Not surprising (Score:2, Interesting)

          by doug_wyatt ( 532721 )
          Once the info is out in GPL for Linux, can't the OpenBSD folks "steal" the knowledge from it? GPL protects the literal code (i.e. copyright) not the ideas contained within it. In the same sense that I can read your GPL'd code and re-implement it under the BSD license (or a comercial license), it would seem they could do the same with this.
        • Re:Not surprising (Score:3, Interesting)


          The interesting thing is that here the code is being used in an open source project (linux), but OpenBSD will not make use of it, because they respect the intent of the GPL.


          It's right proper that the OpenBSD team doesn't want to run afoul of the GPL, but the GPL doesn't prohibit learning. The OpenBSD team should be able to derive a state machine from the Linux code, which would work like the UltraSparc, then program the OpenBSD code against the reverse-engineered state machine, without ever seeing UltraSparc specs, and certainly without ever copying GPL'ed code. It's likely to be sub-optimal, of course.
        • With regards to taking the code from the Linux folks, it's not only a matter of respecting the GPL (if that was even a factor) but more a matter of correct coding. How can the OpenBSD folks be sure Linux code is implemented correctly, per the specs of the documents Sun gave them? They can't, without the documents.

          This was discussed in some OpenBSD mailing lists. It's not only a matter of making the code 'work' on UltraSPARC III systems, but a matter of making it work _correctly_ and robustly. To do that, they need to read the specs.
      • The question we ought to be asking is "Who at Sun did Theo piss of now?!?".
  • Yes .... (Score:5, Informative)

    by Rubbersoul ( 199583 ) on Thursday December 05, 2002 @09:12AM (#4817664)
    much like this article [slashdot.org] from the other day.
  • NDA?? (Score:5, Insightful)

    by countach ( 534280 ) on Thursday December 05, 2002 @09:15AM (#4817678)
    How can it be you need an NDA to get the specs? Wouldn't the cat be out of the bag as soon as someone released source code based on the specs? The best doco for hardware after all is source code that implements the spec.
    • Re:NDA?? (Score:3, Informative)

      by sheriff_p ( 138609 )
      Please read the article. Theo says they've tried, can't really deal with it. But, before you make any comment about the abilities of the OpenBSD programmers, you might want to check if you're using OpenSSH...
      • why did this get modded flamebait???
        They are professional programmers, they made an attempt with *all* available docs and they couldn't do it. Sheriff just mentions that they are no amateurs citing OpenSSH as an example of why they are not. They have strict goals and policies regarding their OS and the project as a whole. Just because they don't bend over...
    • ``The best doco for hardware after all is source code that implements the spec.''
      I can hardly agree with you there. Granted, cleanly written code can be a great boon, but definitely not all code qualifies as such. Some people write things that come close to cryptography! Besides, I am guessing that what they're looking for here is machine dependent, and thus probably at least partially written in assembly, which is almost by nature hard to decipher. (I think the same is true of my comment - I've been reading a lot of philosophy today).

      ---
      A large number of installed systems work by fiat. That is, they work by being declared to work.
      -- Anatol Holt
  • We all have a love/hate relationship with Microsoft (okay, mostly a 'hate' one for Slashdotters) but at least they don't control the architecture, OS, and CPU for the Windows platform.

    Sun even go beyond Apple's level of control, since IBM/Motorola develop the CPUs there, so that documentation is somewhat easier to get.

    Sun has the potential to be the biggest monopoly of all the big technology companies, yet their products are rapidly losing market share. Why? I think companies these days don't like buying into closed architectures. So I think open source supporters should stop calling for companies blood, and instead let the market decide who's best.

    Remember, Microsoft were popular in the 80s exactly for their open architecture.

    In 1991's "Challenges and Strategy" memo, Bill Gates said, Our applications have always succeeded based on their own merit rather than on some benefit of unfair knowledge of system software. We need to explain our hardware neutral approach and the benefits that has generated for end users. We need to have visible events on a regular basis where we solicit the input of anyone who wants to influence our future direction. If we can institutionalize a process that the world feels comfortable with, we will strengthen our position incredibly. This is going to require a lot more creativity than even the "Open Forums" we are discussing. UNIX has OSF and X/Open -- we also need clear ways for organizations of all types (hardware, ISV, IHV, corporation, universities) to feel like they have something invested in our approach and can affect our course.

    Do you see Sun being open? No. So, again I say, let the market decide. It's no wonder that open source is becoming the next big thing in corporate land.
    • by sql*kitten ( 1359 ) on Thursday December 05, 2002 @09:35AM (#4817749)
      Sun has the potential to be the biggest monopoly of all the big technology companies, yet their products are rapidly losing market share. Why? I think companies these days don't like buying into closed architectures. So I think open source supporters should stop calling for companies blood, and instead let the market decide who's best.

      Nice troll. From the SPARC International FAQ [sparc.org]:

      All technical information about the architecture is available for free and without royalties from SPARC International's public website. Anyone is welcome to download the SPARC specifications, which provide all of the technical requirements needed to design processors and other products based on the open SPARC standard.


      And


      • The SPARC instruction set is published as IEEE Standard 1754-1994.
      • SPARC specifications are available for licensing by any person or company, giving customers flexibility and freedom to design their own solution.
      • Control of the SPARC architecture is in the hands of an independent, non-profit organization, SPARC International, whose membership is open to everyone.

    • > We all have a love/hate relationship with Microsoft (okay, mostly a 'hate' one for Slashdotters) but at least they don't control the architecture, OS, and CPU for the Windows platform.

      That's not true. Microsoft, along with intel, steers
      most committees that come to agreements on how
      many pieces of hardware work. It also has a lot
      of de facto power. Look at your keyboard.
      • Indeed; I still remember a time when PC keyboards didn't have Windows keys on them. I was thinking about that just the other day, in fact.

        More than that, though, don't forget that most video card manuacturers work closely with Microsoft to ensure that their new chipsets support the features being implemented in the latest/next release of Direct3D. Of course this is a two way thing - I've no doubt that both parties say "we've this really cool idea that we need you to help us with...", but that doesn't diminish the influence they have on each other.

        At the end of the day, if a feature supported in hardware doesn't make it into Direct3d, it isn't going to be (widely) used. (The same is true, to a lesser extent, of OpenGL, of course)
      • I'm looking at my keyboard -- or I was before I started typing.

        It says IBM up at the top right. It make a delicious clickety-clack when I type and across the bottom I see Ctrl, Alt, Spacebar, Alt, Ctrl, Arrow keys, 0, ., Enter.

        It is one of my most prized possessions...

        I only wish I had a keyboard for my Mac with the "Open Apple" and "Closed Apple" keys. Now those were sweet!

    • We all have a love/hate relationship with Microsoft (okay, mostly a 'hate' one for Slashdotters) but at least they don't control the architecture, OS, and CPU for the Windows platform.

      What?! Microsoft doesn't control the OS for the Windows platform?
    • How are you defining "rapidly loosing market share"? Most of the market analyses over the past 2 years have shown Sun gaining market sharein Unix server and workstation shipments against IBM, HP/Compaq, SGI, et al.

      In the high-end market place, where Sun makes most of its money, Linux and OpenBSD have hardly any market share and UltraSPARC pretty much rules the roost in market share terms. In the mid-range there is some pressure from Linux, but mid-range Unix servers equate to highest-end Lintel boxes, and at those price points the cost of the OS is marginal to the overall cost. At the low end, yeah there is market pressure, but mostly because Linux is increasing the size of the low-end Unix marketplace and this is a "Good Thing"(tm).

      So what happened in this case? OpenBSD got caught in the beaurocracy most likely. If the upper management had heard about it then something might have been done, but remember that like most Tech companies Sun is struggling in a tight marketplace and trying to make a little bit of money. They've just lost, what, 25% of their workforce in the last couple of years and we wonder why there is no slack to look after what was probly seen as a low-priority request from a project that contributes only a small amount to Sun's bottom line.

      BTW - Sun generally don't make money on the OS - you have to have over 4(?) CPU's in the box before there is any charge at all, and even then it is free with all Sun hardware even with 72 processor boxes.

      Sun makes money on the hardware, not the OS it runs on, so just why should they want to actively try and stop OpenBSD? The article itself even pointed out a case where Sun was LOOSING sales because OpenBSD didn't run on the better (more expensive) boxes the customer wanted to buy.

  • For more info see this previous /. article from the BSD section that didn't make it to the main page here:
    http://bsd.slashdot.org/article.pl?sid=02/11/26/19 13211&mode=flat&tid=122 [slashdot.org]
  • by natron 2.0 ( 615149 ) <ndpeters79@gmai[ ]om ['l.c' in gap]> on Thursday December 05, 2002 @09:19AM (#4817696) Homepage Journal
    I agree completely with Sun on this one. They have to make a buck, and when a free OS comes along wanting to utilize its systems and take away from its revenue. I work with Sparc 10 systems everyday, and I have come to love the Solaris system, it is pretty flawless and is specifically designed for the Ultra Sparc architecture. Plus, many people the utilize the Sparc Systems with Solaris use specifically written programs for the Solaris systems and are designed in house, this OpenBSD system could be hell on those programmers and Sys Admin.

    • by sql*kitten ( 1359 ) on Thursday December 05, 2002 @09:32AM (#4817732)
      I agree completely with Sun on this one. They have to make a buck, and when a free OS comes along wanting to utilize its systems and take away from its revenue. I work with Sparc 10 systems everyday, and I have come to love the Solaris system, it is pretty flawless and is specifically designed for the Ultra Sparc architecture. Plus, many people the utilize the Sparc Systems with Solaris use specifically written programs for the Solaris systems and are designed in house, this OpenBSD system could be hell on those programmers and Sys Admin.

      But Sun don't many any money from Solaris, it's just the stuff you need to run your apps on Sun hardware. Sun are a hardware company first and foremost.

      Secondly, Sun don't even own the UltraSPARC, certainly not in the same way that Intel own the Xeon - see the SPARC International [sparc.org] web site. SPARC is about as close as you can get to an Open Source processor.

      From reading the article, it seems that Sun simply didn't have anyone looking after the BSD community like they had looking after the Linux community, and when the matter was brought to their attention, they assigned someone to do the job.

      Of course, anyone who pays $$$ for modern Sun kit is an idiot if they want to run anything other than Solaris on it, because Solaris, as well as being a solid and powerful Unix implementation in its own right, is designed from the ground up for SPARC hardware, it doesn't have to make any compromises for compatibility's sake. That's why NetBSD is generally slower than FreeBSD, it deliberately avoids anything too platform specific, and performance suffers as a result.
      • by bsdbigot ( 186157 ) on Thursday December 05, 2002 @10:04AM (#4817879) Journal
        True, SPARC International does publish (for meager $$) a SPARC reference implementation. The reference is essentially the minimum specifications for a processor to qualify as a SPARC. Unfortunately, this information is not implementation specific, and critical components of the overall CPU architecture, such as the MMU, change frequently with each implementation - these are the performance enhancements that SME makes to the base SPARC.

        In many of the older versions of the SPARC specification, the actual SME implementation was close enough to the published spec to get a workable system. At least one implementation, though, was different - the SPARCserver 470 and it's peers used a totally different MMU scheme, and thus there is (to my knowledge) no working BSD/Linux for these systems to this day.

        What Theo's fighting for is the actual implementation information. And, for all the buggering that he gets, you have to admit - he is consistent and has an unwavering conception of open source software; I never thought I'd see the day when a Linux geek would say "just sign the NDA and shut the fuck up." Theo has a little more integrity than that.
      • by dohcvtec ( 461026 ) on Thursday December 05, 2002 @10:36AM (#4818040)
        anyone who pays $$$ for modern Sun kit is an idiot if they want to run anything other than Solaris on it
        I can't speak for everyone, but it seems that things are usually the other way around: Sun hardware is a great platform on which to run OpenBSD. It's not as if "I have this SPARC machine, what OS should I run on it?" Rather, it's more like "I would like to run OpenBSD, what is a good hardware platform to run OpenBSD?" The 32-bit SPARC port of OpenBSD happens to be very mature and stable, and SPARC hardware (especially sun4m) is bulletproof. Now that the OpenBSD sparc64 port is moving further along, the developers really need official documentation to make progress. But to the OpenBSD developers it seems that Sun is ignoring them. IMO I would give it some time, as Sun is a large corporation, and things take time. Especially if Sun did not already have corporate policy/plans for relations with OpenBSD.
        • by Zapman ( 2662 ) on Thursday December 05, 2002 @11:35AM (#4818383)
          From the article:
          University of Alberta's Bob Beck said he is forced to buy out-of-date UltraSparc II-based E450 servers instead of newer UltraSparc III-based V880 machines for the university's SunSITE software exchange.

          This seems odd to me: 1) OpenBSD doesn't support SMP yet, right? 2) v880's must have multiples of 2 CPU's (up to 8).

          Sunsite might be better off grabing some of those 1U v120's, throwing a dual channal diff scsi card in there, and using an a1000 array (or maybe a t3 array... with only 1 cpu you probably need the hardware raid these offer rather than the d1000's or a5200's). More disk, less rack space, less power.

          Now, the v880's rock. Great price point, 8 cpu's, 2 FC-AL planes for a total of 12x73 gig disks, 10 PCI slots (2 x 64bit/66MHz), onboard gigabit fiber... the list goes on. It's a great box (for more details, hit up store.sun.com, select servers, find 'low end servers', and select the v880. And note that that's 'list price'. You can get up to a third off of it from most resellers)

          For reference:
          4x itanium 800MHz dell 7150: 8x73 gig disks is $61,113.00.
          4x usIII 900 MHz sun v880, 6x 73 gig fcal disks is $59,995.00

          (That's the closest 'apples to apples' match I could make. I chose itanium vs usIII because they're both true 64 bit chips. Though the expansion of the Dell isn't as nice... the sun can add 4 more proc's and 6 more disks. The dell can add more memory... 32gig tops the sun v880, and 64 gig the dell)
    • Perhaps read the article. Theo finds is particularly jarring that they claim to be all open and good, yet still play at silly buggers when it comes to proving that.
    • I agree completely with Sun on this one. They have to make a buck, and when a free OS comes along wanting to utilize its systems and take away from its revenue.

      Sun is a hardware company, not a software company. The student version of the Solaris OS used to be $10 and they don't really check whether you're a student or not. On the other hand, I had to pay $40 for a set of CDs for my free OS.

  • Not the whole story (Score:5, Informative)

    by jki ( 624756 ) on Thursday December 05, 2002 @09:19AM (#4817698) Homepage
    I think the /. article gives too bad image about Sun, if you do not read this also:

    But Sun didn't put its open-source community liaison officer, Danese Cooper, in touch with de Raadt until after CNET News.com informed the company of his dissatisfaction. Cooper is "already well-known in the open-source software community," Sun representatives said. But the company acknowledged it needs to improve its work with open-source groups, saying the task would be addressed "within the next few weeks. Cooper has been responsive and is pressing the OpenBSD case within Sun, said de Raadt, but he's reserving judgment until he gets what he needs. "

    It seems they are now working very actively to solve the problem.

  • NDA (Score:5, Informative)

    by shin0r ( 208259 ) on Thursday December 05, 2002 @09:32AM (#4817734) Homepage
    Over the last few weeks this argument has been raging. I've lost count of the number of IRC conversations I've had on ircnet #openbsd, and here's my take on the options presented to the OBSD developers.

    1:If the OpenBSD crowd want the docs, sign the NDA. Linux developers did this. It's not that big a deal.

    2: Look at the Linux source for hints. This surely isn't too difficult.

    Why are Sun not willing to make the relevant docs fully-disclosed to anyone who wants them, sans NDA? In part, the answer is simple: The USIII / III* proc is still pretty new. Solaris doesn't yet fully implement all the chipset features, but will do in future releases. Is it a good idea for Sun to open the proc docs to any Tom, Dick or Harry, including other chip manufacturers, at this stage? Probably not.

    There's been a lot of negative talk propagated by the OBSD community regarding this issue. Classic "blame the faceless multinational" diatribe that most of us grew out of in our teenage years.

    Access to the information the OBSD developers have requested is a privilege, not a right. They want to build a kernel around the USIII, which is great, but the rules have been set by Sun, and are quite clear. Deal.

    (Yes, I do work for Sun btw)
    • Re:NDA (Score:5, Informative)

      by ostiguy ( 63618 ) on Thursday December 05, 2002 @10:12AM (#4817921)
      Linux developers in general have a loose take on legalities and freedom. NDAs are incompatible with the devout interpretation of freedom and the BSD license that the OpenBSD project is built on. While this can mean that some features must go (VRRP, Sun's ECC code), it means that OpenBSD is the safest OSS OS to build on for protecting oneself from legal hijinx.

      And again, the reason that this is a story is because Sun claims they are the open alternative to MS.

      ostiguy
    • Re:NDA (Score:3, Informative)

      by Ded Bob ( 67043 )
      1: If the OpenBSD crowd want the docs, sign the NDA. Linux developers did this. It's not that big a deal.

      I believe that Sun has not offered OpenBSD the NDA to sign.

      2: Look at the Linux source for hints. This surely isn't too difficult.

      Theo wants to take advantage of some special features in these chips that Linux is not currently using, therefore, the specs are required.

      Access to the information the OBSD developers have requested is a privilege, not a right. They want to build a kernel around the USIII, which is great, but the rules have been set by Sun, and are quite clear. Deal.

      Sun gave the specs to Linux under an NDA. OpenBSD wants to play by the same rules.

      I am mostly in the FreeBSD world, so my answers may or may not be accurate.
  • by dnaumov ( 453672 )
    I don't quite get it, I really don't. Why do people make such big noise out of this ? Apple doesn't seem to release their low-lvl documentation, IBM doesn't do that either. So if that's the norm, why make such a big noise about SUN ? What's making me wonder even more is why can't you (*feels being moderated down*) just stick to PCs and Macs ? If you NEED SUN, you probably need it because of their OS and services. If you don't, the door is open and the choice is big.
  • Good oh-penBSD (Score:3, Insightful)

    by dazdaz ( 77833 ) on Thursday December 05, 2002 @09:34AM (#4817745)
    The long term implications of an Ultra secure operating system based on Sparc hardware is a very interesting one. A whole new niche market could be opening up here. More interestingly, this will be I believe one of the steps needed towards the Fortune 500 moving to OpenBSD. It's just a matter of time, before their emphasis on security is doubled, or tripled from what it presently is as industry continues to move online and companies increasingly continue to protect their assets especially due to tight profit margins. I can see paranoia becoming the default at long last and a thirst for highly secure systems.

    I've already seen a couple of financial institutions use OpenBSD. Would be interesting to see figures for real world present usage by industry.

    Rock on OpenBSD.
    • that and decent mp support in openbsd...

      almost no point running it on "enterprise" h/w if it can't take real advantage of the scads of processors most places put in a single box.
  • Other OSs (Score:3, Interesting)

    by Apreche ( 239272 ) on Thursday December 05, 2002 @09:36AM (#4817753) Homepage Journal
    How come other OSs (not just Solaris) seem to have versions for UltraSparc. I know for a fact that Mandrake has a version that works fine on UltraSparc processors. I'm pretty sure BeOS can, and that many other linux/unixes can. I used to know a guy who had DOS running on a sun machine. If everyone else doesn't seem to have a problem why does BSD?
    • Re:Other OSs (Score:4, Informative)

      by asdfx ( 446164 ) on Thursday December 05, 2002 @09:42AM (#4817777) Homepage
      OpenBSD has support for UltraSparc I's and II's (as well as the non-UltraSparc's). There was significant enough change in the way that the UltraSparc III's work that the OpenBSD team can't figure out how to get it to boot. The reason Mandrake works is because Sun already released the documentation to the linux guys under a Non Disclosure Agreement of some sort (The legality of of Open Source and a NDA makes me laugh). I don't know BeOS well enough to say much there, although they weren't mentioned in the article, so I doubt they can use the Ultra III's. I would wager the same holds true for DOS. Anyone know enough about BeOS?
    • Read the article, OpenBSD does work on USI and USII machines, it is specifically the USIII that they are having problems with. And it also states that Sun had given the Linux clan some info under NDA about USIII that has allowed Linux to run properly. BeOS on Sparc? I haven't heard of that port? Unless your comment about DOS also implies that they were using the DOS compat. cards that Sun has (or even worse, running on the old i386 machines)
      • BeOS doesn't run on anything less than Pentium MMX, by design. openbeos.org might change this, some day, but then that won't be called BeOS anymore.
        • At which OS version did they officially drop support for BeBoxen and Macs? I still have OS cd's floating around here somewhere, but haven't looked at BeOS in four years or so.
          • It was Jan 2000 they dropped support for PPC, so that makes it Release 4. I think BeBoxes were supported as long as PPC was.
          • They never stopped support for BeBox and Macs. The only thing is, the only supported macs are the PowerMacs with the 60x and PCI bus. You should check the HW compat list. In a way, it's the Macs that stopped being supported.

            However, if you have a G3 or G4 daughterboard in one of those PowerMacs, BeOS will utilize them, with lots of speedy delight ;->
            • Thanks for the info. One of these days I'll have to put the BeBox back together and load a newer version (The last one I saw was still pre 1.0) and see how it looks.
    • Can I have some of that crack you're smoking, please? Unless I am grossly misinformed, there was never a build of BeOS for any architectures other than PowerPC or x86.
  • by Alioth ( 221270 ) <no@spam> on Thursday December 05, 2002 @09:42AM (#4817781) Journal
    I thought the SPARC processor was supposed to be an open architecture? It is according to Sparc International [sparc.com] - surely if the Sun SPARC processors don't meet the SPARC specification, they aren't SPARC processors any more?

    Or is it not the actual processor - but support hardware/boot rom issues that they are having a hard time getting information about?

  • OpenBSD Journal (Score:3, Informative)

    by Karamchand ( 607798 ) on Thursday December 05, 2002 @09:45AM (#4817794)
    You also might be interested in this OpenBSD Journal article [deadly.org] about the same subject. Usually the discussions about the articles are very insightful on deadly.org
  • by jdreed1024 ( 443938 ) on Thursday December 05, 2002 @09:50AM (#4817812)
    From the article:
    Sun has now promised to give OpenBSD the same information it provided to higher-profile, open-source projects such as Linux. "Sun has committed to working with OpenBSD to...ensure they are extended the same information as other open-source communities," the company said in a statement. (boldface added)

    So really, Sun wasn't hindering the Open Source movement. They already gave the information to the "Linux project" (presumably that means Linus or one of the other kernel hackers) Really it's just that OpenBSD didn't have the documentaton. Big fucking deal. Yes, it sucks that they were overlooked, but really, you can't claim Sun is trying to stifle the Open Source movement by giving stuff to Linux and not OpenBSD.

    I understand that this guy's hardball tactics have worked in the past, and seemed to work here, but really, that's not the right way to go about things.

    Most activists screaming for every corporation to release all code and programming guides don't understand history. In the beginning, personal computers were mainly for hobbyists. They all came with programming documentation, and some even came with full schematics. Then they became commercial, but still the companies were fine about providing technical information to thos who wanted it. I recall one of my earlier video cards came with programming docs, as did an early Adaptec SCSI card. Then competition began to get more cut-throat. The next big feature in your sound card was what could make or break your company. Damned if you're going to give it away to some pimply-faced kid who may or may not be working for the competition.

    The big corporations have been in this mindset for almost ten years now. It's going to take them a while to get out of it. The current economics models these companies have crash and burn when confronted with Open Source. This does not imply that Open Source is bad, rather that it's unexpected. It's going to take some time for public sentiment to overcome the marketing and accounting drones, who suddenly see nothing but a bunch of red numbers in their "total" columns. Most companies have already made gestures of goodwill by opening up a lot of programs. Think how much you had to pay for an Office Suite before OpenOffice/StarOffice. Any idea how much Transarc AFS cost before IBM bought them and released OpenAFS? I could go on and on, but I need to go to work.

    The point is, as I've said before, and will continue to say, you can't say "You must do foo" to a corporation, because they'll laugh at you. Most people don't like being ordered around, let alone corporations. The right thing to do (which was eventually done here) is get press coverage and let the people know that ACME Corp has not responded to your (polite, not bitchy) requests for documentation. Chances are they probably lost the request anyway. (Do you know how much bureaucracy exists in large corporations? It's amazing they get anything done to begin with.) The point is, leaders of Open Source projects may have done wonderful things and contributed tons of ideas and programs to the community, and benefited the world as a whole, but still proprietary source code is not a God-given right. Maybe it should be, and maybe in the future it will be, but not right now. Once that is realized, relations with corporations will get much, much easier.

    • Its not about source code, as if it were, OpenBSD couldn't use it anyhow, a la the Sun ECC code for OpenSSL, which carries some patent limitations that makes in incompatible with a strict constructionist BSD license interpretation (a la Open, and not Free or Net). Its about documentation, which they asked for repeatedly. The *reason* this is a story is because Sun runs around claiming openness. If this were about an IBM or HP chip, it wouldn't be a real story, as Sun is the leading drum beater about how open they are in comparison to MS.

      ostiguy
  • Sparc, BSD (Score:5, Insightful)

    by dhall ( 1252 ) on Thursday December 05, 2002 @09:57AM (#4817841)
    Theo said he would prefer to run openbsd.org on Ultrasparc architecture, since it provides certain levels of hardware security, from following the thread on the BSD forums.

    He's not exactly the easiest person to get along with, but to be honest, this is on par for Sun's dealings with the Open Source commnuity. Sun at times deals with the community like Digital did back in the day. And like Digital, I can honestly see Sun fading into the sunset, from an operating system perspective.

    AIX / HP provide the enterprise level OS's, with several features that are not found in the core of Solaris. AIX with 5.2 has attempted to bridge the gap with Linux, in providing a common environment shared with Open Source applications, including having RPM's integrated with their own package management (as a side note, AIX's LPP package management is more sound then RPM's, IMHO).

    Linux has been edging into the low-to-mid end market, even stealing Sun's thunder with Oracle buy-in. Sun is being squeezed in the middle, and must decide whether they want to focus on the high-end enterprise, or the middle tier web/app/database servers.

    AIX has it's association with Websphere and DB2. Sun has to decide whether it's operating system is worth the cost, or whether they are a hardware company. Unfortunately as long as companies feel they must only run specific OS'es on their Hardware (Apple), they will continue to relegate themselves to a niche market that is ultimately self-limiting.

    IBM still has the monopoly on Z-series Mainframes (Amdahl pulled out of that market). Their philosophy has always been expensive hardware, cheap to free software, and hefty support and services contracts. They make their continued money through licenses and services.
    • Re:Sparc, BSD (Score:2, Interesting)

      Linux has been edging into the low-to-mid end market, even stealing Sun's thunder with Oracle buy-in. Sun is being squeezed in the middle, and must decide whether they want to focus on the high-end enterprise, or the middle tier web/app/database servers.

      yes and no. Oracle and Solaris/sparc still make for very large database servers - and you get support for it - at a cost of course. Sun has also made inroads into Linux, releasing it's own distribution (I know it's a rebadged redhat, but it's a start - and Sun's tech support will support both their linux distribution and Solaris directly).

      AIX has it's association with Websphere and DB2.

      Sun has it's association with iPlanet.

  • by Daniel Phillips ( 238627 ) on Thursday December 05, 2002 @10:38AM (#4818056)
    I have a similar problem with Adaptec. I'm trying to get register-level specs for their AIC-7xxx series of scsi chips.
    On their Linux page [adaptec.com] they claim to support open source:

    We have launched a dedicated Web site to provide a repository of
    information for our open source solutions, including:

    * Our latest Open Source drivers
    * Technical documentation
    * White papers
    * FAQs

    But in fact there is no technical documentation available beyond lightweight lists lists of features and general hardware type. Directly contacting Adaptec, I get nowhere without a product serial number, which of course I don't have because the chips are embedded in an OEM motherboard.

    So maybe I'm just not talking to the right person, but it does look like the company is saying one thing and doing another.

    To be fair, the driver support for Linux is good. Drivers are developed by an Adaptec-sponsored group [freebsd.org] and provided in source form. These drivers are in the mainline 2.4 and 2.5 source trees. This is a far better performance than, for example, NVidia, whose drivers are well-known for breaking every few kernel releases because of their binary-only nature. Still, it's not enough. It seems to me Adaptec is just shooting themselves in the foot by keeping the low level interface specs closed. If they continue to do that, they will certainly be knocked out of the market by other hardware that's better understood by kernel hackers, for which both low and high level optimization can be done by lots of developers. That's exactly what I'm trying to do with their chips, and to be frank, I'm doing it only because I happen to have one available to play with at the moment. But I'll move on without hesitation as soon as something shows up that gives me more scope for interesting optimizations. I'm just not one of those people who enjoys reverse-engineering, though I have immense respect for those who do.

    The way things are, the Adaptec guys who develop the Linux drivers can do plenty of low level optimization based on things that only they know about the hardware, but who will listen to them if they want changes in the core kernel for better support? Plus, who wants to invest in hardware that is certain to become unsupportable as soon as the company EOLs the product? With Linux basically taking over the server market, I see that policy as the most efficient way to become part of the sedimentary fossil record as soon as possible.
    • This is a far better performance than, for example, NVidia, whose drivers are well-known for breaking every few kernel releases because of their binary-only nature.
      >>>>>>>>>
      Bullshit. The binary nature has nothing to do with it. They don't touch the kernel at all. The only thing that could be breaking is the kernel glue code, which is provided in source form with the drivers. I've never had the drivers break on me in a stable kernel release (in their default form) and (once patched) I've been able to track kernel 2.5 since about 2.5.38 (now up to 2.5.50) without them breaking a single time.
    • So maybe I'm just not talking to the right person, but it does look like the company is saying one thing and doing another.
      Have you even tried getting on the phone and calling their documentation department? In the past I've found no register level docs on the web site, but was able to get paper copies w/o much hassle by calling them and ordering it.

      Also, the ahc/ahd drivers are still the amoung the best supported drivers in FreeBSD. They deal with all the various quirks of the chips very well, and kick ass in terms of performance. Justin Gibbs has been writing these drivers for years and years and years, even before going to work for adaptec.

      The driver is full source, even source for the sequencer on the chip. Most other vendors don't go to that level of source code availaibilty. Most vendors give a binary blob to load onto the card for the on-board sequencer.

      In short, I don't think that you have the first clue what you are talking about here.

      As to Theo and Adaptec, well, he's a total pain to deal with and seems to be telling a radically different story about his experiences with Adaptec than the folks that work for Adaptec tell. I suspect that a similar thing is going on with Sun. I have friends that are doing the FreeBSD sparc64 work and they have indicated that Sun has been forthcoming with documetnation and hardware for their efforts. Maybe Theo isn't getting what he wants because he's a total jerk to people and they react to that.

      • Have you even tried getting on the phone and calling their documentation department?

        Yes. As I mentioned in my post, they just asked for a product serial number and it went no further.

        In the past I've found no register level docs on the web site, but was able to get paper copies w/o much hassle by calling them and ordering it.

        Sorry, that's just not good enough, especially considering the above brick wall. If they want their chip properly supported, they should just post the the docs on their web site.

        The driver is full source, even source for the sequencer on the chip. Most other vendors don't go to that level of source code availaibilty.

        Most vendors give a binary blob to load onto the card for the on-board sequencer.


        Many other vendors have similar or worse mental deficiencies, it's true, however there's no safety in numbers here. There used to be lots of dodos as well.

        In short, I don't think that you have the first clue what you are talking about here.

        Give me a break. Go look [adaptec.com] for yourself. [adaptec.com]
  • I thought it was bad form on slashdot to put the term "vs." in the subject line and not have Micro$oft on either side of the equation.

    The open source community needs to show a united front against Micro$soft in order to provide an alternative choice. With this crap, Micro$oft just points to this incident and says "see... Finger pointing and dissention. and by the way... We have taken this into account into our 500th commissioned er... unbiased TCO study which now shows that windows costs $658.67 less than open source"
  • by cant_get_a_good_nick ( 172131 ) on Thursday December 05, 2002 @11:58AM (#4818552)
    This story was posted in the BSD section [slashdot.org], I wrote something there. Didn't start enough of a flame war, so I'll repost it. Before flaming, make sure you read the email thread [theaimsgroup.com].

    OK, I'm karma capped, lets some good ol' flaming start...

    Theo de Raadt: (calls up Sun) Hello, I demand some documentation.
    Sun Guy: Who the f*** are you?
    TdR: I'm Theo de Raadt.
    SG: Which Theo de Raadt?
    TdR: The one that is incredibly smart and productive and gets real pissy when I don't get my way; the one that forked OpenBSD because the NetBSD folks didn't like how pissy I got and drove users away.
    SG: Oh that one. What documentation do you demand because you somehow infer a right to having?
    TdR: On the UltraSparc III processor.
    SG: Oh, the one that you spent no R & D money on, that you spent no manufacturing money on, but you feel you have an absolute right to have it and if you don't get it you get pissy?
    TdR: Yeah, thats the one.
    SG: OK, here is our link.
    TdR: This isn't enough. I want more.
    SG: What other documentation are you demanding?
    TdR: I don't know. It is your job to figure out what documentation I don't have and to get it to me when I demand it.
    SG: If you don't even know what to ask for, how are you demanding more?
    TdR: Those other guys get more.
    SG: Which guys?
    TdR: The Linux guys.
    SG: You mean the ones that we kind of work with because we have an Intel distro and we should really appease the guys that kind of put it together? The OS that we might try to sell some software on?
    TdR: Yeah, I want what they have. I deserve it.
    SG: Why?
    TdR: Because I want it to make a server.
    SG: Using what OS?
    TdR: A free one, that will put no money in your pocket for OS licenses, no money for support, that will most likely not sell any Sun software because it usually runs as a fairly stripped down firewall box, and won't even sell any of your real expensive hardware where you make the real money from since we don't support SMP. Since you lost a lot of money when the dot-com bubble burst, and your stock is now close to historic lows and have had a couple rounds of layoffs, you must be real enthused about doing some work which probably won't get your company any money at all?
    SG: Ahh, so you demand we get some internal engineers for you who luckily will be really eager to stop their real work fending off fierce competition from IBM Windows HP and Linux, gather all our UltraSparc-III stuff for you, run it through our lawyers who luckily enough will drop all work involving our lawsuits about Microsoft and Java (and possible shareholder and wrongful termination lawsuits) sanitize it for you because from your reputation for getting pissy over things (witness ipf) you won't take kindly to an NDA and rush it to you on your schedule not ours.
    TdR: If you don't, I'll get pissy. Yes, and make sure you get that NDA stuff out. We're opensource, and we don't like NDAs, and since we're always right your NDAs should go away because we say so.

    I know why Theo would want this, but I can't see the Sun guys dropping everything and making this their number one priority. Though childish, if I was a Sun person, I'd release this stuff first to FreeBSD and NetBSD, knowing it would eventually trickle down to OpenBSD, just to piss off Theo.
    • That's cute. But I have to object to the idea that
      providing the doc would be some sort of measurable expense for Sun.
      If Sun doesn't have the documentation already
      printed and bound, then they're a bunch of wankers,
      not engineers. All they'd have to do is drop a
      photocopy in the mail.

      Sun is trying to sell their stuff to customers. As a
      customer, I don't buy stuff that isn't documented,
      because I've got better things to do than spend my
      time reverse engineering the hardware platform.

      Computers are not toasters. They are programmable
      general-purpose devices. If you don't have
      documentation, you can't program it. That makes
      the computer in question less than utile.

      Don't buy undocumented hardware.

      • Stuff's pretty random, even in big organizations. Ask the Samba guys about MS protocols, and they'll tell you that its pretty much a steaming pile. Disorganized. I can see why this stuff would be disorganized internally. Bob's got this here, in PDF, Joe's got this part in Word, Jennifer has this LaTeX stuff. Have to get it all together, filter it, and run it by the lawyers. I'm not implying this will cost millions, but the cost is not zero either.

        Theo is a genius, has done more for computing than I ever hope to. But he is arrogant. Sometimes that might help - he was so mad at NetBSD he went off and formed OpenBSD, and the world's a better place. Didn't like the old firewall license, and he gets a new one, one thats even better. Thing is in those cases he had options - if they don't like me playing here I'll make my own gym. But he doens't have options with Sun - if he pisses them off, there's no OpenSPARC org he can talk to. This is probably a time that being arrogant hurt him.

        Even with expenses of zero, there's still the NDA part. Theo doens't want to sign an NDA, which the Linux guys are happy to do. Theo then complains about how they get stuff he doens't. Ummm....

        Don't buy undocumented hardware.
        Hmm, Theo is, and then complaining about it.
  • Two thoughts (Score:3, Informative)

    by swordgeek ( 112599 ) on Thursday December 05, 2002 @12:09PM (#4818631) Journal
    First of all, as much as I admire his work it must be said: Theo is an abrasive asshole. He is idealistic to the point of being utterly inflexible and insulting. He'd get farther if he behaved like a grown-up.

    Secondly, to all the people who are accusing Sun of having no strategy, no plan, no policy, no hope, etc.. Just because YOU haven't bothered to find it out doesn't mean that it doesn't exist! There are a LOT of posts here that berate Sun for doing something that they clearly are not, or failing to explain something that they make perfectly plain. Go do your damned research!
  • by Cyno ( 85911 ) on Thursday December 05, 2002 @01:41PM (#4819418) Journal
    Sun seems to enjoy playing both sides of this war, giving and helping when necessary to maintain community support while playing their cards with the big companies instead of turning their backs on them like the community would have them do. Sun is a good company overall, but I sure wouldn't want to work there again. They are rather insignificant these days, now that openoffice is GPL. If they get in bed with OSS before its too late they might stick around long enough to make some great change in the industry, assuming marketting and morons don't flood them out.

    Capitalism is for the weak. If you need money to survive YOU SUCK!
  • Its not Sun Microsystems unless you go threw the "bit of run around". Even if you are a reseller of their products. That is the way that Sun operatates. They are not trying to be evil they just unoganized and have to many rules.

Anyone can make an omelet with eggs. The trick is to make one with none.

Working...