Slashdot Mirror
More on OpenBSD 3.7 Release
putko writes "As previously reported, OpenBSD 3.7 is released. Here's some interviews with the people behind the release about the new features, including information about which companies are complying with requests for documentation and permission to freely distribute required firmware, and which are not. Ralink Tech and Realtek 'GOOD,'Intel 'BAD.'
The next time I build/buy a wireless product, I'll want Realtek or Ralink Tech inside -- because getting software to work with it will be easier. Ralink Tech and Realtek are Taiwanese, by the way."
Have any of you noticed the the hardware producers are standing in the way of open source software ? If you intend to install a Linux BSD or SunOS, drivers for the videocard`s, LAN card`s, TV Tuners, digital camera`s are very hard to find. On the driver CD suplied by the vendor you will find only drivers for Windows. So the point of this news should be not who are able to distribute the firmwares then why are they not suplied by the vendor on the install CD and why can`t they be included in the OS.
Think like a hacker, act like a hacker, but never become a hacker !
All the packages in OpenBSD 3.7 packages directory are bad. They all expect libraries of previous releases, makes me think they were simply copied from 3.6, and older in a few cases. I had to make links to libc.so.39 as libc.so.38, libc.so.37 and libc.so.36 to make various apps work, same for ssl, crypt, libstdc++ and a bunch of other libs.
At least the core OpenBSD 3.7 is complete and I imagine the packages will be brought up to date in time. Till then, compile your own or use ports.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Yes, Ralink provides Free (as in GPL) Linux drivers for their rt2400/rt2500 cards here. My roommate has a laptop with an rt2500 wifi card, and it works beautifully in Linux.
0 1 - just my two bits
the full comment that gave it that legendy reputation is in the following source file (you have to scroll past the license boilerplate first).L ENG5
http://fxr.watson.org/fxr/source/pci/if_rl.c?v=RE
note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
"An employee suggested to me that we load 3.7 on a few machines here as an evaluation. [...] I made the employee uninstall 3.7 from the machines and lets just say he's not with us anymore."
You kicked an employee out because an evaluation that he suggested didn't work out? That is, pardon my French, completely fucked. The whole reason you do evaluations is so that you don't end up in a position where new products put people's job on the line.
Apart from anything else, from now on if an employee suddenly discovers a product that at a stroke will double productivity, halve costs and save small kittens from drowning, do you think they're going to tell you about it? No, they're going to hide behind conformity, in the hope that that way they'll keep their jobs.
Congrats, you've singlehandedly halted improvement of your company's computing infrastructure. I'm sure it'll mean far less trouble for you, right up to the point where an innovative competitor buys you up and fires everyone.
For the love of God, please learn to spell "ridiculous"!!!
The only catch is that firmware is still closed-source. It can be downloaded, but I am not certain about redistribution conditions.
I don't know how true this is, but there is another reason that vendors may not release hardware info.
I have heard that a lot of hardware is pretty bad and is mostly fixed with software hacks in the driver. Companies may be not want people to know how broken some of their products are.
redistribution is not permitted by intel's license (hence the 'Intel BAD' in the story leadup)
...
and, straight from iwi(4)
The official person to state your views to about this issue is peter.engelbrecht@intel.com at (858) 391 1857.
vodka, straight up, thank you!
I bought the same card and it's very easy to tell the difference between revisions. The latest version of the card (revision 4) which contains the RT2500 chipset is a half-height PCI card, unlike the previous revisions which were full-height.
So, yes, faulty designs do exist, and one of the best-known for it is also one of the best-known for not releasing hardware specs, which does tend to make for some interesting implications.
Of course, even when documents ARE released, there is often a lot that is UNdocumented. The 486 had an interesting "load/save all registers" instruction, which basically allowed you to preserve or restore a complete CPU state. The hardware industry is littered with all sorts of other obscure undocumented syscalls, which is one reason why Open Source drivers for 3D graphics cards generally underperform - not because they are no good, but because the proprietary drivers include undocumented calls which improve performance.
This goes along with why manufacturers are dead-set against reverse-engineering. Not because they fear someone learning some "industrial secret" that really IS something the manufacturer shouldn't divulge, but because they fear people discovering device commands that they currently sell to the highest bidder.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Henning Brauer: Nobody ever gave us anything back. A plethora of vendors ship OpenSSH--commercial Unix vendors (basically all of them), all of the Linux distributors, and lots of hardware vendors (like HP in their switches)--but none of them seem to care; none of them ever gave us anything back. All of them should very well know that quality software doesn't "just happen," but needs some funding. Yet, they don't help at all.
That just blows. A while back the OpenBSD team had to raise funds to acquire Dell hardware so that their CVS server could scale up. The CVS server that holds repositories for all Open* projects. You would think that one of these companies would have just donated the hardware. But nope.