Slashdot Mirror


Novell Won't Lose Right To Sell Linux

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.

34 of 216 comments (clear)

  1. Well, duh. by EveryNickIsTaken · · Score: 4, Informative

    Anyone who read the comments section of that story would know this.

  2. Premise is counterintuitive by Salvance · · Score: 4, Insightful

    Isn't the whole point of open-source software free distribution, repackaging, use, modification, etc.? Unless there are non-OSS components that Novell is distrubting, I don't see how the FSF or anyone else would ever have any control over their "distribution rights", unless Novell tried to close the source and violate the license agreements.

    --
    Crack - Free with every butt and set of boobs
    1. Re:Premise is counterintuitive by at2000 · · Score: 2, Informative

      GPLv2:

      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 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. [...]

      FSF can also ask for an order from the court to refrain them from distributing any more copies. This order will precede the rights granted by the license.

    2. Re:Premise is counterintuitive by hendersj · · Score: 5, Informative

      Stallman has said unequivocally that Novell has not violated GPLv2. He's said there should be something in GPLv3 to prevent this sort of thing from happening, but very clearly has said that there is no Section 7 violation.

      --
      Insanity is a gradual process; don't rush it.
    3. Re:Premise is counterintuitive by greginnj · · Score: 2, Informative

      Let's not forget that while Stallman can opine authoritatively on his intent when writing the GPLv2, his intent or his current interpretation thereof is not binding on a civil court. The GPLv2 exists independent of Stallman's interpretation, and anybody who holds copyright on software distributed by Novell would have standing to challenge them in court if that copyright holder feels that Novell infringed. Stallman's opinion would serve as a possible interpretation offered by the defense, nothing more.

      --
      Read the best of all of Slash: seenonslash.com
    4. Re:Premise is counterintuitive by theLOUDroom · · Score: 2, Informative

      Stallman has said unequivocally that Novell has not violated GPLv2.

      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 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."

      If you buy a CD from Novell and then burn me a copy, I've just indirectly reveived a copy from Novell, but I have NOT been transferred all the patent licenses that you have.

      It's also worth noting that RMS can issue whatever statement he wants, but if someone else doesn't like Novell distributing their GPLv2 software in this manner, Novell could still be on the receiving end of a lawsuit.

      --
      Life is too short to proofread.
    5. Re:Premise is counterintuitive by hendersj · · Score: 2, Informative

      Stallman has said unequivocally that Novell has not violated GPLv2.

      Got a link to back that statement up? Yes. Link.
      --
      Insanity is a gradual process; don't rush it.
  3. They can distribute linux by at2000 · · Score: 4, Interesting

    They can distribute linux, but can they distribute glibc, coreutils, gcc, gdb, bash, tar, gzip, gpg, grep, gettext, readline, troff, ...?

    1. Re:They can distribute linux by LurkerXXX · · Score: 4, Informative

      Anything under a BSD or GPL license, yes, they can distribute (as long as they provide source for the GPL stuff). They didn't violate the GPL, so they don't lose the license. If GPL3 is ugly, they will probably simply keep using the regular GPL version.

    2. Re:They can distribute linux by drinkypoo · · Score: 5, Informative

      If GPL3 is ugly, they will probably simply keep using the regular GPL version.

      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.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:They can distribute linux by at2000 · · Score: 4, Insightful
      For sure we are talking about new version of the said programs/libraries.

      The parent article said:

      If the foundation decides to take action, the ban would apply to new versions of Linux covered under a licensing agreement due to take effect in March.

      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.

    4. Re:They can distribute linux by Wannabe+Code+Monkey · · Score: 2, Interesting

      Anything under a BSD or GPL license, yes, they can distribute (as long as they provide source for the GPL stuff). They didn't violate the GPL, so they don't lose the license. If GPL3 is ugly, they will probably simply keep using the regular GPL version.

      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 covered by version 2, they would still be in violation.

      From the GPL:

      Preamble

      ...
      Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

      Terms and Conditions

      7. ... 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.

      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.

      What's more likely is that Novell is just using this as a marketing technique where they can say, "Other Linux distributions are probably infringing on lots of Microsoft's patents, we have the only distribution safe from a lawsuit from Microsoft." Either way, I don't like the way Novell is heading, but Stallman was smart enough to foresee this possibility when he wrote the GPL and I think he should get more credit than he does.

      --
      We always knew Comcast was corrupt, here's the proof: http://tech.slashdot.org/comments.pl?sid=1909890&cid=34545432
    5. Re:They can distribute linux by ConceptJunkie · · Score: 2, Interesting

      And I think that now that the GPLv3 hysteria has died down a bit, I think people are becoming more accepting.

      No, I just think they are waiting for the next draft.

      --
      You are in a maze of twisty little passages, all alike.
    6. Re:They can distribute linux by omeg · · Score: 2, Informative

      You're correct. They'd have to start maintaining their own GPLv2 fork of the GNU toolchain, as they wouldn't be able to use any GPLv3 code. Any code that Novell would want in the GPLv3 versions of the software would be rejected. Afterall, it seems that Novell is exempt from patent infringement litigation, which means that there's the possibility of patented code being inserted into GPL programs if they're allowed to edit it, and that would be a serious problem. Because they've made this dodgy deal with Microsoft, I actually wouldn't be very surprised if they tried using this loophole to get Microsoft to be able to sue other major Linux vendors.

    7. Re:They can distribute linux by drinkypoo · · Score: 4, Informative

      How dare anyone tell me what I can and cannot do with my own hardware. I am looking forward to the GPL2 / GPL3 fork so we can get that nut Richards Stallman out of our business.

      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.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:They can distribute linux by F452 · · Score: 4, 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.

    9. Re:They can distribute linux by CoughDropAddict · · Score: 3, Informative

      I don't know about anyone elses, but IMHO GPL3 is as invasive a liscense agreement as the one in Windows Vista. How dare anyone tell me what I can and cannot do with my own hardware.

      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?

    10. Re:They can distribute linux by drinkypoo · · Score: 4, Interesting

      I haven't wanted to release code under the GPL since 98, when I actually started listening to what RMS was saying instead of what we all thought RMS was trying to say. The man's a lunatic.

      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.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  4. Not Linux, no... by morgan_greywolf · · Score: 3, Insightful

    Linux, as in referring to the Linux kernel? Not likely, of course, for reasons TFA states.

    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.

  5. The whole point of GPL v3 ... by Anonymous Coward · · Score: 2, Insightful

    is to make sure people cannot distribute FOSS in an 'encumbered' manner.

    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.

  6. Try removing glibc some time by myowntrueself · · Score: 4, Informative

    try this on a debian/ubuntu system:

    apt-get remove libc6

    --
    In the free world the media isn't government run; the government is media run.
    1. Re:Try removing glibc some time by friedman101 · · Score: 2, Funny

      okay, i did it. now wh

    2. Re:Try removing glibc some time by Raul654 · · Score: 2, Interesting

      I remember I nearly fell out out of my chair when I found out Ubuntu Dapper didn't come with gcc by default. The idea that Linux would (nay, could) be shipped without gcc was quite shocking. IMHO, where usability is concerned, it's a huge a step in the right direction (by not requiring the end user to compile his own code) but it was shocking nonetheless.

      --


      To make laws that man cannot, and will not obey, serves to bring all law into contempt.
      --E.C. Stanton
  7. What about GNU projects moving to GPL 3? by the_womble · · Score: 4, Informative

    Its true that the FSF does not have the power to move the Linux Kernel to GPL version 3.

    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.

    1. Re:What about GNU projects moving to GPL 3? by FishWithAHammer · · Score: 2, Insightful

      Except for all the GPL2 software that's already out there.

      --
      "You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
  8. Why I read Slashdot by flynt · · Score: 5, Funny

    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.

    This just reinforces why I read Slashdot instead of other news, there's no chance of something like this happening here.

  9. Not That Simple by John+Hasler · · Score: 3, Insightful

    > Well, the Free Software Foundation has absolutely no control over Novell's
    > 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.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  10. Gnu tools by flaming-opus · · Score: 4, Interesting

    But the current versions of those tools are all licensed under GPLv2. If the FSF wants to play hardball, and releases future versions under GPLv3, Novell, or anyone else for that matter, can fork the GPLv2 version and continue developments from that base. The FSF would have to count on the community adopting the v3 versions, rather than the v2 versions. Since the number of FSF developers is small, relative to the number of other contributors, it's a fight the FSF may not want to start.

    1. Re:Gnu tools by clacke · · Score: 2, Insightful

      This is exactly the fight they want to start. And the draft process is open exactly because they don't want people to jump ship once they switch. I highly doubt that any Debian developers will do that, and I don't think that any of the commercial entities will fork it for Novell's sake.

      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 upstream, you won't. The community will take what GNU gives them.

    2. Re:Gnu tools by seandiggity · · Score: 2, Insightful

      ...not to mention that the developers who are most involved with GNU projects wouldn't want to work on Novell's forked projects A) because many share RMS's ideology and B) because they have no incentive to jump ship on the project they've been working on for Novell's version (in fact, the corporate oversight is a turn-off).

      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 gonna be easy, even if you can port BSD-licensed replacements for some of the core utilities.

      ...I didn't mean to leave out KDE but I couldn't do the "clever" wordplay.

      --
      Geeks like to think that they can ignore politics, you can leave politics alone, but politics won't leave you alone.-rms
  11. Way to shoot F/OSS in the foot by Moraelin · · Score: 3, Interesting

    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.

    The thing is, the whole thing doesn't even have a moral high ground any more if it tries to rule with an iron fist over anything else you might do, including business relations, deals, IP, God-knows-what-else. I mean, wth, if MS even hinted at including a "we can revoke your license if you make deals with companies we don't personally approve of" clause in their EULA, everyone would be screaming bloody murder. Yet here we are talking about, basically, "let's change the GPL so we can punish Novel for making a deal with MS", as if it was some righteous thing to do. WTF?

    The very idea of sneaking in some sort of "thou shalt not make deals with MS" or generally "though shalt toe the party line" in the name of "freedom of speech" rethoric is... bizarre, to say the least. If ESR and RMS have freedom so dear (and you'd think so given all the rants about how the GPL is all about your freedom), then the advice that comes to mind is to actually respect it, and I don't mean just for code. Freedom means just that: being free to do whatever the heck you like. Including dealing with MS, writing/installing/distributing a binary-only module, or whatever. As long as I'm _not_ in fact suppressing your coding freedoms, have the decency to not try to suppress my (other) freedoms either.

    Honestly, the whole idea is reminiscent of some of the worst crops of banana-republic dictatorships. Start by fighting some colonial/imperialist/whatever oppressor, and end up with less freedoms than you had under the old colonial oppressors.

    --
    A polar bear is a cartesian bear after a coordinate transform.
    1. Re:Way to shoot F/OSS in the foot by cparker15 · · Score: 3, Insightful

      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.

      No, you wrote your tirade in a Web browser, which displays with the aid of a graphics toolkit, which runs on top of your window manager, which runs on top of X, which runs on top of the kernel called "Linux". You can't write things "in Linux". People need to understand the distinction between a kernel and some programs run on top of an operating system, which runs on top of a kernel.

      This "idealogical crusade", as you put it, is what gave developers the freedoms necessary for creating Linux and all of the other free components of your operating system.

      There's also a fundamental difference between free/proprietary and open source/closed source. They may look similar on the outside, but in actuality, they are very different. Generally, a person who uses free software shuns proprietary software because they understand the dangers that come coupled with it. Conversely, a person who uses open source software typically doesn't have a problem with using closed source software and often uses both in parallel without making an effort to replace the closed source software with an open source software alternative.

      Free is a matter of principals and ethics. Open source is a matter of convenience and cost.

      If you want to abandon the freedoms that free software affords you and lock yourself into a proprietary system where its creators have complete control over what you can and cannot do with your computer, by all means, go right on ahead. But don't come crying back to the community when Microsoft or Apple have implemented a feature in their operating system that prevents you from being able to run your open source software in conjunction with their closed source software*, because you've been warned well in advance.

      * See also Trusted Computing.

      --
      Have you driven a fnord... lately?

      You must wait a little bit before using this resource; please try again later.

  12. Re:GPL is'da bomb by sconeu · · Score: 2, Informative

    Drivers are part of the kernel, which is not under GPL.

    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.

    --
    General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
  13. Re:GPL is'da bomb by EsbenMoseHansen · · Score: 3, Insightful

    but GPL is a "bomb". Not a "time bomb" (for the explosion is not certain), but a remotely activated one whether or not you trust the people, who hold the activator, you'd be comfortable without the bomb entirely.

    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.

    --
    Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.