Slashdot Log In
OpenBSD Clashes with Adaptec In Quest for Docs
Posted by
timothy
on Sun Mar 20, 2005 03:54 PM
from the not-support-you-note-they-note dept.
from the not-support-you-note-they-note dept.
TrumpetPower! writes "OpenBSD developers have been asking for documentation from Adaptec for over four months. Adaptec's response has been to deliberately misunderstand what is being asked of them. A former Adaptec employee admits that the hardware is buggy and tricky to get right. So, as a result, OpenBSD 3.7 will ship without Adaptec RAID support. Personally, I'm glad that Theo isn't resting on his laurels."
Related Stories
[+]
BSD: Hifn Restricts Crypto Docs, OpenBSD Opens Fire 304 comments
Mhrmnhrm writes "After totally closing off public access to documentation for their chips roughly five years ago, Hifn is again offering them, but with an invasive registration requirement. Needless to say, Theo de Raadt and the rest of the OpenBSD team were not amused, and following a Hifn manager's missive, the gauntlet has been thrown. Either open the docs fully, or be removed from the system. This wouldn't be the first time... the same thing happened to both Adaptec and Intel following similar spats."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading ... Please wait.

Why just OpenBSD? (Score:5, Insightful)
Why just documentation? (Score:5, Insightful)
They are under an obligation to provide usefulness on legit architectures, but they aren't doing that. Adaptec should get over their shame of bugs, and allow the driver people at OpenBSD a chance at making things work.
There is no general fix for this problem, often specs are released way too late. On the other hand, releasing open source drivers will open specs for the same device. These specs aren't just trade secrets, they're actually necessary for building drivers.
Re:Why just documentation? (Score:5, Insightful)
Exactly what obligation does Adaptec have?
Re:Why just documentation? (Score:5, Insightful)
Re:Why just documentation? (Score:5, Insightful)
Nowadays, I purchase equipment based more on its compatibility with FreeBSD (and occasionally OpenBSD) than any other factor (incl. performance and price), as that's what it's going to be used with.
As far as responsibility or obligation is concerned, Adaptec's got none to the Open Source community, unless you can consider it a direct failure of its responsibility to its shareholders. Just because Open Source is "fighting the good fight", doesn't mean anyone owes us anything.
There's an old saying (Score:5, Insightful)
"Never ascribe to malice that which is adequately explained by incompetence." - Napolean
Re:There's an old saying (Score:5, Funny)
I wonder how this will affect Adaptec? (Score:5, Interesting)
Re:I wonder how this will affect Adaptec? (Score:5, Insightful)
The one advantage it does have is security, which is vital for running large scale servers. These servers have reliabilty as a high priority, so RAID is the norm.
Simple solution... (Score:5, Insightful)
Just a note (Score:5, Informative)
I have not been using OpenBSD sice 1999, but hardware support was never its strong point... though what it supported was,like all the BSD's, supported extremely well.
It's a good call, in spirit of BSD. Scott's drivers are exellent and they just need to port those.
Re:Just a note (Score:5, Informative)
The management utility in the FreeBSD ports tree is binary-only. OpenBSD refuse to accept binary only crap, which is why they want this documentation.
OpenBSD confirms it... (Score:5, Funny)
this is a good solution (Score:5, Insightful)
People say that Theo should stop being so annoying, but the only way shareholders find out is when it gets massively publicised like this.
It worked for the 802.11 drivers. It's worth a shot here.
Probably software raid (Score:5, Interesting)
reminds me of Promise (Score:5, Informative)
Reminds me of Promise's definition of "Linux support" for a card I bought.
In the case of the SX-150 SATA raid card (which has a hardware XOR engine and whatnot), that meant "we have binary drivers for distributions which are several years old".
There is some source. Well, it's a 'wrapped' binary driver, and it's only available from "some guy" in Germany who begged Promise support long enough they gave it to him. You a)cannot compile it into the kernel b)cannot compile it for 2.6 because it simply isn't compatible. I sent numerous emails to Promise asking when a 2.6 driver would be available or if there was any updated source code. None were ever answered.
Same story with the tools- unless you're running Redhat 9.0 or some ancient version of Suse, forget ANY on-line monitoring.
Not that the customers are much better- one page I found about the card suggested that "software raid is faster anyway", which is an absurd proposition by itself. Regardless, why would you spend $100-200 more on a hardware-raid card complete with cache memory, and then just use the 2.6 SATA driver which only drives the SATA interfaces?
From what I understand, 3ware has better support for Linux, but that means I have to migrate a large amount of data off the old array..
Re:reminds me of Promise (Score:5, Informative)
Nothing ever changes at Adaptec (Score:5, Interesting)
Substitute "They" for "We" in that sentence and it could have been me speaking, when I was working at Adaptec and trying to release an in-house version of the starfire (a.k.a. "Duralan" ethernet MAC) driver. I hit that same brick wall over and over again while tying to get some chip specs and a linux driver released. Somehow, in their minds, "support" is translated into not releasing specs and drivers. Releasing such information, in contrast, is a failure to support customers. This wierd Orwellian doublethink seems to pervade the thinking of everyone connected with supporting Linux and other free OS's at Adaptec.
It's so amazing to see that nothing has changed at Adaptec in the last 7 years. My own driver episode was "resolved" (unsatisfactorily, for me) by Donald Becker agreeing to sign an NDA for the chip specs. Not to second guess Donald, but my thinking at the time was, "this just postpones the problem. Maybe it would be better just to boycott these imbeciles."
Not to close on a sour note, I should say that Adaptec was a great place to work in many ways, and I always viewed their attitude toward free software as an aberration. I still tend to do so, and perhaps that's wishful thinking on my part.
Threshold of complexity (Score:5, Insightful)
Look at the small and medium end raid market now. Theres not many players, Adaptec,promise,3ware and a bunch that adaptec bought up. Adaptec gains nothing by opening up itself to a point by point comparison with lesser competitors. Their name recognition is carrying them much the way IBM's used to. Further if the hardware is bugged and tricky and adaptec knew about it then they open themselves up to liability.
Their reasons are obvious keep the barriers high and keept those that can't climb them out.
interesting if not down right funny thread: (Score:5, Interesting)
* Subject: Re: Adaptec AAC raid support
* From: Bob Beck
* Date: Sat, 19 Mar 2005 13:56:41 -0700
* Cc: Theo de Raadt , Sean Hafeez , misc@openbsd.org, Scott Long , freebsd-questions@freebsd.org
* In-reply-to:
* Mail-followup-to: Charles Swiger , Theo de Raadt , Sean Hafeez , misc@openbsd.org, Scott Long , freebsd-questions@freebsd.org
* References:
* User-agent: Mutt/1.5.6i
>
> sort of ultimatum is a childish and self-destructive action. I hope
> the other OpenBSD committers veto any such action as being
> counterproductive and harmful to your users.
Horsecookies. What was done was remove AAC support from GENERIC,
because users know what is in GENERIC is supposed to be stable and a
good candidate for use. I've got AAC's. They aren't at the moment.
they die, and you can't do anything with the raid management without
rebooting, and Adaptec has shown no signs of releasing documentation
so that situation can be corrected.
Sure, there's a "free" driver, and a non-free management interface,
so it's only half a driver. Pretending to have a production system
using a raid card that with no supportable management interface so you
have to reboot to fix anything is like buying birth control pills in
packs of 20. Pretty soon you're going to take a good fucking on a day
you really can't afford it. Period.
As such AAC isnt' any more broken than it ever was. OpenBSD
just chooses not to encourage users to purchase a non-supportable
card by including support for it in the GENERIC kernel. Are you
saying it's more honest to leave unstable and incomplete support in
there? People who wish to use it anyway can always compile it in.
> Otherwise, you're likely to discover that most people choose to run an
> OS which works with the hardware they have, rather than sticking with
> OpenBSD.
Or choose to replace the hardware that isn't supportable by the
OS they want to run. Thank you LSI and Dell. LSI cards seem to work
fine.
-Bob
emphasis added by poster
Re:How many people... (Score:5, Insightful)
Of cause what really annoys me is that the Linux developers seem to care even less. Why is it that the developers of free software can't stand togther and demand documentation? And why is it that it's the smallest team that must make these demands?
Re:How many people... (Score:5, Informative)
It did not start with BSD4.4-lite, go to 386BSD, move to NetBSD, then OpenBSD, then DragonFlyBSD and then FreeBSD. Each are their own system which split at one time or another from the same tree.
All four of those systems are maintained today and therefore it is not like Windows 9x complaining about hardware support. Windows does not maintain new versions of Windows 95.
OpenBSD is the extremely secure and extremely open of the BSDs and Unix-likes. OpenBSD refuses to have anything that isn't as Free and Open as their goals describe into their system. Linux and FreeBSD are more into the functionality over ideals idea. NetBSD I cannot speak for though as I don't really follow them.
Me (Score:5, Insightful)
I haven't used OpenBSD in a few years and was really impressed with their rewrite of packet filter. You linux folks should check it out.
Re:Tried e-mailing the guy.... (Score:5, Funny)
Re:Tried e-mailing the guy.... (Score:5, Insightful)