Contributed by mk/reverse on from the of-course-we-are-right dept.
Han Boetes (han <> mijncomputer period nl) writes:
In an interview with RMS on LinuxDevCenter I saw the following question:
FB: What is your opinion on the fact that Linux (the kernel!) supports binary drivers without too many problems? I'll make an example: the OpenBSD project didn't support Atheros wireless chips because they require a binary HAL provided with an incompatible license for their goals and policy. They act consistently. Do you think that Linux (the kernel!) should try a similar rigorous approach?
RMS: Yes! And so should the developers of GNU/Linux distributions. This is very important.
A big thumbs up for OpenBSD from RMS! :-)
This is good news. For once we can only hope people will listen to RMS.
(Comments are closed)
By Hugo Villeneuve (24.202.244.230) hugo@EINTR.net on http://EINTR.net
BSDs may have over 25 years of history but they don't have that many years of free software history.
BSD didn't start as free software in '77. The source was available only to AT&T source code licencee.
BSD didn't become free software until Net1 in '89. There was a valid need for the FSF to exist in '84 as there was no similar project then.
It took BSD Net2 in '91 for most of it to become free (there was a major rewrite project by the community) and to produce the free offspring 386BSD, FreeBSD and NetBSD (and later OpenBSD).
Comments
By mr_ugly (80.232.204.35) on
By F.B (151.38.56.76) on
By Sean Brown (204.209.209.129) on
Support the devices, maybe not ship the driver, but support the ability to add the driver and leave the decisions as to if it will be installed to the end users. Unless of course your completely uninterested in creating something that will be used.
Comments
By j0rd (204.244.192.17) j0rd.spam@gmail on none anymore (DAMN YOU TELUS!)
*nix is at a crossroad now. It's becomming more popular all the time and it's time to decide which hardware vendors are going to back the open source community and which are not. If you like *nix, please buy hardware which supports *nix.
Comments
By Anonymous Coward (68.167.146.78) on
I ran into this same thing back in my Windows NT days (3.5 and 3.51). I had to be careful which hardware I bought because, although Windows 3.1 and Windows 95 were supported by everything, Windows NT was not. I voted with my dollars back then, too.
As for wireless, I don't know about OpenBSD, but Slackware GNU/Linux, which uses the unpatched "official" Linus kernel, supports Orinoco-based cards just fine (e. g. Cisco's 802.11b card). Therefore, they might also work on the BSDs. However, I will not purchase, for example, a "Centrino" system, because Intel will not release the full programming specs without NDAs attached.
The same applies to RAID cards; I do not purchase those that aren't supported by Free platforms like OpenBSD and GNU/Linux. Pure and simple.
As the use of Free platforms begins to grow--and it is slowly growing--we as consumers should indeed vote with our wallets. If we want to see Free platforms supported, then this is our duty. Not doing so is tacit approval for the status quo--limited support for our Free platforms. I agree with Stallman on this one.
Merry Christmas, folks.
By tedu (64.173.147.27) on
By SH (82.182.103.172) on
By Anonymous Coward (205.240.34.204) on
Comments
By Anonymous Coward (24.34.57.27) on
Comments
By Anonymous Coward (69.197.92.181) on
By Anonymous Coward (205.240.34.204) on
By Anonymous Coward (83.103.129.176) on
By Paul-Andre Panon (24.87.10.77) ppanon@shaw.ca on
While you are correct that many people want to just use a computer to perform their work, those people are not using OpenBSD. The stated goals behind the development of OpenBSD are to provide as secure a BSD-based O/S as possible. That's why they've done code inspections and security audits of all the code in the core system before tackling things like SMP. Isn't it obvious that running binary-only device drivers - which can't be inspected for coding flaws and effectively run at the highest level of security access - is completely contrary to those goals?
If you want to just get your work done with the least amount of hassle (aside from dealing with viruses and system crashes), pay the Microsoft tax. If you want the most secure operating system, then do a little bit of work up front and buy a machine with components that will run with OpenBSD. If you want something in between pick a Linux distribution or another flavour of BSD.
But if you're wanting a very secure O/S, you're going to need behaviour bordering on the religious. Absolutely.
By Anthony (68.145.111.152) on
Comments
By Anonymous Coward (68.148.237.181) on
Maybe if Stallman should take his own initiative on this matter instead of being asked about it, I'd think he's serious about this. It's been 2 months or so since OpenBSD raised the issue and I haven't heard anything from him on this. I don't know, for I don't pay much attention to him.
Happy Holidays Everyone!!
By Chas (12.214.171.14) on
RMS does not "hate" the BSD license. To the contrary, it is listed as compatible in a license discussion at the FSF. The only objection they raise is the advertising clause.
RMS does not prefer the BSD license for a simple reason... like many of us, he worked on proprietary software environments in his youth, and the vendors of those environments either discontinued them or implemented changes that he found otherwise objectionable. A good, modern parallel might be if you had invested much of your career in Digital OSF1/Digital UNIX/Compaq Tru64, only to see the vendor slit the product's throat. The GPL is designed to end vendor control of RMS' software. This a BSD license cannot do.
You should care what RMS thinks for a simple reason - if you use the compilers in the base distribution, then you are agreeing to the terms of the GPL. OpenBSD developers have agreed to work with the GPL license by distributing ProPolice, and you are agreeing to GPL and LGPL every time you compile a program.
I've been burned by several software vendors, and I do admit some measure of delight in seeing them struggle with the GPL (and slash their own systems because of it, a la HP). However, for quality, stability, and security, nothing in the GPL sphere beats OpenBSD.
Comments
By Anthony (68.145.111.152) on
Nothing released under the BSD license can be discontinued like commercial software. Companies can keep modifications private, but they cannot withdraw code already released.
"You should care what RMS thinks for a simple reason - if you use the compilers in the base distribution, then you are agreeing to the terms of the GPL. OpenBSD developers have agreed to work with the GPL license by distributing ProPolice, and you are agreeing to GPL and LGPL every time you compile a program."
That's just the compiler, not the whole system. I agree to the license, that doesn't mean I have to buy into the propaganda.
Look, I don't have a problem with the GPL. The GPL allows companies to let their software out without handing it to the competition. They can't do that with a BSD license because it's the next thing down from public domain. What I have a problem with is GPL zealots that think nothing but the GPL is free. The BSD license has a place too.
By RC (4.8.17.8) on
I'll call BS on that. What makes you think so? Just because GCC is GPLd doesn't mean the programs you compile fall under the GPL.
Using a GPL'd program doesn't not imply accepting the GPL license either, you can use it as if it has no explicit license at all, if you wish.
Comments
By Chas (147.154.235.53) on
I'll call BS on that. What makes you think so? Just because GCC is GPLd doesn't mean the programs you compile fall under the GPL.
Using a GPL'd program doesn't not imply accepting the GPL license either, you can use it as if it has no explicit license at all, if you wish.
If you don't distribute a program under the GPL, then there are no restrictions on its use? Riiiiiight... dream on. Modifying the source without redistributing is also covered, as is use in countries where the software is patent-encumbered.
What if there is a gcc bug (or a bug in any other GPL development tool) and you need to apply an OpenBSD-supplied patch? You are then working within the license.
GNU GENERAL PUBLIC LICENSE Version 2, June 1991
...You may modify your copy or copies of the Program or any portion of it... provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
...c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice...
...4. You may not... modify... the Program except as expressly provided under this License. Any attempt otherwise to... modify... the Program is void, and will automatically terminate your rights under this License.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
Comments
By Anonymous Coward (68.148.237.181) on
0. 2nd paragraph:
"Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
If OpenBSD supplied a patch to gcc, it'd be a GPL patch (10 is the exception.) This doesn't mean OpenSSH, CARP, pf, and everything from OpenBSD is under the GPL. If you still don't understand, an example might help. Let's say you wrote your resume in KOffice, and zipped it with GPL's gzip. The GPL doesn't apply to your resume when you use KOffice and GPL's gzip, and you retain full copyright of your resume.
I am anticipating the day BSDs will have a BSD C compiler.
Comments
By Anonymous Coward (151.188.16.16) on
But even this is irrelevant to the issue raised here. The actual issue is the need for hardware manufacturers to release, without NDA, the full programming specs for their hardware and not require any proprietary (non-Free) software to run it. On that, I wholeheartedly agree with RMS.
By Anonymous Coward (67.64.89.177) on
RMS is a hippy that has not done as much as he takes credit for. I especially like the part where he says that specs & POSIX are "more guidelines". Ever wondered why GNU crap never works? This might be a hint...
Comments
By Anonymous Coward (65.49.54.179) on
By Anonymous Coward (24.154.28.58) on
Comments
By Anonymous Coward (207.229.38.13) on
By Nate (24.112.240.105) on
He is, if not insane, delusional. The man believes it is a fundamental right to see the code of anything he is running, I mean, come on. What kind of egotistical jackass really calls anything that doesn't do things his way unfree?
Of all the people in the world I would least like to be locked in a room with, he comes up on top.
Comments
By almeida (66.31.180.15) on
Also, his comments about innovation not being that important were weird too. I'd rather use a proprietary product that does the job than an open product that doesn't.
By ensuring that the code is always free, he's protecting the rights of the community, but not the individual. That's a strange way of looking at it, in my opinion.
I always sort of brushed it off when people said he was crazy, but maybe they had the right idea.
Comments
By Nate (24.112.240.105) on
I like to think of my self as a bit of an outthere crackjob, but he can really leave anyone in his dust.
OpenBSD's ideals are more socialistic, which I suppose is why I feel more for them.
Comments
By Anonymous Coward (128.36.236.30) on
Comments
By Nate (24.112.240.105) on
Comments
By almeida (66.31.180.15) on
By Anonymous Coward (212.202.38.11) on
Comments
By Nate (24.112.240.105) on
Socialism is where people make sacrifices for the good of the society. When people need help they can get it, but it is not a free ride, everyone must work for what they get and the gouvernement is in most aspects of life.
In other words, one is where everyone is completely equal and noone can rise above the rest and the other is one where the people can gain a better life for themselves if they wish but a part of what they earn goes towards the rest of the people.
I picked my words very specifically my friend, I know what I was saying.
Comments
By Anonymous Coward (212.202.38.11) on
Comments
By Nate (24.112.240.105) on
To answer your question regarding OpenBSD, I would say that they are more socialistic, but that they are not truly socialist in behaviour. If they were truly socialist they would have the support of the companies that use their code. I don't really recall any of the Linux companies giving big bucks to OpenBSD for OpenSSH. Really OpenBSD is only closer to socialism than the other sociopolitical structures out there is all. Socialism is where people make sacrifices for the greater good of society, much of what is done is for the good of all.
The communism thing I thought would be really obvious though; to anyone. So I am sitting here shocked as to how best to explain this to someone that did not get my previous post.
Perhaps it is best to say that the goal of the general public license is to ensure that code put under it stays under it and that noone can really remove it from the license without the consent of all people that have touched said code. This ensures that there is no closure, that everyone has an equal right to the code in question and that there is no way to take the code and make your own private thing with it. This is a communistic goal as the goal of communism is that noone can rise above the rest, that everyone has the same rights and priviledges and that everything ever done is done for everyone else.
Is that clearer now?
Comments
By Anonymous Coward (212.202.38.11) on
By Anonymous Coward (217.215.10.111) on
recipe no, but you still have to list those ingredients and nutritional facts. (unless, maybe, if you're selling mom's apple pie at the school bazaar.) the analogy, however far fetched, holds for me.
Comments
By chad (192.77.198.11) on
Comments
By jma (213.36.174.187) openbsd@libkvm.org on
the opensource community by telling hardware companies we want
to buy their products, but we want them open, not as plain
black boxes.
what i can foresee as a society problem _: access to knowledge.
as more and more people in the hardware will make closed boxes,
as more and more people in medical research use intellectual
property to slow down because of money, we tend to leave more
and more a state of democracy.
By Anonymous Coward (207.229.38.13) on
By Evil Ryu (62.175.42.214) on
By MosDave (66.93.0.101) on
Comments
By Anonymous Coward (68.148.237.181) on
Comments
By Anonymous Coward (24.34.57.27) on
Comments
By Anonymous Coward (68.148.237.181) on
Common sense is learned and good judgment is subjective. Compromising freedom to allow your GNU/Linux market to grow is a temporary gain. If the hardware vendors won't open their specs now, then why would they open later when everyone shells out the money regardless?
My common sense tells me sacrificing long term gains for short term gains isn't worth it. My good judgment says I shouldn't give money to companies who don't care about opening their specs to OpenBSD/BSDsoftware.
I guess you could say I am incapable of advocating GNU/Linux's freedom, while they (devs and users alike) are compromising their own freedom.
By 808blogger (66.91.22.5) on
By Kyle Amon (24.129.190.30) amonk@gnutec.com on http://www.gnutec.com/~amonk/
By Anonymous Coward (24.129.190.30) on