/var/opinion - The GPLv2 vs. GPLv3 Debate
As of this writing, the GPLv2 vs. GPLv3 debate is still raging. For the record, GPLv3 doesn't bother me in the least as long as nobody is forced to use it. As for the debate itself, I'd love to say the debate boils down to one thing. But it doesn't. There's not enough room in this column to address all the issues involved; however, a few central issues deserve attention.
First, the debate presents a conflict between two different views of freedom. Linus Torvalds and other kernel developers want people to have the freedom to do whatever they want with Linux, hence their rejection of the current draft of GPLv3. This includes the freedom to produce a Linux-based device that implements some form of DRM, such as TiVo. I feel compelled to mention that Torvalds had made a good case that not all DRM is bad, but as you'll soon see, the argument surrounding DRM can be peripheral to the debate.
The FSF wants users to have the freedom to take the source code that was used to create the binary that runs in any device, modify the code and run a binary of the modified version on the same device. Once again, the argument usually revolves around TiVo.
Forget TiVo for a moment. I would like to pose a different hypothetical scenario. I have two ulterior motives for doing so. The following example fits nicely with this issue's emphasis on embedded systems, and it circumvents the tendency to focus the controversy on DRM.
Think of a gadget manufacturer that wants to ship its gadgets with an operating system on ROM. The end user's freedom is not restricted by DRM. It is simply impossible to flash a ROM with the binary of a modified version of the source code.
One could argue that consumers are potentially harmed because they are stuck with any bugs in the software on ROM. Neither you nor the gadget provider has an easy way to update the software. Fair enough, but is that potential problem a good enough argument to draft a license to prevent this company from using free software?
It depends. The Volkswagen was originally designed with every conceivable cost-cutting measure to make it affordable to the working man. Some models lacked a gas gauge as late as 1959 or 1960 (I can't recall the exact date when the gauge was added). When you ran out of gas, you switched to a spare tank. If you weren't paying attention or overestimated how far you could go on that spare tank, you could run out of gas. That was quite a big inconvenience, but many consumers were happy with that trade-off because it was one reason they could afford to own a car.
Let's go back to that gadget with the software on ROM. Even if there is a bug in the software that is as annoying as running out of gas, many consumers may see it as an acceptable trade-off for being able to own a device that was formerly out of their reach. The only people who are truly harmed by having the software on ROM are the tiny minority of hackers who want to run a modified version of the software on the gadget.
Someone will no doubt point out that not all users have to be hackers to get their gadgets modified. They may have hacker friends. But look around you. Of all the cell-phone users you see daily, how many do you think have ever had the thought enter their minds that they could get someone to modify the software on their phones? How many are brave enough to let them do it? What about people who use GPS navigation systems, DVD players, televisions, microwaves or other devices? What about devices that use Flash ROM, but do not provide a way for end users to update it?
So, you see, although the GPLv3 protects some end users, it is intellectually dishonest to say that, in all cases, the GPLv3 necessarily protects the freedoms of the vast majority of end users. It protects only a minority of hackers or brave, savvy users with hacker friends, and applies only to devices that provide ways to apply updates.
I'm sure this analogy has holes. No example or analogy is perfect. But I hope you can see that, regardless of which side gets your vote, both the GPLv2 and the GPLv3 can stomp on someone's freedom. So this debate is not simply about freedom. It is about whose freedom is more important.
Now let's get to the grand ulterior motive for this column. Do you see how much the debate can change once we stop focusing on DRM and fair use restrictions? I know what that tells me, but what does that tell you?
Nicholas Petreley is Editor in Chief of Linux Journal and a former programmer, teacher, analyst and consultant who has been working with and writing about Linux for more than ten years.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
6 hours 41 min ago - BASH script to log IPs on public web server
11 hours 8 min ago - DynDNS
14 hours 44 min ago - Reply to comment | Linux Journal
15 hours 16 min ago - All the articles you talked
17 hours 40 min ago - All the articles you talked
17 hours 43 min ago - All the articles you talked
17 hours 44 min ago - myip
22 hours 9 min ago - Keeping track of IP address
1 day 17 sec ago - Roll your own dynamic dns
1 day 5 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




Comments
Protecting people from their
Protecting people from their ignorance is not freedom. Hacker or not, having the choice is what freedom is about. Taking it away is on par with what Apple has done with their software and is not in the best interests of its users, regardless of the example you provided. (Minority of hackers, etc.)
Non-flashable ROM
Nick,
You raise an interesting issue, but a device with only non-flashable ROM has always excluded the ability to run a modified version of the program, at least on the ROM. This doesn't change with moving from GPL v2 to GPL v3.
-- tuxi