Proprietary Blobs and the Pursuit of a Free Kernel 405
jammag writes "Ever since the GNewSense team pointed out that the Linux kernel contains proprietary firmware blobs, the question of whether a given distro is truly free software has gotten messier, notes Linux pundit Bruce Byfield. The FSF changed the definition of a free distribution, and a search for how to respond to this new definition is now well underway. Who wins and what solutions are implemented could have a major effect on the future of free and open source software. Debian has its own solution (by allowing users to choose their download), as do Ubuntu and Fedora (they include the offending firmware by default but make it possible to remove it). Meanwhile, the debate over firmware rages on. What resolves this issue?"
1 Answer: (Score:5, Insightful)
Learn from the OpenBSD team
Re:1 Answer: (Score:5, Funny)
Learn from the OpenBSD team
We should tell the users to go fsck themselves?
Re: (Score:3, Funny)
No, you say they're nothing but a bunch of masturbating monkeys
Re:1 Answer: (Score:5, Funny)
Re: (Score:2)
There's a difference between what you *can* do and what you *should* do.
Under GPLv2, Tivoization is allowed, but you "shouldn't" do that either, right?
Re: (Score:3, Interesting)
While the Tivoization is allowed via GPL v2, it has been argued that it was never intended.
This is obviously not the case with the BSD license, and if it was they would have released another BSD license that fixed it.
I have the Answer (Score:2, Insightful)
Re: (Score:2)
Chuck Norris loses to the late, great Bruce Lee [youtube.com].
Re: (Score:3, Funny)
Supporting the freedom for my hardware to not work (Score:5, Insightful)
Once again, the FSF takes a noble goal to a loony extreme.
If the device manufacturers had put the firmware in ROM (flash/EEPROM/whatever) attached to the peripheral rather than downloaded by the driver, does that really change anything? You haven't given the user any more or less freedom; you've just redistributed what lives where and probably increased hardware costs (and made firmware upgrades less simple). However, then those releases could support the device and be fully "free" according to this new FSF decision.
Quite frankly, I'm a pragmatist who admires all the great freedom in Linux (and that's why I choose to use it) and supports hardware manufacturers who release their specs (hence the reason I now have an ATI graphics card). That said, at the end of the day, I want a distro that makes my hardware work without a ton of fucking around because somebody philosophically disagreed with a driver. I also respect those who would rather not use such things.
Therefore, my hope is that the Ubuntu/Fedora will not change their approach. This is one of those dealbreakers on a distro for me.
Re:Supporting the freedom for my hardware to not w (Score:4, Insightful)
Re: (Score:2)
Hey! <glares>
Re: (Score:2)
your tag may be broken...
Re:Supporting the freedom for my hardware to not w (Score:5, Insightful)
I'm inclined to agree, but, apparently, there are hardware manufacturers who sue anyone who distributes their binary blobs without permission, but are quite happy to give Ubuntu and Debian and Redhat permission.. Freedom is not having to ask permission.
Re:Supporting the freedom for my hardware to not w (Score:4, Interesting)
I understand the moral conflict, but it's not like I could buy a complete set of open hardware, and even if I could, I'd just be compromising on a different front.
Re:Supporting the freedom for my hardware to not w (Score:5, Interesting)
Is it any more free than having a distro that's free but not having the freedom to run it on your hardware because it's completely useless?
Having a distro like that serves at least one practical purpose: I can use it to evaluate a given set of hardware for compatibility. That can inform future purchasing decisions.
For instance, having used Linux, I now know that I will never knowingly buy a Broadcom wireless card -- or, very likely, anything from Broadcom -- even for devices I don't plan to run Linux on.
This is just taking that one step further.
it's not like I could buy a complete set of open hardware
Actually, under certain, limited circumstances, you can. I believe the OpenMoko Freerunner was such a device.
Re:Supporting the freedom for my hardware to not w (Score:5, Insightful)
Very limited circumstances, but to continue with the rest of my sentence: How is being forced to use the OpenMoko Freerunner, a phone which I had no interest in using superior than using whatever phone I want, but having to deal with software I may not agree with morally? Until all platforms are 100% open and firmware support is universal you'll always be cutting corner at one end or the other. I guess they are the FSF not the Freedom Foundation though, so I guess I've answered my own question about their stance.
Re:Supporting the freedom for my hardware to not w (Score:5, Insightful)
These limits to your choices are not a sacrifice for your freedom. As freedom in your example means to be able to make your choices according to your requirements, not the availability of the choices that will fulfil all your requirements.
Here we are talking about freedom on another level, and it is how unrestrained you are in your work with the computer system, and the aim is to create a system in which you don't get any forced restrictions, which can be abused. Being disallowed or prevented to do these things with software is an example of a real freedom restriction.
The hardware is removing part of your freedom. At that moment you aren't affected much by this, as neither this is abused, nor it is limiting anything important that you could do. Still, in the long term, if the issue is overlooked, it might lead to many trouble. And it is already creating issues with creating free systems. So doing something about the issue is good in the end.
It doesn't mean restricting you from using the said hardware, just putting this hardware at a little disadvantage, which will draw the line on what is acceptable, and will push the things in the direction that you get more freedom with the hardware in the future.
The aim to create a free phone is also a step in the right direction. While not really that usable, and therefore not helping anyone, it is taking us in the right direction.
Mod parent up (Score:5, Insightful)
I agree w/ parent.
For me the issue is not, do I get the source code or not? Binary blobs are fine. If someone does not want to give the source that is OK w/ me.
But, if I do not have the right to hack it (whatever form it is) or do not have the right to redistribute my hack, then then it is not free and should not be included in a "free" distribution.
Re:Mod parent up (Score:4, Informative)
For me the issue is not, do I get the source code or not? [...] But, if I do not have the right to hack it
Back in the day, Battle for Wesnoth didn't do anything with horizontal scroll events. It had a scheme for moving your viewport around in 2D using only one scroll wheel, which sucked and was hard to figure out. I fixed that; when it sees a horizontal scroll, it switches to the intuitive one-map-axis-per-wheel-axis. I would've hated to fix that without source, and I would've hated keeping using a broken scroll model.
In Nexuiz, at the time, there was no way to handicap yourself (to make the game fun against much weaker opponents). I wrote three lines of Quake C; now you can. How would I do that without source?
If you use sshfs, you might have noticed that it clears all port forwarding; if you've read the manual, you might also know that there's no option to disable it. I actually want sshfs to do port and X forwarding; what do I do? Grab the source code, grep for ClearAllForwardings, comment out four lines, off I go.
In most cases, being able to hack stuff requires source code. In all cases, it makes it a hell of a lot easier; often, so much that it goes from "infeasible" to "very easy".
Re: (Score:3, Interesting)
Re:Supporting the freedom for my hardware to not w (Score:4, Insightful)
There actually are a number of open source hardware projects around. Modern "FPGA" (field programmable gate array) devices are getting incredibly cheap, and can be used to design your own CPU.
(opencores.org is one such site)
It won't touch the latest state of the art, but hey..
Re:Supporting the freedom for my hardware to not w (Score:5, Interesting)
The UltraSPARC T2 is open source. You can download the Verilog for it, and with a big enough FPGA you can run it. Or you can run it in a simulator, or send it off and get it fab'd. You can take the core and incorporate it into a larger design with some custom accelerators (it has a very clean coprocessor interface for doing this) and get that fab'd. It has good performance and good performance per Watt for a lot of workloads.
Open source does not been designed by hobbyists and does not mean without commercial backing. If you make improvements to the T2 design and release your changes, then Sun may well incorporate them in the T3, or if they don't, you can get someone else to manufacture the chips for you.
Re: (Score:3, Informative)
To quote Wikipedia: [Citation needed]
What you're saying would go directly against Debian's free software guidelines.
Re:Supporting the freedom for my hardware to not w (Score:4, Insightful)
If granting distribution rights to someone also meant giving them the right to relicense what they were distributing, the GPL would be defunct.
Re:Supporting the freedom for my hardware to not w (Score:5, Informative)
Re:Supporting the freedom for my hardware to not w (Score:5, Insightful)
Re:Supporting the freedom for my hardware to not w (Score:4, Insightful)
> I would rather have a solid card with a binary blob than a "free" card that stinks.
I'd personally choose that too, but in my experience the nvidia binary driver is everything but solid. On my two Linux systems with nvidia video cards, the nvidia driver is the number one thing that causes me trouble. Sure it works ok with typical "default" settings, but throw in a xinerama setup + S3 suspend support and you'll be faced with undocumented limitations, poor performance and wake up problems cause by the driver module. I have sent bug reports to nvidia about the issues I have had and never heard anything back.
Re:Supporting the freedom for my hardware to not w (Score:5, Insightful)
I've never had problems with Xinerama and nVidia but yeah I suppose S3 could be problematic.
Personally I think I'll stick to Intel for the moment.
I'm not a gamer and as long as it handles KDE 4's compositing, then I'm happy.
Their drivers are stunning and they are completely open.
2.6.28 and 2.6.29 have some really neat stuff for Intel cards.
Missing the point (Score:4, Insightful)
There is a huge difference between cards with proprietary drivers, and cards with proprietary firmware. Drivers run in your OS, are OS dependent, and have significant security risk. Binary drivers are evil (like from Nvidia).
Proprietary firmware, on the other hand, does *not* run in the OS - it runs on the card. The binary firmware blob is OS independent - works for Windows, Mac, Linux, BSD, BeOS, whatever. It is CPU independent - the card generally doesn't care whether the host system is PowerPC, Intel, or ARM. While there is a small chance that firmware can be a security risk (since it gets DMA access to memory), it is far more remote than binary drivers.
There is no reason to object to a binary firmware blob - unless there is some stupid restriction on redistributing it (Hi, Broadcom). All it does is save money by replacing a ROM (RAM is cheaper than ROM) - and makes firmware upgrades trivial.
I can't believe FSF is objecting to this. Someone should do a parody of their new guidelines - with instructions on how to remove all PROMs from the motherboard, I/O cards, disk drives, etc. All those PROMs contain secret proprietary firmware. We can't be buying hardware with proprietary secrets now, can we?
Seriously, they should simply require binary firmware to be freely redistributable - giving you the same same freedom as if it was in ROM.
BIOS is not device firmware (Score:3, Insightful)
I agree that the BIOS must be free. It runs on the host CPU, and malware/spyware in the BIOS can do just about anything - especially with virtual machine technology. I am glad that FSF is insisting on open BIOS.
However, we are talking about *device* firmware here. You know, like inside your disk drive or USB wireless stick. Are they going to insist that their mice and keyboards have open firmware? Yes, open/free hardware is a worthy project, but it really should not try to piggy back on free *software*
Re: (Score:3, Informative)
Way back in the day, nvidia was the first graphic card company to support 3d for Linux
Really? Because I remember running GLQuake with my VooDoo 2 under Linux before nVidia existed.
Re: (Score:2, Insightful)
Translation: If I don't personally need something right this minute to accomplish my short term goals, nobody needs it and anyone who wants it is crazy.
Re:Supporting the freedom for my hardware to not w (Score:5, Insightful)
and what loony extreme would that be? moral/logical consistency?
a "free distribution" by definition needs to be "free" in the FOSS sense. they're simply modifying the definition to elaborate on an issue that had been overlooked up until now.
no one is forcing you to use a free distribution. and the FSF hasn't condemned the Fedora project for taking the pragmatic approach. but it would hypocritical for them to overlook the issue of proprietary firmware blobs in their definition of free distributions after the issue has been raised by members of the community.
i'm a pragmatist too. i run Windows XP because the programs i use for work are Windows-only. but i'm not going to bitch about FSF not including my Windows XP Professional distribution in their definition of a free system just because someone "philosophically disagreed" with an OS.
Re:Supporting the freedom for my hardware to not w (Score:5, Interesting)
Two New Software Freedoms (Score:4, Insightful)
I propose two new software freedoms:
-2: The Freedom to run any hardware, for any purpose
-1: The Freedom to run proprietary software, to run any hardware.
I don't understand why people don't want others have the freedom to install proprietary software on Linux system. I use both Linux and Windows. I enjoy running the latest and greatest games with the fastest video and sound cards.
I want robust support from NVIDIA and Creative. If Stallman had his way, there would be a huge disincentive to have working drivers. I require that my computer works with the hardware I bought for it.
I'm sick and tired of misguided free software enthusiasts applying free software principals to hardware. Yes, I think that as an individual tinkerer I should have the freedom to study and hack hardware that he owns, but hardware is not software. Hardware is a tangible thing. The structure of our laws protect tangible things more fiercely than ephemeral things, like software and ideas.
One of the original purpose of Free Software was to liberate hardware from the limitations of its software by protecting the freedom of the user.
However, Stallman's philosophy that "A free system distribution must not assist users in obtaining any nonfree information for practical use, or encourage them to do so" is ridiculous. Why should this be so? How does this promote freedom?
This is my computer, and it is my choice.
Stallman can't see the forest from the trees.
From http://psr.tumblr.com/post/57576525/two-new-software-freedoms [tumblr.com]
Re:Two New Software Freedoms (Score:5, Insightful)
-2: The Freedom to run any hardware, for any purpose
That has no business as a 'software' freedom, since it explictly affects only hardware. Good 0 Freedom for a Free Hardware Manifesto, though.
-1: The Freedom to run proprietary software, to run any hardware.
Except that propietary software conflicts with every other freedom, and as such the manifesto would contradict itself.
I don't understand why people don't want others have the freedom to install proprietary software on Linux system. I use both Linux and Windows. I enjoy running the latest and greatest games with the fastest video and sound cards.
Who? Stallman doesn't, he thinks running propietary software is inmoral, but he's fighting that the way a true freedom fighter would: by convincing you of it with arguments, not by force. You're still free to make an entire distro centered around NVidia's propietary drivers, you're still free to use GCC to compile propietary software, and you're still free to use GNU Emacs to write it. Your freedom hasn't been affected, you're just being warned about the consequences of doing so.
If Stallman had his way, there would be a huge disincentive to have working drivers. I require that my computer works with the hardware I bought for it.
Yeah, so? Freedom doesn't mean "everybody plays nice with my own wishes". They allow propietary drivers already, no reason why they should incentive them.
However, Stallman's philosophy that "A free system distribution must not assist users in obtaining any nonfree information for practical use, or encourage them to do so" is ridiculous. Why should this be so? How does this promote freedom?
How does this counter freedom? the information is not being censored, it is not being eliminated, it is simply being, well, not advertised.
Stallman can't see the forest from the trees.
Funny, but that's exactly what I'd say about you. You're not only willing to diminish your own freedom for a simple sound card, but you demand (not ask, demand) the help of Free Software developers in doing so.
Re:Two New Software Freedoms (Score:4, Insightful)
Not quite. Good binary blobs for hardware = hardware that can handle
software that people will want to run. Conversely, if your hardware sucks, binary blobs or not, no one will use it because it simply won't do its job. That job: to let people run the software they need/want to run.
Except that it doesn't. Software freedom allows one to "sell his soul" to Company XYZ in exchange for the license to run that company's software or to give that company the finger if he doesn't like their asking price.
In other words, a choice between two open-source drivers is more freedom than the choice between two proprietary drivers if, and only if you can make the open-source goods fit your needs. If not, then you'd lose out on the freedom to use your computer as you see fit.
Here, you make a very fine distinction between censorship and a lack of advertising. Frankly, most people would not see the difference because in this case, there is none. How is not recognizing that yes, there may a proprietary driver/software that can meet your needs better than this free one not censorship? That is eliminating information that would otherwise be available. And yes, that philosophy does indeed actively inhibit freedom. It may not be vendor lock-in, but the result is the same.
Re: (Score:3, Funny)
If not, then you'd lose out on the freedom to use your computer as you see fit.
However by freely choosing to use proprietary software (depending on how restrictive the license is) you lose out on a lot of other freedoms, such as the freedom to run, copy, distribute, study, change and/or improve the software.
It simply seems you value certain freedoms more than others.
Re: (Score:2)
But we are talking about the software running on the hardware device, not the hardware its self.
No one is demanding that nVidia should open up the cad files for their chips and schematics for their boards.
Re: (Score:2, Insightful)
Who, precisely, is saying that you shouldn't?
Re: (Score:3, Interesting)
"I don't understand why people don't want others have the freedom to install proprietary software on Linux system."
Because some see OSS as a political movement, not a tool.
Personally I see it as a tool. Open source allows many different things that I could not do with closed source and, even back when it wasn't as technically sound an option it still often won because I could do what I needed with it.
As a tool many OSS projects have been a great successes - better than most would have believed ten years ago
Re:Two New Software Freedoms (Score:5, Insightful)
Given that an operating system consists mostly of a bunch of drivers attached together with a kernel, there are good reasons to prevent distribution of closed drivers mixed with GPL ones. I don't think it is legal, not without stretching the meaning of the GPL.
Consider the following scenario:
Intel develops new closed undocumented architecture with a 16 core cpu. Similarly to current network or video cards, you need a proprietary driver to enable the super accelerated multicoreness. In order to allow the use of the newer faster cpu's, Linux vendors do what they did with the other proprietary drivers, label these drivers as "not part of the kernel" put them in a wrapper and ship their version of Linux with the proprietary drivers which, for now, intel is giving away for free as a binary blob. For a while everybody is happy and content. The new 16 cores chips becomes the norm. There are even 32 core chips on the market and the 64 cores chips are soon to be released all of which rely on proprietary drivers.
Suddenly, we hear that a large company, Lintelsoft, started by ex MS executives, makes a deal with Intel, a very lucrative deal for Intel, to license the drivers. Intel then says they won't give away the drivers anymore but you are free to buy the brand new Lintel Linux distribution. This distribution, which sells for 699$ a piece is all GPL'd except for those drivers that have become so prevalent that you need them in order for computers to run at a reasonable speed.
Open source programmers scramble to write free replacement drivers that work on their Gnubian distribution but only manage to make drivers that can run the multi core cpu's at 1/20th the speed as Intel won't release documentation or specifications. Linux is rendered mostly useless except for the Lintel distro, (which is also available for free and with sourcecode as Lintelora, excluding the proprietary driver sources of course) You can always plug in the Gnubian drivers in the free Lintelora project and get a working computer but it will only run at 1/20th the speed of the commercial 699$ a pop version and isn't powerful enough to run the new Mozilaurus browser smoothly.
In this scenario, Lintelsoft would have effectively stolen Linux from the open source community, making profit with other people's source code and breaking all versions that are free.
How can we let anyone close up an obviously derived work based on some wrappers?
Notice that, even today I sometimes need to pay to get a fully working Linux from certain vendors, like Mandriva. (if i don't pay, 3d acceleration wont work.) I expect that kind of twisting of the law by commercial vendors. It surprises me that even Ubuntu is including proprietary video drivers nowadays.
What's worst is that legally in order to maintain copyrights you need to make reasonable efforts at protecting those rights. Legally if the open source community waits until the binary drivers become problematic before acting, proprietary vendors will be able to argue legitimately that closed source code has been allowed in the kernel by the open source community for a long time now: The law says that you are not legally allowed to suddenly change your mind about interpretations to suit current needs thus the open source community would be screwed.
Re:Two New Software Freedoms (Score:4, Interesting)
I do not necessarily disagree with that - though I think that scenario is now very unlikely (OSS systems have enough acceptance that it would be ... difficult for Intel to do that).
That is why you encourage Intel to Do The Right Thing. They may - one day - do so. However, if you tell them do it or else chances are they will take or else. Further when your OS can no longer run those extensions then your OS will not be run. Not even microsoft can take that hard line a stance and get away with it - I fail to see why many that have a comparatively minuscule market share think that they can.
So, lets take another scenario (which is much more likely). Intel produces a closed 16 core CPU that requires proprietary microcode. Linux vendors demand it be fully open or they refuse to support it all. Customers needing the 16 CPU core (or wanting it) have two choices: purchase MS products and have it supported or figure out how to hack it into the system yourself through unapproved patches and probably paying someone to re-write what is needed to get it to work (guess which one will be picked). Intel then releases a 32 core processor and noting that few used their last product they decide to not even support OSS at all. While yours *may* happen if I get my way, mine *will* if you get yours.
Of course, what will really happen is option three - RedHat (and several others) will ignore Stallman and do what they need to sell product. Many of the purists have somewhat woken up and have started to use what they are fighting against (licenses, patents, and such) to *force* OSS to what they want but the thing is just too easy to fork. Distro's that go the "pure" way will live only in hobby land.
Of course, that is part of why companies like Redhat are both loved and hated - they brought Linux to the commercial success that it is today but "betrayed" those political/social ideals that many in the OSS community started with. Of course, having never truly believed those (like me, they read ESR and thought that buy made a lot of sense) they didn't really betray anything, they more or less showed that one side could gain a larger market and mind share than the other (which is probably even more infuriating than an actual betrayal).
Now, of course, when HURD is ready then it will sweep the world - but until then I suspect that ESR's view of OSS will win pretty much every time it comes in conflict with Stallman's.
Laches: look it up (Score:3, Interesting)
What's worst is that legally in order to maintain copyrights you need to make reasonable efforts at protecting those rights.
That is a feature of trademark law, not copyright law. Look it up
Every time a Slashdot user mentions diligence in defending your copyright or patent, someone who has never heard of estoppel by laches claims that only trademarks need diligence. Laches: look it up [wikipedia.org]. And while you're at it, look up other estoppel defenses [wikipedia.org].
Re: (Score:2)
If the device manufacturers had put the firmware in ROM (flash/EEPROM/whatever) attached to the peripheral rather than downloaded by the driver, does that really change anything? You haven't given the user any more or less freedom; you've just redistributed what lives where and probably increased hardware costs (and made firmware upgrades less simple).
Correct me if I'm wrong, but you would also have removed the need to reimplement the device's firmware if you only wanted to rewrite the driver, which has obvious advantages from a F/OSS point of view.
Quite frankly, I'm a pragmatist who admires all the great freedom in Linux (and that's why I choose to use it) and supports hardware manufacturers who release their specs (hence the reason I now have an ATI graphics card). That said, at the end of the day, I want a distro that makes my hardware work without a ton of fucking around because somebody philosophically disagreed with a driver.
Exactly. And the thought of being locked into a specific architecture because somebody philosophically disagreed with the idea of letting their users port drivers to their architecture of choice, well, ain't a pleasant one. Hey, lock yourself up all you want, I know that sometimes a short-term gain is worth a
Re:Supporting the freedom for my hardware to not w (Score:2)
"That said, at the end of the day, I want a distro that makes my hardware work without a ton of fucking around because somebody philosophically disagreed with a driver."
Thus why HURD hasn't gotten anywhere.
Re: (Score:3, Informative)
"I want a distro that makes my hardware work without a ton of fucking around because somebody philosophically disagreed with a driver. I also respect those who would rather not use such things."
You want freedom, but only if you dont have to defend it yourself.
Re: (Score:3, Informative)
The point is that the author of the article is Bruce Byfield and he is known as a news troll. There is nothing wrong in projects which try to extend the realm of free software by going into free hardware.
As of the philosophical concerns we know that proprietary drivers for Linux often lack quality (Linux is not an important platform for hardware manufacturers) and we can't fix them.
holy war batman! (Score:5, Insightful)
Oh god, here we go again with another sequel to "Defining Free Software: The Neverending Story"...
It's just like people who argue the United States is a democracy. Then some joker has to stand up and correct them and say it's actually a federated republic. And then someone has to mention that it's a capitalistic federated republic. And then the grizzly-haired guy in back stands up and he says it can't be capitalism because we've got things like the Security and Exchange Commission, and rules and regulations, and the FCC, and the FDA, and and and -- why my god there's an awful lot of socialism here. And then someone has to point out that what we're really talking about is whether something is mostly a free market, because nothing out there is truly one thing or another-- And then the liberal arts major stands up and everybody laughs at him before he can say anything.
I'm going out for a smoke... I already know how this ends. Mr. Rogers wins (in a blood stained sweater).
Re:holy war batman! (Score:4, Insightful)
Oh god, here we go again with another sequel to "Defining Free Software: The Neverending Story"...
It's just like people who argue the United States is a democracy. Then some joker has to stand up and correct them and say it's actually a federated republic. And then someone has to mention that it's a capitalistic federated republic. And then the grizzly-haired guy in back stands up and he says it can't be capitalism because we've got things like the Security and Exchange Commission, and rules and regulations, and the FCC, and the FDA, and and and -- why my god there's an awful lot of socialism here. And then someone has to point out that what we're really talking about is whether something is mostly a free market, because nothing out there is truly one thing or another-- And then the liberal arts major stands up and everybody laughs at him before he can say anything.
You capture the essence of the entire debate, and get modded down for Flame bait... :) Like you can flame someone on the surface of the sun... You just left out one part.
The vast majority that don't care about the vocabulary. They just like the stuff they use, and are amused by the spectacle.
Re: (Score:2)
You capture the essence of the entire debate, and get modded down for Flame bait... :) Like you can flame someone on the surface of the sun... You just left out one part.
The vast majority that don't care about the vocabulary. They just like the stuff they use, and are amused by the spectacle.
Yeah. I'm one of them. Some people take this stuff way too seriously. It's been said before the greatest spectator sport ever is politics. The only thing that would make it better would be if they dressed up in football uniforms while they did it. All those nice padded butts... MMmmmMMMmmmmm.... :D Oh, sorry.. Forgot, room full of guys. achem... carry on.
Re: (Score:2)
I see. So the discussion isn't worth having, by reason of an analogy? Or can we just call that a straw man?
I suppose we'd all better find something else to do. Given how much of Slashdot is devoted to pointless arguments, the only thing that makes sense is to shut the whole site down.
Or maybe you could make an effort to raise the level of discourse. That would be good, too.
On the subject of free software, I don't think there is a whole lot of argument, aside from perhaps a vocal minority. Most people here w
Re: (Score:3, Interesting)
Well, I think the FSF are taking the exact opposite approach to the example you cite in your comment (note that I am not commenting on whether I agree with their definition or not). But that's the key word. Definition. The FSF are trying to define free software; probably to help ensure that things (subjective arguments) like your comment refers to don't occur. Everything in your comment referred to (by example) was, really, about personal opinion--i.e. people arguing semantics. The thing is though, they're
Re: (Score:2, Insightful)
Well, I think the FSF are taking the exact opposite approach to the example you cite in your comment (note that I am not commenting on whether I agree with their definition or not). But that's the key word. Definition. The FSF are trying to define free software; probably to help ensure that things (subjective arguments) like your comment refers to don't occur. Everything in your comment referred to (by example) was, really, about personal opinion--i.e. people arguing semantics. The thing is though, they're aguing about something that is not clearly defined. Clear definitions help rule out subjectivity. An unambiguous definition, whether it's 'right' or 'wrong', states clearly the intended meaning--leaving little room for argument over the definition.
*blinks* Umm wow. I was mocking the common tendancy of smart, geeky types to over-analyze and get lost in the details, and you've just written an entire paragraph to say "It's good to agree on definitions before arguing over substance". You are a case in point tonight my friend. ;)
Re: (Score:2)
Re: (Score:2)
Except all those are actually good points. If someone didn't know anything about the USA then saying "USA is a democracy" will give them a highly distorted view of what the USA is.
The same is true of free software. Like they say, the devil is in the details.
How about when there is no alternative? (Score:5, Insightful)
Sometimes there are simply no good alternatives to binary blobs available. Case in point, the nvidia closed source graphics drivers. As it stands nvidia currently produce the best graphics drivers available for linux hands down. The intel open source drivers don't even come close and both open source and closed source ATI drivers are a joke.
The nvidia driver is the only linux graphics driver which supports:
a) The full opengl spec, in hardware. The intel drivers fall back to software for some opengl calls and don't support frame buffer objects at all.
b) A proper memory manager which enables, among other things, framebuffer objects and true redirected direct rendering, none of this AIGLX bullshit.
c) Any kind of opengl or compositing on multiple monitors
d) Reliable video and opengl vsync
e) Working video decode acceleration for modern high definition h264 video.
f) Proper colour/gamma adjustment for the X screen
g) Overscan adjustment for dvi to hdmi adapters
It also has by far the fastest opengl performance, is the most stable and just generally works the best out of all the linux graphics drivers. If you want decent graphics performance on linux, forget the open source drivers, go with nvidia. I'm sure anybody who has struggled getting dual monitors to work properly with any other driver will agree with me.
I know this might be a hit to my karma, but one area in which open source really isn't up to par is graphics drivers. I'd love good open source drivers for display hardware as much as anybody but for the moment nvidia's closed source drivers just wipe the floor with everything else. If you're going to complain to anybody, complain to ATI for not putting enough effort into their open source driver, although recently this has been improving with additions like DRI2 and GEM.
So before becoming evangelical and denouncing closed source modules as evil, try improving the open source modules so that they come close to the same stability and functionality.
Sam
Re:How about when there is no alternative? (Score:5, Insightful)
If that's true, then you can't accomplish your task using only free software. You apparently care more about "Overscan adjustment for dvi to hdmi adapters" than about using 100% free software - and that's your choice - but not everyone agrees with you. Even for people who do agree with you, there's still some value in *knowing* when you're using binary blobs.
Re: (Score:2)
It sounds like you're confused in at least two ways.
What goals are being harmed by what actions on the part of who here?
Re: (Score:3, Informative)
"Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in."
"Free software is a matter of liberty, not price. To understand the concept, you should think of free as in free speech, not as in free beer. Free software is a matter of the users' fre
Re: (Score:2)
Sometimes there are simply no good alternatives to binary blobs available. Case in point, the nvidia closed source graphics drivers. As it stands nvidia currently produce the best graphics drivers available for linux hands down. The intel open source drivers don't even come close
And yet my expensive nVidia graphics card in my gaming pc does a lousy job when it comes to compositing effects in KDE 4, while the same effects work flawlessly on my cheap, underpowered netbook with a intel grapics chip...
Go to Root Cause (Score:4, Interesting)
For things like wireless drivers the vendors can hide behind the FCC's restrictions and not release open source firmware for their hardware. This is among the worst forms of lazy regulation as it treats all users as criminals, shifts complexity to the masses, and results in products of lesser quality.
Get rid of the bad government policies and our computers would start working better. And we'd have more freedom, both on and off the expansion bus.
Re: (Score:3, Informative)
How about how a closed-source driver which gives my X 3d-accel is better than one that does not?
If I have a MIPS system and the manufacturer decided this platform isn't worthy of his attention, then I'm able to use the open driver to get *some* graphics, while I'm not able to use the closed driver at all.
And who cares? (Score:2, Insightful)
And as soon as anyone cares what the fascist software foundation says, we'll let you know. Seriously, why do those cranks get airtime? You want free? Try digging back to our time, comp.unix.sources. No religion, no restrictions, no 'freedom' with a stack of rules. We just chipped in code and sent it around to share. It's miserable how they have hijacked the word "free."
No, it's not (Score:3, Insightful)
It's miserable how they have hijacked the word "free."
Back then, the "free" was implied. We called it software and that you could use it as you would was assumed. It's only a generation of lawsuits that have pulled us back from the brink of progress.
Get off my lawn kid.
I just don't know... (Score:2, Interesting)
Non-free blobs are a problem, but... (Score:5, Insightful)
I've been watching the non-free blobs issue for awhile (particularly over here at Sun, where in JDK we call them "plugs"), and it's a good discussion to have.
However, looking at the new "Free Distro Guidelines" above, I'm struck by a particular section which seems extreme:
A free system distribution must not assist users in obtaining any nonfree information for practical use, or encourage them to do so. There should be no repositories or ports for nonfree software. Programs in the system should not suggest installing nonfree plugins, documentation, and so on.
and later:
All the documentation in a free system distribution must be released under an appropriate free license. Additionally, it must take care not to recommend nonfree software. [...] What would be unacceptable is for the documentation to give people instructions for installing a nonfree program on the system, or mention conveniences they might gain by doing so.
That's just ludicrous. Frankly, it's just a (very) small step away from requiring that you don't (or can't) run any non-free app on your "free" OS. That single clause has just blown any notion of a "free" (in any sense of trying to protect the end-user's freedoms, which is the FSF's major ideological foundation) distribution. I don't know who the manic that wrote that section is, but it's going to cause immeasurable harm to the Free Software movement.
If we go by that clause, NONE of the distros are free. You'd have to cut out a huge chunk of the Ubuntu distro, remove the entire non-free Debian archive, and I'm not even sure how to get it out of Fedora.
Honestly, the addition of those clauses take it from an entirely reasonable "Please use Free Software, and this distro contains only Free Softare" to a "Free Software! Free Software! (la-la-la there-is-no-non-Free la-la-la)" freakazoidal world.
The rest of the proposal is OK, with minor quibbles, but that clause is a show-stopper. Get rid of it right away. Or lose any credibility that the FSF has.
-Erik
Re: (Score:2)
You don't seem to understand the issue at hand.
These are the FSF's policies for determining what GNU+Linux distributions that they directly promote. If they promote Ubuntu and Canonical promotes Adobe Flash Player then the FSF would be drastically more likely to take a credibility hit than if they remain consistent with the principles that the organization was founded upon.
Or do you think that they have some sort of obligation to endorse random distros?
Re:Non-free blobs are a problem, but... (Score:5, Insightful)
Except that, by saying "you can't talk about proprietary software", you're taking away freedom. It's called censorship.
Proponents of free / libre software shouldn't act like they're afraid of proprietary software. It just makes us look stupid and weak. The grandparent poster is exactly right. It's the same with the GPLv2 vs. GPLv3 wars - GPLv3 is "necessary" because of TiVO? Because of lard-arses who want to watch TV? Fuck that.
Freedom includes freedom of speech. If a free distro wants to include instructions on how to install a proprietary OS alongside it, that doesn't make them suddenly "non-free". Or are we now against "information wants to be free" this week?
Re: (Score:3, Insightful)
I'm as big an enemy of censorship as you're likely to find. I've had my current slashdot sig for something like 10 years now. But a non-profit organization issuing guidelines about how they're going to label things cannot possibly be censorship.
Try again when a government passes a law saying that all distributors of software must meet these guidelines, or maybe when there are roving bands of vigilantes assaulting people who talk about distributing proprietary software.
Non-free software is always a problem. (Score:3, Insightful)
I'm a little lost since I'm not sure how you mean this quote. Exactly who said that quote and where? I didn't find that quote in the grandparent post to which you followed up nor do I recall the FSF ever arguing this. To the contrary, they talk about proprietary software all the time: the problems it poses for society, the conflict between what schools ought to be doing and the message p
Re:Non-free blobs are a problem, but... (Score:5, Interesting)
I can't believe a totally illogical comment like yours is "+5, insightful". There's no censorship to not recommending a distro as "free" software when said distro itself recommends non-free software. It's only a matter of policy for whom and what the FSF wants to recommend. That's no more censorship than if Amnesty stated they would not recommend a political party that recommends torture. OH BUT THAT'S AN ATTACK ON FREEDUM OF SPEACH! No, it's not, idiot.
Fuck, this site is so full of morons that it makes me sick.
Re: (Score:3, Insightful)
No. This is an ideological statement, in the same vein that the GPL is. Both are intended as an implementation of an ideology. The root ideology at the FSF (up until now, it seems) can be shortly summarized as follows:
It is in everyone's best interest that software be freely available and usable by everyone.
The GPL thus establishes some (in my opinion) reasonable and limited restrictions on software, in the name of protecting the Greater Good.
This guideline set (and, in that respect, it can be view
Re: (Score:2)
Re: (Score:2)
That's nonsense.
Whether a given distribution choses to meet these guidelines or not is entirely voluntary. If they chose not to, all they miss out on is being endorsed as a "free distribution" by the FSF. Hint: They weren't being endorsed before either.
Re: (Score:3, Interesting)
All the documentation in a free system distribution must be released under an appropriate free license. Additionally, it must take care not to recommend nonfree software. [...] What would be unacceptable is for the documentation to give people instructions for installing a nonfree program on the system, or mention conveniences they might gain by doing so.
I hadn't bothered to read the damn thing as I expected it to be rather RMS-freakish but this... "The Ministry to Truth today decleared that there is only free software, there shall be no alternatives less it be a ruse by our enemies. Free software is perfect and at no point could there be any mention of imperfection, or anything else that might amount to criticism. It's doubleplusgood!"
That is not free. This is brainwashing into believing there is no alternative, and that anything else on the outside isn't
Raise of hands (Score:4, Insightful)
Other than die-hard believers here on Slashdot, to the rest of the world, what percentage of the population cares of their software gets the Stallman stamp of approval, and what percentage just wants their software to work?
Now I understand that having OSS drivers helps the kernel devs troubleshoot those drivers, and keep them up to date with constantly changing ABIs/APIs. I prefer free software, but I won't be a zealot about it. I am quite comfortable with proprietary software if it is the best solution for my need.
Re: (Score:2)
Now I understand that having OSS drivers helps the kernel devs troubleshoot those drivers, and keep them up to date with constantly changing ABIs/APIs..
That is the issue exactly. Also the fact that Open Source drivers don't leave people with certain hardware behind (because there's no financial incentive to stop supporting old hardware), and Open Source drivers can be integrated better with the operating system, and they can be ported to operating systems that the manufacturers don't care about.
Re: (Score:2)
That is the issue to many devs who just want to put out the best product they can. For others the issue is having a completely "free" box.
Re: (Score:2)
First, device drivers, if properly written, are part of the delivered hardware. If one asks for the drivers to be open, one might as well ask for the firmware in the device to be open. Now, I would argue this would be a good thing, but not such a good thing that I would want to arbitrarily limit the selection by making it a requirement.
Second, at the device driver level, there sh
Who cares *where* the non-free firmware is? (Score:5, Insightful)
I've always wondered why I, as a Freedom-loving-user, should prefer a device which has its non-free firmware embedded in a ROM or Flash chip rather than as a file on a CD or FTP server with my linux distribution.
Because, let's be clear: *where* the non-free firmware is being stored is usually the choice you have.
100% Free hardware would clearly be better, but there's precious little of that around...
So: why is it evil to have the firmware distributed on CD? Why should I care even one itsy-little-bit where it's stored?
Re:Who cares *where* the non-free firmware is? (Score:4, Insightful)
If the firmware comes with a liberal license that says that anyone can distribute it, then no, you probably won't care, but if it doesn't, and you start handing around copies of it, then you'll care when their lawyers come knocking.
Re: (Score:2)
If the firmware comes with a liberal license that says that anyone can distribute it, then no, you probably won't care, but if it doesn't, and you start handing around copies of it, then you'll care when their lawyers come knocking.
Good point. I completely agree with that: distros should make sure that all the firmware they're distributing at least comes with a "anyone may distribute this" license.
I don't suspect having such a requirement would even cause much of a flamewar. :)
More like, who resolves this issue. (Score:2)
Please define "firmware blob" (Score:5, Insightful)
If they mean a piece of firmware for download to a specific hardware device, then that is rarely in the *kernel*. Usually it is held in a separate file on disk, that is downloaded to the device at boot time. If it is in a separate file, the binary firmware blob is then not a part of the kernel, so the point is moot. The little bit of loading code that opens and reads the file and blasts it to the hardware is part of the kernel - and is most likely already part of the open source code.
If they mean a part of the kernel with no open source, then it is kernel code and please stop calling it firmware.
Re: (Score:2)
Blobs can take many forms. Sometimes, they will be provided in separate files. Other times, they may be incorporated into the source of the driver itselfâ"for example, it could be encoded as a large array of numbers. But no matter how it's encoded, any nonfree firmware needs to be removed from a free system
I think the kernel inclusion of stuff they were getting at was/is something like:
static const unsigned firmwareXXXX[] = {...};
This might be in the "source code", but is obviously not the source code for the firmware; it's embedded chunks of data. I can't say whether the linux kernel does this for any of its drivers... would have to look.
I am typing this from Gnewsense (Score:4, Interesting)
I am typing this from a Gnewsense system. I really appreciate the position Stallman holds - that the sole reason he would ever use unfree software would be to write free software to replace it. Thus, until he wrote the GNU system, he used proprietary systems and components until he could write his own free one. I am not able to go that far, but for non-work related things, I usually avoid non-free software, and even at work, I am working with Red Hat and other free software a lot of the time.
I guess I wasn't following things closely as one thing I was surprised at when I started using Debian (and later Ubuntu) was that there was no free Java out there. Gcj/gij and Kaffe are out there, but neither is at a level that can run most modern Java programs. Sun said in 2006 they were releasing Java as GPLv2, but that is still going on as far as I know. No full-featured Java means problems for packages I use like Eclipse or Vuze or Freenet.
Video players also have a lot of problems. Mplayer and Debian had a long history (of no Mplayer), but over the past two years it has been brought into Debian (but not Gnewsense). Flash videos from places like Youtube is a problem as well, I use Gnash, which can see some videos on Youtube and can't with others. It's also a whole rigmarole for me to watch Youtube videos on Gnewsense, I actually paste URLs into a shell script instead of watching them through my browser.
I figure if I'm going to put binary blobs, Java, and so forth on, I might as well being using Microsoft Vista. I agree with Stallman that a system is not 100% free if it allows an automatic method of installing non-free things. I personally think Debian, while not 100% free, is still close enough to suit myself in terms of allowing the option of installing non-free stuff. I don't use Debian any more but I can appreciate their position. With regards to Fedora and Ubuntu, I do not think the "you can remove non-free stuff if you want" argument holds water. That is a slippery slope as far as I'm concerned.
I appreciate Stallman's position very much. The problem with technical people is they tend to think very logically and practically and technically and don't really appreciate what Stallman's stance does. For every Stallman out there, there are thousands of guys in suits out there who want to see Vista, or at the very least some Suse hybrid on everyone's desk. I think we are very lucky to have Stallman around. I have to admit he has been helped by the Linus's and Debian's out there which are a little more practical, and a little less ideological (although to the average suit, they seem as ideological as Stallman). But stepping too far away to me is on a slippery slope to Vista land. It's an old story - if you can't beat it, then sue it for patent crap, start making Suse Linux/Microsoft hybrids and all of that.
Re: (Score:2)
I appreciate your point, and I even support your position. But you have to realize that what this buys us is time. Running a Binary Blob for Nvidia's cards, and running a firmware blob for Broadcom support is no where NEAR the same thing s running Vista. Right now what Linux needs is to survive in the face of Billions of Windows users who want to see us disappear. If we can accept the time being and stay alive, wait until Linux gets a share of the OS Market large enough to really threaten the hardware maker
Re:I am typing this from Gnewsense (Score:5, Informative)
Re: (Score:3, Informative)
Maybe you have not heard of OpenJDK [java.net]?
Re: (Score:3, Informative)
Keep in mind that linux will never get to the point where a free system will "just work" if everybody just accepts proprietary software all over the linux desktop.
I have similar problems with flash. Sure, it is a pain to watch flash on a 64-bit linux desktop. However, I see that as a reason to replace adobe flash, not a reason to find 47 hacks to try to get it to work in spite of the vendor's lack of support.
If you just want something that "works," then buy a copy of Vista. But don't complain when you fi
The only way to truly resolve this (Score:2)
It still isn't free (Score:5, Insightful)
until you have the code for every PGA, the microcode for every processor, the schematics of every logic element. These all embody code of some sort. Where do you draw the line?
Re:It still isn't free (Score:4, Insightful)
Who says you have to draw a line?
From a purely idealogical standpoint, what problem is there for wanting open hardware as well?
There is a reason that it is called nuisance. (Score:2, Interesting)
So familiar (Score:2)
This question is on a par with other weighty issues [wikipedia.org] that mankind has wrestled with in the past.
I've got it! (Score:3)
'What resolves this issue?"
OpenBSD, of course.
Re:I have a solution (Score:4, Insightful)
Let's assume that Nvidia completely opened their driver tommorrow and broke NDAs and third-party licenses to do so.
Stallman would still complain that Firefox allows proprietary extensions.
Stallman would still complain that Google supports proprietary software too much.
Stallman would still complain that patents exist. (He may have a good point here).
Stallman would still complain that some drivers in the kernel contain proprietary firmware.
Stallman would still complain that Ubuntu doesn't use all free artwork.
Stallman would still complain that we use proprietary BIOS on our motherboard.
Stallman would still complain that companies are using GPL software to turn a profit and not enabling their customers to not pay them (ala Tivo).
Remember kiddies, true freedom is only achieved through constant vigilance and annoyance, and an ever-increasing strict list of restrictions that remove choice.
(Yes, I'm prepared to burn karma for the inevitable flame/troll mods, but search your feelings Skywalker, you know these words to be true.)
Re:I have a solution (Score:4, Insightful)