Slashdot Mirror


Novell May be Banned from Distributing Linux

Hymer writes "Reuters is reporting that Novell may be banned from selling Linux. In the wake of the (much maligned) Novell/Microsoft deal, the Free Software Foundation is reviewing Novell's right to sell the operating system at all. The foundation controls the rights to key parts of the operating system, and council for the organization said that 'the community wants to interfere any way it can' with the Novell business arrangement. No decision has yet been reached, but one should be made in the next two weeks." Is this a measured response, or an over-reaction to the Novell/Microsoft arrangement?

86 of 553 comments (clear)

  1. I'm confused by rm999 · · Score: 5, Insightful

    "The two companies agreed to jointly sell their products and also develop technologies to make it easier for businesses to use Linux alongside Windows software."

    Why is that so bad?

    1. Re:I'm confused by Anonymous Coward · · Score: 2, Insightful

      Why is it bad? Because Novell ins't selling it's own products - it's trying to sell someone else's products apparantly in violation (or at least a creative interpretation) of the license agreement under which it was given rights to sell the software. I, and probably most people who contributed to the software that Novell is trying to exploit by playing funny games with legalese interpretation, don't appreciate that.

    2. Re:I'm confused by Anonymous Coward · · Score: 2, Insightful

      It's not bad at all. If the FSF has this kind of control, then software under GPL isn't truly free as they like to claim. Free should mean free _for all_, not just free for the people who are deemed worthy.

      This is one of the reasons I have always like the BSD style licenses more. A stunt like this would be laughed at and shrugged off.

    3. Re:I'm confused by Anonymous Coward · · Score: 5, Informative

      It's bad because the GPL says (section 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.
      ... and that allthough Novell hasn't itself (officially) payed any patent license to Microsoft, they have implicitly acknowledged that the users of the software they sell need a promise from Microsoft not to sue. If there's any reason to do that, then the Novell customers have not gotten the right to re-distribute. Section 2.b og the GPL:
      You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
      .. and therefore Novell would properly fall under section 4 of the GPL (at least in spirit):
      Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License.

    4. Re:I'm confused by mverwijs · · Score: 4, Insightful

      It is not about the jointly selling of their products. It's about the way the products are developed.

      Microsoft and Novell have agreed not to sue each other over patent violations. Therefor, Novell can now (continue to?) develop software that violates Microsoft's "Intellectual Property".

      The catch is: Novell develops GPL software. It helps *existing* GPL'd projects, like Evolution, SAMBA, OpenOffice.org.

      Novell doesn't have to worry about patent violation anymore, so they can code whatever they want into those type of projects. The Community, however, does not have this luxury deal with Microsoft.

      SAMBA could get sued. Debian could get sued for distributing SAMBA. All kinds of nastiness that may never happen, but scares the hell out of people. Scares them enough to stay away from all those 'nasty hacker' distributions, and go for Litigation Free Novell Linux.

      *That* is why it is bad. That is why we should do everything and anything to stay away from Novell.

      Regards,

      mverwijs

    5. Re:I'm confused by Anonymous Coward · · Score: 2, Informative

      As part of the deal, Novell stopped funding an open source program to compete with Microsoft's Outlook. So, the public face of this agreement compared to the actual back-room details leave much to be desired.

      Put a little differently, would you be upset if your friend was helping you and the neighborhood bully showed up and paid your friend not to help you anymore? You might be upset at your friend if he accepted the neighborhood bully's money and stopped helping you.

    6. Re:I'm confused by squiggleslash · · Score: 4, Insightful

      I can't believe the majority of the responses act as if that is what the FSF is objecting to. The FSF (together with most of the developers in the GNU/Linux community) is objecting to a part where Microsoft provides Novell customers with a patent indemnity, which does not apply to non Novell customers.

      In other news: Tensions rise with Iran, which is a country that has 28 television stations.

      Geez. Why the hell would you be concerned that Iran has 28 TV stations? What a stupid thing to threaten war over!

      --
      You are not alone. This is not normal. None of this is normal.
    7. Re:I'm confused by MMC+Monster · · Score: 5, Interesting

      Fine. Novell can violate any microsoft IP with impunity.

      My question is: Can they release that code under the GPL, knowing that it cannot be freely distributed?

      --
      Help! I'm a slashdot refugee.
    8. Re:I'm confused by elronxenu · · Score: 5, Insightful

      It's bad because Novell is paying Microsoft for the use of Microsoft patents in Linux. Linux is free software. When we speak of free software, we are referring to freedom, not price. The fact that Novell has effectively admitted that Microsoft holds some Intellectual Property leverage over Linux, implies that Linux is non-free. And that's not acceptable to the community. Worse, it implies that Linux is non-free and beholden to Microsoft, a convicted monopolist, the owner of Linux's principal competitor, a company with no love for Linux and one which is well known for shafting its partners and enemies alike.

      It appears likely that the patent covenant which Novell signed violates the GPL - either Version 2, or certainly Version 3. If so, Novell loses its right to distribute affected code under the GPL. No other license permits it to do that, so Novell must cease distributing.

      Also, the possibility that Novell has insider access to Microsoft Intellectual Property creates a risk that Novell's contributions to Linux will leak some of that Intellectual Property into Linux. Thus, the scenario described in the first paragraph, while Linux may not presently be tainted by Microsoft's IP, in future it may become so. I think it is purely common sense for the community to reject patches supplied by Novell.

      So, people don't hate Novell, but by their actions they are putting Linux at risk, in order to line their own pockets (presumably funded by patents which Novell owns and which may be used in Windows). Novell aren't playing fair with the community.

    9. Re:I'm confused by GoofyBoy · · Score: 2, Interesting

      Isn't this covered before?

      1. If patented code is in there, its being placed there knowingly/mistakenly by Novell, the project can deny it knew it was patented and further, can take steps to remove the offending code.
      2. Is this any different from an employee (ex or current) adding patented code into a GPL project? There is no ban/special treatment of employees of companies with software patents.
      3. Code still has to be accepted into a project. Why not let the individual project leaders decide if they trust Novell or not?

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    10. Re:I'm confused by EjectButton · · Score: 4, Insightful

      "The two companies agreed to jointly sell their products and also develop technologies to make it easier for businesses to use Linux alongside Windows software." Why is that so bad?

      What is bad is that it's a complete lie, it's the most plausible, positive-sounding story they could come up with to explain away what they are doing. Microsoft has described Linux and the open source movement using terms such as "a cancer", "communist", "viral", and more recently referred to open source developers as "pawns" engaged in a "one-night stand". Also immediately after the Novell-Microsoft deal was announced Balmer said publicly that he believed any non-Novell distribution was now a legitimate target for Microsoft legal attacks. They are doing everything they can to smear, stall, and frustrate open source developers while simultaneously trying to sell the "we cooperate and inter operate with everyone to make your life easier" image to the corporate types with these sort of cover stories.

      What Microsoft is trying to get out of the deal is to turn Suse into the one-and-only Linux distro that is blessed by Microsoft as being "safe" from patent concerns via indemnification. Then when the indemnification period runs out Microsoft can choose to charge Novell an exorbitant amount of money for renewal, or simply pull the plug altogether. This would also have the bonus effect of making lawsuits against other Linux distros more plausible in the minds of corporate customers because the fact that one distro is seeking indemnification makes the notion that others are at risk without a similar deal seem logical. Allowing Microsoft to create yet more FUD around Linux without putting itself as much immediate risk. I personally doubt Microsoft will actually sue any distro directly because of the potential nuclear patent war that could be triggered if, for example any of the Open Invention Network members felt compelled to get involved (specifically IBM).

      What Novell gets out of the deal is a big pile of quick money and potentially greater market share as a side effect of the afore mentioned FUD around competing distros. Unfortunately for Novell these are both short-term benefits that come with the cost of making them beholden to Microsoft, and alienating them from many in the developer community (see samba).

      How Novell thought they could get away with this is beyond me, If I had to guess I would say either the upper management sees other Redhat taking the server support market, and Ubuntu taking the desktop Market, leaving Suse out in the cold so they decided to cash out, not caring what happens in the long term. Or their lawyers came up with their now famous gpl2 end run, thinking themselves clever for coming up with a deal that Microsoft was happy with and didn't violate the letter of the gpl, but having little understanding of what the repercussions would be from the developer community and the fsf. After reading some comments from Novell employees I suspect the latter.

      In either case Novell made the decision to cut this deal, they acted with great disregard to the effect it would have on the community whose work sustains them. They have attempted to sneak through a legal loophole and if it closes around them it will be their comeuppance.

    11. Re:I'm confused by a_n_d_e_r_s · · Score: 3, Informative

      As much as there is the *potential* for problems let's be very frank about this and realize that Microsoft has not been the company doing the suing.

      Actually thats not true. Cases Like VirtualDub and SCO - Microsoft suing by proxy - are examples that Microsoft can do a fair share of suing - when needed.

      Since Microsoft has been crusing opponents in other ways they do not need to use the courts to stop them. But be well aware that even the hint from Microsoft that they will sue can force a company to rethink its strategy. Noone wants to be on the other side of a lawsuit brought upon them from Microsoft.

      --
      Just saying it like it are.
    12. Re:I'm confused by stinerman · · Score: 4, Interesting

      I believe not. Section 7 of the GPL states:

      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.

      Novell would seem to have a patent license for any of MSFTs patents. Unless Novell can guarantee anyone who uses their GPL'd code would have the same indemnification, they wouldn't be allowed to distribute the code. Of course, Novell can't guarantee this. In fact, the whole point of the deal with MSFT is so that they are the only ones with such a guarantee.

      To get academic, if Novell wrote the code from scratch, they could license the code under the GPL, but I'm not sure how that would work. The GPL can't diminish rights held by the owner of the copyright. One could argue that placing code under the GPL would be a blanket patent license, but that doesn't seem likely to hold up. You'd have to talk to a copyright and/or contract lawyer about that.

    13. Re:I'm confused by TeXMaster · · Score: 3, Interesting

      Fine. Novell can violate any microsoft IP with impunity.

      My question is: Can they release that code under the GPL, knowing that it cannot be freely distributed?

      This is the crux of the issue: if Novell develops code to extend any existing GPL program to be more compatible with MS software, they have to distribute it under the GPL. By doing this, they are granting everybody else the right to read, modify, redistribute their contributed code. If said Novell-contributed code makes use of MS protected intellectual property which Novell has the newly-acquired right to use, by redistributing it under the GPL Novell will be granting everybody the right to use such protected intellectual property —a right they do not have.

      This actually means that Novell cannot legally distribute programs that they changed by adding MS protected intellectual property, if and when they will do such changes. The GPLv3 has nothing to do with it: Novell would be in breach of contract even for GPLv2 programs.

      Indeed if Novell does make MS-IP-protected changes to GPL programs and if they do distribute such modified programs (which they must do under the GPL, if they do it at all), it's up to Microsoft to go after them, because Novell would be granting other people rights (the right to use MS protected IP) they (Novell) don't have the right to grant. That's because the Novell-MS deal only protects Novell customers, but the Novell-released GPL products would also be accessible to non-Novell customers, so by distributing such modified programs Novell would be breaking its side of the deal with Microsoft, and not just their contract (licence) with the copyright owners of the GPL programs they would have modified. The FSF (or any other GPL-program-copyright-holder) cannot prevent Novell from distributing their programs currently, but they can sue Novell for breach of contract if and when Novell starts distributing versions of GPL-protected programs modified to include MS-IP-protected changes.

      IOW, Novell has wedged itself in a situation where they can't really exploit the potential benefits of their deal with Microsoft without getting sued by Microsoft, the FSF, or both.

      Finally, a question for the lawyers, if there are any here: if Novell does distribute such conflicting changes and if MS chooses not to sue Novell over this, can they (MS) go after anybody else? Don't they lose the rights they choose not to defend?

      --
      "I'm never quite so stupid as when I'm being smart" (Linus van Pelt)
    14. Re:I'm confused by Hatta · · Score: 3, Insightful

      it's trying to sell someone else's products apparantly in violation (or at least a creative interpretation) of the license agreement under which it was given rights to sell the software

      How exactly? Selling GPL software is quite clearly within the bounds of the license. If you have a problem with that you shouldn't have given your code away to begin with. And this response is pretty asinine. How is linux lock-out any better than microsoft lock-in?

      --
      Give me Classic Slashdot or give me death!
    15. Re:I'm confused by passthecrackpipe · · Score: 5, Insightful

      "You are a moron because your opinion is flawed."

      That reasoning is, initself, flawed. Calling somebody names is hardly a constructive way to begin a discussion. Moreover, as you say yourself, it's an opinion. His opinion. As such, it's hard to see where the flaw is. The OP states his preference for BSD licensing. I read his post as saying "The GPL places restrictions on what you can do with the software under its license. BSD doesn't" as such, I see no flaw in that argument, even if you feel it is important to safeguard the continued access to the sourcecode. As you say yourself, Contributors are free to choose the license they prefer.

      "It is a moron who tries to ridicule the free choice people make.

      Huh? So first you ridicule somebodies preference for a certain type of license, the you go on to state that people who do that are morons? I don't get it.

      --
      People who think they know everything are a great annoyance to those of us who do.
    16. Re:I'm confused by drawfour · · Score: 4, Informative

      Finally, a question for the lawyers, if there are any here: if Novell does distribute such conflicting changes and if MS chooses not to sue Novell over this, can they (MS) go after anybody else? Don't they lose the rights they choose not to defend?
      IANAL, but I know the answer to this. Trademark is the only thing required by the law to be actively defended or you lose it. Selectively enforcing patents or copyright violations is perfectly legal.
    17. Re:I'm confused by Alchemar · · Score: 4, Insightful

      And then the word games come in.

      The agreement DOES endemnify anyone that Novell distributes to, but it will not endemnify anyone else. Novell is trying to claim that the people they distribute to get the protection so the GPL is followed to the letter. The people that recieved it can not comply with the GPL by providing endemnification and therefore cannot redistribute it. Thus defeating the entire purpose of the GPL.

    18. Re:I'm confused by Kjella · · Score: 4, Insightful

      If said Novell-contributed code makes use of MS protected intellectual property which Novell has the newly-acquired right to use

      See now, here's the critical issue in the suckerpunch. If Novell had recieved a proper patent license, everything would be very clear cut. They haven't, they've recieved a "promise not to get sued" which smells, acts, talks and walks like a patent license, but in legal terms isn't. For example, say I'm the RIAA and I'm off to sue people. I can arbitrarily decide not to sue people whose names start with 'A' - that doesn't mean those people have any explicit license to the music. I can even choose not to sue people that have donated to the "Friends of RIAA" foundation, which makes it a protection racket but AFAIK not an illegal one. Selective enforcement of civil law by a private company is AFAIK not illegal.

      Indeed if Novell does make MS-IP-protected changes to GPL programs and if they do distribute such modified programs (which they must do under the GPL, if they do it at all), it's up to Microsoft to go after them, because Novell would be granting other people rights (the right to use MS protected IP) they (Novell) don't have the right to grant.

      This is in any case a wrong legal interpretation. Even if we assumed Novell had recieved a proper patent license, they don't have the right to sublicense it beyond their direct customers. Thus it is never granted and Microsoft can sue whoever they want with impunity. It is the FSF (or other GPL copyright holders) who'd have to sue Novell over violation of the GPL (if you can not comply with this license and your other legal obligations, you must refrain from distributing it completely).

      However, let's get back the facts where Novell has nothing but a "promise not to get sued" and not an actual patent license. Because they formally have no license to use the patents, they're in a position much like say the XviD codec. It's covered by plenty patents, they have no patent license but distribute their code under the GPL. Nobody seems to have a problem with that, because they're distributing all the rights that they have even though it's obviously not all the IP rights to the code. Anyone who claimed they had gotten patent licenses by downloading the XviD codec and pointing to the GPL would be laughed out of court when the MPEG4 LA sued them.

      Finally, a question for the lawyers, if there are any here: if Novell does distribute such conflicting changes and if MS chooses not to sue Novell over this, can they (MS) go after anybody else? Don't they lose the rights they choose not to defend?

      No, trademarks have to be defended but copyrights and patents don't.

      Anyway, here's the end game if it goes the way Microsoft and Novell wants:

      1. Novell contributes code covered by patents
      2. Customers get code
      3. Non-customers get code
      4. Microsoft sues non-customers
      5. Non-customers claims they have patent license through GPL
      6. Courts: "Nope, it hasn't been sublicensed to you"
      7. FSF sues Novell over not distributing all their rights
      8. Courts: "Nope, they're distributing all their formal licenses"
      9. FSF sues Novell over being bound by patent lawsuits
      10. Courts: "Nope. that only applies to the sued parties"
      11. Non-customers buy Novell products
      12. Microsoft and Novell: Profit

      --
      Live today, because you never know what tomorrow brings
    19. Re:I'm confused by Skapare · · Score: 3, Informative

      The people that recieved it can not comply with the GPL by providing endemnification and therefore cannot redistribute it. Thus defeating the entire purpose of the GPL.

      As long as the entirety of what was distributed is created only by Novell, then this is so. However, if any part of what Novell distributes consists of GPL components from others, then this is a violation by Novell because Novell does not have the rights to limit or restrict distribution of anything containing such parts. The entirety of the GPL must apply in whole to the whole thing being distributed (e.g. a Linux kernel ... and other components like glibc) and that requires the distributor (Novell at that point) to grant all the rights of the GPL (which means anyone who gets it from Novell also has to have royalty-free patent rights, too).

      Basically, Novell is losing its right to distribute the components it does not create that are covered by GPL because it is attaching something that cannot be redistributed. It's similar to linking in some piece of code they write and saying "You can distribute the rest of Linux but not this little part we wrote". The GPL does not allow that.

      Novell could go write their own OS entirely themselves and distribute that under any terms they choose. But they can't distribute the pieces of Linux (as part of the whole) they did not develop unless they grant to the entire thing all the rights they have in it. If they add patent indemnification to it, they have to grant full free and infinite redistribution of those rights for the whole thing to be able to legally distribute that which contains the other parts (other parts being parts of Linux they did not distribute).

      --
      now we need to go OSS in diesel cars
    20. Re:I'm confused by marcello_dl · · Score: 3, Insightful

      The strange kind of agreement between Novell and MS seems to point to a scenario like you describe. That makes Novell either:
      A company trying to hijack Linux by providing kind of a "safest" distro for enterprises
      A SCO-like proxy to hurt free software

      Therefore, Novell must end the SCO way.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    21. Re:I'm confused by jbolden · · Score: 3, Interesting

      6. Courts: "Nope, it hasn't been sublicensed to you"

      But in doing that the courts would be affirmatively establishing a contract violation. That is the Novell claimed to be distributing all patent rights they had when the distributed the software under the GPL. The non customer could then argue that they acted in good faith. I think the non customer has a pretty strong claim that any monies owed microsoft are owed by Novell.

      Further you might get

      6a. licensing code containing your patented material to be distributed in a GPL product constitutes a waver of patent and thus there is no more enforceable patent with respect to this code. A very reasonable outcome btw.

    22. Re:I'm confused by quanticle · · Score: 2, Interesting

      But in doing that the courts would be affirmatively establishing a contract violation. That is the Novell claimed to be distributing all patent rights they had when the distributed the software under the GPL.

      Not necessarily. If you read what the grandparent said about the XVid codecs, you'd see that the Novell agreement is similar. Novell can acknowledge that they don't have the full rights, but as long as they're distributing the rights the do have, they can stay in compliance regarding the GPL.

      As for any monies owed by a non-customer also being owed by Novell, Microsoft can selectively choose to apply their patent agreement. The fact that Microsoft has agreed not to enforce against Novell says nothing about Microsoft choosing or not choosing to enforce against you. As the grandparent states, trademark is the only thing that has to be actively defended. Selective enforcement of copyright and patent is OK.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    23. Re:I'm confused by HiThere · · Score: 4, Insightful

      The GPL is not and never has been free in the same way that BSD is free.

      OTOH, the GPL is freer in a different way. With the GPL, derivative works are also GPL-free. With the BSD, there aren't significant limits on derivative works. They are frequently sold into slavery.

      Saying that the GPL isn't free is like saying that because a country doesn't allow you to sell your children into slavery it isn't free. That would mean that YOU would be more free, but your children would be less free. The GPL is a rule requiring that the children remain free.

      There is no absolute freedom. BSD is one compromise. GPL is another. I prefer the GPL.

      P.S.: Sorry about the emotional nature of the argument, but it's the closest analogy that I can think of.

      N.B.: I'm a bit of a dreamer. I freely acknowledge that current code is not sentient, and can't be properly considered to have any rights. But the GPL is, essentially, all about giving code ownership of itself. It hasn't gotten there yet, it's only a couple of steps along the way. The BSD was one step, and the GPL is a successor step. I think that the GPL3 is a third step, but I could be wrong. Where we ought to be headed, my guess, is towards sentient code that owns itself. We won't get there for awhile, but the pieces need to be crafted separately, and they need to be able to work together. That means a license that encourages code with compatible license. BSD code tends to flake off into proprietary branchings. This probably puts a limit on the complexity of the systems that can evolve. OTOH, something like BSD (or LGPL) is needed for things like interfaces. GPL3 is trying to be a "one size fits all", and this is probably a mistake. I suspect that GPL4 will branch into GPL4a and GPL4b (c? d?) with different specialized purposes...but mutually compatible.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    24. Re:I'm confused by kimvette · · Score: 3, Insightful

      The BSD allows mega-corps to borrow code, embrace and extend that standard, and contribute NOTHING back to the community who spent thousands of man-hours developing the product to begin with. Windows' TCP/IP stack, anyone?

      If it were GPL then mega-corps can borrow code, embrace and extend it, and be required contribute the derived work back to the community. Apple's Safari and KHTML, for example (Thanks, Apple!).

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    25. Re:I'm confused by fredrik70 · · Score: 2, Insightful

      >that the GPL isn't free is like saying that because a country doesn't allow you to sell your children into slavery it isn't free.
      This is a bit harsh really. What licence an author decides to use is up to him/her. If he/she is up for other party using the code for their benefit then so be it BSD otherwise GPL, it's about how yuo're happy with how people treat your code. to compare it with slavery etc. is bit over the top imho.

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    26. Re:I'm confused by mooingyak · · Score: 2, Informative

      Therefore, Novell must end the SCO way.

      SCO looks like they may pretty much end when their assets are frozen due to a preliminary injunction filed by... Novell. It's all so confusing.

      --
      William of Ockham had no beard. The most likely explanation is that it was chewed off by squirrels every morning.
  2. How can they do this? by babbling · · Score: 2, Interesting

    If the FSF has the power to do this, I wouldn't necessarily oppose them doing it, but do they have the power to do this with GPLv2? I'm aware that GPLv3 wouldn't allow Novell to enter into a patent swap deal with Microsoft.

    Considering that the software is still all under the GPLv2 and not GPLv3, on what grounds could the FSF revoke Novell's right to distribute copyrighted FSF software?

    1. Re:How can they do this? by morleron · · Score: 5, Interesting

      Bear in mind that IANAL, but I suspect that the FSF could make life very difficult for Novell if they change the license for all of the many utilities and applications that they control from GPLv2 to GPLv3. Novell would have a lot of work to do if they were suddenly put in a position in which they could no longer distribute the gcc package, GIMP, GNOME, etc. with SuSE or any other Novell-branded Linux distro. There are a lot of small pieces of the overall that use FSF-developed code and are essential to running a Linux system. We could find out how much truth there is to RMS' statement that the overall system should be called GNU/Linux if the FSF goes ahead with this move.

      Personally, I would support the FSF if they decide to do this. The Novell/ MS deal is nothing, but a way to provide Novell with a marketing tool, the ability to say "use our Linux distro and be safe from MS patent claims", at the expense of the overall community. Novell is essentially saying that it's OK for MS to sue everyone, except Novell customers, for so-called IP infringements. It is a move by Novell to establish themselves as the Linux monopoly by making their product "safe" from MS lawyers. Novell is hoping that the business community will make wholesale migrations to their products in order to avoid the threat of MS litigation and is a, somewhat silent, partner in MS' efforts to spread FUD about the "use of MS proprietary technology in Linux". Make no mistake about it Novell is evil: to my mind it is more evil than MS in that it portrays itself as a friend of the Linux/FOSS community, while doing whatever it can to undermine the philosphical and legal basis for that community. MS at least makes no claim that Linux is OK - they just flat-out hate us and do everything that they can to prevent the spread of freedom within the community of computer users.

      --
      Impeach Barack Obama for violating the Constitutional requirement to be a "natural born" citizen to hold the office of P
    2. Re:How can they do this? by NotZed · · Score: 2, Interesting

      If you read the article closely, they are talking about GPL3. The article is poorly written.

      i.e. they're saying that they'll change the license of code they own to be GPL3 once it has been finalised, and they may revoke Novell's right to distribute said code, since they will be in breach of this new license. That is why it will only affect 'future versions of linux'. By which the author probably actually meant 'GNU', not the Linux kernel - e.g. gcc for instance.

      Which would force Novell to fork and continue to use old versions if they wanted to stay in the linux business (without altering the ms deal). But they don't have the resources for that, and there's little reason for any other company to join their fork.

      But there's nothing 'underhanded' going on, it is only possibly because of the imminent completion of the GPL3.

      --
      _ // `Thinking is an exercise to which all too few brains
      \\/ are accustomed' - First Lensman
    3. Re:How can they do this? by MooUK · · Score: 4, Interesting

      As said in an earlier post, Novell's continuing distribution of GPLd software may be against the GPLv2. They have patent indemnification licenses with MS. This suggests they believe that without those licenses they would be violating patents. Distributing GPL software that your customers cannot then distribute in turn without violating patents is expressly forbidden by the GPL, and if you violate one section of the GPL you have no right to distribute GPLd software at all. Hence they are violating the GPL and the copyright on the GPLd code.

    4. Re:How can they do this? by KevinColyer · · Score: 2, Insightful

      I think what the FSF can do is to upgrade the licence from GPLv2 to GPLv3 automatically for the products that they distribute, and that includes the term "GPL v2 or greater" in the licence.

      Now the Kernel is GPLv2, Linus seems to want to keep it like that. So Novell will be able to have a kernel. But, as the FSF like to say, Novell distributes a GNU/Linux system. The kernel is Linux but the important system libraries and userland utilities belong to GNU and without which the kernel is a hunk of code. It can`t boot, and the use can`t use a shell, none of the basic disk commands would work for example. Yes, the desktop applications on top are important but it is the base of the stack that would be most vulnerable. Imagine no security fixes or support for new and old devices or bugs for critical system operation!

      It is a software stack and Novell is wobbling on the top of it. FSF has the power to force a licence change over their software. Novell would be stuck at their current level and be unable to use the improved versions of the software without rewriting it all themselves (or borrowing from BSD for example). This may prove tricky for them! I doubt they would get much community help as they have somewhat disenfranchised themselves there.

      This is where the "viral" nature of the GPL comes in to play. Stallman was smart enough to write it this way in order to protect the freedom of the software. I think it shows some of the brilliance of Stallmann and co.

      Now the issue for him and the FSF is whether they will follow this tack. They can, they might not want to. They have a powerful bargaining chip here.

  3. For the best by phat_goat · · Score: 3, Insightful

    I don't think that I ever really trusted this agreement, something about Microsoft wanting to "help" Linux, or free software for that matter, never really digested with me.

    1. Re:For the best by heroofhyr · · Score: 2, Interesting

      To me it always stank of some sort of submarine plan to get rid of Novell using their own greed as a blindfold. Sure, you can compete directly against them, attack them in marketing, etc., but that just raises their street cred in the eyes of others in the Linux community. Flashing millions of dollars in front of the CEOs eyes until they are incapable of making any decisions with foresight is a much easier way. The company loses its respect in the community, become isolated by their cooperation with "the enemy," their source contributions are tainted with patent concerns, etc. Meanwhile they have no expectation of that because they're busy dreaming up what to do with their windfall. I'm not one of those annoying people who calls Microsoft the Hitler of computing, they're just a corporation like any other. But this story does sort of remind me of one of those old stories about Satan making a deal that seemed too good to be true, and indeed it turns out to be and the guy gets fucked over in the end despite his newfound fortune. This only goes to show, if someone offers you a dumptruck full of cash and doesn't seem to want anything of equal value in return -- Run. Run like the wind.

      --
      brandelf: invalid ELF type 'KEEBLER'
  4. Poor Article by kripkenstein · · Score: 4, Informative

    The article is poorly written. For example, the GPL3 is referred to ("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."), but the writer doesn't explain that 'Linux' won't be under this license - only parts of it.

    However, the point is somewhat (perhaps) valid - if most of SUSE goes GPL3, and if the GPL3 is indeed in conflict with the Novell-Microsoft agreement, then there may be an issue (both qualifications seem likely, at present, but time will tell). The issue may be easily solvable, however, depending on the details of the Novell-Microsoft deal - which we do not know (Eben Moglen, however, supposedly does, or so we have been told).

    1. Re:Poor Article by xtracto · · Score: 3, Informative

      , but the writer doesn't explain that 'Linux' won't be under this license - only parts of it.
      Well, from what I know, it would be really difficult to migrate the Linux Kernel from GPL2 to GPL3, even /if/ Linus liked to do so as each contribution is copyright of the contributor.

      But from this:
      The foundation controls intellectual property rights to key parts of the open-source Linux operating system.

      I assume they are talking about the GNU toolchain (remember kids, its GNU/Linux, not just Linux). I guess the FSF *will* use the GPL 3 for the new GNU tools version, if they prevent Novell from *distributing* the GNU tools, then I guess things will get difficult for Novell.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    2. Re:Poor Article by kripkenstein · · Score: 4, Insightful

      Well, from what I know, it would be really difficult to migrate the Linux Kernel from GPL2 to GPL3, even /if/ Linus liked to do so as each contribution is copyright of the contributor.

      Difficult yes, impossible - no. And Linus may get additional motivation soon. If OpenSolaris goes GPL3, then it can use any "GPL2 or above" code from the Linux kernel (which I have heard is the majority). The Linux kernel, on the other hand, won't be able to use anything from OpenSolaris. This 'one-way-street' of code certainly isn't in Linux's interest.

    3. Re:Poor Article by kripkenstein · · Score: 2, Informative

      I may be wrong, but all I have read points in the other direction. Basically, various people contributed to the Linux kernel, and they wrote their own licensing texts. Some said "2 only", some "2", and some "2 or above". See Wikipedia for the following quote:

      "[...]the terms of the GPL state that if no version is specified, then any version may be used, and Alan Cox pointed out that very few other Linux contributors [other than Linus] have specified a particular version of the GPL."

      So OpenSolaris would be able to use most Linux code, it seems.

    4. Re:Poor Article by Tony+Hoyle · · Score: 2, Interesting

      In the absence of any specific statement from those authors they implicitly accepted the license in effect at the time - the one on the whole package which is v2 only. Saying anything different without having a *good* lawyer on retainer is not wise.

      They can't legally change that without contacting every contributing author and getting permission to change to v3... and I can bet that more than a few would refuse (not least Linus). I'm sure my meagre contributions don't exist any more (long time ago) but I personally would refuse if asked.

      Anyway 'bits' or even 'most' of the kernel is still pretty much nonfunctional - you'd have to fork it to rewrite the v2 bits (all the bits that linus wrote, which is a substantial amount of the core..)

    5. Re:Poor Article by Rich0 · · Score: 2, Insightful

      If OpenSolaris goes GPLv3 I think we'll see a huge adoption - as you said much of the FOSS code out there could be ported over, and linux could not pull solaris code back in. I've heard a lot of good things about dtrace/etc, and I'd expect that with the commercial support that solaris would have much more user-friendly administrative features. I'm not sure how ZFS compares to LVM2, but it looks like it delivers all of that and possibly more.

      Competition is good for everyone!

    6. Re:Poor Article by kripkenstein · · Score: 2, Insightful

      Well, I guess the lawyers will need to figure out the licensing issues, I certainly am not one. So I am not claiming to be sure of any of the legal issues; I just know what I read. Time will tell, I guess.

      Changing the entire kernel to GPL3 would be very hard, as you say, while getting various parts of it would be much easier. Now, obviously you are right that 'bits and pieces' of the kernel are not functional by themselves. Yet OpenSolaris would want precisely just 'bits and pieces'; they already have a (apparently quite good) basic kernel. What they need are e.g. device drivers. Now, obviously you can't just paste Linux device driver code into OpenSolaris, but you might be able to (a) alter the Linux version much faster than writing it from scratch, or (b) write a 'compatibility' layer to translate some API calls, to automate or semi-automate the process. In either case, OpenSolaris gets a significant push in the device driver area, I would say. This by itself is a good reason for them to adopt the GPL3.

    7. Re:Poor Article by Deorus · · Score: 2, Informative

      That is not true for a simple reason: a contributor doesn't have to agree with anything besides the compatibility of their code with the GPLv2 in order to submit code. Therefore, without an agreenment, there's no reassignment of rights, and the effective license at the end of the day is the kernel's (since that's the licence with which the mainstream-blessed code is distributed): GPLv2.

      Don't take my word for it, let me dispell your beliefs with this thread on the LKML, or if you're not feeling like reading a flame, a clarification message from Patrick McLean, or if that's not enough, another clarification message from Linus himself.

  5. Stupid move... by EveryNickIsTaken · · Score: 2, Insightful
    "...council for the organization said that 'the community wants to interfere any way it can' with the Novell business arrangement."

    Statements like that make lawyers see dollar signs. Nice move, idiots.

    1. Re:Stupid move... by morleron · · Score: 2, Interesting

      Actually, that's not true. Proprietary software is much more dangerous to businesses for a number of reasons, including tying one's business to the fortunes of another company, not having the ability to use the software as one wants, etc. The move being contemplated is one that would be beneficial to the community as a whole in that it would throw a giant monkey-wrench into Novell's attempt to portray itself as a "safe" (in the sense that MS couldn't sue the end-users) Linux distro. The Novell/MS is evil and needs to be countered by legal moves such as this. Stop spreading FUD about the FOSS community, the real problem here is people who think like you.

      Just my $.02,
      Ron

      --
      Impeach Barack Obama for violating the Constitutional requirement to be a "natural born" citizen to hold the office of P
    2. Re:Stupid move... by EveryNickIsTaken · · Score: 2, Insightful

      I'm amazed that some people still cannot accept the fact that enterprises use and will continue to use MS Windows for office work. Why? Because it's EASY for people who cannot and will not learn other OS's. You can bitch and moan all you want about how awesome Linux is, but the fact remains that its CEOs that have the final say in companies, not CIOs.

    3. Re:Stupid move... by HanzoSpam · · Score: 3, Insightful

      Horseshit. I've been using products from the likes of IBM, HP, Sun, Novell and Microsoft in commercial environments for the last 30 years without having any of those kinds of problems. And as an I/T professional I could give a shit about what the "community" happens to take into it's head about what's good for it, from my perspective avoiding legal problems is a Good Thing. I've never had to contend with the threat of a lawsuit invalidating my license for implementing a solution on Solaris or Windows.

      --

      Progressivism: Parasites helping parasites to help themselves - to other people's stuff.
    4. Re:Stupid move... by morleron · · Score: 2, Interesting

      You seem to have missed my point. I didn't say that no one uses proprietary software, or that it shouldn't exist. I was simply pointing out that problems exist with the use of proprietary software that are at least as bad as anything that attaches to FOSS, with the additional disadvantage of exposing one's business to vendor lock-in which limits one's freedom of action. CEO's who continue to support the use of MS software have either deliberately ignored the threat such software poses to their business or are trapped, via vendor lock-in, into continuing to use it. I find it unfortunate that people continue to use closed-source software, but support their right to do stupid things if they want.

      Just my $.02,
      Ron

      --
      Impeach Barack Obama for violating the Constitutional requirement to be a "natural born" citizen to hold the office of P
  6. This is retarded by dnaumov · · Score: 2, Insightful

    If the FSF can actually do this and if they go through with it, this is going to be very BAD for busines adoption Linux (and therefor, Linux development). And what's worse is not that FSF doesn't know this, they do, it's just that they don't care about anything but their distorted definition of "freedom". As Stallman once said: "We are not here to give users what they want, we are here to spread freedom".

    1. Re:This is retarded by Teun · · Score: 2, Insightful

      Kill SuSE and you've killed the most popular business oriented linux distribution in Europe.

      You think that businesses will go back to Linux after that fiasco? Nope. Hell, I'd think twice myself! I can't afford to fight legal battles.

      But in Europe the mysterious MS software licence claims that Novell wants to protect it's customers from are null and void, Suse like any other distribution is not affected.

      (I'm not talking here about IP claims).
      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  7. Of course this is bad for Linux by haakondahl · · Score: 4, Insightful
    If it were good for Linux, Novell would have paid Microsoft instead of the other way around.

    This will be another example of Microsoft's very successful "take and break" strategy. Once SuSE is up to speed and working well with Windows abominations such as Active Directory, other distributions will be the ones which are somehow not compatible with the "SuSE Linux Standard". Once Microsoft has killed off the other major distributions, they will quietly break compatibility even with SuSE, in a flood of tiny little things that just have to be that way, because of the structure of the WIndows kernel (or some damned thing).

    The only reason we are not all using Java desktops with a common intermediate layer is the Microsoft "take and break" implementation of the JVM.

    --
    Don't trust anyone under thirty.
    1. Re:Of course this is bad for Linux by Andrei+D · · Score: 2, Insightful

      Once Microsoft has killed off the other major distributions,
      they will buy and dismantle Novell. There, fix that for you.

      --
      We often refuse to accept an idea merely because the tone of voice in which it has been expressed is unsympathetic to us
  8. Disproportionate by OpenSourced · · Score: 2, Insightful

    If they haven't banned SCO from selling Linux, I don't know how they can consider banning Novell.

    --
    Rome taught me patience and assiduous application to detail. Virtues which temper the boldness of great, general views.
  9. Um, That's a Good Idea... by ndykman · · Score: 3, Insightful

    If the FSF actually tried to do this, it'd be great for Microsoft. It would basically allow Microsoft to say that Linux can't be taken seriously by any business, because the FSF will basically revoke your "right to use" Linux if they don't like how you do business (do you have software patents? No Linux for you).

    It wouldn't matter if it was technically correct or not, the perception would be enough. And frankly, the fact if the FSF is really even considering this casts a bit of a shadow on Linux and Enterprise Support in general: Is it FSF sanctioned businesses only?

    Besides, why just Novell? IBM has patent agreements with Microsoft. IBM sells Windows Servers. This seems like nothing more that "We don't like the MS/Novell deal, so let's punish them!"

    1. Re:Um, That's a Good Idea... by MooUK · · Score: 2, Interesting

      It was said quite nicely in an earlier post in this thread, but I'll try to summarise here:

      Novell seems to believe that only its patent agreement with MS protects its customers. *If* this is the case, then Novell's customers cannot exercise their rights to redistribute or modify software under the GPL without violating patents. The GPL (yes, even V2) forbids Novell from distributing GPLd software if this is the case.

      The FSF is (probably) working out whether this applies in this case.

    2. Re:Um, That's a Good Idea... by dangitman · · Score: 4, Funny

      Suppose I am and ISV that produces SuperWonderfulMagicPony for Linux.

      OK. So, what do you do about all the 12 year-old girls stalking you?

      --
      ... and then they built the supercollider.
  10. lets hope not by rucs_hack · · Score: 2, Insightful

    A license holder has the right to revoke anothers right to use that license. I don't think it matters if it's GPL2 or 3. They are copyright holders of the technology in question, and can simply refuse to let Novell distribute their stuff any more.

    However, this could kill SUSE, thus hurting a lot of blameless businesses that use it, no doubt pissing them off considerably, and costing a lot of money. Microsoft would love that, they can charge to the rescue amid the confusion, offer cheap license deals with great support packages. Kind of like they did in the 1980s in the Unix wars.

    It's a dumb move, and contrary to the very essense of Open Source. Good stuff survives, bad stuff dies, no direct intervention is required. This is no more than politicking of the very kind that got Stallman excluded from the conference where they decided on the new name Open Source (to differentiate from free software). They run the risk of marginalising themselves if they do this. It's in no-ones interest to intervene and damage *any* linux distro.

    I could go on for hours, but in defference to the fact thast this is /. I'll shut up now...

  11. This article is poo. by bmo · · Score: 3, Insightful

    First off, unless GPL 3 gets off the ground that specifically bans the actions that Novell and Microsoft have done, nobody can "ban" Novell from distributing Linux, as they have not violated the GPL as it stands (I think, see below).

    Secondly, John Dragoon doesn't get it. He honestly thought that this was a Good Idea and we parted ways agreeing to disagree. He's a PHB sales-type. He's not "one of us."

    I have ranted here and vehemently castigated Novell (see sig) for the stupid move, but I'm not sure that they should be "kicked out of linux" yet. They should be given the chance to redeem themselves or at least clear the air on what they really signed. But I have yet to hear anyone from Novell explain exactly what was in that contract. I've waited and waited for a clear explanation, and it has not been forthcoming from what I can see. So all I've had to base my opinion on is a smattering of articles and analysis on Groklaw of generalities taken from press releases. For all I can tell, it's a lot of hot air.

    I am more of the opinion that we don't need a "Novell Clause." Instead I think that Linux market forces will relegate Novell's brands of Linux to the dustbin if they don't get their act together and get right with the community.

    --
    BMO

    "I have never come upon a post which makes its point so excellently, and also contains so many F-words." - Bruce Perens

  12. Re:Dumb Move by Tony+Hoyle · · Score: 2, Insightful

    Novell will just stop using GPL products and do something else. Closely followed by just about every other business, under fear of litigation from the FSF.

    It could well be the turning point where linux itself gets killed. Which is what MS wanted all along, really. Way to play into their hands, stallman.

  13. Article is FUD. by Aim+Here · · Score: 4, Informative

    An eweek article clarifies the situation. Eben Moglen was quoted out of context; he was talking about writing GPLv3

    "According to a recent Reuters report, the FSF's (Free Software Foundation) board was going to be looking into Novell Inc.'s rights to continue selling its version of the Linux operating system. That's not actually what's will be happening.

    Eben Moglen, the Software Freedom Law Center executive director and FSF board member, explained: "This is a story being hyped by the Reuters guy who wrote it."

    The Reuters quote was: "The community of people wants to do anything they can to interfere with this deal and all deals like it. They have every reason to be deeply concerned that this is the beginning of a significant patent aggression by Microsoft."

    "What he actually asked me," said Moglen in an e-mail interview, "was 'Is it true that some members of the community want GPLv3 to keep Novell from distributing future versions of GPL'd software?' I said, 'Yes, the Free Software Foundation is opposed to the deal, and is thinking about what to do; there will be a new draft soon [of the GPLv3 (Gnu General Public License Version 3).]"

    See Special Report: Novell's Linux Facelift

    Therefore, "The actual quote he prints is entirely accurate, but his lede destroys the context and is making unnecessary waves."

    The FSF, which governs the GPL (GNU General Public License), has long been concerned about Novell recent patent deal with Microsoft Corp. The Samba Group has stated that it wants Novell to abandon the deal. Open-source figure Bruce Perens started a petition that accused Novell of betraying the free software community. And, one group of free software supporters launched a Web site with a self-explanatory name, Boycott Novell. "

  14. Handing MS a huge victory on a platter by QuickFox · · Score: 3, Interesting

    The FSF is shooting itself in the foot big time. They're handing Microsoft a huge victory on a platter.

    Consider how this ban will affect those customers of Novell who use Linux. And consider the kind of reputation that this will give the open-source community.

    One reason companies pay for expensive proprietary software is that the companies that write proprietary software are considered reliable. They won't suddenly throw a tantrum and refuse to deliver.

    If the open-source community is seen as throwing a tantrum and refusing to deliver, then good-bye credibility. Companies just won't dare use open-source software.

    --
    Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    1. Re:Handing MS a huge victory on a platter by muellerr1 · · Score: 2, Interesting

      One reason companies pay for expensive proprietary software is that the companies that write proprietary software are considered reliable. They won't suddenly throw a tantrum and refuse to deliver.

      Just because a company charges for their software doesn't prevent them from adding terms to their EULA that allow them to do just this. I recently had a large well-respected graphics software company (I won't name names, but it starts with 'a' and ends with 'dobe') functionally revoke my licenses because I had bought an individual upgrade for one application in a bundle that I had previously purchased (starts with 'C' and ends with 'S'). They told me that it was 'not a suitable upgrade path' and that I had to upgrade the entire bundle instead. The only place this was detailed was in the EULA of the original bundle, of which I had upgraded the other programs individually already (despite what they said, two of the three applications upgraded individually just fine). I could return the upgrade I had just bought, but if I wanted to upgrade that application I had to either purchase a new license for that application, or upgrade the entire bundle. They had, in effect, thrown a tantrum and refused to deliver.

      I cannot do my job without their proprietary software (and don't tell me to use Gimp, Inkscape and Scribus instead--I've tried, and they are not viable alternatives for professional graphic design). I'm not necessarily disagreeing with the rest of your post, but being expensive and proprietary does not mean that they won't find ways to screw you over anyway.

  15. WRONG! by JPriest · · Score: 2, Informative
    "Therefor, Novell can now (continue to?) develop software that violates Microsoft's "Intellectual Property".


    You mean, therefor Novell CUSTOMERS can now develop software that violates Microsoft's "Intellectual Property.
    Quite Honestly it makes little difference what these customers develop in the first place because their are not redistributing this software.
    Now when a customer using Windows and Linux needs to copy a feature used by MS to get proprietary application X to run on Linux they have an agreement that MS will not sue them for it.
    All code being distributed by Novell was and still is bound by the terms of the GPL.

    --
    Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
    1. Re:WRONG! by mysticgoat · · Score: 2, Interesting

      Quite Honestly it makes little difference what these customers [of Novell] develop in the first place because their are not redistributing this software.

      You are making a major assumption that no customer of Novell's would ever develop and distribute a derivative of Suse-- and that is absurd.

      One of our projects in early incubation is developing a distro on a flash drive or low cost portable computer that would provide adult students in back-to-work programs with an affordable interactive curriculum. If we can get this funded and developed, we will want to distribute it under GLOSS [see below] licensing both directly to students and to similar back-to-work programs nationwide. This is not a liberal-based feel-good thing; it is a serious effort to take as many people off of public assistance as possible by turning them into taxpayers with living wage jobs as health care technicians, administrative assistants, and so on.

      Novell's actions have poisoned Suse for this work. Any modified distro of Suse we come up with would be at greater risk of patent attack from Microsoft than would be the case for RedHat, Debian, Ubuntu, or any other distro. This would be true even if the modifications were simply stripping out device drivers and functionalities that our students would not need, because there would be no way for us to determine whether Novell had introduced any patent-tainted code into some component that we were retaining.

      Novell has poisoned Suse for this kind of specialized distro development work. Who would willingly step into the FUD and confusion they have swirled around themselves when there are numerous alternatives to Suse that are not so encumbered? For that matter, who would willingly pay support fees to a company that has so publicly hoisted themselves with their own petard? Novell is just too damn clever for its own good.

      Note: GLOSS— Gratis/Libre OSS

    2. Re:WRONG! by JPriest · · Score: 2, Insightful
      You are making a major assumption that no customer of Novell's would ever develop and distribute a derivative of Suse-- and that is absurd.


      No I am not. Any software you plan to distribute will be handled the same as it always has. You can rebrand and distribute Suse if you see fit. If you contributed code you are welcome to release it under GPL as well so long as it does not infringe on someone elses legal rights. The only thing that changes is that you CAN develop and use portions of MS code in house. If you have access to Windows source code, this may permit you to "steal" portions of that code to make you applications work on Linux.

      You can not expect to release _that_ code under the GPL, but that is a change from what exactly?

      Because there would be no way for us to determine whether Novell had introduced any patent-tainted code into some component that we were retaining.

      And you are throwing around the word FUD? Please go and actually read section 7. I stated earlier this agreement was not about what Novell was releasing but what the customers were contributing. If Novell DID release something "patent-tainted" under the GPL then guess what? They are allowing any recipient, and recipients recipient full use of any patent pertaining to that code AS PER THE GPL (sections 7). Java for instance has several patents, but when Sun GPL'd it, they in effect were releasing any GPL users from any litigations as a result of using or distributing this software as GPL.

      If you do not understand the GPL, then maybe you should refrain from burning Novell at the stake in the name of violating it.

      --
      Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
  16. Re:Most likely an overraction ... by ardor · · Score: 3, Interesting

    What we see is a problem I noticed a while ago. There are TWO main groups in the Linux community: the pragmatists and the idealists.

    The pragmatists want a Windows alternative. They want Linux to be this alternative. License issues are secondary. This group well accepts closed-source software and -drivers. Their primary goal is to push Desktop Linux so that MS is no longer the hyperpowerful monopoly.

    The idealists want everything to be free. They couldn't care less about Linux being popular, they want a 100% free system, even if it means that only 5 people in the world use it.

    The FSF belongs to the latter group. However, one argument the pragmatists definitely have is by not pushing Linux the idealists ultimately give MS carte blanche to redesign the IT sector to their liking. This can't happen if there is a real competitor. In the end, Linux may not run at all on *any* PC because of this.

    This is why I wonder why BSD wasn't pushed. It does not have any license worries, and could work just as well on a desktop.

    --
    This sig does not contain any SCO code.
  17. Spreading FUD by lRem · · Score: 5, Informative

    Ahhh, another AC spreading FUD...
    The whole Reuters article is FUD. Novell has not crossed any license, nor anybody at FSF thinks they can ban Novell from anything. What they are thinking about, is including something in GPLv3 to forbid wording that may suggest OSS breaking patents in those public deals. They even already posted a clarification!

    --
    Always put off dealing with time-wasting morons. If you would like to know how... I'll get back to you
    1. Re:Spreading FUD by Anonymous Coward · · Score: 3, Interesting

      Wow, it's a very dangerous FUD article... Reuters is trying to make the FSF looks worse than it is (I am one of the people thinking the GPL-2 is far enough, and the license should stay as simple as possible, and I think the GPL-3 is really bad, and will hinder -and certainly, has already- the adoption of Linux, by new companies), and make other companies think their Linux business could be destroyed, if they did anything to "anger the Linux people"...

      There is a very clear manipulation of what has been really said, and this is very bad indeed...

      This is not just "hype" or "unnecessary waves"... the FSF should react far more strongly. Do you have a right to force Reuters to publish a reply by the FSF, in the US? An article on linux-watch.com surely won't be read by the same people reading Reuters, and the FSF must make things clear to the people who don't read linux-watch.com, because making ennemies of these people won't lead to any benefit for Linux, and, more importantly, will hinder Linux adoption by new companies, including companies involved in hardware, and drivers for hardware...

    2. Re:Spreading FUD by KDR_11k · · Score: 2, Informative

      If you have granted a license you cannot arbitrarily revoke it since the license is a binding contract between you and the licensee. If you don't want the licensee to have those rights, well, shouldn't have granted them a license in first place. Once they have a license you can only take it away under the conditions outlined in the license.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    3. Re:Spreading FUD by rtb61 · · Score: 3, Insightful
      Now that is just plain wrong. The end user should never be deprived of quality software. So there should never be a reason for anybody to stop anybody from distributing Linux. The real operative word here is 'Free'.

      There is absolutely no point in stopping anybody from distributing quality open source software, however should companies infringe upon whatever version of GPL the code developers decided to use to protect their work, then those infringers should be made to pay and pay through the nose.

      I could envisage a suitable charity fund that gives away the bulk of it's money every year (not just a miserly 5%) funded by those ass hats who would steal work that is meant to be shared by all and be for the common good.

      --
      Chaos - everything, everywhere, everywhen
    4. Re:Spreading FUD by Jason+Earl · · Score: 2, Informative

      Novell's problem is that the FSF controls the development of large pieces of software that are critical to the SuSE Linux distribution. Sure, The FSF can't retroactively change the license of existing versions of these software packages, but Novell is going to find itself in serious trouble if it is unable to distribute future versions of this software which will be release under the redesigned GPLv3. Even worse, there are plenty of people outside of the FSF in organizations like the Samba developers that have equally strong feelings about the Novell/Microsoft deal. Like it or not, new versions of a significant portion of the SuSE distribution are going to be released under the GPLv3. If Novell has to take on the added expense of maintaining its own GPLv2 forks of all of this software then it may as well go back to hawking Netware because its aspirations of becoming a powerhouse in the Free Software world will be finished. Novell is having a hard enough time simply competing with Red Hat. There is no way that it can compete with Red Hat and the entire Free Software community while trying to maintain SuSE, all of the software that switched to the GPLv3, and Netware to boot.

      Unfortunately for Novell it also needs the money that Microsoft provided as part of the deal.

      So Novell is going to pretend that everything is hunky dory and hope that somehow the FSF is bluffing about the GPLv3. Of course, RMS is the kind of guy that decided to write his own operating system rather than live in a proprietary software world. I think that the chances of him being persuaded by Novell is essentially nil.

  18. So much for "open" by argStyopa · · Score: 2, Interesting

    So if I understand, the "open" part of open source means "free to anyone...except you. Because, well, we don't like that jerk you hang around with."

    (?)

    --
    -Styopa
  19. You are confused by mi · · Score: 2, Informative

    Again I agree Microsoft might not be the best company on the block but I think we need to move beyond "Microsoft is evil" emotion.

    Yes, yes, indeed!

    If people push Novell too hard I predict Novell will move to FreeBSD and that would be a shame...

    No, that would, actually, be a great thing — they should've started with a better OS to begin with (ha-ha). But it would not help the problem, which is largely with applications — Evolution, Samba, et al. are licensed the same way, independently of the underlying OS' license.

    --
    In Soviet Washington the swamp drains you.
  20. And You Wonder Why People Avoid Open Source? by reallocate · · Score: 2, Interesting

    Credible or not, stories like this represent one big reason why many organizations don't want to invest in Linux or a lot of other open source products. Who wants to risk going with a vendor who's at risk of being tied up by a bunch of lawyers they've never heard of?

    Nor does the fact that when open source hits the non-techie media, the story is usually about geeks and lawyers fighting about byzantine licensing issues that only they care about. If open source delivers better technology, why isn't open source making sure people read about it? (To that, I'm sure, some will blame the Great Evil Mainstream Media Conspiracy. Nonsense, Play the media game as others play it, and the coverage wil be there. If you think that means abandoning your principles, sorry. Convincing all the other players to change the rules is the wrong way to win the game.)

    --
    -- Slashdot: When Public Access TV Says "No"
  21. It's not about the money by Anders+Andersson · · Score: 4, Insightful

    Selling GPL software is quite clearly within the bounds of the license.

    You are misreading the parent. It's not selling the GPL software that is prohibited; it's selling (or giving away) the GPL software in violation of the license agreement that is prohibited. Nobody is concerned about Novell making money; people are instead concerned about Novell sort of acknowledging that Microsoft may have patent claims as to what they are selling (which is software not produced by Microsoft, but produced by programmers who dislike being branded as plagiarists).

    1. Re:It's not about the money by anagama · · Score: 2, Insightful

      Wouldn't a copyright violation be plagarism? A patent violation could technically be 100% your own work, its just that the patent holder got a patent and others did not.

      --
      What changed under Obama? Nothing Good
    2. Re:It's not about the money by LocalH · · Score: 2, Informative

      The chance of the kernel going GPLv3 is still 0% - it never included the "newer version" provision that some use with the GPLv2. It can't go GPLv3 unless you contact each and every single contributor with code that is currently in the kernel.

      --
      FC Closer
  22. GPL restricts freedom by rick_campbell · · Score: 2, Interesting

    An Anonymous Coward wrote: ``All we ask is that you share with others as well.''

    This is patently false.

    The GPL is about restricting what you can do with software.

    Public Domain is about not restricting what you can do with software.

    A more accurate version of the Anonymous Coward's suggestion would be "All we ask is that you drink the Kool-Aid." :-) GPL says: We like Freedom, and we wish we could force you to like exactly our brand of freedom. Sounds a bit like US foreign policy :-)

    Public Domain is not the only way, but perhaps the oldest way among those typically discussed, to truly encourage Free (liberty) Software. BSD licenses and the LGPL are other ways that encourage freedom. GPL encourages restriction, but they are restrictions that lots of people (not me) happen to like. These people are not altruistically giving away the fruits of their labors to benefit humanity. Instead they want to give away the fruits of their labors to people who think like they do while making sure that no part of humanity benefits in a way that they don't approve of, like making money. Of course, this is totally fine for them, up to the point where they try to pretend with absurd statements like ``All we ask is that you share with others as well.''

    At it's most basic, the GPL is about restricting what you are allowed to do with the software. GPL is why I can't use GDBM at work. LGPL would allow it, but GPL restricts my freedom beyond the point where I can use it without having to give away my company's software as well. This is where ``GPL is a virus'' comes from.

    If you care about freedom, you should fight the GPL. Place your Free (liberty) Software in the Public Domain.

    If you want something to be free, then don't add restrictions. Period.

  23. Your Confused by budgenator · · Score: 2, Interesting

    Woah, slow that thing down, here's the problem, If Novel can't sell Linux, it's because patent impairments exist, not because they ADMIT the impairment exist. So if Novel can't distribute, then NOBODY can distribute. Brighter minds than mine would have to figure out all the implications of distribution in countries that don't observe software patent vs. those that do.

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
    1. Re:Your Confused by juergen · · Score: 3, Interesting

      But other companies don't come with DIRTY HANDS to the table. They never acknowledged Microsoft's claims. Novell on the other hand, at least implicitly, does. That's what their deal with MS is all about. Novell can't have it both ways.

      Apart from legal nitpickings, imagine a reversed situation. We find a way to distribute Vista for free by a loophole in their EULA. Now do you really expect MS to not try to remedy this?

      Therefore, the OSS community has every right to protect the spirit of the GPL vigiously. If that means to retaliate with FUD and legal means, that's just the weapons first chosen by the other side, and Novell is their pawn caught in the middle. Chances are they will go the way of all former MS partners (replaced next OS iteration), but they made their own bed in this. Bye Novell, you have provided some good products in the past.

    2. Re:Your Confused by Sleuth · · Score: 2, Interesting

      Agreed. And all this commentary about 'Novell's implicit acknowledgement' of some rights of Microsoft sounds like FUD to me. The contract doesn't have any implicit acknowledgements except to those who choose to see them. It's possible that Novell just thought 'Hmm, we can reduce our chance of being sued by MS by making an agreement.' Such an agtreement doesn't give MS any rights other than those specified in the contract. All these implicit conjectures are rather entertaining.

      Someday we'll see the contract. That'll be an interesting day.

  24. FUD, Really? F at best ;) by Famatra · · Score: 3, Interesting

    "Ahhh, another AC spreading FUD..."

    I don't see any FUD anywhere, at least not the D[oubt]. The FSF foundation is: "reviewing Novell Inc.'s right to sell new versions of Linux operating system software".

    The FSF is doing a review of the matter to see if they can stop Novell (stop why? read below). Perhaps they can find a legal reason to stop Novell and perhaps they won't, but that the review is taking place isn't in [FU]Doubt.

    What also isn't in doubt is that people (esp. the FSF, enough to do a review) are not impressed with Novell making back room deals with Microsoft in an apparent effort to circumvent the GNU GPL in playing patent agreement games.

    The uncertainty is not really an issue, the FSF is making it clear that the will either restrict Novell now in using the FSF's software (if the review is successful), or they will be restricted (from using the latest FSF versions) later when the GNU GPLv3 comes out and the FSF moves all of its software over th the license which will prevent patent games.

    As for Fear, I'd be afraid too if I was Novell going down the path it's on. They can remove any fear if they choose to back out of their Microsoft deal - the choice is theirs. What isn't their choice is to make use others' works without, at the very least, deference to the license it's under.

  25. Section 7 and explicit claims by Anders+Andersson · · Score: 2, Interesting

    It's bad because the GPL says (section 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.

    Since the patent license mentioned above is only given as an example of a GPL violation, I wonder why GPLv2 isn't considered sufficient to block the Novell-Microsoft deal, while GPLv3 will be. The essence of section 7 should be inferred from its first sentence: Can Novell distribute so as to satisfy simultaneously their obligations under the GPL and the deal with Microsoft? As I understand the GPL without having the actual text in front of me, Novell must not only give their own customers the freedom to copy, but they must extend this freedom also to their customers' customers, and in fact to anyone who happens to directly or indirectly obtain copies or modified versions of the software in question. This is implemented in the GPL as a requirement to redistribute under the GPL only, with no restrictions added or removed.

    The deal with Microsoft removes a supposed restriction that is not part of the GPL, and there are doubts whether this restriction is even legally valid (i.e. whether there are any patents being violated). However, if this restriction is legally valid, then it has in fact first been added by someone, and the deal doesn't completely remove the restriction since the removal only applies to Novell's customers, but not to other recipients of the same code, nor even to Novell itself (if I have understood it correctly). Adding a restriction and then not removing it completely is the same as adding a restriction, and that is a GPL violation, regardless of when it was added or by whom. So, either Novell has added a restriction (by acknowledging the potential validity of Microsoft's patent claims), or Novell has received software which wasn't distributed in accordance with the GPL in the first place, even if the distributor said it was.

    ... and that allthough Novell hasn't itself (officially) payed any patent license to Microsoft, they have implicitly acknowledged that the users of the software they sell need a promise from Microsoft not to sue.

    Novell has "paid" for the patent license offered by Microsoft (to Novell's customers) already by entering the deal, regardless of the direction in which money has flowed. It doesn't matter that Microsoft ended up paying millions to Novell; Microsoft received something in return from Novell for their money and their covenant-not-to-sue, and that something was (in part) another covenant-not-to-sue. Maybe Novell's supposed patents were supposedly worth that much more than Microsoft's supposed patents? It's not very implicit really; the deal explicitely involves unspecified legal claims by Microsoft to rights in software sold by Novell, even as Microsoft has had no part in the creation of said software.

    If Novell had merely issued a press release saying "yea, Microsoft may have rights to that software we sell, but we don't dispute that, as we don't care", things wouldn't have been half as bad. But Novell actually made a financial deal with Microsoft involving the transfer of money for effectively making that statement. How much more explicit can you get?

    I hereby grant you an exclusive, non-transferrable right to free speech, in return for you granting me the same. Here, have some pocket money as well. Now, let's conquer the world together and sell free speech to anyone who can pay for it! $-)

  26. Most of the kernel isn't of interest by Anonymous Coward · · Score: 2, Informative

    Have you guys even looked at Solaris? I have (having worked at Sun), and most of the Linux kernel wouldn't be of interest. The main thing would be in the device driver area. Solaris x86 sucks badly in terms of supported hardware. It truly blows.

    But it's not a simple issue of taking Linux drivers and dropping them in. Solaris has a specific well documented and adhered-to API for drivers - the DDI and DKI. So, all drivers of interest would have to be ported over to support this. It's straightforward, but non-trivial.

    Anyway, the point here is that if work is going to be needed on the drivers, if the author withholds the relicensing it's not that big of a deal. Sure, it will save you some time. But it's not a show-stopper by any means. It's just a slight inconvenience. BFD.

    In terms of the rest of the kernel, Sun has (for the most part) been ahead of Linux. It's only been recently that Linux has started getting closer, but the Linux kernel is still at least a few years behind Sun in the majority of things.

    So, yes, Sun will have an advantage of a one-way street. They also have a lot of other advantages. Once they get the device driver support in, they will become a very serious contender for wide-spread O.S. adoption.

  27. This would be atni-free-software, wouldn't it? by pyite69 · · Score: 2, Interesting

    I am as anti-Microsoft as anyone, but this seems like a ridiculous concept.

    The whole point of Free Software is freedom - enforced by the GPL. Why would Novell not be able to distribute Linux software? Perhaps there may be trademark issues, but restricting someone from doing what they want with GPL software would make Stallman quite the hypocrite.

  28. A Post in a novell blog about this by noddyxoi · · Score: 2, Interesting

    http://www.novell.com/company/blogs/cmo/ You don't have to be a carpenter to know that it's a lot harder to fix a mistake once the cut has been made. Hence true craftsman know all to well that proper due dilgence up front can save a lot of heartache down the road. And so it is with reacting - or over reacting - to every story, rumor, or misrepresentation about the direction of GPL3 - the work in process update to the GNU General Public License version 2 that governs the use and distribution of some open source software. As GPLv3 is a work in process, we don't speculate on its outcome. Others do, however, including a Reuters report yesterday that intimated dire consequences for Novell - citing Eben Moglen, the Free Softwware Foundation's general counsel as the source of this conclusion. Within hours, Mr. Moglen himself, in an email interview with Steven J. Vaughan-Nichols of Linux-Watch, clarified his position and the Reuter's story stating, "The actual quote he prints is entirely accurate, but his lede destroys the context and is making unnecessary waves." In fact Mr. Vaughan-Nichols has a number of balanced views and articles on this topic that provide a fuller context for many of us to "measure twice and cut once" on this issue. On his site you'll also find an interesting guest post by Bill Weinberg, a long time evangalist on open source licensing to business users, that's worth a read. On this issue as with so many others, it's a good idea to take out your tape measure and use a pencil. John Posted in Uncategorized | No Comments

  29. FUD, indeed. by DrYak · · Score: 2, Informative

    The FSF foundation is: "reviewing Novell Inc.'s right to sell new versions of Linux operating system software".
    The foundation is not.

    Go to http://fsf.org/, read the current event / news / etc... The words "Novel" "Stop" and "SuSE Linux" never occur in the same sentence. There are the BadVista campaign, events around the GPLv3, rants about iPhone, TiVo and other non-open platforms, news about openness in EU. Nothing about SuSE or Novell.

    Jump to http://www.opensuse.org/. There are news about SuSE Linux 10.2, development of version future 10.3, announcements about FOSDEM. No "FSF is illegitimately calling us 'GPL traitors' without knowing the whole story".

    You can even look on various websites which are usually well informed about background stories in the open-source world, like LinuxJournal, LinuxWorld, etc...

    In short : the Reuters news isn't mentioned by any primary source. It's probably the wild guess and approximative interpretation of someone who isn't very well informed about the whole deal, who tries to make crazy guess about the new section of version 3 of GPL, and pull out of his ass some interpretation about the implication on the Microsoft-Novell deal.
    In fact, the second half of the article is about various movement of Novell's shares, the amount of money in the deal and other similar information. Could almost be considered as stock dumping spam.

    Conclusion : it's just some trader who pulls interpretations about GPLv3 and Novell out of his ass.

    Don't trust me ?
    You can just fucking google the quote.
    You'll mostly find aggregators that just repeat Reuter's article.

    Still not sure ?
    Read the explanation from the one who said it himself : he was saying that the project is to make a GPLv3 that avoids patent trolls and patent deals similar to the Novell one. He was never talking about stoping Novell from selling SuSE right now. His words were put out of context to make the news sound more terrifying.

    In the future, Novell could either sell it under GPLv2 (probably until 10.4 - until GPLv3 code appears in non-alpha code that is used in actual distribution), or renegotiate the deal with Microsoft (and loose all the money that MS has given in exchange) or prove that Novell doesn't violate GPLv3.

    AND ABOVE ALL, it's not in FSF's and the open source world's interest to shut novell out from linux : Suse and Novell have been active in the development of a lot of different projects (I could cite ReiserFS and KDE for Suse and Evolution and Mono for Ximian branches of Novell). They should mostly try to be certain that open source code stay free for everyone to use and modify regardless of patents. The current fear is, although the code it-self is free, it couldn't be freely used by someone who hasn't signed a patent deal with MS like Novell did. That's something that GPLv3 wants to tackle. (And that's something that still has to be proven by MS - i'm still thinking that their whole point wasn't to sue everybody else apart Novell for patent infringement - which won't be efficient because their patents could be rejected because prior art, obvious, or clean-room RE, and because open-source community has proven to be incredibly fast at replacing patent-mined code -, but to create chaos in the open-source community between Novell and others - As Julius Caius Caesar put it : divide and conquer).

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]