Novell Won't Lose Right To Sell Linux 216
BinnyVA writes "You know the story about Novell losing the right to distribute Linux? Well, the Free Software Foundation has absolutely no control over Novell's distribution of Linux. A zealous Reuters reporter apparently conflated the FSF with the open source community in general, took some quotes out of context, and ended up with a sensational headline that fooled a number of people. The Novell deal is completely within the bounds of the GPL, GPLv3 isn't even done yet, and even when it is the Linux kernel is unlikely to be covered by it." Linux.com and Slashdot are both owned by OSTG.
Well, duh. (Score:4, Informative)
Re: (Score:2)
Premise is counterintuitive (Score:5, Insightful)
Re: (Score:2)
I think the FSF is probably more interested in keep peoples rights from being abused when it comes to existing OSS applications, or large-scale/severe infractions.
I think they aren't an evil organization, they are willing to overlook minor infractions.
Re: (Score:3, Informative)
WTF are you talking about? The kernel is GPL, specifically V2 only - as opposed to "V2 or later". Linus doesn't like GPL3, so the kernel will likely remain under V2 for some time to come.
Re: (Score:2)
Either way, non-GPL kernel modules are allowed. They are frowned upon by the kernel developer communit
Re: (Score:2)
A driver implemented as a module is NOT part of the kernel, any more than the desktop on TOP of the kernel is part of the kernel.
The fact that the GPL kernel calls a non-GPL piece of software does not make the non-GPL software a violation of the GPL on the part of the kernel.
Whole thing is nonsense, except to FSF fanatics.
Re: (Score:2)
I think you are wrong, since a module becomes part of the kernel when loaded. If you were right, why would the kernel complain that a non-GPL module taints the kernel?
Re:GPL is'da bomb (Score:4, Insightful)
The problem with the above is that it is untrue. Nothing anyone does can prevent me from using & distributing any OSS software, as long as I don't distribute binaries without the source, suitably licensed. So please, tell us what this bomb is? At worst, the software could be abandoned or closed, which is always the risk with any software --- no matter the license. At least, with OSS, you have the source.
Re: (Score:2, Informative)
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. [...]
FSF can allege Novell, on that they distribute the program not as expressly provided under the License. If this is proven in court, they automatically lose the right to distribute the program.
7. If, as a consequence of a court judgment
Re:Premise is counterintuitive (Score:5, Informative)
Re: (Score:3, Informative)
Re: (Score:2)
Lets stop putting the cart before the horse. Nothing Novel has done to date would stop them from using or distributing linux under any of the GPL licenses. Why are we so upset over some suture incedent that has yet to happen when there is no indecation of it happening?
Show me one thing they are doing that Violate either GPLv2 or the new and underimproved GPLv3 and I will
Re: (Score:3, Informative)
Got a link to back that statement up?
Stallman seems to be a pretty careful guy. I'm not sure that hearsay from a stranger on the internet is enough to convince me he did say exactly this.
There seems to be an obvious case to be made that this agreement violated the spirt of the GPL, and a pretty good case to be made that this agreement violated the letter of the GPL v2 as well.
The relevant text would be:
"For example, if a patent l
Re: (Score:3, Informative)
Got a link to back that statement up?
Re: (Score:2)
No it doesn't. It changes it so If novel specificly adds something, it is in violation. Even with this deal, I could add something, microsoft could claim it as theirs, and sue everyone but novel's customers and novell still won't be in violation.
Can't people read? If they could they would see that
Re: (Score:2)
Are you a lawyer? Because the FSF has lawyers, e.g. Eben Moglen, to make sure that its intentions are correctly spelled out. And that includes spoiling the Novell-Microsoft agreement. If you are not a lawyer, I cannot see how you could assert anything about the yet unpublished GPLv3. The section about spoiling the Novell-Microsoft agreement isn't even in the draft yet.
Re: (Score:2)
What specificly is in the GPLv3 that stops those deals? Nothing, And actualy read it and look for the part, don't repeat what someone has incorectly stated to you.
That fact is there there isn't anything. Unless novel opensources something under the GPL and doesn't allow the rights to be perpetuated
Re: (Score:2)
They can distribute linux (Score:5, Interesting)
Re:They can distribute linux (Score:5, Informative)
Re:They can distribute linux (Score:5, Informative)
Or in other words, we will end up with a Novell-only GPL2 fork of the GNU toolchain, and everyone else will use the GPL3 version? That is quite frankly an utterly untenable position, especially since they wouldn't be able to backport GPL3 code back into their GPL2 programs, meaning that they would have to independently re-engineer every fix or upgrade, or be left in an incompatible state.
Let's think about this from another angle for a second, though; do you really want to do business with a company in bed with Microsoft? Me neither, which is why I also won't give Sun a dime.
Microsoft is the devil (at least in computer-land) and anyone who does business with them is tainted, to say the least, regardless of licensing issues.
Re: (Score:2)
Also, any code that still says GPLv2 or later, or whose author expressly puts it under GPLv2 for Novell and GPLv3 for the FSF they could use.
Likewise, BTW, no contributions that are licensed GPLv2-only can be used in GPLv3 projects.
How many people that would be I don't know. It'd still be worse than everyone sticking with the same GPL. If GPLv3 dri
Re: (Score:2)
Frankly I think those people will not be around long. It would be a horrible nightmare. And I think that now that the GPLv3 hysteria has died down a bit, I think people are becoming more accepting.
Re: (Score:3, Interesting)
No, I just think they are waiting for the next draft.
Re:They can distribute linux (Score:5, Interesting)
Well, I agree that RMS has an image problem. He's a scruffy bearded guy talking about freedom. The former makes you sort of persona non grata in most social circles, because most people care very much about appearances. And let's face it, he would be more effective if he didn't look like he lived under a bridge, or smell like stale cheetos.
But that doesn't make him wrong. Users want freedom. They do not want to be locked in. The only way we can provide freedom to users is to have freedom of software, because software is how users actually use the computers. It's what actually makes you a user, and not just a person sitting in front of a collection of inert boxes.
I don't see what's so crazy about trying to ensure that we can actually use the hardware we paid for.
Re: (Score:2)
Re: (Score:2, Interesting)
Nobody's arguing that software shouldn't be "free" as in OSS, or even "free as in beer".
Where Stallman and the FSF fanatics go wrong is in presenting themselves as "the Messiah" in "saving the world" from ANY violation of their notions of "the way things MUST be done."
This whole bru-ha-ha over Novell is an example. Nothing Novell did was particularly damaging to OSS. Even if Microsoft TRIES to make the deal useful to them in some future patent court case, they aren't going to win it on the basis of the Nove
Re: (Score:2)
That's users who know about the issue. A great manu users (I'm really tempted to say lusers) could not care less about their software freedom or about avoiding lock-in. They don't know the difference between the computer and Windows, and have painfully leared to do the necessary tasks step by step. All they care about is that the interface is pretty with a lot of bells and whistles, so that they can be "Wow:ed".
Re: (Score:2)
Re: (Score:2)
Nothing in GPLv3 or GPLv2 prohibits the distribution of GPLv3 and GPLv2 packages together, so this in itself does not cause a problem. With the second part, I doubt that GPLv3 will be made more restrictive, although I am open to the possibility. I think that it will either remain equall
Re: (Score:2)
Not if they don't remove that silly DRM clause. The very fact that Stallman et al are willing to use the GPLv3 as a bully pulpit for their political views (with which I happen to agree vis-a-vis DRM, BTW) compromises some of the legitimacy of the license and will make it look to many people like some kind of stand in favor of piracy.
You know it isn't and I know it isn't, but CEOs and lawmakers are not likely to see i
Re:They can distribute linux (Score:5, Insightful)
And while it sounds like you understand better, this:
Not if they don't remove that silly DRM clause. The very fact that Stallman et al are willing to use the GPLv3 as a bully pulpit for their political views (with which I happen to agree vis-a-vis DRM, BTW) compromises some of the legitimacy of the license and will make it look to many people like some kind of stand in favor of piracy.
suggests you're missing something. Stallman and the FSF are pressing forward with the same vision and agenda as they always have. Now that free software has achieved some mainstream acceptance -- despite being quite radical already -- you seem to be afraid of pushing the original goals of the project for fear of what short-sighted corporations might think. I'd rather see the goal of freedom be preserved, as I think you do also. Let's not worry about popularity contests. Stick with principal, and let the chips fall where they will. The original license was all about politics, as are all our decisions about how to conduct a free (or closed, or somewhere in between) society.
Re: (Score:2)
Sure, since as everyone knows, the only reason to dislike DRM is because you want to pirate software/movies/music/etc.</sarcasm>
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Informative)
Re: (Score:2)
Novell is by no means alone here. If the FSF "attacks" them with unreasonable terms, they won't be the only company to pull the rug out from under the FSF and its relevance in terms of the marketplace.
Re:They can distribute linux (Score:5, Informative)
Well, I do think you have a point, but the whole point of the free software movement is that the software is Free. I don't see a problem or a disconnect here. Well, okay, I see a problem, largely that those who are in favor of DRM being used to lock down the computer so that you cannot modify it will not be able to use the code in a product which does that. Here is the "objectionable" part of the license:
The Corresponding Source also includes any encryption or authorization keys necessary to install and/or execute modified versions from source code in the recommended or principal context of use, such that they can implement all the same functionality in the same range of circumstances.
So the only form of DRM that the GPLv3 seeks to prohibit (by castration) is that which prevents you from modifying any GPL-licensed code on your device. Let's take a close look at what this actually means. If your box (like a Tivo) is only able to run signed code, then you must give people the means to sign that code. Otherwise, that code cannot be licensed under the GPL.
Well, if you don't believe this, why would you use the GPL anyway? The whole point of the GPL is Software Freedom. It's not about your freedom precisely; as the developer of new software, you already have freedom because you hold the copyright. If you want to license it both under the GPL and to a company under a proprietary license, you have the right to do that provided your licenses do not conflict.
Put another way, people who release code under the GPL want that code to be editable. That's why they use the GPL. Otherwise they could use the BSD license, or just release it into the public domain. But instead, they have chosen the GPL. For their code to wind up in a product where it cannot be modified and run is a serious perversion of their wishes. I think that Tivo was probably the biggest reason that this clause ended up in the GPLv3 draft. I think a lot of people who worked on the Linux kernel were pretty upset when their code was used in such a way that the ability to modify it, the whole reason it's GPL-licensed, was utterly nullified.
Put simply, if you want to be able to use GPL code, you have to be willing to comply with the author's wishes. If you're the type that would follow the letter of their wishes, but not the spirit, then frankly, we don't need you in the Free Software community anyway.
Re: (Score:2)
Re: (Score:2)
This is where the fanaticism shows.
Let's turn it around. Why would anyone wanting to DRM a piece of code write it under the GPL in the first place?
If they aren't going to OSS that code, why would the GPL even be considered as the license for that code?
In other words, the whole anti-DRM provision is irrelevant, because nobody considering using DRM would
Re: (Score:2)
Could you elaborate on what would constitute such a conflict? The only problem with dual-licensing that I see is if you accept contributions without requesting copyright assignment. The problems has already been solved in some way, e.g. by MySQL, although I don't know which method they use.
Re:They can distribute linux (Score:4, Informative)
Huh? How does GPLv3 tell you what you can and cannot do with your own hardware?
Or is your real beef that you cannot tell your customers what they can and cannot do with their own hardware after they buy it?
Re: (Score:2)
I guess that's where his problem is. It is possible that he views the hardware as his hardware even after it has been sold to the consumer.
Re: (Score:2)
That's like saying the only problem with moving the earth is finding a fulcrum and a sufficiently long lever. The cost would be substantial, and the odds of finding enough external developers are not very good.
Re: (Score:2)
The WORST anybody can claim about the deal is that Novell got a lot of money for ALLEGEDLY allowing Microsoft to POSSIBLY say in some FUTURE patent court case that the Novell deal SUPPORTS their contention that Linux infringes their IP.
Did you miss that Steve Ballmer essentially said exactly that just a few days after the agreement was signed, and that the SUSE distribution is the only distribution safe from Microsoft litigation, as it does not have the "undisclosed balance sheet liability" that the rest of the distributions have? This could be considered an unfair advantage in the marketplace for Novell-supplied distributions of Linux, and could drive a lot of businesses over to Novell from the other distributions.
Re:They can distribute linux (Score:5, Insightful)
The parent article said:
Replace "Linux" with any program in the list, and this is what they can do.
If everyone else is using the GPL3 version, sooner or later what distributed by Novell will be obsolete.
Re: (Score:2)
Re: (Score:2)
If the FSF decides to only distribute future versions of its software under the GPLv3+, then Novell may be stuck with 2007 versions of GNU. That won't sit well with customers.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
What number of applications do you consider "lots of apps"? Is it at all comparable to the entire suite of GNU software?
Re: (Score:3, Interesting)
That may or may not be exactly true. I believe the Microsoft/Novell deal covers the cross licensing of various patented technologies. If Novell implements one of Microsoft's patents in a piece of software, and then tries to distribute it as GPL'd software c
Re: (Score:2)
I think this is exactly what is going on, and your other argument isn't what is happening at all. This is a typical 'don't use your patents against us, and we won't use ours against you' business deal. It's very common. You can give Stallman all the credit you w
Re: (Score:2)
The only way for Novell to actually benefit from this deal would be for them to implement Microsoft's patents in new pieces of software that they (Novell) owns outright and distributes under a license other than the GPL. This software would also have to be sufficiently untangled from other GPL software. They could not take a current project covered by the GPL and implement one of Microsoft's patents in it. Or the deal between Microsoft and Novell would have to be such that every patent implemented by Novell, and distributed as part of a software package covered by the GPL, would have to be transferable to (or at least free to use for) every person who receives a copy of said software package.
This is exactly what they're doing. Think about where Novell are coming from - they want to sell to big business. Currently, big business uses solaris, windows, AIUX, HP-UX, allsorts. If Novell want to sell these people support contracts for SLES, they need a way to make their product as attractive as possible. One of the big attractions to corporations is if your software you're trying to sell them can interact seamlessly with whatever they already have. Novell are building commercial tools that allow int
Re: (Score:2)
Or the deal between Microsoft and Novell would have to be such that every patent implemented by Novell, and distributed as part of a software package covered by the GPL, would have to be transferable to (or at least free to use for) every person who receives a copy of said software package.
If the italicized part means that every user would be required to ask Microsoft for a free license, then the software cannot be distributed under the GPL (as far as I have understood it). Licensing software under the GPL requires that any patent license is redistributable to subsequent recipients of the software, without asking the patent holder.
Way to shoot F/OSS in the foot (Score:3, Interesting)
Re: (Score:3, Insightful)
No, you're missing the point (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
You don't seem to get it. The core of the GPL is the protection that you cannot take GPLed code, modify it, and redistribute it with your own imposed restrictions. This prevents unscrupulous characters from taking the code that other people have contributed and co-opting it in a way that benefits only the unscrupulous characters. I.e., it prevents this code from being "embraced and extended". Copyright law gives most of the power to accomplish this, but there is a particular weakness when it comes to pa
Re: (Score:2)
Please. Be honest now. The problem isn't that they made a deal with MS. The problem is that they deal they made was crafted specifically to get around the clear intention of the GPL and many of those that release their software under the GPL. Intentionally or unintentionally on their part.
They either violated the license or found a loophole that many want fixed in the next version.
There is some problem with
Re: (Score:2)
Well, now that would be a great way for OSS to shoot itself in the foot. "Here, we'll give you some ideological crusade disguised as a license, and we can revoke it at any time for as little as making a deal with a corporation we don't like, or having more patents than we like, or also distributing some closed source programs we don't like, or simply because we've had a bad day and don't like you any more." Dunno about Novell, but I'm willing to bet that a lot of companies would drop Linux like a hot potato. Heck, I would, and I'm writing this in Linux.
I think you've entirely misunderstand the issue. First, a quote of the original Novell press release:
Under the patent agreement, both companies will make up-front payments in exchange for a release from any potential liability for use of each others patented intellectual property, with a net balancing payment from Microsoft to Novell reflecting the larger applicable volume of Microsoft's product shipments. Novell will also make running royalty payments based on a percentage of its revenues from open source products.
And now section 7 of the GPL (version 2):
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
You don't have to be a lawyer to realise that Novell are, at the very least, treading close to the line here. The Novell-Microsoft deal implies that there are patent issues with GPLed software Novell sells, and that royalties are being paid by Novell to avoid litigation. The GPL says that software distributed under the license must incur no additional conditions on
Novell is just playing it safe (Score:2)
The fact is: there's a lot of GPL-ed code out there that _is_, in fact, encumbered by IP problems as it is. If you want to be free of any patents or other IP issues, then for example I hope you're not using or distributing an MP3 player or DVD player.
And for a while that's just what Novell did. E.g., one of my annoyances with SuSE 10.0 (which is the one I'm using) is that they removed all MP3 codecs, all DVD decoding, etc. They actually crippled their ver
Re: (Score:2)
I don't think that the FSF would have cared about the Novell-MS deal if it hadn't included the "we will not sue each others' customers" part, as that could empower Microsoft to claim with some credibility that Novell-supplied free software the only "safe" free software. The problem is that this software would hardly be free anymore.
Not Linux, no... (Score:4, Insightful)
But to new versions of the GNU toolchain (gcc, gdb, gas, automake etc.)? To new versions of binutils? To new versions of coreutils? Maybe, yes, if GPLV3 looks anything like the current drafts.
Re: (Score:2)
Gnu tools (Score:5, Interesting)
Oh, they'll start it alright. (Score:2)
Re: (Score:2)
Re: (Score:2)
1. Attack DRM. Consequences for FOSS? Slithe says it'll set it back 5-10 years (probably hyperbole. What is the basis of the logic? I've yet to see any.)
The reason the switch is a problem is that the GPL is now a victim of its own success. There is quite a bit of code out there that has been licensed under the GPLv2. Since the GPLv3 adds additional restrictions, GPLv2 code is incompatible with GPLv3 code. If the GNU project licenses future versions of the GNU tool-chain under the GPLv3, and several major projects remain under the GPLv2, this could either seriously hamper adoption of GPLv3 or it could cause a lot of chaos as distros have to maintain two dif
Re: (Score:2, Insightful)
Maybe the number of FSF developers is small, but managing your own fork would still force you to remove resources from maintenance and development on other projects, so unless you have a strong motivation to cut of your upstr
Re: (Score:2, Insightful)
Does anyone really believe that Novell will update/develop/maintain the GPLv2 versions of ALL of the packages in SuSE that will likely be GPLv3'ed? Recreating GNOME as NOME-vell isn't
Re: (Score:2)
Once the fsf lays down the gauntlet, how many foss developers are going to do a doubletake, and get really nervous about getting tied up in a mess.
Re: (Score:2)
Re: (Score:2)
More likely the opposite.
A few people sem to be forgetting that large parts of the toolchain (compiler, libc, emacs) were previously forked away from the FSF. What happened then was the forks away form the FSF did much better. Eventually things merged back in (except in emacs / xemacs case).
We'll see what will happen this time, but I wouldn't bet against the non-FSF forks being successful.
Free Software Idealists vs. Op
The whole point of GPL v3 ... (Score:2, Insightful)
In other words, if you distribute GPL v3 code, you wouldn't be able to attach conditions, like patent licenses for instance. Free means free and any attempt to circumvent this goes counter to the spirit of the GPL.
Re: (Score:2)
I fail to see how they can keep Novell from distributing gcc, binutils, and so forth if they don't even modify them. Or is the "mere aggregation" clause completely out now. Libraries might have some leverage, but the only one that links to more or less everything is glibc, which is under the LGPL. I sure wouldn't mind concerted efforts to kill glibc, but for purely technical re
Re: (Score:2)
I fail to see how they can keep Novell from distributing gcc, binutils, and so forth if they don't even modify them.
All of these packages are copyrighted. The copyright is owned by the FSF. You may not distribute copyright works unless you have the permission of the copyright holder. The copyright holder (the FSF) grants a non-discriminatoy licence for free to anyone who is willing to abide by a set of conditions preventing them from limiting the freedoms of other software users (the GPL). If Novell do not act in accordance with the GPL (version 3, at some hypothetical point in the future) then they are not going to
Try removing glibc some time (Score:5, Informative)
apt-get remove libc6
Re: (Score:2, Funny)
Haha mod parent up +1 Funny. (Score:2)
Re: (Score:3, Interesting)
What about GNU projects moving to GPL 3? (Score:5, Informative)
However, the FSF is the principal sponsor of the GNU project, and run by the same people.
So, we can expect most GNU stuff to move to GPL 3. If GPL 3 mucks up the Novel deal, I do not see that Novel is going to find it very useful to be able to distribute the Linux kernel without all the GNU stuff.
Re: (Score:2, Insightful)
Re: (Score:2)
Nothing is preventing the last v2 codebase from being forked. Once that happens, the question will be how many of the developers are loyal to the FSF/GPLv3, and how many would rather stick with GPLv2? The answer to that question will
Re: (Score:2)
Why I read Slashdot (Score:5, Funny)
This just reinforces why I read Slashdot instead of other news, there's no chance of something like this happening here.
Not That Simple (Score:4, Insightful)
> distribution of Linux.
The FSF owns significant copyrights in the Linux kernel as well as in many utilities and applications.
> The Novell deal is completely within the bounds of the GPL...
While I agree that this is probably true, it is a legal opinion. I am not a lawyer. Are you?
> GPLv3 isn't even done yet, and even when it is the Linux kernel is unlikely
> to be covered by it.
True, but irrelevant.
I agree that the Reuters reporter is an ignorant doofus, but this is no reason to follow him off the deep end.
Re: (Score:2)
> GPL [linux-watch.com], so I think it is fair and reasonable to state it as a
> fact and not an opinion.
Richard Stallman is also not a lawyer (nor a judge) and neither he nor his organization own most of the copyrights in question. While his opinion carries a lot of weight I give it a great deal of respect, it remains an opinion.
To repeat (this _is_ Slashdot), In my opinion Novell is in full compliance with the GPL. H
furthermore... (Score:2)
Novell isn't in the clear yet (Score:2)
Talk about irresponsible reporting! (Score:2)
The first part is unconditionally, unequivocally untrue. As the copyright holders in part of the Linux kernel, Novell has the right to distribute it ONLY because the FSF (and other copyright holders) have licensed them to do so via the GPL. Therefore the FSF does in fact have a great deal of control over Novell's distribution of Linux. Novell must distribute under the GPL, or they must secure a separate lic
Re: (Score:2)
And yet, Richard Stallman and Eben Moglen seem to agree that you are mistaken. [linux-watch.com]
Re: (Score:2)
Most of the Hurd Mach kernel is not FSF copyright assigned either.
Tempest in a teapot. (Score:2)
Re: (Score:2)
The Novell deal, while legal, goes against the spirit of the GPL, because they have negotiated a patent deal with a third party, but only for only their own customers.
The GPL 3 will fix this problem by ensuring that any patent deals must be applied to anyone who receives the code (customers or not).
Time to fork the GPL (Score:2)
Microsoft ships GPLed software alongside all KINDS of non-GPL-ed programs that are only available for their own customers, and Microsoft (obviously) also "protects" their customers from all those same patents.
Apple ships GPLed software alongside all KINDS of non-GPL-ed programs that are only available for their own customers, and Apple's APSL
Re: (Score:2)
That's a different situation. If the entity that owns the patents is also the one distributing, then section 7 of the GPL already covers that, and the patent protection is passed on to whoever recievers the code, directly or indirectly.
The Novell case is different because Novell is distributing, and Mi