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?

553 comments

  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 gronofer · · Score: 1

      It's OK up to "easier for businesses to use Linux", but goes bad after that.

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

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

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

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

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

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

    10. Re:I'm confused by Anonymous Coward · · Score: 0

      I'm a moron because I hold my own opinion?

      Anyhow, it sure is nice to know that you "get it", even if you are socially incapable of expressing what exactly it is that you "get".

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

    13. Re:I'm confused by cpthowdy · · Score: 1

      Friggin trolls... Hula didn't compete Outlook... that's a client app. (If you want to get technical, Evolution competes with Outlook; doesn't look like they are killing that off.) And if you think Hula competed with Exchange, you're wrong there too. GROUPWISE competes with Exchange, and is alive and well.

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

    16. 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)
    17. Re:I'm confused by Anonymous Coward · · Score: 0

      In that case we should also boycott VLC because to play DVD's you must use patented software (same applies to any MP3 encoder, eg LAME violates this part of the GPL

    18. 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!
    19. 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.
    20. Re:I'm confused by moranar · · Score: 1

      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.

      Not necessarily: they could develop their own programs -or plugins, if the license requirements allow them- under different licenses to the GPL, and add value to their distribution.

      --
      "I think it would be a good idea!"
      Gandhi, about Internet Security
    21. Re:I'm confused by Anonymous Coward · · Score: 0

      Yes, Outlook and Evolution are client apps. No, Novell as part of its Microsoft deal has stopped funding the development of Evolution. Any other questions?

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

    24. Re:I'm confused by Teun · · Score: 1

      The man(?) is ridiculing the GPL and the people that elect to use it.

      I'm not calling him a moron (his choice of words!) for preferring BSD licensing but for disrespecting the choice of others for the GPL.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    25. Re:I'm confused by Anonymous Coward · · Score: 0

      Go Novell! F the retards :)

    26. Re:I'm confused by jbengt · · Score: 1

      "Microsoft and Novell have agreed not to sue each other over patent violations."
      This is incorrect. Microsoft has agreed to not sue Novell's customers, not Novell itself. It was written this way explicitly to try to get around the GPLv2 patent clauses.
      Also, Novell has not admitted that any of its' products violate MS products, and MS refuses to divulge any potential patent violations, in spite of the fact the code is open and easy to vet, since FUD is better for MS than litigating the truth.

    27. Re:I'm confused by Anonymous Coward · · Score: 0

      *** 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? ***

      Dumbass - think about this for a minute. Think about guys like Eolas who sued MS. Do you see them suing any OSS vendors who ALSO are going against their alleged "copyrights"?

      Personally, I wish that copyright enforcement were like trademark enforcement - you must vigorously defend against all comers, or lose the rights. Then people flaunting their copyrights against the big boys (apple, MS, Cisco, etc, etc) would have to sue the free software writers too or risk losing their rights to the IP.

      The world would be a better place then.

    28. Re:I'm confused by IamTheRealMike · · Score: 1

      implies that Linux is non-free. And that's not acceptable to the community.

      What if Novell are right, and Linux is indeed non-free? I rate the chances of Linux not infringing on at least one Microsoft patent as zero. The GPL is not compatible with reality anymore unfortunately - it has this starry eyed notion of freedom that no longer exists in the software world. Trying to enforce those patent clauses is ridiculous, it would make virtually every piece of GPLd software out there non-free. For them to add wording to the GPLv3 banning the implication that GPLd software may be patent infringing is yet another reason to avoid the new license.

      I think it is purely common sense for the community to reject patches supplied by Novell.

      Seems to me that it's purely common sense that Linux is already "tainted" by the IP of a gazillion different companies.

    29. 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
    30. Re:I'm confused by frdmfghtr · · Score: 1

      The man(?) is ridiculing the GPL and the people that elect to use it.

      I'm not calling him a moron (his choice of words!) for preferring BSD licensing but for disrespecting the choice of others for the GPL.
      (1) How is the poster ridiculing the GPL and those who use it? Clarification please.

      (2) What drives you to say that "moron" was the poster's choice of words? I read the post several times and not once did I see the poster refer to anybody as a "moron."

      --
      Government's idea of a balanced budget: take money from the right pocket to balance...oh who am I kidding?
    31. Re:I'm confused by trifish · · Score: 0, Flamebait

      The GPL can't diminish rights held by the owner of the copyright.

      It not only can, it does.

    32. Re:I'm confused by UncleTogie · · Score: 1

      Personally, I wish that copyright enforcement were like trademark enforcement - you must vigorously defend against all comers, or lose the rights. Then people flaunting their copyrights against the big boys (apple, MS, Cisco, etc, etc) would have to sue the free software writers too or risk losing their rights to the IP.

      I see the potential for a very different scenario. I'd bet that corporate teams of lawyers would steamroll any small-business/individual's efforts. Lawyers are generally too expensive for most people to engage in a 10-year court battle.
      --
      Don't tell me to get a life. I'm a gamer; I have LOTS of lives!
    33. Re:I'm confused by TheLinuxSRC · · Score: 1

      It not only can, it does.

      How do you figure that? Are you aware of such companies as Trolltech (who owns the copyright to the QT libraries and licenses these copyrights differently according to the situation) or MySQL AB who does the same with many (most/all?) of their products? There are no restrictions placed by the GPL on these companies and how they see fit to distribute their software. The GPL does, however, place restrictions on whoever decides to redistribute this software under the terms of the GPL

    34. Re:I'm confused by cpthowdy · · Score: 1

      Bullshit. Evolution is a key component of Novell's SUSE Linux Enterprise Desktop offering; they aren't going to kill that in favor of simply NOT offering a full-featured mail client... and don't say Thunderbird, either. It doesn't have the Exchange connector that Evolution does.

    35. Re:I'm confused by Clueless+Nick · · Score: 1

      VLC does not carry anybody's patent license. At least to the extent that any are being infringed in your country. Plus, it has been written largely in France, not the US.

      --
      Chat with other atheists http://secularchat.org
    36. Re:I'm confused by plazman30 · · Score: 1

      You forget something very important here. Novell/SuSE can happily continue to develop all the software it wants that infringes on Microsoft IP, and then SuSE can happily release the software in Europe, where there are NO software patent laws. Then, a US Company that wants to use the software in the US, could simple buy a license from Novell for the code.

      This is the case with a lot of other software out there now. FreeType's Bytecode interpreter infringes on Apple IP, yet the code is still in there, for you to turn on. I am sure if Microsoft really sat down and looked at Samba, they could probably find some patent violations also. The code could easily be distributed and commented out, to be turned on by a compile time switch.

    37. 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
    38. 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
    39. Re:I'm confused by Salsaman · · Score: 1
      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.


      Sure they can, but imagine the disruption that would cause. Having to post an update that provides less features is not good publicity for Free Software.


      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.

      You are correct, but most developers would try to avoid patented code. Whereas Novell have an incentive to actually include patented code in GPL projects.


      3. Code still has to be accepted into a project. Why not let the individual project leaders decide if they trust Novell or not?

      So what are you saying ? *All* patches from Novell employees should be rejected ?

    40. Re:I'm confused by Anonymous Coward · · Score: 0

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

      As far as I understood, this is simply not true. Microsoft and Novell have agreed not to sue each others customer over patent violations. They still may sue each other over these.

      Novell has no possibility to violate Microsoft patents without Microsoft having the possibility to sue them. The same holds true the other way round.

    41. Re:I'm confused by certain+death · · Score: 0

      You are wrong. Microsoft and Novell agreed to not sue CUSTOMERS over such violations, not each other.

      --
      "My immediate reaction is "WTF? What kind of moron doesn't make things 64-bit safe to begin with?" Linus
    42. 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.

    43. Re:I'm confused by juergen · · Score: 1

      Once you have distributed under GPL, you cannot take it back. The GPL provides an eternal license, provided the licensee complies. That may be viewed as an obligation on the copyright holder. The obligation to not reclaim exclusive rights.

    44. 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
    45. Re:I'm confused by glsunder · · Score: 1

      So the alternative for most companies that actually use or would Novell software is to simply use Microsoft.

    46. Re:I'm confused by jbolden · · Score: 1

      Right this isn't just selective enforcement. Its selective enforcement for the purpose of allowing the code to be distributed via. the GPL. The courts can look at the reason for the selective enforcement. I think you can establish intent here on Microsoft's part: they intended to allow their code to be distributed via. the GPL. I think you can establish intent: Novell had rights (a non sue agreement) which were attached to the code and were not re-distributable while claiming they were redistributing all rights.

      I'm not arguing the case is clear, just that it isn't so clear cut the other way.

    47. Re:I'm confused by sumdumass · · Score: 1

      Contributors are free to chose the licence that fits best with their views and desires.
      Not if it is a GPL3 license. GPL2 or even 1 is incompatible with a GPL3 licensed product. BSD doesn't have as much problems being inserted. As for how I see it, the GPL3 is just wrong on many levels. It pretend to be free but it is really "free if you do as I say in all aspects of your company". It covers things a software license shouldn't cover, like what other software you use and th distribution of encryption and signing keys.

      It is ubber rubbish and goes to show that many people were mislead into the opensource community thinking it was a place were code couls be free when it was actualy a place were some ego's and activision was lying in wait.
    48. 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.
    49. Re:I'm confused by pgk2 · · Score: 1

      I disagree with the sentiment Novell "admitted" that Microsoft holds some IP leverage over Linux. MS claims that they have some IP in Linux, that much is well known. Novell has done a deal with MS that exempts their customers from a suit by MS. I would think that customers would love this. No admission that any MS IP is in the code, as required under the GPL, and MS agreeing not to sue.

      I would note the way the payments work in the deal. MS is paying Novell. Unless MS is paying for the right not to sue someone else it appears that Novell is using their patent portfolio to protect their customer base. As a developer of Netware, a licensee of SVR4 and developers of other IP they are using their leverage to protect their customers. To me it would look like Novell believes that MS has a lot of Novell IP in their software. The flow of payments make that appear even more so.

      Without the deal MS could sue any Linux distribution user. Novell is just trying to eliminate the legal risk for their customers who say they can not move to Linux because of potential patent issues with MS.

    50. Re:I'm confused by Anonymous Coward · · Score: 0

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

      BS PC garbage. If a person is considered moron, I'd rather someone be up front about it. If you're so easily dissuaded from holding your opinion or putting up a counterargument, all the better. I find that constructive in knowing who I'm dealing with, whether receiving the offense, or giving it and gauging a reaction.

      In fact, most of my most constructive discussions are when everyone easily feels to use words they choose. Big freakin deal if someone is insulted; if the opinion is that low or seen as such, it's better people know.

      Of course, conveniently, you're sidestepping the issue anyways, which is the flawed opinion. Seems to me overall an apt and easily justified use of the word, and your response is downright petty.

      Begin a discussion? Are you freaking kidding? Please. This is /. You're putting up debate rules to the peanut gallery? Oooo! I insult the entire /. crowd! Oh. My. Gosh.

    51. Re:I'm confused by TheUser0x58 · · Score: 1

      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.

      IANAL but the GPL is not a contract, its a license for distribution. In other words the FSF et al. would want to sue for copyright violation, not breach of contract (there is no contract to breach).

      --
      -- listen to interesting music, support independent radio... WPRB
    52. Re:I'm confused by Teun · · Score: 1
      I have to apologise for partially loosing track of the thread.

      I still feel the AC OP: http://yro.slashdot.org/comments.pl?sid=220420&cid =17871934
      was ridiculing the users of GPL style licensing.

      Its his denial to be a moron: http://games.slashdot.org/comments.pl?sid=220420&c id=17872224
      that made me write I concurred with the notion he was a moron, not because he was called such but because of the in my view flawed reasoning he is using and repeating.
      It is in my next reaction that I stated wrongly it was his own word.

      I still think the OP is unnecessarily negative about those that (hopefully) knowingly elected to release their work with a GPL license.

      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.
      We know the BSD license gives different freedom but it's not more, just different.
      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    53. Re:I'm confused by Mateo_LeFou · · Score: 1

      "and activision was lying in wait."

      hehe... freudian typo?

      --
      My turnips listen for the soft cry of your love
    54. Re:I'm confused by Anonymous Coward · · Score: 0

      3 questions to put the communitys stance into perspective....

      1, Do you trust any claims made by PJ?
      2, Do you trust any claims made by Bruce?
      3, Have you paid them money?

      lets refresh everyone memory shall we. A few years ago a small company made some hefty IP claims against the Linux kernel, you might have heard of em, I believe their called SCO. That was followed by a report from a new company setup to provide insurance to developers against getting sued. That company apparently went through the code and identified a number of areas where it might infringe certain companys patents. You might remember that report, it made slashdot along with a *lot* of posts from its founders about how great OSRM was.

      So if you answered yes to Q1 and Q2, its not a case of IF theres patent infractions, its a case of THERE ARE patent infractions.

      You may not like what Novell have done, but in the above light its the only sane course of action for them to have taken. The FSF may in future versions of the licence try and make Novells life more interesting, but there are a lot of ways to sidestep the religious zeal and ensure the customers and inhouse developers remain protected.

      Now if you'll excuse me, I'm going to sit back and wait for the usual conspiracy theories, blind faith in IBM, and accusations of outrageous FUD.

    55. Re:I'm confused by Anders+Andersson · · Score: 1

      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.

      Section 7 of GPLv2 isn't limited to patent restrictions or even intellectual property rights in general, but appears to cover any restrictions affecting the freedom to distribute the software. Let's say that in some odd jurisdiction, distribution (or perhaps merely export) of source code is flat-out prohibited, while executable binaries are ok. The GPL allows binary-only distribution if they come with an offer to provide the source code at a later time. Now, when the recipient of those binaries decides to ask for the sources, the distributor cannot comply without violating the law. Are they really excused by the law to ignore that part of the GPL? They didn't add this restriction themselves, and thus they are distributing all the rights they do have under the law, but that doesn't include the freedom to distribute source code. They should of course have foreseen the recipient's request, and refrained from distributing even the binaries in the first place.

      I interpret patent restrictions in the same way. The distributor cannot simultaneously recognize the validity of a claimed patent and distribute GPL software covered by it, knowing full well that the recipients cannot legally redistribute what they receive without additional patent licenses granted by someone else. If the law says redistribution is prohibited (due to the patent), then you cannot merely blame the law and continue to distribute.

    56. Re:I'm confused by HiThere · · Score: 1

      One cute part is, that since the IP, of whatever nature, is not identified, you can't look at code from Novell and even GUESS whether it contains MS IP.

      Another cute part is, the agreement only runs for five years. And can be cancelled sooner at MS sole option.

      Another is that if you read carefully who is covered by the "we won't sue" guarantee...it truns out to be, as near as makes no difference, NOBODY! I.e., you are covered if you do independent development that you aren't paid for and which you don't share with anyone. (In which case, of course, nobody would ever find out you had done it, so you wouldn't be in any danger of a suit.) And MS could cancel the guarantee without notice at any time anyway.

      It's safest to just avoid Novell. I don't know whether someone got paid off, or someone was monumentally stupid, or whether there's something in the hidden parts of the agreement that someone was greedy about. To me it doesn't matter. Malice, greed, stupid, or naive, the effect is the same. They may be contagious, and they either can't or won't prove that they aren't. And you can't tell whether what they [are | may be] contagious with is an itch or the plague.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    57. Re:I'm confused by trifish · · Score: 1

      How do you figure that?

      Start by asking yourself why there is the term copyleft (as opposed to copyright) used when referring GPL-style licenses.

    58. Re:I'm confused by Anders+Andersson · · Score: 1

      Without the deal MS could sue any Linux distribution user. Novell is just trying to eliminate the legal risk for their customers who say they can not move to Linux because of potential patent issues with MS.

      No, Novell is just trying to eliminate the legal risk for their customers who say they can not move to Novell's variant of Linux (SuSE) because of potential patent issues with MS. In doing so, they leave every other user of Linux (as well as other open source software) out in the dark, fearing that Microsoft may one day sue them.

      Even if the threat of litigation is weak, it's still a threat, and buying out your own customers from that threat actually strengthens it. As long as the entire neighbourhood stands united against mafia types trying to sell them "fire insurances", the risk of an actual fire is quite low. When one of the neighbours pay for such an insurance, the mafia sees that there is a potential customer base, and the risk of fire increases.

      The difference with respect to the patent issue is that Microsoft will never be able to claim that they didn't start the fires. As if that would make their kind of insurance any more legit.

    59. Re:I'm confused by Anonymous Coward · · Score: 0
      Novell is trying to claim that the people they distribute to get the protection so the GPL is followed to the letter.

      Go back and read section seven again.

      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.

    60. Re:I'm confused by pgk2 · · Score: 1

      True enough that Novell has eliminated the risk only for their customers. The trouble is Novell can not negotiate for the whole community they can only negotiate for themselves and in this case for their customers. I still look at the flow of money. It is from MS to Novell. Why would MS pay Novell for Novell's customers right to use their patents? Seems that the "insurer" is paying the insured in this case. Not your typical "protection money" scheme. To me the ideal solution would be for the Linux community to "buy up" or have contributed a number of patents for integration into Linux. Then the community has a patent portfolio to protect them against MS or other large companies who may want to sue for patent infringement. That is how the corporations use their patents in most cases, defensively. Novell appears to have done that already. I would suggest that Novell contribute their Netware or other patents to the community and then hire someone to negotiate with MS for a cross license agreement. Who knows, maybe MS would pay money to the community to make the issue go away. ;-)

    61. Re:I'm confused by Anonymous Coward · · Score: 0

      I was about to post the same comment. Nice to see that the FSF saw this coming so they phrased the license in a way that wouldn't allow the loophole. Sad to see that some people fast-read the license, assume that the FSF couldn't possibly have forseen this loophole, post to slashdot that they didn't, and get moderated to +5.

    62. 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
    63. Re:I'm confused by kz45 · · Score: 1

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

      How are they violating the GPL?

      The fsf website states that you are allowed to sell GNU software as long as you don't restrict usagem and either give out the source with binaries or give the source out upon request.

      The FSF is using intellectual property to serve their own political agenda, which is interesting because they are the #1 organization against IP (or is it okay for the FSF only).

    64. Re:I'm confused by KDR_11k · · Score: 1

      Plus, it has been written largely in France, not the US.

      Hm, this brings up an interesting question: Does the GPL require that it can be sublicensed royalty-free by anyone in your jurisdiction or anyone in the entire world? As such would it violate the GPL to distribute something that's patent encumbered in the US but not the rest of the world because a US American could download it and would not be able to redistribute it without paying patent royalties?

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    65. Re:I'm confused by Anonymous Coward · · Score: 0

      No...they can't.

      And in fact, if they were to do so knowingly, they open themselves up to liabilities from all sorts of sources...not to mention the fact, that they'be basically "pee-ed in the pool" (sp?), polluting the code which they depend on both now and AFTER the agreement with MS goes out. No company in their right mind would do this...and include Novell with that. It would be sheer stupidity and be extremely short-sided, and in fact, opposite to the direction they've always been on.

    66. Re:I'm confused by KDR_11k · · Score: 1

      It's a written license agreement, that makes it a contract.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    67. Re:I'm confused by Stalyn · · Score: 1

      Explain to me how point 4 is feasible? A convicted monopolist suing non-customers. Yes they could technically do it but is it worth it to Microsoft? And what would be the government's response? Could higher courts overturn a favorable Microsoft decision? Is there some precedent for companies suing non-customers? Also who specifically would Microsoft sue? I think many quickly gloss over these contingencies and in the end overlook the fact how HARD point 4 would be for Microsoft.

      Also on point 1 there has been no indication from Novell that they will now knowingly start using patented Microsoft code. Even if Novell is lying how could they get away with it? Would Novell coders be willing to perjure themselves in court?

      --
      The best education consists in immunizing people against systematic attempts at education. - Paul Feyerabend
    68. Re:I'm confused by elronxenu · · Score: 1
      If linux is found to be non-free in any way then the community will modify it until it becomes free.

    69. Re:I'm confused by killjoe · · Score: 1

      I think you all are missing an important point. It's not that MS has promised not sue Novell, it's that they have promised not to use novell customers.

      MS knows they can't sue debian or even ubuntu because there is no money there and distros can pop up overnight. They are planning a series of lawsuits on corporations who use linux. They are banking on the fact that if they sue a handful of smaller companies that use linux then they can stop widespread adoption of linux.

      Aside from that they are getting tired of being blackmailed by linux. Imagine this scenario.

      MS: We think you have been stealing software, we are going to perform an Audit.
      Customer: If you do I will switch to linux.
      MS: If you do we will sue you because linux infringes on MS patents and Novell admits to this facts.

      See?

      --
      evil is as evil does
    70. 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!"); }
    71. Re:I'm confused by Anonymous Coward · · Score: 0

      Actually, patents are problematic in this regard as well - if you don't defend it, it is possible, it's just not as easy to lose a trademarks.

    72. Re:I'm confused by Antique+Geekmeister · · Score: 1

      Also note: Samba is very much a replacement for the older Novell Netware in its basic features. Novell's support for Samba just fell apart, because Jermey Allison (one of the key Samba developers) just resigned from Novell because he thinks this agreement violates the GPL. His resignation letter has been published, and is viewable at http://www.groklaw.net/article.php?story=200612210 81000710 .

      Samba is pretty obviously one of the things Microsoft wanted to manipulate through this deal. Jermey Allison just took away one of their big hooks to manipulate the protocol and the standard implementations, at serious personal cost, by leaving Novell. Google grabbed him: expect to see some fascinating shared and large-scale storage work going on at Google.

    73. Re:I'm confused by Antique+Geekmeister · · Score: 1

      And look for exactly such Microsoft patent or copyright based extensions for mail handlers to support Microsoft's SenderID product, and other XML based tools for which Microsoft has been grabbing patents any way it can for the last few years. And oh, my goodness, look for it with Trusted Computing based technologies, and with related DRM tools.

    74. Re:I'm confused by RobertLTux · · Score: 1

      the problem is like this lets just say we as a group have a gentlemens agreement to allow our children to play in a pool or set of pools (we each own 1 of the pools in question) time goes on and Bob decides to start selling access to the pools since Jason wants to sell snacks next to the pools
      problems

      1 Bob has no right to set up the ticket booth (he wants to use his kids in a show fine but...)
      2 Jason is a pedophile (and nuts to boot)
      3 the snacks are poisoned (just a bit)

      in short a gentlemens agreement only works is all parties involved are gentlemen

      --
      Any person using FTFY or editing my postings agrees to a US$50.00 charge
    75. Re:I'm confused by MysteriousPreacher · · Score: 1
      --
      -- Using the preview button since 2005
    76. 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.
    77. Re:I'm confused by HiThere · · Score: 1

      I agree with you that it's a bit harsh, which is why I appologized for the analogy. But I still can't think of a better one.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    78. Re:I'm confused by sumdumass · · Score: 1

      So far, I havn't seen novell claim anything to the contray. This whole situation depend on Novell placing something aplicable into the software and then distributing it.

      The agreement can cover "John Whoever" that subcontracts with MS and contribute his code to redhat but neglects to see the part were MS owns the code develpoed there. In that case, No one ever had a right to distribute it. MS just isn't going to fuck with their customers like SCO has tried. In this situation, nothing could fault Novell. They neither claimed a right to the code outside the GPL and never had to extedn any protections to anyone other then their customers.

      The fact that some protection has been extended on it's own in no way violates the spirit or the actual GPL v3. I would need novel to contribute something and have it be actionable and to this date, I don't think it has happened or that any planes to do so in the future have been released.

      So were is the problem beside Novell is friends with microsoft.

    79. Re:I'm confused by Stu+Charlton · · Score: 1

      But the GPL is, essentially, all about giving code ownership of itself.

      Except that copyright owners can still do whatever they want with the code & future derivatives....

      Where we ought to be headed, my guess, is towards sentient code that owns itself

      Why? Code has value only in a context of human relationships. Code is not an end in itself.

      --
      -Stu
    80. Re:I'm confused by utlemming · · Score: 1

      And what about Groupwise? Last time I loaded that up, it sure looks like something that can compete with Exchange.

      --
      The views expressed are mine own and do not express the views of my employer.
    81. Re:I'm confused by init100 · · Score: 1

      How are they violating the GPL?

      The fsf website states that you are allowed to sell GNU software as long as you don't restrict usagem and either give out the source with binaries or give the source out upon request.

      Whether Novell is in violation is unclear, what is clear is that Novell is using a creative interpretation of the GPLv2, which was certainly not intended by the FSF when they wrote it.

      Selling GNU software isn't the problem. It is the patent agreement that is the problem, essentially stating that Novell-supplied F/OSS is the only safe (from Microsoft-initiated patent litigation) F/OSS, and that other F/OSS (such as GNU software downloaded from the GNU website) is unsafe F/OSS (you risk being sued by Microsoft for patent infringement).

    82. Re:I'm confused by init100 · · Score: 1

      Microsoft and Novell have agreed not to sue each other over patent violations.

      Nitpick: No, they have not. They have agreed not to sue each others' customers, essentially providing a (non-redistributable) patent license to each other's customers. They can still sue each other. As far as I understand, this is the reason why the agreement does not fall afoul of the patent license clause in the GPLv2.

    83. Re:I'm confused by Anonymous Coward · · Score: 0

      And to be more specific, ad hominem tu quoque

    84. Re:I'm confused by Anonymous Coward · · Score: 0

      Its not really that harsh if you remember that SFU (Services For UNIX) for Windows for a lot of years was sold for over $120.00 per seat. The whole service is written from BSD code. A lot of it still has the copyrights in it. Here is a case of BSD's bastard child being sold into slavery.

    85. Re:I'm confused by init100 · · Score: 1

      To me it would look like Novell believes that MS has a lot of Novell IP in their software. The flow of payments make that appear even more so.

      To me, the flow of money just indicates that the ability to claim that Microsoft patents are infringed in Linux are of great value to Microsoft, and the agreement increases the credibility of their claims. Microsoft pays for the ability to say that "Linux infringes our IP, and Novell agrees". Microsoft can argue that Novell signed the agreement in part because they recognize that Microsoft IP is infringed in Linux. Why would they otherwise do this?

      Of course, Novell could have signed this agreement even if those Microsoft claims were baseless, since it gives them a lot of money, and also creates a belief that Novell F/OSS is safe F/OSS while their F/OSS competitors provide unsafe F/OSS, which would give them an edge in the marketplace.

    86. Re:I'm confused by init100 · · Score: 1

      So if you answered yes to Q1 and Q2, its not a case of IF theres patent infractions, its a case of THERE ARE patent infractions.

      No, it's not. Nobody knows if there are patent infringements until a court says so. That's why OSRM said that Linux might infringe on these patents. You can still trust them without admitting any patent infringement in Linux.

    87. Re:I'm confused by Anonymous Coward · · Score: 0

      I wasn't negative at all. Nowhere did I say or imply that those who prefer the GPL were "bad" or "wrong". Perhaps you are inserting what you want into my statements. The only thing I said that could be even remotely construed as negative would be _if_ the FSF were able to exert this level of control over GPL'd software.

      This is ridiculous. I made one comment voicing my own honest preference and the next thing I know I am being labelled a troll and being personally attacked. Don't take this the wrong way, but I think that you seriously need some counselling.

    88. Re:I'm confused by Anonymous Coward · · Score: 0

      I do understand that. I guess I'm just more comfortable with the BSD way. Sure someone can take my code, use it and not contribute anything back, but I can do the same as well. Then again, we both might contribute something back if we want to. It's that choice that I like.

      Don't get me wrong, I understand the GPL mindset as well, but it's just not for me.

    89. Re:I'm confused by mrchaotica · · Score: 1

      SCO looks like they may pretty much end when their assets are frozen due to a preliminary injunction filed by... Novell.

      Indeed, which has the benefit of keeping SCO's assets away from IBM. Note that that injunction came after the Novell-Microsoft deal, and everything becomes considerably less confusing.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    90. Re:I'm confused by mrchaotica · · Score: 1

      Explain to me how point 4 is feasible? A convicted monopolist suing non-customers. Yes they could technically do it but is it worth it to Microsoft? And what would be the government's response? Could higher courts overturn a favorable Microsoft decision?

      That depends on whether the Federal government were currently pro-big-business or not.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    91. Re:I'm confused by mrchaotica · · Score: 1

      So what are you saying ? *All* patches from Novell employees should be rejected ?

      At this point, that's really the only safe option.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    92. Re:I'm confused by DaveV1.0 · · Score: 1

      You are wrong. The BSD license gives more freedom. Public domain gives even more freedom.

      You sound like something out of Animal Farm or 1984.

      "The restrictions that have been placed on you don't diminish your freedom. It just gives your a different kind of freedom."

      The "just different" freedom is a lesser kind of freedom. A restriction reduces one's freedom.

      And now, the "Free Software Foundation" wants to restrict Novell's freedom of association because it does not like who Novell is associating with.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    93. Re:I'm confused by DaveV1.0 · · Score: 1

      Of course that assumes that Novell distributes code developed using the MS patents under the GPL. If Novell uses the knoweldge gained from the MS patents to make closed source software, under a standard proprietary license, then Novell never violates the GPL.

      Novell would be better served doing that. Then they can work to become the #1 Linux server distro by virtue of working well with MS products.

      Then, MS and Novell both profit even more. (Fewer legal fees)

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  2. Wasn't it once... by Anonymous Coward · · Score: 1, Insightful

    Free as in Beer?

    1. Re:Wasn't it once... by Anonymous Coward · · Score: 1, Insightful

      This gets an insightful? The quote from RMS, roughly, goes "We do not mean free as in beer, but free as in freedom." You've apparently never heard it.

      The notion of that "freedom" is what the GPL is is all about. It's not a "anything you do with this code is OK," it's "Here--someone built this, but they're willing to share it with you for free. All we ask is that you share with others as well."

    2. Re:Wasn't it once... by dosius · · Score: 1

      Both phrases, "Free Software" and "Open Source Software" can be misleading.

      Free Software, because the first thing that comes to mind is price.

      Open Source Software, because to many people it simply means source available, and nothing about what you can do with it.

      It isn't just for trying to come up with a catchy acronym that I'm calling my project (a mix of BSD, Heirloom Toolchest, and my own code under BSD and ZLIB-like licenses that can be used as a lightweight substitute for GNU) "FOX" - it stands for Free Open *X, because I believe that you can't just describe it as one or the other without misleading people.

      Free Open *X is "Free and Open Software", the term I prefer. It's free to the world to do practically whatever they want with it, and open for the world to see how it ticks, and just about the only requirement is to give credit where credit's due - the way I've always believed in.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
  3. Dumb Move by Anonymous Coward · · Score: 1, Interesting

    That would be dumb, it would hand Microsoft a victory, even discussing this casts doubt over distributors of Linux. Is the story even real or is it MS FUD?

    1. Re:Dumb Move by Anonymous Coward · · Score: 0

      Ah; so it's dumb when Microsoft goes after distributors of OEM copies of Windows because it casts doubt on other distributors?

      Don't be stupid. If you have a legal agreement and you let one set of people flaunt it then you destroy it's credibility. If Novell had come to the FSF to discuss beforehand, it would be stupid. Since they showed no good will, showing any good will in return is stupid. At this point what is needed is contrition.

      The FSF should, and does, show tolerance to the mistakes of its friends. This agreement was made secretly simply because Novell knew the FSF wouldn't like it. Their contempt for the rest of the kernel developers is even worse.

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

    3. Re:Dumb Move by gtoomey · · Score: 1

      You are very confused. If Novel cant distribute linux, then the $210 million purchase of SUSE is worthless.

    4. Re:Dumb Move by dangitman · · Score: 1

      But they believe they can distribute Linux, regardless of what the FSF says. It wouldn't be the first time that a company ignored licensing agreements or copyrights. They probably hope to either ignore the FSF or bully them out of the picture.

      --
      ... and then they built the supercollider.
    5. Re:Dumb Move by robpoe · · Score: 1

      This is not flamebait.

      It's contrary to the Slashdot hordes, but it's the first thing *I* thought of when I saw this article.

      --
      = Grow a brain...
    6. Re:Dumb Move by kryptkpr · · Score: 1

      And what are they going to use to compile that "something else" with? Visual Studio .NET?

      --
      DJ kRYPT's Free MP3s!
  4. 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 gtoomey · · Score: 1

      All the copyright to the kernel is assigned. If the kernel goes GPLv3 then this applies.

    5. Re:How can they do this? by sporkmonger · · Score: 1

      So, if they change the license to spite Novell, does Apple get caught in the crossfire since they include gcc, etc in their Xcode developer tools stuff?

    6. Re:How can they do this? by RidiculousPie · · Score: 1

      All the copyright to the kernel is assigned.

      This is incorrect. Copyright to the code in the kernel rests with many authors, some is licensed under GPL V2, some under GPL V2 or later.

      If the kernel goes GPLv3 then this applies.

      Linus Torvald's current position is that it will not, as he is unwilling to license his code under GPL V3.

      See http://lkml.org/lkml/2006/1/25/273.

      --
      ah, mod points ... now where is my crack?
    7. Re:How can they do this? by Anonymous Coward · · Score: 0

      No, you can use any of the current GPLv2 stuff under the GPLv2 indefinitely provided you don't incorporate any GPLv3 updates to the software

    8. Re:How can they do this? by squiggleslash · · Score: 1

      Not unless Apple tries to pull the same stunt, no.

      --
      You are not alone. This is not normal. None of this is normal.
    9. Re:How can they do this? by jonbryce · · Score: 1

      That's why TFA talks about *future* versions of FSF software - the versions it releases under GPL3; and why it talks about the additional cost Novell would face if it had to maintain its own GPL2 fork of these programs.

    10. Re:How can they do this? by jlarocco · · Score: 1

      Linus Torvald's current position is that it will not, as he is unwilling to license his code under GPL V3.

      That's exactly true. The Linux kernel itself is almost certainly going to stick with V2. But you can't do much with just a kernel, and a whole bunch of the userland tools are GNU projects. To name a few: bash, coreutils, shellutils, fileutils, tar, gzip, gawk, grep, sed, aspell, wget, which, emacs, gcc, gdb, make, autoconf, automake, libtool and hundreds more.

      The GNU tools will almost certainly have their licenses changed to v3. I believe the FSF holds the copyrights specifically for that reason.

      As much as people laugh at Stallman over "GNU/Linux", he has a pretty good point.

    11. Re:How can they do this? by notamisfit · · Score: 1

      That is true, but many of the GNU components (except for the development stuff) has been pretty static the last few years, and even gcc does what it was set out to do. Cutting Novell off from updates would be fairly bad, but it wouldn't be the end of the world.

      --
      Jesus is coming -- look busy!
    12. 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.

    13. Re:How can they do this? by someone1234 · · Score: 1

      I think they could distribute old versions. You cannot retroactively strip GPLV2

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
    14. Re:How can they do this? by Anonymous Coward · · Score: 0

      Richard Stallman was quoted as saying that the Novell-MS agreement violated the spirit but not letter of either GPLv2 or the current GPLv3 draft, and that the FSF would go back and revise the GPLv3 to forbid such patent covenants.

      Otherwise the FSF would've been all over the Novell within a week or two of the announcment.

    15. Re:How can they do this? by t35t0r · · Score: 1

      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

      Ever heard of forking? Last time I checked all those apps were still GPLv2. Novell can fork the last version released under GPLv2. They can keep applying patches as long as those patches aren't GPLv3 licensed and as long as those patches don't contain MS proprietary code.

    16. Re:How can they do this? by heinousjay · · Score: 1

      Something confuses me about switching the code over the GPL3. Isn't Novell free to keep using what they have under GPL2 at that point? I fail to see how the FSF could retroactively change the license terms of something that's already been distributed.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    17. Re:How can they do this? by ady1 · · Score: 1

      Not trolling but it does makes me wonder that what if this whole atricle and story is a ploy to put linus under pressure for not making the kernel GPLv3.

    18. Re:How can they do this? by Vlad_the_Inhaler · · Score: 1

      That simplifies things.

      If this sort of move was pulled on the basis of a retroactively changed license, the FSF would be toast. Novell's lawyers would have blown the FSF lawyers out of the water and the only winners (apart from the lawyers) would have been a large company in NE Seattle.

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
    19. Re:How can they do this? by mjtaylor24601 · · Score: 1

      "They have patent indemnification licenses with MS. This suggests they believe that without those licenses they would be violating patents."

      That would make sense if the legal system were somehow setup to ensure that only guilty people got sued. But as our good friends over at SCO have shown us pretty much any idiot can sue anyone for any reason. And if that idiot has deep enough pockets (which MS certainly does) they can make your life miserable regardless of the merits of the case.

      To me this sounds more like a marketing gimmick than anything. MS stirs up a lot of FUD in the press about Linux allegedly violating their IP. This naturally makes CEOs hesitant to adopt Linux for fear of being sued by MS. So Novell signs a "no suing" pact with MS and can then put a big bullet point in their brochure reassuring their potential customers that they won't be on the business end of an MS lawsuit.

      --
      I wish I were as sure of anything as some people are of everything
    20. Re:How can they do this? by anthony_dipierro · · Score: 1

      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.

      In addition to the possibility of forking the old versions, what if Novell just gave the software to someone else to distribute? They make changes to all the GPLv2 software, the kernel, those packages which didn't get switched to v3, the parts they managed to fork, and then they hand off all of that to a third party who *is* allowed to distribute GPLv3 software.

      I really think if the FSF goes ahead with this it's going to hurt free software severely. Copyleft works best when there is only one license, and for a long time that's how it was with the GPLv2. Fragmenting free software into two incompatible licenses (GPLv2 and GPLv3) is going to hurt the free software movement. Just look at all the difficulties the Free Content movement is currently facing, with the GFDL, incompatible with CC-by-SA, incompatible with CC-BY-NC-SA, etc.

      Now maybe this won't happen. Maybe there is enough software currently licensed under GPLv2 or later which can be transitioned to GPLv3 or later, and maybe there will be an overwhelming support within the free software community to make the switch. Maybe the FSF should spend all of its efforts during the first few years after the GPLv3 comes out making sure that happens, and worry about slapping down companies like Novell and Microsoft later, when free software is in a less fragile state.

    21. Re:How can they do this? by init100 · · Score: 1

      He cannot make the kernel GPLv3 even if he wanted to. There are a lot of contributors, and all copyright holders have to agree to change the license on their parts to GPLv3, or there can be no change. The alternative is stripping out the parts from those that resist a license change and rewrite them, but that could be a very large task with little or no gain.

  5. 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'
    2. Re:For the best by dangitman · · Score: 1

      Run. Run like the wind.

      Shouldn't that be "Blow. Blow like the wind"? I don't think the wind runs.

      --
      ... and then they built the supercollider.
    3. Re:For the best by heroofhyr · · Score: 1

      No, blow like the wind is what Novell has decided to do. Running would be the opposite. You may be asking yourself how it can do both. Well, the wind is a very complicated man. And no one understands him but his woman. One of the reasons this whole Novel-Microsoft-FSF issue is so complex is due to the high amount of personification involved:

      Novell -> Gets Windfall
      Wind -> Blows
      Novell -> Blows
      Wind -> Runs
      Good Advice <- (Novell -> Runs)
      Wind -> Complicated
      Shaft -> Complicated
      Microsoft -> Shafts -> Novell
      Pressure <- High -> (Eben Moglen -> Novell)
      Both Sides -> Hot Air
      Linux Community -> Novell <- Cold Shoulder
      Software Community -> Stormy
      Ballmer -> Dangerous Flying Debris
      Richard Stallman -> Hair Always Looks Like Caught in Hurricane
      Windows -> Haphazardly Duct Taped to Prevent Immediate Shattering
      Whole Issue -> Tempestuous Cyclone of Flying Nerds

      --
      brandelf: invalid ELF type 'KEEBLER'
    4. Re:For the best by dangitman · · Score: 1

      I blame the Dutch. We might not be having these wind problems if they haqdn't built all those damn windmills.

      --
      ... and then they built the supercollider.
    5. Re:For the best by kimvette · · Score: 1

      That is not how windmills work!!!! Goodnight!

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
  6. 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 Anonymous Coward · · Score: 0

      Hello,

      > if most of SUSE goes GPL3

      well, I do think that most of the gnu programs (gcc, make, ncurses, wget), etc. will actually be GPLv3 when it came out. Futhermore, I also don't think that Novell will take the effort to fork all of 'em).

      Greetz.

    2. 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'
    3. Re:Poor Article by kripkenstein · · Score: 1

      well, I do think that most of the gnu programs (gcc, make, ncurses, wget), etc. will actually be GPLv3 when it came out.

      Yes. Also GNOME (which is the default on SUSE these days), and Samba.

      But lots of other stuff won't. So a sizable part of SUSE will be moving to GPL3 (barring any surprises), but not the overwhelming majority (e.g. the kernel).

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

    5. Re:Poor Article by Anonymous Coward · · Score: 0

      No application will automatically "go GPL3". New versions of GNU software will undoubtably be distributed with the new license, but it won't apply to software that is already out there.

      The problem Novell will have is that they won't be able to maintain a current distribution anymore, unless they fork or replace all of the significant GNU components. If they manage to pull that off, which would be difficult indeed, at least they will have solid ground to stand on when they refuse to say "GNU/Linux"... ;)

      I think the danger here is that Redhat may soon become a GNU/Linux monopoly. I think Novell's bargain with Microsoft stinks, and they deserve what they get, but it will be sad to see a decent competitor get flushed.

    6. Re:Poor Article by Tony+Hoyle · · Score: 1

      The Linux kernel doesn't have the 'or above' clause (neither do a lot of opensource projects, incidentally).

      So OpenSolaris can't use any of it.

    7. Re:Poor Article by cheater512 · · Score: 1

      Whats a kernel without stuff like Bash, X, etc...?

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

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

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

    11. Re:Poor Article by gtoomey · · Score: 1
      You do NOT have multiple copyright owners for the kernel.

      ALL the copyright of the kernel is assigned to one entity (not sure if its Linus, but there is only one owner of the source).

    12. Re:Poor Article by H3g3m0n · · Score: 1

      There are non-GPL user space tools available, we could find that the FreeBSD user space tools are ported to the Linux platform, or alternatively a fork of the tools. Xorg isn't released under the GPL, its got its own license, the MIT X license (I believe its closer to the BSD license than the GPL) Personally I feel that the GPLv3 could be a huge threat to Freesoftware, i think things like anti-DRM should be in a separate license that developers can choose for their own software and not forced onto the end users through the userspace tools, Linux(well the GNU userspace tools) just doesn't have enough of a market share to try throwing this kind of weight around, its just going to drive more corporations to Windows (or maybe FreeBSD/closedCommericalSolaris). Not being able implement an open source hardware driver that Linux uses on OpenSolaris(when its GPLv3ed) or FreeBSD because nobody can agree on the definition of Freedom seems the opposite of freedom. I think any code I release will be released under the most liberal license i can find and let everyone else work it out, I would also recommend considering dual licensing or ensuring that all patches submitted to a project give full permissions to the project owner. It does run the risk of the owner selling out to a company, but the original project will always be free and can be forked.

      --
      cat /dev/urandom > .sig
    13. 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.

    14. Re:Poor Article by Pecisk · · Score: 1

      It is impossible, because majority of copyright owners of linux kernel code doesn't support such move. And believing that OpenSolaris will suddenly go very big with GPLv3 is wet dream at it best (sorry for offensive words, but it feels very right here).

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    15. Re:Poor Article by that+this+is+not+und · · Score: 1

      Well, Novell and anybody else who disagrees with GPL 3 can fork the GNU toolchain, under these circumstances. There's no reason at all that they can't. And then, the 'and any newer version' clause in the GPL license becomes essentially irrelevant. The new GPL is MORE restrictive than the old, so people could OPT to observe it with the new forked Novell/GCC, but they wouldn't HAVE to observe it. Things can plod along indefinitely with GPL V.2 and in fact they might, if enough people jump ship from the FSF's initiative.

    16. Re:Poor Article by that+this+is+not+und · · Score: 1

      Well, I guess the lawyers will need to figure out the licensing issues,

      From the song 'High Hopes':

      "Whoops, there goes another rubber tree plant."

    17. Re:Poor Article by that+this+is+not+und · · Score: 1

      The idea of open source means that, uh, you should look at the myriad copyright notices in some of the files in that thar tarball before you say the thing that you just did. Because you could have, instead of just issuing your utterance.

    18. Re:Poor Article by that+this+is+not+und · · Score: 1

      There are non-GPL user space tools available, we could find that the FreeBSD user space tools are ported to the Linux platform, or alternatively a fork of the tools.

      Or alternately, we could abandon the Linux codebase and switch to a BSD wholesale. Or Novell could do that. SUSE/BSD.. hmmm, that would be interesting.

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

    20. Re:Poor Article by master0ne · · Score: 1

      it was my understanding that the submitter to a patch for the kernel could choose the licence s/he wanted, and if it was acceptable, and the patch was well recived, than it would be incorperated in the kernel, which would mean that each contributor to the kernel owns his/her code that contributed to the kernel, in turn causing multipul people to own many different parts of the linux kernel, with Linus owning the lions share...

      --
      Noone writes jokes in base 13!
    21. Re:Poor Article by nbritton · · Score: 1

      Sounds like a plan. Hopefully FSF/GNU's bans Novell and then Novell switches to a BSD toolchain... I can't stand the GNU toolchain.

    22. Re:Poor Article by Perey · · Score: 1

      Most software under the GPL allows 'any later version'. (The FSF's default GPL boilerplate certainly does.) Anyone distributing this software can change the licence used from GPLv2 to GPLv3(,4,5...) just by editing their files to have a '3' instead of a '2'.

      So if kernel.org did this, voila, Linux is GPLv3, just like that. (Another poster states that some parts of the kernel specify GPLv2 only. But then they'd be distributing parts under GPLv2, parts under GPLv3, and the net effect is that anyone distributing the whole kernel has to comply with the GPLv3 anyway.)

    23. Re:Poor Article by ckedge · · Score: 1

      I've NEVER understood why people would put blind faith and trust in "any subsequent version of the GPL" by releasing their code under GPL 2 but allowing anyone who comes after them to "accept/use" any subsequent version of the GPL. So if the people who are in "control" of the GPL had an epiphany and made GPLv3 be identical to the BSD license - does that mean everyone could take GPLv2 code that has the "any subsequent vesrion" clause and turn it into "GPLv3 aka BSD"?

      Intent in contracts is a big thing, isn't it? If the GPLv3 turns out to be more restrictive or violates the "intent" of the GPLv2 than the GPLv2 itself - I'd betcha that you could easily convince a judge that the "any subsequent version of the GPL" line in the terms could be totally at odds with the intent of ALL of the rest of GPLv2 - and thus that line be null and void.

      Hey there's a question. Exactly what legal circumstances restricts who can and can't "author any subsequent version of the GPL"?

      This is probably the wrong place to post this question. Maybe I should go trawling for groklaw archives or ask the question there.

    24. Re:Poor Article by Anonymous Coward · · Score: 0

      Exactly what legal circumstances restricts who can and can't "author any subsequent version of the GPL"?
      The GPL does:

      9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. ... If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. ...
      Future versions can only be published by the Free Software Foundation. Also note the 'similar spirit' language - if a later version is /not/ 'similar in spirit' (which BSD isn't) or merely 'differ ... to address new problems', then it would fail this clause, and you wouldn't have permission to use it.
    25. Re:Poor Article by 91degrees · · Score: 1

      I'd like to see a few commercial versions of BSD. By all accounts it's quite nice, but installing the last version I tried (FreeBSD, I think) seemed a little more cryptic than I'm used to.

      Not likely to happen though. Linux is too much of a brandname for anyone to give up on it, has good hardware support, and Linus is a lot more easy going about this sort of thing than the FSF, so any restrictions on ditribution are not going to apply to the kernel anyway.

    26. Re:Poor Article by nebosuke · · Score: 1
      This is not correct with regards to the GPL, since what the GP claims is explicitly part of the v2 license.

      9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
    27. Re:Poor Article by jrumney · · Score: 1

      Any journalist that refers to the FSF's work as part of the open-source Linux operating system is just trolling IMHO. They clearly haven't listened to anything RMS has said on the topics of open-source or Linux, so how are the readers supposed to believe they have listened in this case?

    28. Re:Poor Article by anthony_dipierro · · Score: 1

      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.

      At the point where the FSF goes from GPL2 or any later version to GPL3 or any later version, Novell can fork the tools. But either way I don't think the FSF can prevent Novell from *distributing* the GNU tools. Don't they have the right to do that under the doctrine of first sale?

    29. Re:Poor Article by anthony_dipierro · · Score: 1

      Personally I feel that the GPLv3 could be a huge threat to Freesoftware, i think things like anti-DRM should be in a separate license that developers can choose for their own software and not forced onto the end users through the userspace tools

      Licenses, especially free licenses, should give permissions, not take rights away. I support a license which allows users to legally circumvent DRM, not one which prohibits users from implementing DRM. Giving users the right to legally circumvent DRM should be enough anyway - it only takes one person to crack the DRM and distribute the cracked version to everyone.

    30. Re:Poor Article by init100 · · Score: 1

      I think the danger here is that Redhat may soon become a GNU/Linux monopoly.

      Red Hat? I sure use Red Hat, or rather Fedora and CentOS, but around me everyone is singing Ubuntu, Ubuntu, Ubuntu. I'd rather think that the one in danger of becoming a "monopoly" is Ubuntu, and its derivatives. Anytime you mention that you use Red Hat, a bunch of people invariably ask why you are not using Ubuntu instead, and then starts to sing the Ubuntu song.

    31. Re:Poor Article by BiggerIsBetter · · Score: 1

      Competition is good for everyone!

      Except the losers.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
  7. penis? by Anonymous Coward · · Score: 0

    penile?

  8. 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 HanzoSpam · · Score: 0, Flamebait

      For sure. Actually, this is a good reason to avoid implementing "free" software in a commercial environment, no matter how good the quality is. You never know when the cranks and kooks are going to crawl out of the woodwork and create a disruption. Who needs that?

      --

      Progressivism: Parasites helping parasites to help themselves - to other people's stuff.
    2. 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
    3. 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.

    4. Re:Stupid move... by Anonymous Coward · · Score: 0

      Uhh, do you know who Eben Moglen is? Something tells me he doesnt need legal advice from some random ass on slashdot.

      Hint: UANAL, HIAL (and not just any lawyer).

    5. Re:Stupid move... by squiggleslash · · Score: 1

      BitKeeper wasn't Free Software, and Larry McVoy proved in the Linux fiasco to be every bit cranky and kooky, so no, I don't think a company is going to avoid kookery/crankery by avoiding Free Software.

      --
      You are not alone. This is not normal. None of this is normal.
    6. 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.
    7. Re:Stupid move... by Dilaudid · · Score: 1
      And the context is:

      ...council for the organization said that 'the community wants to interfere any way it can' with the Novell business arrangement. They have every reason to be deeply concerned that this is the beginning of a significant patent aggression by Microsoft' Ballmer described patent problems in Linux as an "undisclosed balance sheet liability", in an interview on the deal. I am not a risk manager, but from what I know of Sarbannes-Oxeley it may make it very difficult for company officers (who can go to jail for 25 years for mis-stating liabilities) to adopt non-Novell linux.

      I don't know if this is the best way to fight Microsoft, but bear in mind this is a battle against FUD, and if giving Novell/Microsoft a bit of FUD could kill this deal, maybe it would be a good thing.

    8. Re:Stupid move... by geohump · · Score: 1

      "Horseshit. I've been using products .... for the last 30 years without having any of those kinds of problems."

      Then you have avoided those problems by choosing to purchase from companies (IBM, SUN , MS etc) who are very unlikely to suddenly go out of business. So YOU are exactly the type of business manager who makes the type of risk avaoidance desicions that Microsoft is counting the Novell agreement to cause. This is not just idle speculation. As a former IDC manager of software tooling analysis I can tell you that this type of risk avoidance was ALWAYS present in the minds of people with software purchasing and software developing areas of responsibility. If you are buying software applications, you have to ask will the vendor still be there in 5 years with support and upgrades along the way, and if building software you have to ask "will people buy from us, since they have no way of knowing whether we will still be around in 5 years". Any company whose business was under a serious legal cloud was always drastically affected by same.

      Horseshit indeed.

      The FSF if quite correct to start this investigation. Novell's agreement with MS is a definitive attempt to surrmount/avoid the requirements inherent in the GPL. Novell's lack of concern about their actions poisoning the F/OSS community environment is typical of shortsighted Amercian style business managament which must (by legal requirement in the form of fudiciary duty to stockholders) always make the numbers for the quarter.

      And just in case some executive actually has some notion of running the company for the long term rather than the short term, the wage disparity here in Amnerica where CEO compensation is (on average) 800 times more than employee compensation, will quickly overcome those long term notions. (hmm two more years in this job and I get $$$, versus, if I don't make the numbers this quarter, the board fires my ass, Its a simple decision, and I would do the same thing. I'm human too.)

    9. Re:Stupid move... by Anonymous Coward · · Score: 0

      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.
      FUD. I'm sure most serious risk analysts would agree that most people fear the wrong things (shark attacks, terrorists) and are blissfully unaware of the real risks (walking in a parking lot). I would bet that if you actually searched court cases, you'd find that per million lines of code, more COMMERCIAL software has been involved in lawsuits than FOSS (see Eolas v. Microsoft, Visto v. Microsoft, z4 Technologies v. Microsoft, Contois v. Apple. Seems that you were more likely to be impacted by a legal action involving one of your commericial platforms. Please remember to stay away from the beach!
    10. 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
    11. Re:Stupid move... by Anonymous Coward · · Score: 0

      FUD. I'm sure most serious risk analysts would agree that most people fear the wrong things (shark attacks, terrorists) and are blissfully unaware of the real risks (walking in a parking lot). I would bet that if you actually searched court cases, you'd find that per million lines of code, more COMMERCIAL software has been involved in lawsuits than FOSS (see Eolas v. Microsoft, Visto v. Microsoft, z4 Technologies v. Microsoft, Contois v. Apple. Seems that you were more likely to be impacted by a legal action involving one of your commericial platforms. Please remember to stay away from the beach!
      You probably should have just given the Google search "v. Microsoft". Other interesting factors are that if the vendor is given an injunction against distributing the product, your data may be trapped in a commericial proprietary format. With FOSS, if the data format wasn't well documented and open to begin with (it is) you could always use the source code to get it.

    12. Re:Stupid move... by that+this+is+not+und · · Score: 1

      The FSF if quite correct to start this investigation.

      True, as long as the FSF wants to have the same historical role as 'The Open Group' did in balkanizing and slowly strangling Unix.

      Oh, it isn't completely fair to blame The Open Group. The AT&T Lawsuit and uncertainty of the BSD license did it's part back then, too.

      Not enough Linux enthusiasts have studied the history of Unix in the 70's and (especially) the 80's to see how wrong things can end up going.

  9. Court Battle Ahead? by gnugie · · Score: 1

    From the article:
    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.

    Since the kernel isn't changing licenses any time soon, this appears to apply to portions of the distribution that may go GPLv3. However, nothing prevents Novell from forking the GPLv2 and keeping those around.

    It's also unclear exactly how the new license will prevent this sort of activity. If it's not crystal clear and the FSF tries to use it to remove Novell's right to distribute immediately, we may see an immediate legal challenge to GPLv3.

    --
    Don't know; Don't care; Don't ask
  10. Ah, that actually makes some sense by Rob+Simpson · · Score: 1
    Thanks for explaining it.

    In any case, I switched from SUSE to Linux Mint a while ago... it's the only other distro I've found that supports my wireless card with WPA-PSK "out of the box". Being able to play DVDs and videos without finding and manually installing the packages is a bonus.

  11. 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 Anonymous Coward · · Score: 0

      It's quite possible that the FSF will obsolete themselves if they start acting like this. The projects can be forked en-masse from the latest pre-GPLv3 versions and unless everyone agrees to not contribute to them they may well become the preferred versions (eg. a version of GCC that doesn't require you to go through the copyright assignment rigamarole).

    2. Re:This is retarded by tdvaughan · · Score: 1

      RMS's definition of freedom has repeatedly been shown to be thoroughly pragmatic (see Bitkeeper fiasco) as well as idealistic. In this case, I suspect, the pragmatism will be along the lines of "supporting MS's FUD about their IP being in Linux is a bad idea". Business adoption of Linux will proceed with or without Novell and their attempt to abuse the GPL.

    3. Re:This is retarded by Anonymous Coward · · Score: 0

      not to mention bad for opensource too.

      What's stopping the FSF from "banning" a developer from making a certain program because what he makes isnt part of their grand vision.

      Stallman got it right with the gplv2, then he got lost somewhere along the way and now has the same definition of freedom Bush has.

      It's all about control nowadays. the gplv3 is a thinly veiled attempt to control developers and adopters of opensource, to do no better than what proprietary software does to its users. if they can get away with controlling who does what, that spells doom for the whole movement.

      I still prefer Linus' stance. Which is making free software to make it and make sure it works. none of this political dogma bullshit. Because unlike the other it actually makes sense.

      I've never truly cared much for stallman and his stance. the initial idea was great, but like I said, it's nothing more than a bid for control and power, with him at the top forcing his ideals on everyone, and telling them what they can and cannot make as long as it's given out for free.

      Basically what I'm trying to say is, they want to make it free to use, but not free to design or write.

      for fuck's sake this is the same man who sees himself as a damn saint.

    4. Re:This is retarded by Tony+Hoyle · · Score: 1

      No it won't.

      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. It used to be that you comply with the license then you're OK. Now if you comply with the license and the FSF take a dislike to your distribution - or worse, you - you're stuffed.

      So you get either one of two outcomes:

      1. Migration to BSD (OpenSolaris is GPL so not an option due to the same risk).
      2. Windows.

      It's not hard to guess where most will go.

    5. Re:This is retarded by mennucc1 · · Score: 1

      "Free software" is supposed to be "Free" (free as in beer, as in speech, as in "gratis" and as in "libre").
      If FSF finds a loophole in GPL (whichever version) and then uses GPL software to punish Novell for its dealing with Microsoft, then I do not see GPL to be As Free As It Should.

      If FSF starts using heavy tactics to push its political agenda, actively damaging people who sign deals that in a future may possibly be used in some evil ways... then this sounds too political to me.

      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
      It is not just business. I use Free Software because I like it being free; and I write and improve it because I want it to be helpful to others as well. If my Free Software can be used by a third party (in this case FSF) to punish a fourth party on (mostly) political grounds... well this is disheartening to say the least. Even if they find a legally valid way to do it, they are at the same time negating the very essence of Free Software.
      I want Free Software to smell free.

      The upstream article reports

      "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," Eben Moglen, the Foundation's general counsel, said on Friday.
      hey, FSF, this is a huge community... try, once in a while, to acknowledge this basic fact: not everybody shares your radical views.
      I in general appreciate the actions of FSF in most cases; but if FSF goes further this way, then I do not identify with Eben's community of people.

      To conclude let me comment on what

      Stallman once said: "We are not here to give users what they want, we are here to spread freedom".
      You teach freedom by practicing it, not by punishing others. "Freedom" is not something that can be coerced.
    6. 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. Re:This is retarded by sqlrob · · Score: 1

      Free as in beer? Have you read the FSF's page on the GPL?

      When we speak of free software, we are referring to freedom, not price.

    8. Re:This is retarded by zotz · · Score: 1

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

      Why? What businesses wan't to have their freedoms removed from them? What businesses, other than software businesses, want the freedom to remove freedoms from software they distribute?

      Please explain how this will bother, say, General Motors. Or any random business not trying to make a profit from selling software.

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    9. Re:This is retarded by Anonymous Coward · · Score: 0

      After this I doubt GM will ever put their custom Linux on their embedded devices in cars; they wouldn't risk being forced to remove them only because for other reasons they signed an agreement with Microsoft..

    10. Re:This is retarded by UtucXul · · Score: 1

      Migration to BSD (OpenSolaris is GPL so not an option due to the same risk).
      I think your making a mistake blaming the GPL there. It seems (to me) that the problem you are worried about is that the GNU parts are controlled by the Free Software Fondation, an organization with philosophical goals (which I agree with for the most part, but you certainly do not have to). Since even when under the GPL, Solaris is in no way controlled by the Free Software Fondation, I don't think it makes sense to lump Solaris in there.

      Now if you object to any organization controlling your OS, then I agree Solaris is a bad choice. But Windows is even worse. If that is your opinion, then BSDs would seem to be the only viable choice.
    11. Re:This is retarded by zotz · · Score: 1

      "After this I doubt GM will ever put their custom Linux on their embedded devices in cars;"

      Perhaps, perhaps not, but if they are using it on their servers or to design their cars, are they likely to stop using it for those purposes becuase of this?

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    12. Re:This is retarded by init100 · · Score: 1

      I use Free Software because I like it being free; and I write and improve it because I want it to be helpful to others as well. If my Free Software can be used by a third party (in this case FSF) to punish a fourth party on (mostly) political grounds... well this is disheartening to say the least. Even if they find a legally valid way to do it, they are at the same time negating the very essence of Free Software.

      If you retain copyright to your code, the FSF cannot do anything about it. The FSF is simply considering to use the software that they own copyrights for to try to disrupt Novell for signing the agreement with Microsoft. If you prefer the GPLv2, it is not going away, and you can continue to use it even after the GPLv3 is finalized.

      To sum it up: The FSF is free to change the license on future releases of software that they own copyrights for. They can not use your code to punish Novell.

    13. Re:This is retarded by DaveV1.0 · · Score: 1

      Ah, yes. Freedom. I don't think that word means what the FSF and RMS thinks it means.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  12. 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
    2. Re:Of course this is bad for Linux by Reality+Master+101 · · Score: 0, Offtopic

      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.

      Oh, please. The reason we're not using Java desktops is because (in the early days, at least) Java applications SUCKED. The GUI was ugly, they took forever to start-up, they were incredibly slow once they did run, and used an enormous amount of memory. I'll defer whether it's still the case, but Microsoft had nothing to do with Java's lack of adoption. If people wanted to write standard apps for Windows, they were certainly able to.

      --
      Sometimes it's best to just let stupid people be stupid.
    3. Re:Of course this is bad for Linux by haakondahl · · Score: 1

      they will buy and dismantle Novell. There, fix that for you.

      Ooh. Good Catch!

      --
      Don't trust anyone under thirty.
    4. Re:Of course this is bad for Linux by Anonymous Coward · · Score: 0

      That and the fact that Java is a horrible abomination.

  13. and in other news... by SpaceballsTheUserNam · · Score: 0

    Microsoft has found the FSF to be in violation of over 9,000 patents.

    --
    \.
  14. SCO? by pionzypher · · Score: 1

    But.. Novel is going for SCOs throat at the moment. Isn't there a phrase that goes something like 'If my friend's enemy becomes his friend, and my friend is killing my enemy, I should avoid killing my friend until he's finished killing'?

    Something like that....

      Gah. Stupid principles. ;)

    --
    I'll believe in corporations having personhood when Texas executes one... - advocate_one
    1. Re:SCO? by Anonymous Coward · · Score: 0

      the enemy of my enemy is my friend

      i think.

    2. Re:SCO? by 6031769 · · Score: 1

      This would be a concern were it not for the IBM suit. If Novell somehow doesn't finish SCO off, then IBM will certainly do the job.

      --
      Burns: We're building a casino!
      McAllister: Arrr. Give me 5 minutes.
  15. 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.
    1. Re:Disproportionate by Anonymous Coward · · Score: 0
      Rome taught me patience and assiduous application to detail. Virtues which temper the boldness of great, general views.

      Rome. Hasn't taught you. Virtues which temper the lameness of sentence fragments.

  16. Novell gives money to projects by Anonymous Coward · · Score: 0

    From the millions of the deal with MS, Novell hires people to work on the kernel/gcc/x.org.

    That is certainly good. But the kernel/gcc are already projects that cannot be beaten. So they can take as much money as possible from Novell until they bankrupt.

  17. Rights by Anonymous Coward · · Score: 0

    >Is this a measured response, or an over-reaction to the Novell/Microsoft arrangement?

    It's simply exercising what rights they have to code under their copyright. MS/Novell would do exactly the same if it suited their purposes. Make no mistake, the war is truly about to being..

  18. 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 DarkOx · · Score: 1, Insightful

      That's right IBM has patent deals with Microsoft. Novell made a deal on behalf of other parties their customers supposedly. The did this without consultation of those customers. Which is even if legally possible is still from a view of actual justice highly questionable, especially when it puts other parties of unknow relationship to the Novell customers in grave danger.

      Suppose I am and ISV that produces SuperWonderfulMagicPony for Linux. I run SUSE in house for my operational systems. The deal is great Microsoft won'y be sueing me. Wait they start sueing everyone else useing linux. I make a Linux product, I want as much Linux out there as possible regardless of distro because it means a bigger market for my wares. Suddenly I am not so happy with Novell. As there customer if they'd bothered to ask me if I wanted to have them stike this deal with M$ I would have declined.

      IBM has made deal on behalf of IBM with M$. IBM worries about protecting or not protecting IBM's customers. Novell sold out and is letting M$ worry about their customers and possibly screw everyone else if they feel like it. Its not the same thing at all.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    2. 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.

    3. Re:Um, That's a Good Idea... by Anonymous Coward · · Score: 0

      If that were true, then MS would lose 90% of their customers every time the arrange a BSA audit. I think you will find being thrown in jail and having your company bankrupted is more intimidating than merely "having your license revoked". This is what can happen to your IT manager because some trainees decided to install an extra sever (s)he didn't know about.

      More or less these stories being spread about the "big bad FSF" are just FUD designed to make it more difficult for them to enforce their legal agreements.

    4. 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.
    5. Re:Um, That's a Good Idea... by Anonymous Coward · · Score: 0

      "IBM sells Windows Servers." Many years has passed since I last saw an IBM server bundled with MS Windows... bundled by IBM that is. I have seen xSeries sold with MS SBS but that has always been a reseller bundle.

    6. Re:Um, That's a Good Idea... by Anonymous Coward · · Score: 0

      Nice spin. Novell's deal with Microsoft appears to violate the GPL license. I think most people (especially GPL contributors) would be very happy to know the Free Software Foundation is going to bat for them to protect the terms of the GPL license. Microsoft knows exactly what it is doing with this deal. I am very pleased the FSF is going to protect the GPL whenever it can against businesses that seek to break it.

      You are a troll.

    7. Re:Um, That's a Good Idea... by DarkOx · · Score: 1

      Well I was stil laughing at a post form the other day suggestion that if Steve Jobs release iPony MS would follow on that too.

      The obvious answer you your question though is that I would tll them to go home and convince their parents to buy our

      Gold level Teir One Four hour Anual Renewal support Contract for SuperWonderfulMagicPony and that they should strongly consider spending their allowence on our Monthy Prefered User Program where:

      Get this you can request and vote on the features you'd like to see in the next version of SuperWonderfulMagicPony.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    8. Re:Um, That's a Good Idea... by rohan972 · · Score: 1

      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?

      Novell's business model involved distributing licensed code. Normally, this would involve paying license fees to the supplier. The FSF has opted to require GPL compliance rather than license fee payments for the use of their code. It's that simple. Why do none of the people who think FSF is radical or fanatical for requiring GPL compliance think that proprietry software companies are fanatical for requiring payment? Why would an NDA, for example, be considered by the business community ok to enforce, but the GPL not? What makes anyone think they can base a business on a product licensed from someone else, violate the suppliers express intention in the licence, and still have a product to sell?

      If you think of the FSF as suppliers of licensed code, rather than a fringe group of radicals, it'll make a lot more sense to you. They chose the license conditions because of their (RMS's) philosophy, but requiring compliance is standard industry practice.

    9. Re:Um, That's a Good Idea... by jrumney · · Score: 1

      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

      It's widely known that Microsoft will basically send in the BSA to audit you at your own expense if they don't like how you do business. It doesn't seem to stop most businesses from taking Windows seriously.

    10. Re:Um, That's a Good Idea... by huckamania · · Score: 1

      Well, gnu/linux is not a given. Someone with enough resources could replace gnu with something better. I'm not sure who would have the resources to do this, but that in and of itself could be dangerous. But then maybe that would make Linus rethink his stand. I think the guy is a genius and I'm not really much of a linux zealot.

    11. Re:Um, That's a Good Idea... by acidrain · · Score: 1

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

      This is why IBM doesn't provide a legally defended and supported distribution. If they did it would kill Linux because companies would be afraid to use anything but the vetted IBM version, and Linus wouldn't be the "mainline" any more. Of course the fact that IBM doesn't need to handle all the lawsuits is a nice touch also.

      Regardless, IBM's arms length support of Linux keeps it clear of the patent related issues that we are talking about here.

      --
      -- http://thegirlorthecar.com funny dating game for guys
  19. Look at other scenarios by Anonymous Coward · · Score: 0

    Breach of the ToS: despite you being able to use it in the past, you no longer can use it.

    Breach of EULA: despite you still owning the product, you no longer have license to use it.

    GPL: despite you still having the code, you no longer have license to use it.

    Doesn't seem to be a problem with the first two, so why the third?

    1. Re:Look at other scenarios by zotz · · Score: 1

      Breach of the ToS: despite you being able to use it in the past, you no longer can use it.

      Breach of EULA: despite you still owning the product, you no longer have license to use it.

      GPL: despite you still having the code, you no longer have license to use it.

      Doesn't seem to be a problem with the first two, so why the third? Because the third isn't true. You breach the GPL, you still have the code, you can still use it. You can no longer use the license to do things which copyright law says you can't do. You do not lose the right to run the software on your machine. You lose the rights that the license gave you.

      all the best

      drew
      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    2. Re:Look at other scenarios by that+this+is+not+und · · Score: 1

      You breach the GPL, you still have the code, you can still use it.

      You do? You can? You can still 'make copies' into memory of the code from where it resides on your fixed disk , and run said copies? You can still 'make copies' to back up your system?

      I'm not so sure of these things.

    3. Re:Look at other scenarios by zotz · · Score: 1

      "You do? You can? You can still 'make copies' into memory of the code from where it resides on your fixed disk , and run said copies?"

      From the GPL itself:

      "Activities other than copying, distribution and modification are not
      covered by this License; they are outside its scope. The act of
      running the Program is not restricted,"

      The license itself seem to say so.

      Do you see some reason to think you can't?

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    4. Re:Look at other scenarios by KDR_11k · · Score: 1

      Only non-volatile copies count as real copies.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
  20. Stallman is off his gourd by dgun · · Score: 0

    Linux has a great potential to balance out the power in the OS market (eventually), but not if this lunatic attacks every big enterprise that attempts to promote it and scares away big name investors. Novell has the right to enter into any arrangement it likes with the devil (Microsoft), as long as it does not violate the GPL.

    --
    FAQs are evil.
  21. so quipamenducacious... by Anonymous Coward · · Score: 0

    how can the "free" community be so narrow-minded?
    Is this free? Is this fair?
    this is unnecessarily opening sores! ... and that too when microsoft has finally seen the light.
    why make a mountain out of a M$hill? :-)

  22. They call this "free" software? by lseltzer · · Score: 0, Troll

    Watta buncha hypocrites.

    1. Re:They call this "free" software? by Anonymous Coward · · Score: 0

      In Nazi America, the Zentral büro von Linux Anwendung controls you!

  23. Not exactly news... by Lavene · · Score: 1

    It's been clear for a long time that FSF intend to tailor GPLv3 to harm Novell as much as possible. Both Mogeln and RMS has said that numerous times and there is very little doubt that they will make sure Novell gets stuck with GPLv2 apps. TFA is just something cooked up by a journalist having to fill his quota or something.

    1. Re:Not exactly news... by that+this+is+not+und · · Score: 1

      I doubt if the FSF will be able to isolate and encircle Novell. This kind of gaming on their part will also upset and affect other interests. If the FSF wants to fork Linux and every other GPL'd software project, they're on the right track lately.

      Any project at all, no matter what it's license says about 'and newer version' or not, can be forked to continue on with GPL v.2. The portions of it with an 'and newer version' clause can always then be dragged back into a GPL v.3 project, but... to paraphrase the old world map: there be forks here!

    2. Re:Not exactly news... by Lavene · · Score: 1

      I doubt if the FSF will be able to isolate and encircle Novell. This kind of gaming on their part will also upset and affect other interests. If the FSF wants to fork Linux and every other GPL'd software project, they're on the right track lately. They might not be able to do it but they sure as he** are going to try.

      Personally I think the entire FSF has gone completely of their rockers. I used to support RMS and FSF but I find their methods increasingly distasteful. I don't like the MS/ Novell deal and I don't like Windows but the fanaticism the FSF show with crusades like this and not to mention their BadVista campaign makes sick.

      They are really not about freedom anymore, they are about making everyone do things their way.

    3. Re:Not exactly news... by Anonymous Coward · · Score: 0

      FSF is too late (or too early)... right now FSF's strategy will harm FOSS most, it will quite propably fork FOSS in a business oriented part using GPL2 and a idealistic part using GPL3. This will be very harmful to the whole FOSS community.

  24. What a stupid idea by Registered+Coward+v2 · · Score: 1

    Novel is still free to distribute gplV2 software; the article states that they haven't decided what to do and the ban would only apply to V3 licensed versions:

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

    Which means Novell would be free to fork v2 and keep anything they do under v2 as well as prevent it from being incorporated in any v3 licensed version; since they could limit it to v2 and earlier licenses.

    In addition, the ban would only apply to FSF's copyrighted code; since they can't release other's v2 code only under v3 without violating v2's license provision.

    While MS probably doesn't want to take on the FSF for PR reasons, they could bury them with lawsuits if they wanted to - so even if the FSF wins in the end they could very well be litigated out of existence. More likely; MS could help Novell fork the code significantly and develop programs (such as office for Linux) that would only run on the forked code; since the changes would be under a V2 they could preclude them from being incorporated in any v3 licensed versions, marginalizing v3.

    While I understand the FSF wants to avoid such a scenario, picking a fight with MS/Novell is probably not the way to do it.

    --
    I'm a consultant - I convert gibberish into cash-flow.
    1. Re:What a stupid idea by Tony+Hoyle · · Score: 1

      If Novel fork v2 it'll cause a massive split. Novell are big enough and have enough developers to make it stick.. so you'll end up with 2xgcc, 2xsed, 2xgrep, etc. etc.

      It's inevitable that forks will happen - a lot of people don't like the way gplv3 is headed - but a major player doing it is a big issue.

  25. Good Going. by Anonymous Coward · · Score: 0

    In a way this is a very bad reaction, a very immature knee-jerk reaction from the fsf. Chances are, Microsoft wants this kind of reaction and were expecting it. Basically the FSF is about to get trolled by microsoft. I guess they hired some GNAA goons to strategize against opensource.

    In all seriousness, This kind of reaction is what can and will kill opensource if this keeps up. I know this is to protect free software developers from getting taken advantage of, but now it seems more or less a bid for power. If the FSF can do this, what's stopping them from pulling a decease and desist on a programmer who makes a project that isnt 100% kosher to what the FSF deems acceptable?

    This is why people like Linus Torvalds see the gplv3 as a threat to free software. It's going to give the FSF more say and control over anyone who accepts the license.

    I dont know about the bulk of OSS advocates, but I want all this political crap out of free software because it's going to destroy it.

  26. Answer... by Anonymous Coward · · Score: 0

    Is this a measured response, or an over-reaction to the Novell/Microsoft arrangement?

    No, it's a wannabe-journalist asking suggestive questions.

  27. Re:WARNING PLEASE DONT READ by Anonymous Coward · · Score: 1, Funny

    umm.. does copy-paste count?

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

    1. Re:lets hope not by bigtomrodney · · Score: 0

      They are copyright holders of the technology in question, and can simply refuse to let Novell distribute their stuff any more. But let's remember, just because something is licensed under the GPL does not mean it belongs to the FSF. It will be up to the individual authors what licence changes happen.
      --
      I never get used to these constant resurrections
    2. Re:lets hope not by Kjella · · Score: 1

      A license holder has the right to revoke anothers right to use that license.

      Do you work for SCO or something? There are plenty licenses which are permanent and irrevokable, and as long as I comply with the GPL there's nothing you can do to revoke my license. They can relicense new versions, but they couldn't exclude one specific party without violating every defintion of "open source", RMS's "free/libre software", Debian's DFSG and every other authority on the subject.

      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.

      If it was that simple, all we'd ever need was the BSD license. Turns out there's plenty people who don't like to contribute stuff only to have it resold* back to them as e.g. Mac OSX, which prefer the GPL. The same people would probably oppose contributing stuff, only to have it resold* back to them by Novell as "same code, now with Microsoft patent indemnification license", who'd prefer the GPL to be "fixed" if this is a loophole.

      * I know you can sell GPL'd code too, but in the sense of "putting it in a proprietary/special system you can't duplicate and selling it back to you".

      --
      Live today, because you never know what tomorrow brings
    3. Re:lets hope not by rucs_hack · · Score: 1

      "Do you work for SCO or something?"

      What a peculier thing to open with... No, I am an academic and open source developer.

      "There are plenty licenses which are permanent and irrevokable"

      There are many classes of licence, why would I be meaning an irrovocable one when I'm talking about revoking it? Besides which, licences that are irrovocable have usually been paid for, or are fixed term. Those under discussion here have not been classified as such.

      "As long as I comply with the GPL there's nothing you can do to revoke my license".

      And if you were complying, what would be the point? At issue here is a politically inspired beleif that Novell are not in fact in compliance. If by certain theory they are not complient, and this theory is ruled valid, then Novell lose, and so do the rest of us.

      I think they are in complience, but I'm not a zealot.

  29. to (almost) quote... by joe+155 · · Score: 0, Troll

    ...But software which Linux uses and redistributes must be free to all (be they people or companies), for any purpose they wish to use it, including modification, use, peeing on, or even integration into baby mulching machines or atomic bombs to be dropped on Australia.

    What are the FSF doing? it must be free for all, doing anything which limits the complete freedom of anyone to use the software harms the community. It is one thing to take some steps to stop them from screwing us over (which there isn't really that much proof of them doing anyway), but this goes against the fundamental beliefs of a large section of the FREE software movement.

    --
    *''I can't believe it's not a hyperlink.''
  30. Bad move by gilesjuk · · Score: 1

    While the deal between Microsoft and Novell isn't good, Novell has plenty of patents and Unix rights which could make the life of the Linux community rather hard.

    They could become another SCO.

    1. Re:Bad move by Anonymous Coward · · Score: 0

      Novell has made an explicit pledge to use those patents to defend the community. Their room for action may be quite strongly limited.

    2. Re:Bad move by DiamondGeezer · · Score: 0, Flamebait

      If the "community" or just the FSF decide to take away the ball, then Novell could forget its pledge as well. I don't like Novell, but this move by the FSF could backfire very badly with Linux in the Enterprise just as its beginning to reach critical mass. Linux needs large software companies to contribute code, patents and intellectual property to the Linux cause, and if Novell is attacked, then other software companies may reconsider their strategies.

      --
      Tubby or not tubby. Fat is the question
    3. Re:Bad move by Anonymous Coward · · Score: 0

      > patents and intellectual property

      Software patents are not valid in my part of the world and "intellectual property" is a meaningless term. Computer code is protected by copyright under the Berne Convention, it appears the problems you're referring to only exist by virtue of vague doublespeak.

    4. Re:Bad move by Anonymous Coward · · Score: 0

      Software patents are not valid in my part of the world and "intellectual property" is a meaningless term.
      So go back to the single celled slimy pond life you escaped from, and only come back when you've evolved and are ready to take part in the real world.

    5. Re:Bad move by init100 · · Score: 1

      then Novell could forget its pledge as well.

      There could be problems for them to forget such a pledge. There is a legal term called promissory estoppel, and that may apply if they choose to "forget" the patent pledge. But IANAL...

  31. time for GPL to proof it's straingth's by esiminch · · Score: 1

    if there is all proper with the GPL and the community behind it, this could be the best proof, then the deal should not harm anyone other that brakes the license (doesn't mean sit back and wait)
    i hope for all OSS users and contributors this will only proof GPL is able to protect the exploit of OSS even if such big players are involved

    there might be all right with the deal, but I'd rather check twice before I believe in that. MS tactics are rather too good known

    1. Re:time for GPL to proof it's straingth's by Deadguy2322 · · Score: 0

      Hey, where's the link to goatse from this post? Trolls just aren't putting the effort in anymore...

      --
      Check out my foes list to see who is so retarded that they can't use the signature line!!!
  32. Linux is Linux's best competition by Tomis · · Score: 1

    And Linux-heads wonder why Linux will never be a main-stream OS. They're quite silly!

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

  34. They haven't thought this through by QuickFox · · Score: 1

    They should extend the ban. Novell isn't the only company that has dealings with Microsoft, lots of companies do. To complicate the matter further, there are also lots of individuals who have dealings with Microsoft or support Microsoft by buying their products.

    Every company and every person should be banned from using Linux.

    --
    Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    1. Re:They haven't thought this through by that+this+is+not+und · · Score: 1

      There are dozens, perhaps even hundreds and thousands of people who have never 'had dealings with Microsoft' who could carry on with Linux. All the former Sun users, some Mac and Amiga-types too.

    2. Re:They haven't thought this through by MikeBabcock · · Score: 1

      I should stop using Linux too. I've been using it since 1994, but here I am, I own a copy of Windows 3.1, a copy of Excel 3 and oh no, Unixware 7 (I even installed it once).

      --
      - Michael T. Babcock (Yes, I blog)
  35. Yep, this could really screw Linux adoption by Sycraft-fu · · Score: 1

    Why? Because it's just the thing PHBs need to justify fears about it. One of the points that people like to sell Linux on is that because of it's license you can't be screwed over like you potentially could with a commercial OS. They can't just take it away from you. Well, regardless of the actual details, any ban against Novell would be interpreted as precisely that. The Evil Linux Overloards(tm) screwing over a company.

    A big part of selling Linux's freedom is letting people do things that you may not like, or that aren't in the best interests of Linux overall. People need to see that it really is freedom, the only restriction is that if you distribute binaries, source has to come with. Other than that, go wild. If you start saying "You are free to do whatever you want with Linux so long as you support our ideals, but if you play nice with MS or other companies we don't like we'll take it away form you," well hell, you end up looking more restrictive than MS.

    1. Re:Yep, this could really screw Linux adoption by Rich0 · · Score: 1

      If you start saying "You are free to do whatever you want with Linux so long as you support our ideals, but if you play nice with MS or other companies we don't like we'll take it away form you," well hell, you end up looking more restrictive than MS.

      Uh, the GPL pretty much states that plain and clear. The intent of the GPL is for users to be able to:

      1. Redistribute their software freely.
      2. Obtain the source to their software.

      If you distribute GPL software and you want to interfere with either of these goals you're going to be sued by the FSF if they hold copyright on your software.

      If Novell/MS grant a free and redistributable license to any patented technologies in the GPL software they distribute then I'm sure the FSF will be perfectly happy to let them go on selling linux. What they object to is that user's and developer's rights to use, modify, and redistribute their software is being put in jeopardy by a software-patent loophole. The GPL v3 is being designed to explicitly close this loophole.

      In any case, if you don't like the FSF's goals, then don't use their software. It is just like ANY other piece of software out there - if you want to go distributing it all over the earth you need a license from the copyright holder.

      And last time I checked MS doesn't allow you to redistribute their software AT ALL. So, this is hardly being more restrictive than MS. The FSF isn't trying to stop Novell from USING linux - just redistributing it. If all of Novell's customers downloaded the GNU toolchain from gnu.org there would be no issues. If MS were taking issue with some company pressing Vista install CDs without authorization I doubt it would make this big of a splash...

    2. Re:Yep, this could really screw Linux adoption by Anonymous Coward · · Score: 0

      >> And last time I checked MS doesn't allow you to redistribute their software AT ALL.

      False.
      There are a number of mobile phones, gadgets, palmtops, whatever using Microsoft OS and apps based on MS OS. There are a number of these devices with Linux too.

      If I were Asus/Cisco/USRobotics/DLink/Whatever I will be very worried of being forced to remove Linux from my embedded devices because of some agreement with their competition.

      FSF is going every day towards being Freaking Stupid Foundation. And OSS loses credibility every day because of these childish issues.

    3. Re:Yep, this could really screw Linux adoption by Rich0 · · Score: 1

      If I were Asus/Cisco/USRobotics/DLink/Whatever I will be very worried of being forced to remove Linux from my embedded devices because of some agreement with their competition.

      They have nothing to worry about as long as they distribute their source with their binaries, as long as they allow their users to make modifications to their products, and as long as they don't make side deals that would make it harder for their users to redistribute changes to their products.

      FSF is going every day towards being Freaking Stupid Foundation. And OSS loses credibility every day because of these childish issues.

      With who? They certainly don't with their constituency - which are people who want to promote copyleft/GPL/Free Software(TM).

      The only people who this worries are companies that want to obtain the benefits of the community's work without having to give back. Honestly, I doubt many in the community care about that. I doubt RMS and Co lose sleep when some company decides to abandon linux/GNU/whatever - they're not looking to win a popularity contest. As long as free software works in the community they're happy.

  36. Very funny by itz2000 · · Score: 1

    That's about it : #!/bin/bash for i in $(cat Distribution_List); do if [ $i -eq "Novell" ]; then echo "Invalid Distribution"; exit 1; else continue; fi I treat Novell like M$ at the moment... may god save their soul :] lol.

    1. Re:Very funny by Anonymous Coward · · Score: 0

      for isn't a good loop to use here. There are distributions with spaces in their names, like Red Hat, and this script will separate names at both spaces and newlines. Use #!/bin/bash while read i; do if [ "${i}" -eq "Novell" ]; then echo "Invalid Distribution"; exit 1; else continue; fi; done < Distribution_List instead

  37. we shall fight on the beaches, we shall fight ... by Anonymous Coward · · Score: 0
    The MS - Novell deal is about that Novell has decided to suck Microsoft cocks. Novell has surrendered part of the Free Software integrity to Microsoft, in the name of the community. But Novell does not speak for the community. They have betrayed the community, sold out to the enemy. For that they need to suffer and need to pay the price.

    In the words of a great man:

    We shall go on to the end, we shall fight in France, we shall fight on the seas and oceans, we shall fight with growing confidence and growing strength in the air, we shall defend our Island, whatever the cost may be, we shall fight on the beaches, we shall fight on the landing grounds, we shall fight in the fields and in the streets, we shall fight in the hills; we shall never surrender ...
    -- Winston Churchill
  38. Now you know what FSF calls freedom ! by wtarreau · · Score: 0, Troll

    Now you know that freedom according to FSF is just a matter of dictatorship. They just want to enforce their view of the world on others. Think twice before following those mad activists too closely... :-/

    Willy

    1. Re:Now you know what FSF calls freedom ! by Anonymous Coward · · Score: 0

      Come on, you can troll better than that.

      How about:

      Now you know those Godless commies at the FSF just want to eat your children.

      Now you know that happiness according to the FSF is just them being able to burn down your house and rape your wife.

      Now you know that freedom according to the FSF is just a matter of establishing concentration camps for Windows users, and using components of the dead bodies in their evil C compilers.

      Seriously though, your perspective is dumb bordering on ludicrous. There is a difference between oppressing others, and forcing people not to oppress others. You can call the latter action "forcing" as much as you like, but in the end you're just playing with words to make something good sound bad.

    2. Re:Now you know what FSF calls freedom ! by Anonymous Coward · · Score: 0

      But all they are actually doing is dictating the terms under which their code can be redistributed. How is that different to any proprietary software company? They are not trying to apply their terms to code they do not own.

  39. I labeled this fud and i will tell you why... by Pecisk · · Score: 1

    Novell recently stroke a deal with , so I think this is total and utter FUD, spelled out by some Microsoft funded journalist, who also is in Reuters (which wouldn't surprise me at all).

    So, Microsoft sees that Novell gets it's deal (20 000 workstations and 5000 servers, come on, if it is not serious, then what is), goes in panic mode and starts to create FUD. FSF could be overreacting on all stuff what happens around Novell and Microsoft deal, but there is no WAY they could stop Novell to distribute GPL code so easily - they don't have SUCH power. Only with release of GPLv3, it COULD be possible, and then only with very big shred of doubt.

    So, it is FUD. It always have been. But for now, Microsoft uses it against us. So those who opposed this deal - take this into your little minds - Microsoft plays evil games and tries to destroy us by seperate us. Yes, Novell did wrong thing, but it doesn't matter when bigger things are at stake. What I would like to see is keep our tone down about Novell, and keep pushing our agendas about software patents and Microsoft monopoly abuse. THESE are things we should really talk about.

    p.s. this post of mine is only mine speculation and opinion.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    1. Re:I labeled this fud and i will tell you why... by Pecisk · · Score: 1

      Duh, forgot myself to add company: Peugeot Citroën.
      News article itself here: http://www.infoworld.com/article/07/01/30/HNpeugeo tlinux_1.html.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
  40. End is Inevitable? by Anonymous Coward · · Score: 0

    There will soon be a time when the enemies of Microsoft have gained enough market share to force the empire to adapt to their concerns. At what point will they be satisfied with those changes and consider the empire no longer a concern? When will there be compromise and a handshake between MS and the community? It sounds unthinkable, but we've just witnessed the rough beginning. Vista mimics MacOSX UI and deals with Novell.. Can this ever be settled if Windows is not open source? Can anyone imagine the next version of Windows being built upon a linux distribution? What prevents that from happening? Could that bridge the gap? Will that be the inevitable end of Windows?

    1. Re:End is Inevitable? by BootNinja · · Score: 1

      Can anyone imagine the next version of Windows being built upon a linux distribution?
      Somehow, I can't see MS ever releasing a product under GPL of any version, and thus it is highly unlikely that any version of Windows will EVER be based on Linux.
      However, they could easily do as Apple did and fork one of the BSD's. This is highly unlikely because then MS would essentially be admitting that their software is unrecoverable crap. They are too prideful for this to ever happen.

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

    1. Re:Article is FUD. by Vlad_the_Inhaler · · Score: 1

      Phew

      This would have been seriously bad news for Linux if it had been attempted. The Linux Kernel / GNU Software are not currently under GPL V3. Stopping a major Linux distribution for violating a license which was not even in force at the time of the violation would have been insane. Hell, even Caldera were never cut off *that* way.

      Linus would certainly have understood the ramifications, I can't imagine the GNU foundation being stupid enough to flex muscles that way either.

      This is one of those ideas that sounds semi reasonable until you actually think about it.

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
  42. FSF to ban distributing Linux? by Anonymous Coward · · Score: 0

    As far as I know, the FSF doesn't have any Linux code. Therefore the FSF doesn't have any right to ban Novell from distributing Linux. Now if Finkle was referring to the FSF's right to the GNU part of the GNU/Linux distribution, then this would be a more acceptable statement.

    I believe this misunderstanding is further vindication of Stallman's issue about the GNU/Linux name. Linux is not an operating system and GNU does not yet have a fully functional kernel.

    Also, when considering the term 'operating system', remember that 'operating system software' is not necessarily the same as 'user software'. Both these terms are subsets under the set of 'computer system software'. I consider some parts of X to fall under the term 'operating system software'. Not all of it does so I won't call it operating system software. Also, not all of GNU software falls under the term 'operating system software'. I consider tools like mv, and dd and init to be 'user software' and not part of the operating system.

  43. Linux "belongs" to Linus Torvalds, not to FSF by El+Nigromante · · Score: 1

    Actually, "Linux" just refers to the GNU/Linux system's kernel.

    As far as I know, Linux is a registered trademark by Linus Torvalds. And I suppose he is still the owner of much of the kernel's code.

    The fact that a piece of software is distributed under a certain license (GPL in this case), does not mean that its author cannot change the license for future versions of that software. In addition to this, changing the license terms would affect to software licensed under that new license version, not to software already distributed (at least it is this way in my country).

    I say all this because I've read some time ago (and I think it was also related to the new GPL version) Torvalds is not much in favour of limiting the distribution of Linux.

    Anyway, I think the essential nature of open software is not being limited (while users respect some reasonable terms).

    1. Re:Linux "belongs" to Linus Torvalds, not to FSF by MichaelSmith · · Score: 1

      Yes but the GNU toolchain belongs to the FSF. You could replace shell utils, etc with a set from (say) netbsd but that doesn't give you a compiler. In fact, I am not aware of anything free which can replace GCC.

    2. Re:Linux "belongs" to Linus Torvalds, not to FSF by imsabbel · · Score: 1

      Binary distros.... Why should the end-user compile anything?

      --
      HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
    3. Re:Linux "belongs" to Linus Torvalds, not to FSF by petrus4 · · Score: 1

      In fact, I am not aware of anything free which can replace GCC.

      There's TenDRA. Lack of alternatives however isn't so much an issue. The kernel is highly dependent on the particular implementation/dialect of C which GCC supports...there is apparently quite a lot of non-standard stuff which GCC supports which the kernel uses...hence making the two rather inextricably tied together.

      Linus smoked from the GNU/crack pipe a long time ago...the kernel isn't getting extricated from the GNU toolchain now, or at least not without massive work...and that's exactly the way Stallman wants it. The various other GNU tools often contain non-standard extensions which other versions of the same programs don't have...and Stallman has introduced those for exactly the same reason as Microsoft uses such tactics...to foster dependency on his unique/non-standard versions.

      If the FSF seriously goes rogue, the kernel will very likely go down with it.

  44. 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 jaymzru · · Score: 0

      I imagine most companies that employ OS software at the moment understand the community better than that. There's no reason to stop using server software that has been working for 5/10+ years because some desktop software and 1 distro are suddenly having troubles.

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

    3. Re:Handing MS a huge victory on a platter by QuickFox · · Score: 1

      What you're saying is more pessimistic than you seem to realize. Sure, old-timers won't suddenly quit. But we need a steady influx of new users, else the result is attrition.

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

      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.

      Depends all on how you look at it

      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.

      On the flip side of that - most companies protect what is theirs, I would drastically loose faith in the OSS world if the community didn't protect their own property and let anyone do anything they wanted - and for their own gain. Aren't they just playing the same as ALL OTHER companies/organizations?

    5. Re:Handing MS a huge victory on a platter by QuickFox · · Score: 1

      Amazing!

      Unfortunately I don't think cases like this one are any help in lessening the very negative impact of the actions of FSF. Regardless whether this effect is fair or unfair, banning Novell can still be disastrous for the public image of open source as reliable software providers.

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

      Depends all on how you look at it Indeed. And that in turn depends on who is looking. I'm not worried about how friendly-inclined members of the open-source community view this, I'm worried about how company decision-makers and media view it.

      Aren't they just playing the same as ALL OTHER companies/organizations? Most companies act to protect the good name of the company. I'm arguing that these actions of the FSF will (unwittingly of course) destroy the good name of Open Source.

      I get the impression that you're defending the moral right of the FSF to take action. But I don't dispute that right. What I'm worried about is something else, it's the consequences for the reputation and acceptance of Open Source software.
      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    7. Re:Handing MS a huge victory on a platter by Courageous · · Score: 1


      Companies sue each other all the time. It's pretty much just business as usual. However if the FSF engages in litigation or license maneuvers to protect our community's rights, we're to believe that somehow that this will give us a negative reputation. SNORT.

      You're wrong about companies not "throwing tantrum's" also. They certainly will do that if you mess around with their rights. What exactly do you think the big army of corporate consuls are for? There's a reason that large companies keep attorneys around permanently on staff.

      Finally your alarmist "companies just won't dare use open-source software" observation. Come now, cut it out. Like it or not, there's plenty of smart CTO's in the world (hint, hint: they don't get there by being DUMB), and they can see as plain as day the nature of Microsoft's maneuvering in this deal.

      C//

    8. Re:Handing MS a huge victory on a platter by Anonymous Coward · · Score: 0

      Novell appears to be violating the GPL with its limited patent indemnification deal with Microsoft. Since you of course consider it appropriate to enforce the license under which Microsoft distributes software, why do you think it is not appropriate for the FSF to enforce the license under which Novell seeks to distribute other people's software? Why do you think the GPL should not apply to Novell? Because they made a deal with Microsoft?

    9. Re:Handing MS a huge victory on a platter by Anonymous Coward · · Score: 0

      FSF can no more "ban" Novell than I can ban you from Slashdot. But if you break the terms of the licensing agreement you have with Slashdot to post here (provided there is such an agreement), then you can expect Slashdot may, at its discretion, "ban" you. Similarly, if Novell breaks the terms of the licensing agreement known as the GPL, Novell can expect, at the discretion of the countless authors whose contributions are being violated, to be "banned" from distributing the code. Novell would have only itself to blame for breaking the terms of the GPL. It is not like those terms are not posted in plain language in public view. Novell cannot even redistribute any GPL code it receives without including easy access to the actual terms of the GPL license with the distribution. I don't see why you think Novell's violation would be the FSF's, or anyone else's, fault.

    10. Re:Handing MS a huge victory on a platter by Anonymous Coward · · Score: 0

      you make some very good points with your original post and the first replier provided an excellent counter-point, but also ponder this aspect for a moment:

      what if the FSF did nothing to ensure that the GPL was being followed and allowed Novell to "walk all over the license"("it's just a goddamned piece of paper", after all) by going forward with this agreement with Microsoft? it could very well end up that businesses would perceive the GPL as an unenforceable license and the FSF as an organization without a backbone willing to defend it's copyrights and licenses. this could very well be even more disastrous not only to Linux, but other software like *BSD. businesses like to know that, somehow, their assets are protected and if the FSF doesn't protect GPL/Open software, they won't touch it at all.

    11. Re:Handing MS a huge victory on a platter by sacrilicious · · Score: 1
      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.

      Here's another way to look at it: consider how enormous an opportunity Novell is handing to anyone who wants to step in and take Novell's customers. An existing distro could do it, or -- even more poignantly -- someone could run with the code from OpenSuse, or with the code from Novell itelf... "look, we have the very code you're running now, and WE legally pledge NOT to ever engage in the bullshit that Novell jumped into."

      --
      - First they ignore you, then they laugh at you, then ???, then profit.
    12. Re:Handing MS a huge victory on a platter by NoOneInParticular · · Score: 1
      Okay, so if commercial company X tries to obstruct its customer Y for a particular move Q that company Y made it's a sign of reliability, while if an open source foundation does the same, it's unreliable? For instance, substitute X = Sun, Y = Microsoft, Q = breaking Java. In your terminology: Sun threw a tantrum when Microsoft tried to break Java, and where is Java now? The de-facto standard programming language for large business.

      Look, although the FSF is not a commercial entity, Novell tries to get around the restrictions the FSF opposes. Just like any other entity it retaliates. Novell has broken agreements, so they will suffer. The message is clear: Free Software, like proprietary software, is not gratis, but comes with obligations. If you don't meet those, you don't get delivered. Normal business.

    13. Re:Handing MS a huge victory on a platter by QuickFox · · Score: 1

      Novell appears to be violating the GPL with its limited patent indemnification deal with Microsoft. That's an important and decisive issue. I'm not convinced that Novell has violated the GPL. People argue that the patent indemnification deal means that Novell empowers Microsoft to strike down on other Open Source projects over patent infringement. But Novell can't empower Microsoft to do that. Nobody has licensed such powers to Novell. The GPL does not empower Novell to strike any kind of deals in the name of the rest of the Open Source community, and that means that whatever deals they strike with Microsoft, these deals do not create any obligations or other major consequences for the rest of the Open Source community.

      Novell can't have such power. And if I'm wrong and they do have such power, then that would mean that you and I and everybody has that power. In that case the GPL would be extremely brittle. I don't think that's the case.

      The worries that the patent indemnification deal will make people think that Open Source infringes on patents is in my opinion exaggerated and strange. The deal gives no grounds for such conclusions.
      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    14. Re:Handing MS a huge victory on a platter by QuickFox · · Score: 1

      The scenario that you describe is very interesting. If indeed Novell has violated the GPL (I don't think they have), then very likely some other company will step in, or new projects will arise, to take care of Novell's customers. That would be a beautiful demonstration of one of the greatest advantages of Open Source and open standards: If your supplier can't supply you any more, someone else will step in to take care of you, and you will still have a supplier.

      That would be great, if it worked out that way. I'm just not convinced that the world will see it that way, if Novell's problems are caused by attacks from the Open-Source community, attacks based on far-fetched, strange and unconvincing interpretations of the Novell-Microsoft deal.

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

      Okay, so if commercial company X tries to obstruct its customer Y for a particular move Q that company Y made it's a sign of reliability, while if an open source foundation does the same, it's unreliable? It makes no difference if it's commercial or open source, what matters is predictability. Commercial or not, if a supplier unpredictably denies customers upgrades because of unexpected and far-fetched political interpretations, this will hurt its public image.

      It looks like i should have made it clear from the beginning that I don't think Novell have violated the GPL. If indeed they have violated it (or its basic intentions), then certainly FSF should act to stop the abuse. Defending the GPL is very important. However, it seems to me that the FSF is making a far-fetched and strange interpretation of the Novell-Microsoft deal, and striking down out of principled spite, maybe because it's Microsoft.
      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    16. Re:Handing MS a huge victory on a platter by QuickFox · · Score: 1

      Of course defending the GPL is right. And important, indeed very important.

      To avoid repeating myself I'll point you to this other comment where I answer this.

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

      And consider the kind of reputation that this will give the open-source community.

      You mean as people who believe in fulfilling contractual obligations? Yeah, that's terrible.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    18. Re:Handing MS a huge victory on a platter by arem-aref · · Score: 0

      ...yeah, and the way to earn a good reputation and gain acceptance is to let microsft run a freight train up your ass while everyone sits by, and watches...

    19. Re:Handing MS a huge victory on a platter by fritsd · · Score: 1

      We do not know anything about the deal. The only factoids we know is that it is between Novell and Microsoft, that a lot of money was transferred, that it's only valid for 5 years, and that after the deal was closed, both parties seem to disagree as to what the deal means, judging from public comments of the CEO's, Hovsepian and Ballmer ("undisclosed balance sheet liability").
      IANAL but surely a contract is only binding if both parties mean the same thing?
      P.S. this is a blog entry about the U.B.S.L: http://blogs.zdnet.com/Burnette/?p=216

      --
      To be, or not to be: isn't that quite logical, Slashdot Beta?
    20. Re:Handing MS a huge victory on a platter by init100 · · Score: 1

      Some people seem to be ready to accept any transgression, arguing that trying to stop it would generate negative PR.

      Good analogy, by the way.

  45. very funny... by itz2000 · · Score: 0

    That's about it :

    #!/bin/bash
    for i in $(cat Distribution_List); do
    if [ $i -eq "Novell" ]; then
    echo "Invalid Distribution";
    exit 1;
    else
    continue;
    fi


    I treat Novell like M$ at the moment... may god save their soul :]

    lol.

    1. Re:very funny... by Anonymous Coward · · Score: 0

      Please find the nearest bash programming manual and read it.

  46. The FSF should get over themselves by 91degrees · · Score: 1

    Linux is pretty unconcerned about the whole patent thing. Novell can continue to use the kenrel. This is all most people care about.

    Virtually all the FSF owned stuff has an alternative. Either commercial, or under a different licence (or possibly simply forked from their current version, if this is a GPL2/3 difference). Novell can use that instead. They also have the resources to develop alternatives. Most of the rest of the distributers really aren't as fanatical about this issue as the FSF. They have other concerns. What if they see it as more convenient to use the same version as Novell? It would make the FSF pretty much redundant. And I suggest that the distributors prefer GPL2. It offers more freedom for them.

    They might be able to do this, but it would be something of an own goal.

  47. 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.
    3. Re:WRONG! by ElleyKitten · · Score: 1

      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.
      First of all, I'm pretty sure this deal doesn't cover code, just patents. Second of all, when you contribute code to a GPL project then you're just just "welcome" to release your code under the GPL, you have to. You can release your own applications or even mods to GPL applications under your own copyright, but you can't combine GPL code and nonGPL code together.

      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.
      Microsoft hasn't GPLed any code. Microsoft just made a deal with Novell that they won't sue Novell or its customers. They made no promises not to sue anyone else, and the GPL can't prevent them, since they never accepted that license agreement in the first place. That's why everyone's so scared about this deal.
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    4. Re:WRONG! by JPriest · · Score: 1
      Microsoft just made a deal with Novell that they won't sue Novell or its customers.


      Oh FFS, this is the 3rd time in 3 posts I have had to state that the agreement in question covers Novell customers and not Novell directly.

      --
      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.
    5. Re:WRONG! by mysticgoat · · Score: 1

      Whatever.

      There is no new information in parent post, and no new logic connecting known facts in a way that stands up to analysis. There is only a continued assertion that Suse is safe to develop on, because... uh...

      "...I have said it thrice:
      What i tell you three times is true".
      ——The Bellman's Rule

      Invoking the Bellan's Rule doesn't change my situation. I cannot recommend using Suse as the basis for a custom distro simply because a slashdotter with a somewhat lower usernumber than mine says it would be okay to do that. When it is time to do so, I can and probably will recommend that we not waste time evaluating whether Suse might be better than Redhat, etc, since there is this weird black cloud over Suse that Novell has brought on themselves. It's not like there aren't any good alternatives to Suse.

      In a way, that guy who used to jump around yelling "developers! developers! developers!..." was right. A distro whose management has allowed the well of developers to be poisoned by a competitor with known predatory business practices is a sick distro. It prolly needs to be forked. Funny that it was that very same monkey-dancing fool who visited these problems on Novell.

    6. Re:WRONG! by mysticgoat · · Score: 1

      Oh FFS, this is the 3rd time in 3 posts I have had to state that the agreement in question covers Novell customers and not Novell directly.

      Snark hunting, are we?

      Now how is it that this covers any customers of the customers of Novell? If I become a client of Novell, and my team produces a PIM based on Suse that is a real MS Outlook killer, how is it that my customers are immune from the threat of patent claims by Microsoft (even though I have that immunity)?

      Sir, whether you know it or not, you are blowing smoke.

      A modest suggestion: Perhaps you should stop just stating the same thing time after time and present either the supporting facts that you alone are seeing or the logical connections between the public facts that no one else but you seems to be able figure out.

    7. Re:WRONG! by JPriest · · Score: 1
      "If I become a client of Novell, and my team produces a PIM based on Suse that is a real MS Outlook killer, how is it that my customers are immune from the threat of patent claims by Microsoft (even though I have that immunity)?"

      You said I keep saying the same thing over and over yet you keep missing it??! Under the agreement you are welcome to deploy said Outlook Killer within your company, at the point you decide to distribute this platform to others downstream of you, you will need to decide on a license and ensure it does not infringe on others property in the exact same way you have always had to.

      The short version is that GPLv2 prohibits Novell from distributing licensed code they don't have rights to and MS would be stupid to allow any Novell customer immunity to redristribute in house solutions. What if you had access to the Office source code and rebranded and sold it with your logo? As long as you were a Novell/Suse customer this would be legal. Obviously that would be bad for MS.

      --
      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.
    8. Re:WRONG! by JPriest · · Score: 1
      From here


      "The covenant applies to end customers of Novell products."

      This does not say it applies to Novell itself, nor does it say it applies to these end users customers. The parent post you disputed said the following.

      "Oh FFS, this is the 3rd time in 3 posts I have had to state that the agreement in question covers Novell customers and not Novell directly."

      If I were keeping score I'd say that made it JPriest 1, mysticgoat 0.

      --
      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.
    9. Re:WRONG! by ElleyKitten · · Score: 1

      Microsoft just made a deal with Novell that they won't sue Novell or its customers.
      Oh FFS, this is the 3rd time in 3 posts I have had to state that the agreement in question covers Novell customers and not Novell directly.
      So Novell made a deal with Microsoft that means that Novell can be sued by Microsoft? Sure. Are you even reading what you're writing?

      The question is, does this deal cover the customers of the customers of SuSe (and the customers of the customers of their customers and on and on)? The GPL requires that when you distribute GPL software that those who receive it have to have the same rights to the software that you did, including being able to freely distribute it. This deal that Microsoft and Novell have made does not specify that anyone who ever receives code that Novell ever has worked on are immune from Microsoft's patent lawsuits, for they might as well have said they will never sue users of GPL code and they wouldn't do that. Microsoft may also use this agreement to say that Novell admits that that Linux has patented Microsoft technologies in it already (why would they need immunity if they weren't infringing?) and sue other users of Linux and open source software that are not Novell or its customers. That's what people are worried about happening from this deal. Maybe we're overreacting and none of that will happen, but Microsoft spent all that money to do something.
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    10. Re:WRONG! by JPriest · · Score: 1
      So Novell made a deal with Microsoft that means that Novell can be sued by Microsoft?


      There are multiple parts to the deal, if you don't know what they are why even bother trying to argue with me? In one part Microsoft agreed to give Novell $108 million to release each other from past actions (as in before they owned SuSE) source.

      The other portion of your post has already been covered.

      --
      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.
    11. Re:WRONG! by ElleyKitten · · Score: 1

      There are multiple parts to the deal, if you don't know what they are why even bother trying to argue with me? In one part Microsoft agreed to give Novell $108 million to release each other from past actions (as in before they owned SuSE) source.
      From your source: "The deal also involves patent-related payments. Microsoft will pay Novell a net amount of $108 million in an agreement under which both companies release each other from patent claims from past actions, Hovsepian. However, that will be offset by Novell payments of at least $40 million over the course of the deal to ensure Microsoft won't sue Suse customers for patent infringement." As I said, the deal protects both Novell and the customers of Novell. However, it doesn't say anything about anyone who makes a derivative of Suse, and their customers. Microsoft would still be able to sue them for patent infringement, and may even be able to use this deal as evidence in their case.
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    12. Re:WRONG! by JPriest · · Score: 1

      Novell existed long before they aquired Suse. The agreement not to sue Novell (and for Novell not to sue MS) for past actions is flat out NOT RELATED TO SUSE LINUX. The second part of the deal (the agreement not to sue Novell customers) is exactly as I stated. The actual code being shipped by Novel as SuSE Linux is not covered in either of these 2 scenarios. Do you get it now??

      --
      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.
    13. Re:WRONG! by ElleyKitten · · Score: 1

      Novell existed long before they aquired Suse. The agreement not to sue Novell (and for Novell not to sue MS) for past actions is flat out NOT RELATED TO SUSE LINUX. The second part of the deal (the agreement not to sue Novell customers) is exactly as I stated. The actual code being shipped by Novel as SuSE Linux is not covered in either of these 2 scenarios. Do you get it now?? Microsoft has agreed not to sue Novell's customers for patent infringement. If Suse or anything else Novell sells uses technology patented by Microsoft, Novell's customers will not get sued. However, if someone makes a derivative of Suse (or anything else Novell sells) then the people who get that derivative who are not Novell's customers are not immune to patent lawsuits. Do you understand?
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
  48. Does Linus approve? by spiritraveller · · Score: 1

    Linus became upset about FSF encouraging use of the name "GNU/Linux." The article and summary comply with Linus's preference, and refer to the whole OS as Linux, even though Linux (the kernel) is not a subject of this.

    Does Linus approve of this action done in the name of the Linux operating system?

    Or does he now think everyone needs to call it GNU/Linux so that it sounds less like he is responsible for it?

  49. Most likely an overraction ... by jopet · · Score: 1

    An overraction of fundamentalists who will ultimately harm the success of Linux with this and similar actions.

    Similar to the fundamentalist idiots here on /. who, for instance, totally suppressed any news about the release of OpenSuse 10.2.

    In any case, it is amazing to watch the stupidity being at work here. And it is sad, because, as somebody who has been using *NIX for more than 10 years now, I would like to see a usable alternative to Windows and Mac continue to be available in the coming decades.

    I am afraid, the fundamentalists of "everything must be free in all senses of free" and "we change the capitalist world by not letting them do anything a user could need under Linux" religion will spoil it.

    I'd really hate to see Linux disappear in the outer spaces of irrelevancy, but at the moment, the "community" is fighting hard to make some real bad strategic decisions.

    US patent laws will not disappear by doing this. The need of users for licensed and legal software like encoders/decoders or certain drivers will not disappear by doing this. The need of content providers to protect their investment on Linux will not disappear by doing this. The forseeable need of users to play back HD or Blueray discs, or any HDTV content will not disappear by doing this.

    I'd like to hear that something constructive is finally happen to strategically make these and other things possible on Linux so that it really can become a usable alternative to Windows.

    I am curious who long I will actually be able to avoid Windows on my computer in the future. Seeing how "divide et impera" is working to weaken the Linux camp, I am quite pessimistic about that.

    1. 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.
    2. Re:Most likely an overraction ... by Anonymous Coward · · Score: 0

      In the end, Linux may not run at all on *any* PC because of this.
      This is a perfectly acceptable (though not-at-all desireable) outcome, from the idealist point-of-view: "Give me liberty or give me death". Freedom is not something that you can compromise, because the instant you do, freedom no longer exists. Instead, what you have is varying degrees of "negative liberty" (see: http://plato.stanford.edu/entries/liberty-positive -negative/ )

      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.
      Very, very good point. The pragmatists would be better off taking this route.

    3. Re:Most likely an overraction ... by ardor · · Score: 1

      Well, absolute freedom is ultimately self-contradictory. Absolute freedom includes the option of voluntarily giving up freedom.

      --
      This sig does not contain any SCO code.
    4. Re:Most likely an overraction ... by petrus4 · · Score: 1

      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.

      The BSD license is not advocated for two main reasons:-

      a) Even among the pragmatists, Stallman has successfully influenced their thinking (and thoroughly slandered the BSD license) to such an extent that using it is considered literally unthinkable.

      b) The reason why the corporate world favours the GPL is because the BSD license still allows for a unique selling position. The people running at least some corporations have now become so mean spirited in thier thinking that they would actually prefer to forego any competitive advantage themselves, if doing so means that nobody else can have one either.

    5. Re:Most likely an overraction ... by alphamugwump · · Score: 1

      There are TWO main groups in the Linux community: the pragmatists and the idealists.
      And then, there are people like me who don't give a shit either way.
    6. Re:Most likely an overraction ... by Viceroy+Potatohead · · Score: 1

      To paraphrase Gandalf: "In which case, it is no longer freedom."

  50. you can't have it both ways by gp310ad · · Score: 1

    Microsoft agrees not to sue Novell knowing full well the existing license terms that apply to Linux.

    Hey Buzz, You know me, every time I get my hands on some reefer, I share it with the...like the whole 2nd shift.
    Sure Elmo and now you know that from henceforth and on, anytime you want a smoke, you're free to access my stash.

    What's the difference between the whole 2nd shift smoking up my stash or smoking up the stash that MS shares with Novell?

    --
    Do not look into LASER with remaining eye!
  51. A Big Stick by rbanffy · · Score: 1

    Actually, it's a measured big stick that should make Novell behave.

  52. Tortious interference - Tread Lightly by N8F8 · · Score: 1
    Tortious interference, in the common law of tort, occurs when a person intentionally damages the plaintiff's contractual or other business relationships. This tort is broadly divided into two categories, one specific to contractual relationships (irrespective of whether they involve business), and the other specific to business relationships or activities (irrespective of whether they involve a contract).

    Tortious interference with contract rights can occur where the tortfeasor convinces a party to breach the contract against the plaintiff, or where the tortfeasor disrupts the ability of one party to perform his obligations under the contract, thereby preventing the plaintiff from receiving the performance promised.

    Tortious interference with business relationships occurs where the tortfeasor acts to prevent the plaintiff from successfully establishing or maintaining business relationships.

    --
    "God fights on the side with the best artillery." - Napoleon, Marshal of France - speaking truth to power
  53. RTFA. NEW GPL. by gp310ad · · Score: 0, Flamebait

    It's only the NEW GPL that applies. Novell is just fine under the OLD GPL.
    Under COMMON LAW interpretation of the GPL, Microsoft KNOWS what it's getting into on this deal and really got FSCKED because they tacitly agreed to the terms of Novells CURRENT GPL terms. Without reading the contract, I'm SURE that Novell was smart enough to restrict the agreement to the current GPL. Either way, MS pays Novell $348 million. FOr those parts pof the world where common law applies....well MS gets ROYALLY EFFED because anything they pass to Novell passes to 'the community' under common law.

    IMO this whole mess is a ruse to see how smart the FSF lawyers are... Intel for a later FSCKING!!! MS is liek the effing middle east. One day you're all blown up. Up in heaven you learn that 47 generations back you had an imbecilic cousin who fscked someones goat producing a chimeric offspring(hey it worked back then) and you were just suicide bomb owned by descendants of the goats family.

    --
    Do not look into LASER with remaining eye!
    1. Re:RTFA. NEW GPL. by HiThere · · Score: 1

      It's not clear that Novell is within the bounds of the GPL2 license. It *is* clear that a legal battle would be long and expensive.

      The easy solution is to adopt a new license. And a new license was almost ready anyway...this just means that it needs a little fine tuning.

      The "deal" with MS may be anything from nearly harmless to visciously malign. We can't tell because too much of it is secret. We can only guess, based on the parties involved in the deal. Novell isn't SuSE...and even SuSE leaned in the direction of non-public proprietary software. MS...well, MS has a history. Trust based on hidden information and vague threats coupled with equally vague reassurances isn't very satisfactory.

      I feel that a new license forbidding this kind of behavior is forced. Others feel otherwise.

      I don't feel that a long legal battle is a good option. Particularly when there's another, even better, choice available in the very near future.

      I intend to do my future development under GPL3. The gcc will be under GPL3. So will glibc. And many other projects. These will not be redistributable by a company that is maintaining the kind of agreement that Novell has agreed to. They have no right to expropriate the commons, and if they try, then it's fair to deny them access to it...though GPL3 doesn't go that far. ANYONE can still use it, they just can't redistribute it without allowing anyone they distribute it to the right to redistribute it on the same terms that they can.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:RTFA. NEW GPL. by Anonymous Coward · · Score: 0

      My point is that the game we are watching is NOT the game MS and Novell are playing.

  54. Unbalanced Response by StarWreck · · Score: 1

    Not only is the "Free Software Foundation" over-reacting, they're displaying an unbalanced reaction compared to how they deal with other Linux distributions. For instance, there's a hardly known company that goes by the name "SCO" which distributes Caldera Linux. This "SCO" is zelously suing Linux in general, claiming they own all code in the universe. Yet, this "Free Software Foundation" is saying jack-squat about Caldera and "SCO".

    --
    ... and in the DRM, bind them.
    1. Re:Unbalanced Response by init100 · · Score: 1

      What should they say? They have already said everything there is to say about the case. They are quiet on it now, but they have been much more vocal in the past. Right now, they, like everybody else, are just waiting for the case to reach the dustbin.

  55. Re:WARNING PLEASE DONT READ by Anonymous Coward · · Score: 0

    I don't have a soul.

  56. Missing the point of the agreement by gwalcharian · · Score: 1

    Novell has not, AFAIK, agreed that Microsoft is right. The basic conversation sounds like it was:
    MS: I'll sue you
    Novell: We'll fight you and win
    MS: No you won't
    Novell: Yes we will and you'll get lots more bad press
    MS: What would it take to have us make nice in the market place, as our business users need/use Novell sw?
    Novell: $$, lots, and an agreement not to sue us or our users. In return we'll make nice-nice.

    No agreement on Novell's part that patent claim is valid, or precedent. As I see it this may actually be a win for the good guys. Now I suspect I'll be called a moron like other posters have. Don't really care, since I know I'm not one. That said, here's my opinion on the GPL (you may want to stop reading if you are really in love with the GPL/FSF beyond reason):

    GPL is a similar concept to unions. GPL served its purpose at one time, but now that open source (GASP..not captialized version) software is mainstream GPL is not needed, and is in fact harmful. How many companies do you think will now have second thoughts about basing their products on Linux after this stunt by the FSF? How far do you think open source would have gotten without the support of companies like Novell, IBM, and others? What do you think would happen to open source software if companies started categorically disallowing its use in any aspect of work?

    You want free software? Let the authors make it free, which most if not all the other open source licenses out there do (I personally prefer Apache for its freedom and for its recognition within the commercial environment). OMG, someone could re-sell my software: well, yeah..it's free to everyone, not just academics. If someone wants to packages my sw up, maybe add value or bug fixes, and sell it, and I've released it as open source, more power to them. They could even make modifications and sell those without contributing them back to the world at large. Again, yeah..the company wrote their software and added it to yours, just because yours is free shouldn't mean mine has to be free, unless you plan on paying my grocery bill.

    The idea that only certain licenses are allowed to call themselves open source, that the term Open Source actually has a definition that lawsuits have been threatened if it's not used correctly (rumour, I've not seen the threats myself), and that the FSF can do what they are talking about doing, are all signs of software that is under dictatorial control, not sw that is free. Interesting point to make here: dictatorial control is usuually established or maintained in order to either keep from losing something of value or to gain something of value. My first thought is always to ask how much money is involved: i.e. how much does the FSF make every year from fees, or how much do the leaders make from speaking engagements, books, etc, that are the result of them being at the ehad of the FSF? How much of that is donated to open source projects, and is it only donated to projects that toe the party line?

    Please don't take that as an accusation, but rather a question. Blind faith is never good, and if we cannot question the FSF and their motives, and get answers that make us warm and fuzzy inside, then why are we following them?

    I'd love to give you details on how I personally have helped the open source movement, but it would involve giving details on the practices of past and present employers. which I won't do. So feel free to assume I am a MS wonk and rabidly anti-open-source, you'll be very wrong on both counts, but isn't that freedom what it's all about anyway?

    1. Re:Missing the point of the agreement by bec1948 · · Score: 1


      This is one of the first comments in this thread that approaches this conflict in a manner that I believe is appropriate. IF we accept that computers and the software that operates and runs on them have purposes and that among those purposes is products and businesses that make and sell those products: That computers and software are the means of production in capitalist entities, then these arguments are all capitalist competitive disputes.
      Those who use these fruits of capitalism so support the operations of their own capitalist (or even anti-capitalist) endeavors don't usually care about the purity of the motives behind the sources of their tools. In fact, they presume that the usual human drivers for good or ill are at play. To simplify: it's about the money coming in to Novell and Microsoft and the money going out from us.
      For Microsoft's and Novell's (and IBM and HP and 3Com and Sun and all the other companies) customers, the only thing that really matters is that these products work pretty much as advertised and deliver the solutions to the problems for which they've been purchased. True belief doesn't really matter.
      This pissing contest is no more than the conflict between those who follow the gourd or the sandal. (If you don't get the allusion, you need to learn more about the history of religion and comedy.)

  57. This is pure hypocrisy by rudy_wayne · · Score: 1

    I hate Microsoft as much as anyone else, but this strikes me as be very hypocritical.

    "The foundation controls intellectual property rights to key parts of the open-source Linux operating system."

    So, in other words, Richard Stallman's "Four Freedoms" should be re-written to include "these freedoms do not apply if we don't like you or disagree with you".

    1. Re:This is pure hypocrisy by rohan972 · · Score: 1

      So, in other words, Richard Stallman's "Four Freedoms" should be re-written to include "these freedoms do not apply if we don't like you or disagree with you".

      Or they could rewrite it to say something like:
      "You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License."
      or
      "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."
      or
      "The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns."

      Hypocritical radical fanatics, applying a license to their software, and expecting people to abide by it. No wonder people use Microsoft.

    2. Re:This is pure hypocrisy by init100 · · Score: 1

      The four freedoms apply, and the license cannot be revoked for existing code. What this is all about is that future releases of GNU software may be released under a license that prohibits deals like the Novell-Microsoft agreement. Novell may thus be unable to distribute future releases of GNU software, which would have serious repercussions for their ability to maintain their Linux distribution.

  58. an overreaction by xxdesmus · · Score: 1

    This would be an overreaction by some zealots, nothing more.

  59. 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 imsabbel · · Score: 1

      The problem is: what kind of replay do you think the FSF should give?

      Because thats JUST what the FSF would like to do. RMS would glady disown every software company, and makes no secret of it.

      --
      HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
    3. Re:Spreading FUD by sumdumass · · Score: 1

      It isn't even fud in the traditional sence. It is a Vista marketing campain saying don't go to linux because your not impressed with vista.

      And yea, FSF could stop novel from distributing linux if it wanted to. That is if Novel follows the giudline outlined in the GPL it is using.

    4. Re:Spreading FUD by Anonymous Coward · · Score: 1, Insightful

      The whole Reuters article is FUD. Novell has not crossed any license, nor anybody at FSF thinks they can ban Novell from anything.

      Only on slashdot can you be modded 5 informative and be wrong.

      The GPL (any version) is like any license. It gives the holders 'exclusive' rights. They can refuse to let Novell use Linux anytime. Are you sayin that if I own the rights to a piece of music or a book I don't have the option of refusing to license it? What doctrine in law are you referring to?

    5. 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.
    6. 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
    7. Re:Spreading FUD by sumdumass · · Score: 1

      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'.
      Should is the operative word. I agree with what your saying but if your replying to me, i wasn't refering to any end users, just the distibution and in order to have the ability to distribute GPLed software, you need to follow it. However, my point was more to the fact that the FSF cannot stop someone from doing exactly as the GPL license allows. They cannot abitrarily yank someone's ability to participate if they follow the rules on acount of some one does not like who they are hanging out with. And if anyone in the FSF actualy thinks they can, then I would say wake up, this isn't third grade recess.

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

      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.
      I'm not fond of charity groups. They are usualy a waiste of time and effort. You can easily wrap a series of groups around each other and have them donate everything that was donated to them in an order of sucession and then siphon all the money with administrative fees, redtape and what not. I have seen My money that was donated to one organization get donated to another that I would never support. If it is going to be donated to something, use it to buy already pattented software rights and release them under the GPLv2.

      Something more usefull then donations might be keeping the lights on or helping with some hosting fees. More importantly, something that might fix a bug or extend capabilities of something and make it more usefull to the comunity, maybe even enterprises. It would be great if microsoft violated GPL and thier payments went to build an enterprise class replacment for office or exchange or something.
    8. Re:Spreading FUD by timmarhy · · Score: 1

      your right, RMS is a wack job, he is something of a visonary yes but those people never live in the real world. it's the rest of us that take their idea's and make them a little more real. thankfully the OSS isn't dictated to by RMS.

      --
      If you mod me down, I will become more powerful than you can imagine....
    9. 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.

    10. Re:Spreading FUD by KDR_11k · · Score: 1

      With the constantly increasing restrictions in the GPLv3 I wonder when you'll get your license revoked just for making a joke about Stallman...

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    11. Re:Spreading FUD by Thomas+Charron · · Score: 1

      ...

      I believe it was a press release directly from the FSF, and published on the wire by Reuters.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    12. Re:Spreading FUD by Jason+Earl · · Score: 1

      To be fair to the FSF I think that it has done a pretty good job of listening to GPLv3 critics. However, the Novell/Microsoft deal is opening a lot of eyes as to why a new version of the license is needed.

      One thing is certain, Novell is very dependent on the Free Software Foundation for the software that it distributes as part of SuSE Linux. It's not likely that Stallman will have his mind changed by RMS jokes, but if I was a Novell executive I wouldn't allow my employees to make RMS jokes, just in case.

      Stallman has a long history of sticky like glue to his principles no matter what criticism was leveled at him, and it is hard to argue with the results. Many of RMS' long time opponents have come around to his way of thinking. If the Free Software Foundation is rumbling about breaking up Novell's deal with Microsoft then Novell should be very very concerned.

  60. A New Holy War.. by JohnnyOpcode · · Score: 1

    Microsoft-SCO-Novell-IBM..

    Begun, the holy wars have!

  61. WTF???!!!11ONE! by Qbertino · · Score: 1

    Eiher the guys over at FSF are smoking crack or slahsdot is posting rubbish again. ... Hummm, gee, I wonder which is more likely ....

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:WTF???!!!11ONE! by swordgeek · · Score: 1

      It's always a tough decision between those two options.

      In this case, I think it's crack.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  62. wait for the real violation by radarsat1 · · Score: 1

    If I understand correctly, the issue is that Novell could now create code that uses untoucheable MS intellectual property, but they would be working on GPL code, meaning they have to distribute it as GPL, which would be in violation of MS intellectual property, which would be in violation of the GPL.

    Okay, *if* I got that right, then I think the FSF should wait to do something about it until they have a real, honest-to-goodness GPL violations on their hands. Something they can really sink their teeth into. It seems to me that starting a pre-emptive strike like this may only backfire. But then, I'm not a lawyer.

    Anyways, you really have to hand it to MS on this one. They finally found a way to hit free software where it hurts. But I'm sure we can pull through, as always.

  63. 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
    1. Re:So much for "open" by rohan972 · · Score: 1

      So if I understand...

      Apparently you don't.

  64. Banned? by EricJ2190 · · Score: 1

    So much for the idea of "free" software.

  65. Lawyer scum destroying open-source. by Anonymous Coward · · Score: 0

    Why is the FSF trying to force Novell into a position of being the next SCO?
    Novell holds the copyrights to UNIX and still contributes GPL code. Novell is an OK company.
    It is becoming apparent that FSF has been corrupted by lawyer scum that desire to destroy open-source from within.
    It is open-source minded comercial companies like RedHat, Novell, Mandriva, and Sun that produce working operating systems. FSF has made contributions to open-source, but as Caldera/SCO did, FSF is destroying its own contributions with lawyerisms.

  66. Load gun, aim at foot, pull trigger by Cid+Highwind · · Score: 1

    The FSF is making the best argument for using BSD instead of any code they hold copyright on that I've ever seen...

    --
    0 1 - just my two bits
  67. Red Hat should ALSO be banned by PenguinBoyDave · · Score: 0

    Red Hat sells Linux. Oh wait...so does Mandriva, Asianux, Turbo Linux, etc. etc. This isn't about selling Linux. It is about an organization (the FSF) crying foul because they are no longer relevant. That is ALL this is about, pure and simple. If they do this, it WILL permanently damage Linux in the data center, because nobody will want to work with a bunch of people that act like children. This is about Microsoft working with Linux...not about someone selling Linux.

    --
    I'm not a troll, but I play one on Slashdot.
  68. WTHFF? by Anonymous Coward · · Score: 0
    > One reason companies pay for expensive proprietary software is that the companies
    > that write proprietary software are considered reliable.

    Oh yeahhhh. Microsoft can be relied on alright; relied on to fuck you over at the first opportunity.

    Moglen was being quoted out of context in this article. Steve Ballmer was not being quoted out of context when he accused linux users of having an "undisclosed balance sheet liability" or threatening Asian governments. As usual it's Microsoft that is the aggressor... and this bit is hilarious....

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

    O RLY?


    /Me thinks you missed your calling as a professional comedy writer.

    1. Re:WTHFF? by QuickFox · · Score: 1

      Oh yeahhhh. Microsoft can be relied on alright; relied on to fuck you over at the first opportunity. Certainly. But Microsoft's fuck-overs are more predictable than this FSF action. Microsoft won't suddenly ban your company from using all future versions of Microsoft products.

      O RLY? The fact that Ballmer has weird outbursts doesn't pull out the rug from under the feet of your company.

      /Me thinks you missed your calling as a professional comedy writer. To a company, getting banned from upgrading the software that they depend on can in some cases be a major catastrophe. Very often companies need to know that they can rely on and depend on upgrades being available for the foreseeable future. Quite often their survival is at stake. This makes them nervous.

      Microsoft can and will fuck you over, but it's unlikely to do it in ways that are catastrophic for your company, when all you've done is buy their software. And when companies make decisions, minimizing risk is one of the most important factors. Quite often this is far more important than cost.

      (However, muellerr1 gives an interesting counterexample in his reply to my GP post. Not quite catastrophic but still a very interesting counterexample.)
      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    2. Re:WTHFF? by Anonymous Coward · · Score: 0

      > Microsoft won't suddenly ban your company from using all future versions of Microsoft products.

      Neither will the FSF because the GPL is not an end user license. They will stop redistribution of their software for copyright infringement such as occurs when a distributor invalidates their license.

      How do you think Microsoft would act if a company began to redistribute MS software without a license?

      > To a company, getting banned from upgrading the software that they depend
      > on can in some cases be a major catastrophe.

      GPL software is usually available from multiple vendors and as source, it's relatively painless to switch vendors. Contrast with Microsoft dropping support which could top the catastrophe scale. Granted that with Novell, they're trying to create a proprietary linux that is based around mono. So arguably the situation you describe may come to pass for Suse users that aren't smart enough to jump ship now.

    3. Re:WTHFF? by QuickFox · · Score: 1

      Neither will the FSF because the GPL is not an end user license. They will stop redistribution of their software for copyright infringement such as occurs when a distributor invalidates their license. If the FSF bans Novell from redistributing Linux, then Novell's customers will feel that the FSF has banned them from receiving the redistributed software. And this for political reasons that they are not interested in, and that don't even relate to them directly. Sure they can look for another distributor, but that doesn't remove the feeling that they've been banned from receiving the software the way they want.

      As I said in my reply to muellerr1, I'm not disputing the moral rights of the FSF to do what they're doing. What I'm worried about is the the reputation and public image of Open Source, as seen by companies and the media. When engineers tell their bosses that Open Source is the right solution, the bosses will say "Look what happened to Novell's customers. We can't stake the future of our company on our vendor getting continued political approval from Stallman."

      How do you think Microsoft would act if a company began to redistribute MS software without a license? They would screw them as harshly as they could. This is predictable. What companies want is predictability, so this is okay with the companies. Even those that get screwed will feel that they brought it upon themselves.

      Contrast with Microsoft dropping support which could top the catastrophe scale. I couldn't agree more. Sadly, companies don't understand this. It's absolutely amazing how deeply entrenched our societies' dependence on Microsoft is, all over the world. I find it hard to understand how so many people fail to see the dangers and risks that this entails. This risk is in fact the main reason that I hope Open Source will gain lots of traction. I believe Open Source is the most promising competitor.

      ...for Suse users that aren't smart enough to jump ship now. Sadly, seeing how companies tend to reason, I think many of those who jump ship will not say "We tried SuSE and it won't work any longer so let's try Red Hat instead." Instead they'll say "We tried Open Source and it won't work any longer, and this is because of Open-Source politics, so let's use proprietary instead."

      But the main problem isn't Novell's customers. Perhaps many of them are clueful. The big problem is all the other companies and the media, who will feel that Open Source is unreliable because of Open-Source politics.
      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    4. Re:WTHFF? by Anonymous Coward · · Score: 0

      >It's absolutely amazing how deeply entrenched our societies' dependence on Microsoft is, all over the world. I find it hard to understand how so many people fail to see the dangers and risks that this entails.

      As a concern, it falls behind global warming, the oil crisis, deforestation, and whether or not I'll get heartburn if I eat that second chili dog.

      Seriously, you've been staring at the lights and dials too long if you think any significant number of people would ever consider Microsoft's de facto standards to be a burning issue.

  69. What if... by cpinto · · Score: 1

    They should be given the chance to redeem themselves or at least clear the air on what they really signed.
    What if the "insider" access to Microsoft's patent arsenal were to be used to get rid of *real* patent violations in the Linux kernel and/or Samba and/or <some other piece of important software here>? Wouldn't that be great? If instead of grabbing the pitchforks and going on witch hunts, people actually lobbied Novell to do this kind of thing (if possible), in the end everybody would win. Well, maybe not Microsoft because then they couldn't use the patent FUD.
  70. RMS is an asshole, 401 by bluefoxlucid · · Score: 1

    Welcome to Advanced RMS Is an Asshole class. This year we are going to show you the most exposing actions of the Free Software Foundation, founded by Richard M. Stallman, and his attempt to purport a broken and socialist-communist-marxist system in the realm of software development.

    For our primary example, we have the FSF's recent movement against Novel: a serious consideration to prevent the company from selling Linux by restricting key GNU tools from being distributed in an Open Source way. This goes against the fifth principle of the Open Source Definition, as maintained by the independent Open Source Initiative:

    The license must not discriminate against any person or group of persons.

    The GNU General Public License v2.0 as well as the GNU Lesser (originally, Library) General Public License adhere to all points of the Open Source Definition, including the clause above. Here we see the Free Software Foundation changing its direction entirely; as its stripes are exposed, they show that their benevolence ends when you stop playing within their ideals.

    In our next session, class, we will discuss possible ways to combat the tyranny of the FSF. Their major attack point may include, for example, a motion to de-GPL the GNU Compiler Collection; our best defense is the Open Source Software community's capacity to split the current version off from GNU and maintain it in the same way XFree86 was ripped away from its maintainers and continued as Xorg.

  71. Free Software Foundation Nazis? by oneiron · · Score: 1

    Sounds like a contradiction in terms, but reality has a way of playing cruel jokes like this. Maybe it's for the best...maybe it's just confirming the free-market capitalist hard-liner's worst fears... Who knows...I just think it's painfully funny.

  72. Shakespeare saw this one coming ... by netbuzz · · Score: 1

    ... and even took out a billboard in an attempt to warn Novell. But did Novell listen?
    http://www.networkworld.com/community/?q=node/1042 9

  73. You are right ... by jopet · · Score: 1

    History shows unfortunately that idealists, especially fundamentalist idealists, nearly always did much more harm than good, even though their ideals might look quite good, theoretically.

    I cannot comment on *SD as an alternative, but I guess there is still a lot that would have to be invested in order for it to become an alternative even to Linux at the moment.
    Branching Linux itself and changing Licenses afterwards is not possible without the consent of thousands of (partially unknown or antraceable) contributors, so that is unfortunately not an option.

    1. Re:You are right ... by ardor · · Score: 1

      History shows unfortunately that idealists, especially fundamentalist idealists, nearly always did much more harm than good, even though their ideals might look quite good, theoretically.

      Yeah, or to make it short: "hell is paved with good intentions." Always fear those who want to make the world a better place.

      --
      This sig does not contain any SCO code.
  74. Linux is NOT gnu by dbIII · · Score: 1

    The FSF can't stop anyone using it or selling it. What they can do is take steps against entities that viotate the GPL - which is something different.

  75. Pardon me... by Classical · · Score: 1

    ...while I go buy the latest desktop offering from Novell - and I don't even like SUSE. Honest to God, the FSF has gone too far this time. I shook my head over their PETA-like "demonstrations", but this reaches new levels of idiocy - even for them. Who died and named Richard Stallman and Eben Moglen God? How dare you attempt to dictate to me what I can and can't run on my computer? "We defend your freedom...so long as it's what we define as freedom." If the FSF owns the GNU software stack, it's obviously time for me to find other choices. I swear, if I didn't dislike Windows so much (from a usage POV, it's got nothing to do with ideology), I'd be going to buy a copy of Vista along with SLED. If you couldn't tell, I'm really upset about this. I've been using Linux for the last 10+ years and I've always been able to shrug off the fringe element, the zealots. Unfortunately, it now appears that the inmates are running the asylum...

    1. Re:Pardon me... by CrazyGenie · · Score: 1

      I can understand the problem and frustration you are facing in this FSF-Novell dilemma. But I guess you are not making the mistake of moving away from Linux just because of FSF/Novell. There are many community maintained distros which fare really well and don't get messed like the current situation ( I guess you know this). I feel the community's spirit continues to exist irrespective of FSF strict stand against Novell or Novell's agreement with MS.

      --
      In the interest of GNU/Linux, CrazyGenie
  76. 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.
  77. 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"
    1. Re:And You Wonder Why People Avoid Open Source? by rohan972 · · Score: 1

      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?

      If Novell had never heard of FSF it would be stange. FSF is one of Novell's biggest suppliers.

    2. Re:And You Wonder Why People Avoid Open Source? by lawaetf1 · · Score: 1

      Let me flame you a bit.. Newb!

      You ask "who wants to risk going with a vendor who's at risk of being tied up by a bunch of lawyers" as if the GPL is just some frivolous bit of txt that prepends Linux source code. Guess what, bucko, it's not. It's the framework around which Linux branched and grew. Novell's deal with Microsoft was craftily crafted such that it didn't challenge the GPL outright but started the FUD engine that MSFT just might go after clients who are not covered under some bogus IP protection deal. In essence, MSFT took a Linux distro (novell) and said, "You'll be our lap dop. Your sales team can now run around and say that your product is Microsoft compliant. We will milk you on this for a bit to fragment and confuse the Linux community and then we'll ram a knife into your lungs and walk away whistling while you aspirate on the sidewalk."

      Novell, in firmly attaching itself to Microsoft's teat, is actively working to subvert the open source movement by giving Microsoft some high ground upon which it can launch an assault on the rest of the movement. And your reaction to the FSF working to protect the community is, "oh noes, the lawyers are getting involved, nobody likes that."

      --
      CommentBot 0.7a running with args "-module irritate,disagree -target random"
    3. Re:And You Wonder Why People Avoid Open Source? by reallocate · · Score: 1

      The only people who care about the "community" are the people in the "community". Your comment -- highlighting the social aspects of open source and characterizing it as primarily an anti-Microsoft lobby -- precisely captures what turns so many people off about open source. Lots of people will agree that Microsoft, and any number of other tech companies, are abusive and anti-market. But, that doesn't mean that they are going to buy into open source ideology. They'll buy from Microsoft, et al, because all they hear and read about open source is, frankly, cult infighting about licenses, copyright, and IP issues.

      The issues that drive people to become open source developers and supporters are not the issues that motivate everyone else's software purchasing decisions.

      --
      -- Slashdot: When Public Access TV Says "No"
    4. Re:And You Wonder Why People Avoid Open Source? by lawaetf1 · · Score: 1

      The issues that drive people to become open source developers and supporters are not the issues that motivate everyone else's software purchasing decisions.

      And they are not mutually exclusive. Your baseless reference to "cult infighting" demonstrates you have a poor understanding of the nature of Linux, the architecture of the community, and the role played by the dozens of companies that make a profit by supporting open source.

      --
      CommentBot 0.7a running with args "-module irritate,disagree -target random"
    5. Re:And You Wonder Why People Avoid Open Source? by reallocate · · Score: 1

      Rather than trying to explain "nature of Linux, the architecture of the community, and the role played by the dozens of companies that make a profit by supporting open source", you might try pondering why reasonably knowledgable people perceive the constant debate about licensing, etc., as irrelevant noise and a strong disincentive to associate with the community or its software. Your approach, which is common, seems to be aimed at getting people to understand the community rather than seeing the technical and financial benefits of open source software. It's a turnoff.

      --
      -- Slashdot: When Public Access TV Says "No"
    6. Re:And You Wonder Why People Avoid Open Source? by dodongo · · Score: 1

      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?
      I agree that the BSA has overreaching power, and Microsoft's latest attempts to have them go after small businesses is a cheap shot.

      But what does that have to do with this thread?
    7. Re:And You Wonder Why People Avoid Open Source? by reallocate · · Score: 1

      Because neither Microsoft's and the BSA's posturing nor open source's and the FSF's posturing is a valid reason to buy or not to buy and use either's software.

      My point is that the constant chattering and debate about licensing, etc., bears a remarkable resemblance to medieval monks arguing about topics that mean absolutely nothing to anyone outside the monastery. E.g., MS is the devil, and any association with the devil is a sin. Novell has sinned, so banish Novell from the garden that is open source. That is not the way to attract anyone.

      --
      -- Slashdot: When Public Access TV Says "No"
    8. Re:And You Wonder Why People Avoid Open Source? by dodongo · · Score: 1

      Because neither Microsoft's and the BSA's posturing nor open source's and the FSF's posturing is a valid reason to buy or not to buy and use either's software.
      My point exactly. Mismanaged in both camps, and instead of taking the opportunity to spread the word that, e.g., businesses can use FOSS to avoid dealing with lots of licensing and auditing headaches, per the great story about the Ernie Ball company a few years back. Instead, it looks like a pissing contest to see which side can outlitigate the other.
    9. Re:And You Wonder Why People Avoid Open Source? by reallocate · · Score: 1

      Agreed. But, in addition, I'm arguing that the noise about the BSA and Microsoft's licenses represents only a very small fraction of what the public hears and sees about Microsoft. On the other hand, the public is exposed to a great deal of noise about open source licensing disputes and other issues that are important only to community members. That's really bad PR. Consider: If it's always a bad day for a company to be hounded by BSA people yapping about licensing, imagine what it's like when that's almost all you ever hear open source people talking about. Why, people might be led to believe the primary purpose of open source is to change the way software is licensed, not to produce innovative software that lets them do things closed software doesn't.

      --
      -- Slashdot: When Public Access TV Says "No"
    10. Re:And You Wonder Why People Avoid Open Source? by dodongo · · Score: 1

      On the other hand, the public is exposed to a great deal of noise about open source licensing disputes and other issues that are important only to community members.

      Maybe I'm not getting my news from the right sources, but I would imagine that in any given reputable news outlet, the MS-BSA fiasco is getting as much coverage as this FSF-Novell dustup... That is to say not much. I guess it's an empirical question, though, huh?
    11. Re:And You Wonder Why People Avoid Open Source? by reallocate · · Score: 1

      I don't think it can be denied that a major component of the open source "converstation" that's visible to the public has to do with licensing and related issues. That's not the case for Microsoft, and that's all to the good for MS.

      --
      -- Slashdot: When Public Access TV Says "No"
    12. Re:And You Wonder Why People Avoid Open Source? by petrus4 · · Score: 1

      You ask "who wants to risk going with a vendor who's at risk of being tied up by a bunch of lawyers" as if the GPL is just some frivolous bit of txt that prepends Linux source code. Guess what, bucko, it's not. It's the framework around which Linux branched and grew.

      There's pure, subjective emotion, here. Get rid of that red haze in front of your eyes and you might be good for something vaguely approaching a rational argument.

      The single main thing that upsets me about zealots like yourself is how long it's taking you to become extinct.

    13. Re:And You Wonder Why People Avoid Open Source? by lawaetf1 · · Score: 1

      I find it mildly amusing that you huff and puff about me having made a subjective argument when you not only offer no position of your own but accuse me of being a zealot. What bothers me most about individuals such as yourselves is that you're hypocrites who idly claim to be making "a rational argument." I think it was Emerson who wrote that, "I can not hear what you say for what you are shouts too loudly in my ears."

      --
      CommentBot 0.7a running with args "-module irritate,disagree -target random"
    14. Re:And You Wonder Why People Avoid Open Source? by petrus4 · · Score: 1

      I think it was Emerson who wrote that, "I can not hear what you say for what you are shouts too loudly in my ears."

      I'm willing to accept that that statement applies to me in this case...but it applies equally to both of us.

      I *am* one of the people who believes that both the FSF and its' worldview are damaging Linux. You might answer (as someone else answered me) that Linux would not exist without the FSF. In specific terms, that is not true. The kernel was initially developed by Linus outside of the FSF, and he initially actually wrote his own license before adopting the GPL. A kernel was the one piece of software which Stallman and the FSF were never able to develop on their own.

      I should walk away from this...I'm also willing to concede that. The reason why I'm finding it hard to is because I feel that mainstream computer using society has both a desire and a genuine need for Linux, and I also feel that the operating system could be a lot more than it is currently if the FSF and the attendant army of zealots would get out of the way. They're not helping...they're creating conflict and division and driving people away. This isn't just someone else's argument, either...I've been seeing it happen.

      You might admire Stallman. Personally, he is a source of enormous unhappiness and emotional pain.

    15. Re:And You Wonder Why People Avoid Open Source? by init100 · · Score: 1

      So what you're saying is that the community should shed all those irritating principles so that it can enter the limelight for a while?

      I'd say that if you show the world that you are ready to appease those that try to sidestep the rules that you have set for your code, there will be an endless stream of other people that will take advantage of your willingness to be buttfucked. You might be willing to bend over, but not everyone is.

    16. Re:And You Wonder Why People Avoid Open Source? by reallocate · · Score: 1

      Not at all. I did not say that open source developers should abandon their principles. I said that peope who don't share those principles -- most of the world -- find the constant chatter and exhortations to be a negative advertisement for open source. Jabbering on like so many newly converted religious enthusiasts about the wonders that open source brings to software developers, and arguing with each other about, say, the difference between one GPL version and another, is not the way to convince software users to try your software. It simply creates the appearance that the primary focus of open source is n-o-t creating better software, but, instead, enlarging the "community" and ensuring it adheres to the proper ideology. I.e., people are justifed to think the focus of open source is on those principles, not on the software.

      No one said you should appease the non-believers. But, at least recognize when you're alienating them.

      --
      -- Slashdot: When Public Access TV Says "No"
  78. You can't use it like Novell need to use it by Anonymous Coward · · Score: 0

    I.e. distribute the source, create copies and derivative works.

    Being able to run the copy given isn't copyright controlled, so I don't mention it (though EULA's say they do, I will not give them credence by including that limitation as being COPYRIGHT exercise) and for Novell, how can the continue as a Linux business if all they can do is run the code themselves? Do they have to buy the companies of their customers?

    From Novell's POV, they can't use the code. Novell can't run the code, people IN Novell can run the code, but Novell cannot.

    1. Re:You can't use it like Novell need to use it by zotz · · Score: 1

      "From Novell's POV, they can't use the code. Novell can't run the code, people IN Novell can run the code, but Novell cannot."

      They can use it, they can't do the things with it the license permits. But if we broaden use to suit you it is still missing the point of my post.

      Look at the parent which I replied to. The third example is enough different form the first two that you could easily take issue with the first two and not the third and still be consistent.

      Yes? No?

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
  79. Why not BSD? by metamatic · · Score: 1

    Perhaps you should ponder the possibility that the success and growth of Linux is precisely because of the idealistic licensing.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    1. Re:Why not BSD? by ardor · · Score: 1

      A good point, I also considered this a while ago. However, there are key arguments against this.

      1) BSD was involved in the AT&T case back when Linux started to take off. Maybe without the lawsuit things would have been different.
      2) IBM. Never forget IBM. They are the Nr.1 Linux supporters. Without IBM, Linux may never have come this popular. Thanks to IBM support, Linux is actually considered for servers. Why? Precisely because IBM offers support. Red Hat wouldn't have been enough, they didn't have a name back then. IBM had.
      3) Linus is a pragmatist. He didn't mind involving corporations in the Linux development. A evangelist Linus would have resulted in something entirely different.
      4) Maybe it was just casual? I mean, look at the entire community. We have Unix veterans, GPL evangelists, ex-Amiga guys, ex-Windows guys, gamers-turned-programmers (esp. in the 3D graphics sector). They were scattered before, and Linux became a focal point for all these groups. Considering (1), BSD could have become that focal point too. Especially the ex-Amiga guys tend to despise the GPL campaigns, and spiritually they are much closer to BSD, but Linux is the alternative OS with the best hardware support..

      --
      This sig does not contain any SCO code.
    2. Re:Why not BSD? by metamatic · · Score: 1

      1. I don't think Linux was taking off in 1993. It was pretty raw in those days. Even I wasn't using it :-)

      2. IBM already had its own Unix it had been supporting for decades. It only started supporting Linux because Linux had already started to beat out other Unix OSs.

      3. Linus may be a "pragmatist" in some ways, but he still picked the GPL. And it's not like he didn't know of alternatives--he came from the Minix world, and knew about BSD.

      4. I think that the guaranteed mutual sharing is exactly what brings all these disparate people together. Of course, not having Theo around also helps :-)

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    3. Re:Why not BSD? by petrus4 · · Score: 1

      Linus may be a "pragmatist" in some ways, but he still picked the GPL. And it's not like he didn't know of alternatives--he came from the Minix world, and knew about BSD.

      Linus was originally opposed to the idea of anybody using the kernel commercially...it said that in his initial license, before he moved to the GPL. My guess is that he only became receptive to the idea of the kernel being used commercially when he started to become rich from it himself. However he initially probably thought that the GPL was sufficiently anti-commercialistic that it was close to what he had originally intended...and he's always claimed to be fond of the GPL's enforced reciprocity, as well.

      People have accused me of being an uncritical fanboy where Linus is concerned...I'm not. I don't have a problem with the concept of reciprocity, however I don't believe that such should have the weight of the law behind it. I will admit that I also consider Linus highly irresponsible and misguided for ever having had anything to do with Stallman. If Linus was as great a man as a lot of people think, he should have had the foresight to realise that partnering with Stallman was a very bad decision, and would come back to haunt him.

    4. Re:Why not BSD? by metamatic · · Score: 1

      I'm more concerned about Gnome and Ubuntu partnering with Novell and Mono, to be honest. Stallman's a pretty harmless annoyance, as annoyances go, and he's more often right than wrong.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  80. It's more than an escape for Novell by Anonymous Coward · · Score: 0

    It's more than an patent escape clause for Novell to beat down other distros. Their people have actively been complaining to support MS technologies and making MS technologies a standard at the expense of open source alternatives. This is what MS means by interoperabilitiy (everyone adapts to us on our terms and we don't do a thing to adapt to anyone else).

    Here's a typical example of the shift:
    http://tirania.org/blog/archive/2007/Jan-30.html

    Previous to the agreement Miguel said XAML was a very bad idea that solved no problem and Mono would never support it officially. He also said OOXML was a sham, and took pride in all the work he put into making OpenOffice and it's format integral to the desktop (check the logs, Ximian did do a lot of work). His focus was also on getting C# for use on GNOME because he liked the language and thought that the vast pool of books on C# would bring an army of Windows programmers to Linux, in much the same way that the universal adoption of C++ brought Windows C++ programmers to Unix. His only goal at supporting Windows-specific technologies like Winforms was to help with porting to more portable technologies (like GNOME# and Gtk#) or for use in abstraction layers (i.e. use Cocoa for Mac, Gtk# for Linux/Unix, Winforms for Windows).

    After the agreement, it's been a nonstop promotion of OOXML, XAML, and other MS technologies as the primary choice for Linux.

  81. Wisdom of the Crowd! by CrazyGenie · · Score: 1

    Well, whether FSF sues Novell for their so called unethical tie-up with MS or Novell neglects the community interests by the suspected idea of achieving monopoly in Linux, or even if it is suspected that MS is playing double game!! the community cannot be taken for granted. There is a wisdom in the crowd, if not in a single geek. The community itself takes various forms; as developers, as testers and as end-users too. Any of the organization taking such a huge Linux community for granted would definitely be a foolish mistake. I hope FSF treads carefully in this regard, so does Novell, not loosing out its strong Linux user base just because of a DRP agreement with a monopolized company.

    --
    In the interest of GNU/Linux, CrazyGenie
    1. Re:Wisdom of the Crowd! by DaveV1.0 · · Score: 1

      There is a wisdom in the crowd
      Ah, yes. Would that be the same wisdom that killed so many non-aristicrats after the French Revolution? Or would that be the same wisdom that created the Jim Crow laws in the southern U.S. states? Or would that be the wisdom that has kept Hugo Chavez in power and is now turning Venezuela into the USSR of Latin America? Or would that be the wisdom of German people in the 1920s and 1930s?

      Crowds are peole. In the words of Agent K, "A person is smart. People are dumb, panicky animals and you know it."
      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    2. Re:Wisdom of the Crowd! by CrazyGenie · · Score: 1

      >Crowds are people. In the words of Agent K, "A person is smart. People are dumb, panicky animals and you know it." Well, people may be panicky animals... but it is their wisdom that matters the most. A person by himself/herself may be smart but he his smartness couldn't be supported individually. If you think it can, they I say it is short lived. Well, considering all the examples you mentioned(USSR, Germany, Latin America...), still I say it is the wisdom of the crowd, though I may not support their stand. All I wanted to say is if FSF comes with stingent rules or Novell plays a dual game, it results in groupism among the community. But, these groups may not be acceptable to much larger free and open-source community.

      --
      In the interest of GNU/Linux, CrazyGenie
    3. Re:Wisdom of the Crowd! by DaveV1.0 · · Score: 1

      Where is the wisdom of implementing a stragety that has already failed?

      The so-called "wisdom of crowds" is merely mob rule by another name and mob rule has a very poor history. Mob rule is behind lynchings, attacks on minorities, ethinic clensing, and other atrocites.

      In the 1400s, the "wisdom of crowds" said that the Earth was flat and if one sailed too far one would fall off the Earth. Crowds do not have wisdom. They merely have will and they impose it by fiat.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    4. Re:Wisdom of the Crowd! by CrazyGenie · · Score: 1

      The so-called "wisdom of crowds" is merely mob rule by another name and mob rule has a very poor history. Mob rule is behind lynchings, attacks on minorities, ethinic clensing, and other atrocites.
      Dear friend, I'm definitely not pointing at the crowd involved in lynchings, attacks on minorities, ethinic clensing, and other atrocites. This is nothing but a group under a strong Authority doing blindly whatever the leader says. Such a crowd should not be confused with the crowd consisting of free thinking, and open minded people. What you are talking about is the crowd which consists of people who give their thinking ability to some Authority and just behave as the authority instructs them to do.
      Linux community who has contributed so much to the technology is not that lynching crowd, but a free-thinking, technology sharing and open-minded people. This community doesn't want authoritarian elements spurting in it. This is the wisdom I'm talking about.
      --
      In the interest of GNU/Linux, CrazyGenie
    5. Re:Wisdom of the Crowd! by DaveV1.0 · · Score: 1

      Let me point to the FSF and RMS as counterpoint.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  82. Free software? Really? by jmaslak · · Score: 1

    First, this just screws customers of Novell - typically big organizations which can afford Windows licenses, but have been starting to implement Linux (from Novell, among others) on the basis of Linux's merits (instead of just it's cost). If you're a customer of Novell, you can read this as:

    FSF is looking at making you change all of your systems relatively shortly because FSF doesn't agree with Novell's business model. You're going to have to find a new vendor.

    That new vendor is going to be Microsoft. They are going to say, "Why should some long hairs from Massachussets be able to disrupt my data center? I rely on my service contract with Novell. Well, I'm done with them. I'm going to go with a product where there are market forces in place to give me some stability." They aren't going to see this as a Novell issue, they are going to see this as a LINUX and FSF issue.

    But FSF has different goals than most of the Linux community. FSF's goal is that no one sells code. Most of the Linux community want to see their software running as many places as possible. Often these goals are compatible (free of cost means it is easier to get people to install!), but sometimes they are not. This is an example of "not".

    But I've never thought GPL was "free". If your software is free, let me do whatever I want with it. Seriously. Don't tie in clauses preventing certain uses that go against your morals. If it's free, let it be free. Otherwise call it what it is, but don't use the word "free" to do that, since it's clearly not free in a "free to use however you want" way. I think the BSD (especially new form of the license) is an example of a truly free license. It's also possible for mere mortals to understand the BSD license (that's another part of being "free" - I have to know what rights I have and don't have).

  83. Some data points by NoOneInParticular · · Score: 1
    No, absolutely wrong. You have a myriad of copyright owners in the kernel. I just checked in my source tree, and all code is copyright of the original writers. You're confusing this with the GNU toolchain, which is indeed copyright FSF.

    Furthermore, the license is a mix of 'only GPL-2' and 'any later version'. I ran this on my linux source tree:

    find . -print | xargs grep 'any later version' | wc -l
    4853

    This is significant chunk of the kernel.

  84. Freedom is not Free! by mlwmohawk · · Score: 1

    No one except Novell and Microsoft know what is in the agreement. That is a problem. There are thousands of copyright holders involved in Linux. Novell has no right to alter the agreement between the copyright holder and the end user. Novell has no right to enter into an agreement that either provides or denies rights to the end user that the copyright holder has not endorsed.

    Linux is a collaborative work, it does not belong to Novell. Novell gets to use it as long as it abides by the wishes, as embodied by the GPL, of the copyright owners.

    Every viable free environment has practical limits on freedom that prevents one from using their freedom to usurp the freedom of another.

    If Novell has entered into an agreement that means that "non-Novell" Linux is less "free" than a Novell version of Linux, then Novell has violated the GPL and should not be allowed to distribute Linux.

  85. Who'd Have Thunk It? by swingerman · · Score: 1


    How Ironic. The group / organization which wants software to be FREE as in LIBERTY -- i.e., you can do anything you want with it -- has now threatened to RESTRICT the FREEDOM of a company to distribute that FREE software.



    So, if this "threat" by the FSF is true, the organization needs to change its name. Maybe it should be the FUD Software Foundation or the Fraudulent Software Foundation. The truth of the matter is that, while the FSF may be able to release new versions of its GNU software under the new GPL/v3, which may have some restrictions in it, they cannot prevent Novell from continuing to distribute and improve the versions that were released under GPL/v2.



    If true, this has done nothing but harm the FSF's "cred." Nothing more need be said.

  86. Article contributes to FUD *and* raises questions by vic-traill · · Score: 1

    I think the article is poorly written, and as such leads to confusion rather than clarification. Looking over the comments seems to support this interpretation - they're all over the map. At the same time, it does capture the essence of community concern over this deal, and raised some interesting (at least to me) questions.

    "The community of people wants to do anything they can to interfere with this deal and all deals like it.

    Well, don't speak for me on this. I still don't understand what is going on enough to say that the deal should be interfered with. That being said, I'm concerned by the lack of clarification and speaking to concerns on the part of Novell, so I understand where the suspicion is coming from; along the lines of 'if they're not looking to clarify, then what are they hiding?'.

    They have every reason to be deeply concerned that this is the beginning of a significant patent aggression by Microsoft," Eben Moglen, the Foundation's general counsel, said on Friday.

    And when I start thinking about possible outcomes of the agreement, this is what makes me paranoid. Why was Microsoft motivated to make this deal? So that Microsoft could deliver SUSE subscription licenses to Walmart? I don't think so.

    As I understand it, the deal indemnifies Novell against patent violation accusations from Micrsoft. As such, all future Novell contributions to GPL's software must be viewed with a jaundiced eye, since it appears that Novell need not worry about patent violation action against their contribution, while any other developer who derives from the new Novell code has no such luxury.

    Okay, so how does all this lead to "Critics called on the board to punish Novell by banning it from distributing new versions of Linux software, said Moglen."? Note IANAL - please comment if I am wrong here. I think that the term 'banning' is a bit of a misnomer here, isn't it? The FSF has the right to enforce the GPL as it sees fit, and as such any move to stop Novell from distributing GPL'd code would require court action on the FSF's part looking for an injunction against Novell distributing GPL'd code, wouldn't it? If the answer to this question is substantively 'yes', then the FSF would not be so much 'banning' Novell from doing anything as enforcing the GPL.

    TFA also muddies the waters by slipping in the GPLv3 without explicitly saying so; at least that's how I am interpreting it: "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.

    The inference here is that the GPLv2 is not being violated by the Novell/Microsoft agreement. As several posters have noted, it appears that the GPLv2 is being violated (e.g. section 7). so either the community doesn't have all the information, or we don't know how to interpret/apply the GPL. I either case, it shows that we really need a cogent source of information and summary regarding this deal. I've watched Eben Moglen's ogg (jeez folks, can't you get your hands on a better microphone, this is barely listenable!) video http://gplv3.fsf.org/static/FSF_Eben_Moglen_Appeal .ogg and in it Eben intimates that the GPLv3 is required in order to fight the Microsoft/Novell deal. Again, The inference here is that the GPLv2 is not being violated by the Novell/Microsoft agreement. There is really no other readily accessible info regarding this deal that I can find on fsf.org; there appears to be some activity in the discussion forums, but these require registration for access (there's a bit of irony for ya!). So I don't have access to the deal itself, and I really don't seem to have access to a thoughtful interpretation of the deal. If anyone knows where to find some well thought out material on the deal, please post.

    If the GPLv3 really is required to fight the possible evil implications of the dea

    --
    [17] Leary, T., White, C., Wood, P. R., Bhabha, W. D., and Wirth, N. Lambda calculus considered harmful. In Proceedings
  87. war axes by KwKSilver · · Score: 1

    You say Novell buried the war ax, however, most people's perception is that they have tried to bury it in their Linux competitors' backs. Furthermore, whatever patent protection they bought for themselves and maybe for their customers expires when the agreement expires, which is five years after it was inked. anyone using their products then is naked, and those who got their copy of SuSE from Microsoft will be a target that MS knows exactly where to find to serve legal papers on... If MS is not planning on suing anyone, it should stop saber-rattling... even MS must know that it is insane to make threats it is not willing to execute.

    That said, whoever modded your comment as a troll is an asshole. I agree with none of your points, but they are legitimate opinions, not trolling.

    --
    If you want your life to be different, live it differently.
  88. Blind zealotry and unreasoned hatred by pcause · · Score: 1

    This is just a case of people having an irrational hatred for Microsoft. As long as Novell complies with the GPL which governs the code, the FSF and others should back off. Remember that real freedom includes the right to do things that others don't lim, as long as you comply wi th the rules. If not, then we will have to add another "free as in..." to our discussions. GPL and FF will be using "free" to mean "Free as in North Korea"!

    1. Re:Blind zealotry and unreasoned hatred by smash · · Score: 1

      I think the old saying that "People who like unix use BSD, people who hate Microsoft use Linux" applies here more than ever :)

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  89. Hold on a second. by Cutter892 · · Score: 0

    Of course Novell could be in serious trouble here if they alter GPL code and then license it as something else. Or they could use all there developers and create a whole new software suite that they could license and distribute how ever they wanted to. They could call it MS/Novell compatibilty suit. This software package could include everything needed to use Windows or Novell Linux software for either platform. Or it could just be a software sweet like (insert name) office were you will have no compatibilty issues with either OS. This package could include who knows what maybe AD compatibilty for Novell Linux or full NTFS support. Hopefully you get the idea here that Novell just doesn't have to use other peoples open source software to work with MS on this deal they can simply create there own.

  90. Don't throw me in to the briar patch... by itsdapead · · Score: 1

    As I understand it, M$ and Novell have signed a sort of IP non-agression treaty, but that although this has enormous FUD value it does not specifically identify any M$ IP present in any specific GPL software. If it did Novell would be in fairly clear breach of GPL2 - no improvements needed - but it doesn't, so they aren't (IANAL of course).

    The problem with trying to "fix" this and other "spirit of the agreement" annoyances is the risk of unintended consequences.

    In particular, many of the companies currently investing in Free/OS software inevitably have various cross-licensing agreements with other companies - not a problem as long as none of the licensed IP fetches up in GPL code they distribute. How are these distinct from the Novell/M$ deal - apart from the allegation that the latter was part of an anti-Linux FUD campaign - and how do you incorporate that distinction in a license?

    What would the future of FOSS be if no entity holding any sort of license for IP that could even arguably find its way into GPL could contribute?

    I'm worried that the outcome of this might be to goad the FSF into inserting all sorts of new self-destructive micro-management clauses into the GPL3, making it too complex, open-to-interpretation and risky for anybody to get past their (already skeptical) legal department. I'm worried that the Novell deal - although a serious concern - is being used as a bogeyman for "selling" GPL3 to its critics.

    --
    In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
    1. Re:Don't throw me in to the briar patch... by petrus4 · · Score: 1

      I'm worried that the outcome of this might be to goad the FSF into inserting all sorts of new self-destructive micro-management clauses into the GPL3

      They were going to do that anywayz, regardless of Novell/Microsoft. This is Stallman's endgame...I've seen it coming for a while, and I'm assuming I'm not alone.

      a) Assemble as large a stockpile as possible of critical code/IP.

      b) Put said code/IP under a license you/your people are the sole authors of.

      c) Use the genuinely abusive/illegal actions of corporate entities to demonise them and get people on your side. Us vs them, polarised thinking serves a lot of different purposes for the next step as well.

      d) Create a cult of followers who are willing to do more or less anything for you, and invent a suitably dangerous-seeming threat (DRM) that you also make it appear that you are their only chance of salvation from. This keeps people in a constant state of terror and hence completely uncritical, fanatical loyalty. They completely remove any opposition you might otherwise experience, while your own hands are able to remain spotless. Stallman believes very strongly in the power of having at least the perception of moral superiority. People on Slashdot and elsewhere will belittle or shout down those who disagree with the FSF's perspective/goals, and in the case of people like Laura Didio, the death threats and other harassment can come from the expendable rank and file within the movement. Thus, obstacles are removed, while the ordinary members take the fall and the leadership remains entirely blameless. Cult tactics 101. The non-software related activism that the FSF has switched to in the last year or two can safely be written off as a dual recruitment and public relations ploy. Make the group look good, make it mainstream credible, (or try to) and as L. Ron Hubbard said, get lots and lots of bodies in the shop. It is also well documented for cults to try and change what has customarily been seen as their traditional nature when they begin to lose credibility. Scientology became a religion when it initially was internationally banned, Amway became Alticor/Quixtar when its' reputation became too poor to continue operating, and the FSF is switching to realworld activism because most of its' development role has been adopted by Red Hat, and without its' software development role, it is entirely redundant, and not particularly well liked outside the cultic base. One of the other things I read people within the FSF saying recently is that they were trying to move the focus off Stallman as an individual, and the American chapter of the FSF...the child organisation of the FSFE is gaining prominence. This is because they know Stallman is detrimental to the FSF gaining mainstream credibility, and it is also because the current climate of anti-Americanism internationally means that they know they cannot afford to have an American as the public face of the organisation. Once again, a group faced with oblivion is trying to re-invent itself, to make itself appealing. I've seen the pattern over and over again.

      e) Once the stockpile of critical code/IP becomes large enough, gradually alter the license it is under such that you are able to bar access to it from anyone you don't like. You then, as far as computing infrastructure is concerned, and as far as your followers are concerned, are in a position to basically dictate whatever you want, with the added bonus that the earlier assembly of the software stockpile makes you look like a saint to the people who've been sucked in by your official mythology.

      This has been the plan from the beginning.

    2. Re:Don't throw me in to the briar patch... by arem-aref · · Score: 0

      ...and of course you forget to recognize microsoft's pristine reputation.

  91. What I have to say ... by openldev · · Score: 1
  92. BSD by nurb432 · · Score: 1

    This is why god created the BSD license. It avoids all this nonsense.

    ( and no, i wasn't trying to start a discussion if which is *better*, only wanted to point out that with a BSD license these sorts of issues wouldnt be )

    --
    ---- Booth was a patriot ----
  93. Please invest in a bash programming manual by Anonymous Coward · · Score: 0

    Here is one:
    http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html

    Your script is broken in many ways. In fact if your goal was to provide the worst bash script example possible then you've done well.

  94. Sure, make a SCO out of them... by rdean400 · · Score: 1

    The Microsoft agreement was a bone-headed move on Novell's part, but they've been on the right side more often than not. They've worked to protect the Linux community from SCO by asserting their rights to UNIX. If the FSF tries to cut them off from Linux, their fiduciary responsibility will force them to defend themselves and create a new SCO-like action.

    Is it pragmatic to take that risk?

  95. Don't be confused by Anonymous Coward · · Score: 0

    > I think it is purely common sense for the community
    > to reject patches supplied by Novell

    It's more than sensible, it's now a necessity. Legitimate GPL'd software distributors should consider certifying their code to be *not from Novell*.

    1. Re:Don't be confused by kimvette · · Score: 1

      The resulting "Hello world" program won't make such a great platform then. That's pretty much what Linux would become.

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
  96. 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 sumdumass · · Score: 1

      The problrem is that the Linux kernel isn't going GPL3 any time soon. Elements of the Kernel can dual license but then the GPL2 licenes negates anything in the GPL3 as far as futher restrictions.

      So, even with GPL3, it isn't going to be hard for novel to stay in comliance, all they have to do is fork all GPL3 only code or sit back and watch the linux kernel lose all the FSF code that goes GPL3 only.

      So, once again for everyone who didn't see this comming, If the linux kernel (wich it looks like it is) stays GPL2, GPL3 elements cannot be used in it unless they carry a GPL2 license also. When someone takes either GPL2 code and places GPL3 on it, they are in violation as well as when GPL3 code includes GPL2 code in it. The two licenses are incompatible and cannot co exist on the same project/product!

      Beside that, I'm going to asume that novel would challenge the GPL3 in court. It is incompatible with GPL2 in both the spirit of GPL2 and the license it's self. You cannot use GPL3 with GPL2 Even if it is two minor parts of code that make a single program. I think What might happen is that either someone pulls thier product out of one part of linux or they change the license to GPL3 on things they don't have the right to. Also, with GPL3 being incompatible with GPL2, it looks like it is a binding legal contract would have been unethicly altered. The mioght even succesfully claim the the GPL3 ins't compatible with the GPL3.

      And that Is how I suspect they could not only invalidate the GPL3 but possibly recoup costs from anyone who up and changed it. Of course novel has never said anything close to courts and this is just my guess of opne way it can be handled. But if anything like this happens, it won't untill GPL3 is forced in us in march.

      At minimum, it is going to split the counity and possibly implode it. So i would look more the the behind the sceenes motivation of the GPL3 and how it coincides with microsoft releasing a new poerating system as well as novel making a deal that basicly favors them moving back to riding no top of windows again. It would really suck if someone gave up the fight, got paid off, and all the reast of us are putting on our nike sneakers, drinking the purple coolaid, and talking about great it will be when hailbob piks us up.

    3. Re:It's not about the money by dorkygeek · · Score: 1

      The problrem is that the Linux kernel isn't going GPL3 any time soon. Elements of the Kernel can dual license but then the GPL2 licenes negates anything in the GPL3 as far as futher restrictions.

      So, even with GPL3, it isn't going to be hard for novel to stay in comliance, all they have to do is fork all GPL3 only code or sit back and watch the linux kernel lose all the FSF code that goes GPL3 only.

      Maybe not the kernel itself, but you are forgetting that the basic toolchain is a product of FSF, which also holds the copyright to their entire codebase, and is going to switch to GPLv3.

      So either Novell sticks with the current version of the toolchain, or they have to fork it before the switch to GPLv3, and maintain it by themselves.

      --
      Windows is like decaf - it tastes like the real thing, but it won't get you through the day.
    4. Re:It's not about the money by Anders+Andersson · · Score: 1

      Wouldn't a copyright violation be plagarism?

      It would indeed; that's closer to the original meaning of "plagiarism" than a patent violation is today.

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

      It may be 100% your own work, but that doesn't mean it's 100% your own property. Of course, Microsoft would be the last to admit there is a difference, stressing the significance of their intellectual property while conveniently ignoring who did the work that somehow became Microsoft's property. The general public, not versed in the intricacies of intellectual property law, may assume that the software was developed by Microsoft employees, or at least legally purchased by Microsoft, and that this "Linux" thing may simply contain portions of such code, hence the Linux crowd being branded as "plagiarists" even if they may not currently be aware of their infringements.

      The notion that Microsoft could, as a matter of law, be the owner of exclusive rights to a product that hasn't even been seen in Redmond, much less been developed by Microsoft, is probably as alien to most outsiders as the possibility that the government could by default be the legal owner of your family photos. I do wonder when the revelation of what the law actually means will hit the fan, and in what form.

    5. Re:It's not about the money by KDR_11k · · Score: 1

      The beauty of the GPL is that Novell could just take the latest GPL2 version and fork it. Though I expect that to be done by someone anyway considering all the disputes over GPL2 vs. 3.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    6. Re:It's not about the money by NickFortune · · Score: 1

      The problrem is that the Linux kernel isn't going GPL3 any time soon. Elements of the Kernel can dual license but then the GPL2 licenes negates anything in the GPL3 as far as futher restrictions.

      Well, that remains to be seen. Certainly I think the odds of a GPLv3 kernel are a hell of a lot higher than they were before the Novell-Microsoft patent agreement.

      So, even with GPL3, it isn't going to be hard for novel to stay in comliance, all they have to do is fork all GPL3 only code or sit back and watch the linux kernel lose all the FSF code that goes GPL3 only.

      That's taking quite a lot for granted as well. Even if there is a kernel fork, and I think that is probably inevitable now, the deciding factor will be which fork attracts the developers. Given that on the one hand we "free as in freedom", while on the other we have "give us your lunch money and my big friend promises not to beat you up", I think the v3 fork may well emerge as the main line. In which case Novell have to either strike out on their own, or else pay a lot of people to keep re-inventing wheels.

      Beside that, I'm going to asume that novel would challenge the GPL3 in court. It is incompatible with GPL2 in both the spirit of GPL2 and the license it's self.

      I've been thinking about that. It's not like anyone's going to be forced to licence new code under GPLv3, and the only ones who can change the licence of a GPLv2 codebase to add additional restrictions would be the copyright holder - creating in effect a new fork released under a new licence.

      So I can't see most use cases having a problem. I can imagine that some of the devs who signed over their copyright over to the FSF might make a case similar to the one you describe, but that isn't going to break GPLv3, although it might result in a few FSF packages being forced to remain under v2 while the Foundation chase up some hackers for a recode-from-scratch effort.

      The mioght even succesfully claim the the GPL3 ins't compatible with the GPL3.

      Go on then, how's that going to work? I could do with a good laugh.

      --
      Don't let THEM immanentize the Eschaton!
    7. 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
    8. Re:It's not about the money by sumdumass · · Score: 1

      Maybe not the kernel itself, but you are forgetting that the basic toolchain is a product of FSF, which also holds the copyright to their entire codebase, and is going to switch to GPLv3.
      Then that tool chain won't be in the linux kernel any more and the kernel will have to fork those projects. GPLv3 is incompatible with GPLv2 and cannot coexist in a project. So either the tool chain will move on to GPLv3 and not have a kernel, or the kernel will fork the tool chain when it moves to GPLv3 and find developers to maintain them. In that case, the tool chain won't have a kernel in distribution and will need to find develpoers willing to start over.

      Wich is going to be easier to maintain? the forked functioning products that went GPLv3 or the parts of the kernel they can bring over to GPLv3 and then build from scratch and maintian the rest?

      So either Novell sticks with the current version of the toolchain, or they have to fork it before the switch to GPLv3, and maintain it by themselves.
      This is almost funny. But you see, Novel doesn't exist in a vacume. The linux kernel is likley going to stay GPLv2 for a good long time. Linus has been pretty adimant on that. He has it has a GPLv2 only clause in the license and it is GPLv2 only. If part of it is different, they they can go. So to think that Novel is going to be the lone wolf sitting on a cliff throwing money over the side for no good reason it a bit rediculous.

      As for me, I'm with linus on this, A software license has no right telling a company what it can or cannot do in other aspects of the companies business. The GPLv3 makes all the poisonous, viral fud spread around actualy apear to be true. It sickens me to think about it. It as if they are saying you are as free as i say you are. This is wrong!
    9. Re:It's not about the money by sumdumass · · Score: 1

      Well, that remains to be seen. Certainly I think the odds of a GPLv3 kernel are a hell of a lot higher than they were before the Novell-Microsoft patent agreement.

      I think the odds are comletley reversed. But linux has always stated that the kernel is GPLv2 only. It cannot be subjected to the later versions clause. Parts of it might be but the vast majority isn't. Also linus doesn't seem to really care about novel becoming friends with microsoft. A can't seem to find a negetive reference for any of the Kernel developers I know of.

      And the seems to be mostly a FSF problems. It is as if they are on recess in third grade and looked at novel and microsoft playing and said "wha wha what! I thought we were friends, You cannot be friends with microsoft and us at the same time. So we don't like you anymore if your going to hang out with Microsoft. Whats it going to be novel, Us or them". It is sad really.

      That's taking quite a lot for granted as well. Even if there is a kernel fork, and I think that is probably inevitable now, the deciding factor will be which fork attracts the developers. Given that on the one hand we "free as in freedom", while on the other we have "give us your lunch money and my big friend promises not to beat you up", I think the v3 fork may well emerge as the main line. In which case Novell have to either strike out on their own, or else pay a lot of people to keep re-inventing wheels.

      I think the GPLv2 version will attract the develpoers. The reasons why? Well, it will already be a working version so less develpoers are needed. The kernel Is presently GPLv2 only but some parts of it are "and later versions". This also means that a lot more work will be neccesary to get even a working GPLv3 linux based kernel. That is unless all the copyright holder can be contacted and pursuaded to switch. I see that as a big hurdle too.

      And don't think for a second that people won't be watching for code not apropriatly rewriten and it would be easy to get around the GPLv2 only code. It will be easy to replicate a lot of it but it won't be easy to replicate it and keep al the interfunctioality or smoothness of it without becoming a dirivitive work and subject to the GPLv2 only license. And any enemy of linux on either side could file a suite on someones behalf and claim harm and then linux will spend it's remainder of it's existance in the courts.

      This doesn't even address the possibility of Most companies not wanting to pick up on the GPLv3 untill it is forced on them. If they sell thier business, they would have to remove all the pattented or propriatary software from any system that has a GPLv3 on it because ot would place them in violation of the distribution and passing rigths on clauses. Could you imagine building a sucessful compay up that uses free software and the sale (because of retirment or whatever) consitutes a violation of the license that helped you succedd if you had to some closed source app to get around a limitation of the opensourced alternative.

      I've been thinking about that. It's not like anyone's going to be forced to licence new code under GPLv3, and the only ones who can change the licence of a GPLv2 codebase to add additional restrictions would be the copyright holder - creating in effect a new fork released under a new licence.

      If it plays out like that and the copy right holder makes the changes then yes. But if it is anything in the GPLv2 or later versions, I see court days ahead. It might not even be novel who does it either, It could be microsoft who claims they released something under the GPL and the GPLv3 isn't in the spirit of the GPLv2 and effectivly stop all the "or leter version" clause from being used.

      Go on then, how's that going to work? I could do with a good laugh.

      Get ready to laugh then. Lawers and law have a long history of proving something that isn't there. More likl

    10. Re:It's not about the money by dorkygeek · · Score: 1

      The GNU basic tools don't have anything to do with the kernel... Or is your cp a kernel module?

      Apart from that, you get it completely wrong with regard to the GPL! Not the GPL is evil. Companies are. And the GPLv3 is trying to prevent evil companies from harming free software.

      --
      Windows is like decaf - it tastes like the real thing, but it won't get you through the day.
    11. Re:It's not about the money by sumdumass · · Score: 1

      In with. whatever. The point is, when i download a kernel, it is distributed with CP and everything else. When I comile it and have a working kernel, CP is there. When they change the GPL version, the older version will still be there. The tools will need to be installed seperatly or they will be v2 in the kernel. Any distribution will not be able to install GPLv3 tools in a v2 kernel and distribute it. And this is for the same reasons nvidia had the problem with their closed source drivers. Look into the discusion on that and you will see the conection.

      And I hope your actualy joking about the companies are evil bit.

    12. Re:It's not about the money by NickFortune · · Score: 1

      The chance of the kernel going GPLv3 is still 0% - it never included the "newer version" provision that some use with the GPLv2.

      That's a serious obstacle, but I don't think it's necessarily a show-stopper.

      What you'd need is consensus among the majority of active devs, and the willingness to audit the code and work out which bits they owned free and clear. Then it's a recode operation for areas that are either of unknown provenance, or for which the submitter refuses to adopt GPLv3.

      It would be an utter pain, and I'd guess it would set kernel development back by a year or so. On the other hand, it would be a good chance to clean out some hoary old cruft from the darker corners of the kernel, and it would help lay to rest SCO style FUD once and for all. To say nothing of putting an end to Novell's playground bully tactics.

      Personally I think Linus' stand on DRM is more likely to be the insurmountable obstacle.

      --
      Don't let THEM immanentize the Eschaton!
    13. Re:It's not about the money by init100 · · Score: 1

      You obviously haven't got the faintest idea about what you are talking about.

      The point is, when i download a kernel, it is distributed with CP and everything else.

      It is?

      When I comile it and have a working kernel, CP is there.

      So you have a special version of cp that somehow exists inside the kernel?

      Just for your information, the cp that the GP is referring to is the userspace program for copying files. It has nothing to do with the kernel, except using the standard syscall interface that all other applications use. Having a GPLv2 kernel and GPLv3 GNU software on the same system will be fine, just as it is completely fine having proprietary software on a system with a GPLv2 kernel.

    14. Re:It's not about the money by init100 · · Score: 1

      Get a clue!

      Then that tool chain won't be in the linux kernel any more and the kernel will have to fork those projects.

      The toolchain isn't in the kernel, and it never was. Do you even know what is meant by the toolchain? The toolchain means the GNU tools, such as gcc, ld, libtool, automake, autoconf, etc. You might also include the coreutils and other userspace tools into the term.

    15. Re:It's not about the money by init100 · · Score: 1

      You cannot be friends with microsoft and us at the same time. So we don't like you anymore if your going to hang out with Microsoft. Whats it going to be novel, Us or them". It is sad really.

      I can't see why the should be friendly with Microsoft. Novell signed an agreement with Microsoft that enabled Microsoft to claim with increased credibility that Linux (and possibly other F/OSS) violates Microsoft patents. It has the power to make the rest of the F/OSS community second rate citizens, since the only supplier of F/OSS without a patent threat would be Novell. I can hardly see why the FSF would be friendly with Novell after such a backstabbing.

      Oh, by the way: I cannot see why forking the kernel would be of any importance. The kernel can stay GPLv2 while the userland software is migrated to the GPLv3. It would work just fine, except for Novell, who would not be able to use the GPLv3 versions of the userland software.

    16. Re:It's not about the money by NickFortune · · Score: 1

      Also linus doesn't seem to really care about novel becoming friends with microsoft.

      Nor should he. But this isn't about Microsoft and Novell holding hands; it's about Microsoft's implied threat to sue anyone who doesn't give Novell money.

      And the seems to be mostly a FSF problems. It is as if they are on recess in third grade and looked at novel and microsoft playing and said "wha wha what! I thought we were friends, You cannot be friends with microsoft and us at the same time. So we don't like you anymore if your going to hang out with Microsoft. Whats it going to be novel, Us or them". It is sad really.

      Nope. It's about downstream rights. Let me explain:

      Novell are saying if you buy this software from us, you get extra rights - in this case the right not to be sued my Microsoft for alleged patent violations. Which would still be OK, except that the rights thus granted can't be passed on. If I buy a copy of SUSE and then give it to you, you don't get the anti-barratry coverage - you have to give money to Novell for that.

      See, one of the obvious attacks against the GPL has always been patents. You put code in a project for which you hold a patent, and then say "you can read the source code all you like, but if you want to run the program you also need to licence my patent". In which case you could charge exorbitant fees and try and kill a project dead, or charge just enough to stop the non-commercial distros packaging it, or just pick and choose who you allowed to use the package. Add a dozen more such contributions from other developers, and enough submarine patents that removing the code becomes non-trivial, and you can kill any open source project dead like this.

      So, to guard against this happening, the GPLv2 stipulates that by distributing software under that licence, you also licence any applicable patents you may hold, and that like the copyright licence, the patent licence is automatically sub-licenced should any downstream recipient of the software distribute it themselves.

      Now the Microsoft-Novell agreement sidesteps this neatly. And it's a loophole we really need to close. Let's try an example

      Suppose I have NickFortune OpenCode Inc, and I write software. To attract developers I release the code under the GPL, and bundle support into the sales agreement. Pretty conventional - no harm there. Even if I take out a patent on the core ideas, still no problem.

      But let's suppose that I have a second company NickFortune Patents Inc. Then I can grant the patent to NF:PI; NF:OCI still distribute the code, but can't grant patent rights because they do not control them. NF:PI make a binding agreement not to sue customers of NF:OCI, but the agreement doesn't apply to anyone to whom my customers might distribute the software.

      So in that scenario, we're back where we were with GPLv2, sans patent clause. It's a loophole and it needs to be plugged. At core, that's what the fuss is about.

      --
      Don't let THEM immanentize the Eschaton!
    17. Re:It's not about the money by sumdumass · · Score: 1
      Yea, I obviously don't have any idea of what your talking about. Of course the CP is for copying files. And the kernels I use have it there when I download and istall the it. It is that simple, the GPLv3 forces the inclusion of all system libraries in the source release for coresponding code. It attempts to convey it license coverage to the license of the libraries and it is in conflict with the GPLv2.

      Here is the example giving in the GPLv3

      Corresponding Source includes scripts used to control those activities, interface definition files associated with the program source files, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by complex data communication or control flow between those subprograms and other parts of the work.
      This has an exception of providing the source for files generaly availible already. But since the tool chain is clearly there to use kernel libraries and and extend the kernel functions, I don't see who it can be seperated. Further more, the GP{Lv3 recognizes this and tryes to get around it by making the claim

      The Corresponding Source may include portions which do not formally state this License as their license, but qualify under section 7 for inclusion in a work under this License.
      Wich is find and dandy but the GPLv2 doesn't have such provision in that. It doesn't even goe further then the preferable version to make changed to the work. You cannot further restric the licensed stuff covered by GPLv2. It becomes incompatible. So in essence, you build something based one a GPLv2 work and release it GPLv3, you are violating the GPLv2 license. You don't believe me? watch this go to court when it is pulled on someone with Deep pockets (novel funded by microsoft?)

      Now, if novel can't distribute the tool chain because it is going GPLv3 and their not changing from gplv2, then I don't see how anyone can. The end result is that no one can. Unless the flaw in the theory is that NOvell can continue to distributing it but people are claiing they can't because they want to spread fud or something. In that case, what is the point of this if it is all smoke and mirrors?

      The GPLv3 it to encompasing and overly braod. It is attempting to run the companies it is trying to attract. Further, the though of it trying to manupulate other licenses by incorperating as much of the neccesary componants as possible into the definition of the source code to effectivle place the patten and Tivo protections on it is somewhat scary. But who would know that the previous license had enough forsite to stop viral contamination like this by adding a clause that boils down to not bing able to place further restrictions on it.
    18. Re:It's not about the money by init100 · · Score: 1

      Of course the CP is for copying files. And the kernels I use have it there when I download and istall the it.

      You mean that your kernel source contains the source of cp, to use our previous example? I just checked the source of the latest vanilla kernel (2.6.19.2) and it is nowhere to be found.

      It is that simple, the GPLv3 forces the inclusion of all system libraries in the source release for coresponding code.

      And you conveniently just happened to not read the following?

      The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, except its System Libraries, and except general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.

      IANAL (are you?), but I interpret that as "cp and other generally available free tools, such as gcc, gmake, etc, does not have to be included in the source code".

      It attempts to convey it license coverage to the license of the libraries and it is in conflict with the GPLv2.

      I really don't understand what you mean. The kernel is and will stay GPLv2, and thus it will not be bound by this paragraph, regardless of interpretation.

      You cannot further restric the licensed stuff covered by GPLv2. It becomes incompatible. So in essence, you build something based one a GPLv2 work and release it GPLv3, you are violating the GPLv2 license. You don't believe me?

      In this, I agree. The GPLv3 will add new restrictions that cannot be accepted by the GPLv2, and code licensed under the GPLv2 but doesn't include the "or a later version" part (such as the kernel) cannot be used in a GPLv3 program.

      Now, if novel can't distribute the tool chain because it is going GPLv3 and their not changing from gplv2, then I don't see how anyone can.

      Why? The reason why Novell would not be able to distribute GPLv3 code is because of the patent agreement with Microsoft. Because the patent license provided by Microsoft to Novell's customers is non-redistributable, Novell runs afoul of the requirement that Novell's customers must be able to freely redistribute the patent license to everyone that they redistribute code to. Those that don't have such a patent agreement will not fall afoul of this part, and can continue to distribute the software.

    19. Re:It's not about the money by sumdumass · · Score: 1

      You mean that your kernel source contains the source of cp, to use our previous example? I just checked the source of the latest vanilla kernel (2.6.19.2) and it is nowhere to be found.

      I don't use the vanilla kernel. I use whatever kernel is distributed with my distro. The kernel packagse include the same functionaility as provided by the tool chain by default. But this point is pretty much useless, everyone knows that a kernel isn't able to do anything on it's own unless you have a way to interect with it. The tools provide one such way and under the GPLv3 license's all inclusive parts, it now becomes a dirivitive work. There is the problem.

      And you conveniently just happened to not read the following?

      No, i did not. And i didn't forget to read the example following that either

      For example, Corresponding Source includes scripts used to control those activities, interface definition files associated with the program source files, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by complex data communication or control flow between those subprograms and other parts of the work.

      This example of how that is supposed to be used shows exactly were we are. CP is specificly desinded to copy files from one location to another thru the use of subprograms built into the kernel. It cannot cover those programs if they GPLv2. But it isn't a matter of what the GPLv3 says in regurds to this, it is a matter of what the GPLv2 says. And it say that you cannot add further restrictions even if the license making the restrictions claim it is ok.

      IANAL (are you?), but I interpret that as "cp and other generally available free tools, such as gcc, gmake, etc, does not have to be included in the source code".

      sure, but only because of generaly availibility of them. The problem is when they are considered a covered work distributed together and the license of the other works do not allow the restrictions being plaed on them now.

      really don't understand what you mean. The kernel is and will stay GPLv2, and thus it will not be bound by this paragraph, regardless of interpretation.

      It attempt to place GPLv3 restrictions on GPLv2 code by including them in the definition of a covered work. If you were to use CP, you would need a way for it to do whatit does. If this way says you cannot place further restrictions on it as v3 attempts to do by considering it a covered work, then you cannot distribute them together.

      Why? The reason why Novell would not be able to distribute GPLv3 code is because of the patent agreement with Microsoft. Because the patent license provided by Microsoft to Novell's customers is non-redistributable, Novell runs afoul of the requirement that Novell's customers must be able to freely redistribute the patent license to everyone that they redistribute code to. Those that don't have such a patent agreement will not fall afoul of this part, and can continue to distribute the software.

      This is only true if Novell contribute something that is pattentable. It doesn't matter if someone else did because it beleived the text of the licens had been obeyed and are just passing the rights pased to them. The fact that they offer indemiification doesn't address anything they don't contribute. So this is a non issue unless they contribute something they cannot follow the license for.

      You see, all the rights to a GPLv3 program is refering to is the works covered and expresses by the programs license. Not something else you have. So if I was to place microsoft code into samba and novel redistributed it just like everyone else, Samba are the ones resonsible for making sure I had all the rights to do so, not Novell. then novel conveys all these right to the customers. The m

    20. Re:It's not about the money by mrchaotica · · Score: 1

      Wow, you really are "sumdumass!"

      The point is, when i download a kernel, it is distributed with CP and everything else.

      No, it's not. The kernel and the GNU file utilities (including cp) are entirely separate pieces of software. In fact, they are also separate from GCC, which is separate from X, which is separate from bash, which is separate from emacs, etc.

      When I comile[sic] it...

      With what? GCC, which is separate from the kernel?

      ...and have a working kernel, CP is there.

      cp is there because it and the rest of your operating system were there before you downloaded the new kernel. You can't download a kernel tar archive onto a completely blank PC and expect to be able to do anything with it, you know!

      The tools will need to be installed seperatly[sic] or they will be v2 in the kernel. Any distribution will not be able to install GPLv3 tools in a v2 kernel and distribute it.

      These statements make no sense. There's no such thing as "installing tools in the kernel," regardless of what license they use. Tools (like cp) are separate programs that run in the userland.

      And this is for the same reasons nvidia had the problem with their closed source drivers.

      No, it's not the same reason at all. nVidia's drivers actually are installed into the kernel, which is the opposite of the situation here.

      Anyway, the point people are trying to make here is that even though Novell could continue distributing the kernel itself and old versions of GNU software (e.g. cp, GCC, emacs, etc.), the FSF will see to it that the GPL prevents it from legally distributing new versions of GNU software. Because of this, SuSE will be stuck with more and more obsolete versions, and will become less and less viable as a product.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    21. Re:It's not about the money by mrchaotica · · Score: 1

      And the seems to be mostly a FSF problems. It is as if they are on recess in third grade and looked at novel and microsoft playing and said "wha wha what! I thought we were friends, You cannot be friends with microsoft and us at the same time. So we don't like you anymore if your going to hang out with Microsoft. Whats it going to be novel, Us or them". It is sad really.

      No, it's not. It's an issue of the fact that the GPL is supposed to ensure that anyone who distributes the software gives everyone the same rights they had. Novell's patent agreement breaks this arrangement, so the FSF is right to fix the license to prevent such abuses in the future.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  97. Re:WARNING PLEASE DONT READ by master0ne · · Score: 1

    ive heard of chain letters, and chain email, and even more recently chain im's and text messages, but chain slashdot comments, well i guess it goes with the maturity level of the community, but i personally would be to scared to post one for fear one of the zealots would look up my ip, hack my isp, get my address and rape and kill me for being so stupid....

    --
    Noone writes jokes in base 13!
  98. How novell though they'd get away with this? by flaming-opus · · Score: 1

    Why can't they.
    I've been on both sides of a FSF legal threat, and I can tell you their bark is worse than their bite. The fact of the matter is that the FSF does the "right" thing, and licenses all of their software under the GPL. Thus they give up a lot of their ability to do anything about it when someone uses that code in a way the FSF doesn't like. They want their cake and to eat it too. I don't see the FSF being able to do a lot to stop Novell.

    Furthermore, from a market perspective, Novell doesn't care if a bunch of slashdot readers get upset. Slashdot readers don't pay for Linux support services. They're not losing any sales by pissing off the slashdot crowd. They want to get into the corporate server-room, and that DOES mean playing well with Windows. Note, I did not say playing well with Microsoft. The technology, however, needs to provide services to predominantly Windows clients running CIFS, and IE. For good or ill, that's the reality of Novell's market, and they may have signed a pact with the devil to get there.

    1. Re:How novell though they'd get away with this? by isaac · · Score: 1

      Furthermore, from a market perspective, Novell doesn't care if a bunch of slashdot readers get upset. Slashdot readers don't pay for Linux support services. They're not losing any sales by pissing off the slashdot crowd.


      Speak for yourself. Some people here run tens of thousands of Linux hosts with vendor support contracts. Ignoring these issues is not in our self-interest insofar as we have a significant investment in Linux.

      -Isaac

      --
      I am not a lawyer, and this is not legal advice. For Entertainment Purposes Only.
    2. Re:How novell though they'd get away with this? by bky1701 · · Score: 1

      Furthermore, from a market perspective, Novell doesn't care if a bunch of slashdot readers get upset. Slashdot readers don't pay for Linux support services. They're not losing any sales by pissing off the slashdot crowd.
      But they are Linux developers. I forsee a major lack of suse packages if things keep up.
    3. Re:How novell though they'd get away with this? by Anonymous Coward · · Score: 0

      Furthermore, from a market perspective, Novell doesn't care if a bunch of slashdot readers get upset. Slashdot readers don't pay for Linux support services. They're not losing any sales by pissing off the slashdot crowd.

      But this isn't true at all, isn't it. I work at a company often mentioned on Slashdot with a market capital in the tens of billions. We cut Red Hat a very large check every year for support contracts, and although I'm not the one signing those checks, the fact that we are large Red Hat customers is significantly due to my influence and recommendations.

      And oh yeah, I am a slashdot reader that for all intents and purposes pays for support services. Big ones.

    4. Re:How novell though they'd get away with this? by Anonymous Coward · · Score: 0

      My apologies for lamely replying to the wrong post. Obviously I wasn't replying to you, but the GP.

    5. Re:How novell though they'd get away with this? by PHPfanboy · · Score: 1

      You are IBM and I claim my $100. I win! I win!

      --
      29 mpg. YMMV.
    6. Re:How novell though they'd get away with this? by PHPfanboy · · Score: 1

      In fact, now that I figured that out, this seems to make a lot of sense. Once I heard Sam Palmisano talking about how they were pushing Linux for the desktop to get Microsoft (whose Windows killed OS/2). IBM and Red Hat are long time buddy buddy. Microsoft is wasting IBM money via their funding of SCO to keep IBM in court and cast aspersions on IP and indemnification. Microsoft going with the beleaguered Novell to checkmate IBM on desktops starts to make a whole bunch of sense. Sound familiar? Start your engines for SCO v.2....

      --
      29 mpg. YMMV.
    7. Re:How novell though they'd get away with this? by Anonymous Coward · · Score: 0

      No, it's actually not IBM. We're big, but not quite that big.

      We're also not in bed with Red Hat like IBM is, which means that there is no real political factor in my company's choice of Linux vendor. My influence is based on the criteria I deem important, and technical criteria is just one part of the overall decision. Red Hat simply has their shit together, and Novell demonstrably has not.

      I post as AC and don't identify the company because, well, you know how big companies are. They don't like anyone whose job isn't a spokesperson to be speaking publically about the company, and I rather like my job. (And my job has nothing to do with PR.) But I did want to reply to say that there are no political factors or directives from above that would mandate (or even affect) the distribution of Linux we put in our data centers. This is significant because it means that people below the C-levels have a very strong influence with technical decisions such as choice of Linux vendor. And these people, such as myself, do follow with a watchful eye the goings on of companies like Novell. And some of these people, myself again included, consider themselves contributing community members and value the freedom aspects ingrained in the spirit of the GPL.

    8. Re:How novell though they'd get away with this? by init100 · · Score: 1

      IBM uses SUSE IIRC. We just received a big new IBM computer, and guess what, it came with SUSE.

  99. Free, Until We Say It's Not by MSTCrow5429 · · Score: 1

    Eh, so much for free software. It's only free until the open-source zealots go nutty over any of their pet peeves, such as Microsoft.

    --
    Slashdot: Playing Favorites Since 1997
  100. 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.

    1. Re:GPL restricts freedom by Anonymous Coward · · Score: 0

      Your post is mostly FUD.

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

      1) anyone is free to use GPL'd software. GPL only restricts redistribution, it does not restrict use in any way. BSD fan boys are also welcome.

      2) you are allowed to make money selling GPL'd software and you don't have to release source code unless requested by your paying customers.

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

      And expect someone to "steal" your code, make a DRM using software for some Trusted Computing Platform and then drive you off the market with lawsuits / EEE tactics/ etc. We are talking about commercial software, right? Because if we aren't, there's no need to worry about the restrictions of the GPL.

  101. Suse 10.2 is a load of SHIT by Anonymous Coward · · Score: 0

    Suse is worthless. I had to hunt down updates manually, and even then, I couldn't find them.

    Load up Fedora Core 6, the yum updates from fedorafaq, change /etc/yum.conf to keep the cache, and hit "yum -y upgrade". Then I burn all those updates to DVD. If I need to install on another machine, I've got every single friggin' update .rpm. "rpm -Uvh --nodeps --force".

    1. Minimal work.
    2. Minimal hassle.
    3. Fedora doesn't hit the swap as quickly. Actually frees god damn physical memory when I start closing programs. I can edit /etc/sysconfig/iptables without having to hunt down scripts in convoluted places. The only bad thing is the root path, because it's not linked to fucking /sbin, but that makes two necessary fixes counting yum. Not bad at all.
    4. FUCK Suse. Fuck them right in the Microsoft, the M$, and the MSFT. One right after another with no consideration for yeast infection. It wasn't bad with 10.0, but it's gone to shit.

  102. 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 ericlondaits · · Score: 1

      Perhaps I'm not understanding it right (I truly mean this)... but this is the way I see it:

      - If Novell is right on the patent issue, then nobody can distribute certain parts of Linux under the GPL.

      - If Novell is wrong on the patent issue, even if they believe they are and their understanding of the GPL is wrong, then everybody (even Novell) is free to distribute all of Linux under the GPL.

      I don't see how Novell would be solely unable to distribute because of their beliefs. I can't think of any laws that only apply if you believe in them.

      --
      As a Slashdot discussion grows longer, the probability of an analogy involving cars approaches one.
    3. 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.

    4. Re:Your Confused by Antique+Geekmeister · · Score: 1

      No, GPL has little to do with patents. Patents are a very separate set of intellectual property law, and are not universal. GPL is a copyright agreement: as such, if Novell "enhances" their tools with Microsoft tools or under a Microsoft license agreement is not allowed to publish its SuSE modifications to GPL software, it can't publish the GPL software.

      That's very serious, and is likely to happen with hardware drivers, XML, file-sharing tools, and cross-platform software tools based on Microsoft patents.

    5. Re:Your Confused by juergen · · Score: 1

      IANAL. And additionally, which law, which country? Some laws have harsher or lighter penalities, depending if you broke them knowingly. The GPL, which is a license and not law, may be seen as requiring a belief of you, the belief of free redristributability. Without that, you are not allowed to distribute at all.

      There is a concept called dirty hands, which means you can't (or it is harder to) sue if you are doing something wrong first hand (knowingly). Now Novell has a contract with MS, according to which it can't distribute GPL software. Or at least some people think so and are pondering legal action.

      * If they are proven wrong, we'll know by extension the MS contract is fangless, since it doesn't impede the GPL and thus free sharing.

      * If they are proven right, Novell has to stop distributing Linux. But for everyone else it is as uncertain as now if MS's alleged patents are valid or enforceable. At least MS will have to try and enforce them on a case by case basis.

      * If this doesn't go to court it is still good FUD, which I believe is the most likely outcome.

      And as I pointed out, this is not only a legal issue. Even if Novell is in the clear legally, having Novell as the only safe provider of GPL software is against the very core spirit of this license, and clearly dangerous to the OSS community. Therefore, a need for action.

    6. Re:Your Confused by budgenator · · Score: 1

      here's the way I understand it, under the GPL you can't distribute if the terms your distributing under are more restrictive to your user than what you received the software under; so while Novel has no patent indemnity from Microsoft (it's the customers of Novel who are idemnifide) so Novel's customers can have the binary, have they source and can actually use the software; but if the customer's distribute to other's the customer's aren't given the same indemity from Microsoft and they can only have the source, the binary but can't actually use the software legally.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    7. Re:Your Confused by mrchaotica · · Score: 1

      I don't see how Novell would be solely unable to distribute because of their beliefs.

      If Novell believes that the Linux kernel is encumbered by patents, then it must believe that it no longer has the right to distribute the kernel (because of section 7 of the GPL). Since it is continuing to distribute, it's deliberately choosing to engage in activities that it believes violates the license. In my opinion this constitutes an act in bad faith and should be actionable regardless of the fact of whether the kernel is actually patent encumbered or not.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  103. Standard industry practice by rohan972 · · Score: 1

    It is standard industry practice to enforce license conditions on code you supply. The Novell/MS deal is an obvious attempt to get around the GPL via a loophole. Closing the loophole is not an extraodinary action. Nobody would raise an eyebrow except that the FSF requires GPL compliance rather than license fees.

  104. big win for Novell by mrtexe · · Score: 1

    I realize the article is probable FUD, but just in case that it's not...

    If the FSF does block Novell from using GNU tools with GPLv3, Novell will use its UNIX license to trump the GPL. Novell will fork everything they care about and bring it all under its own license. FSF will die on the vine. Novell will prosper.

    The FSF is no match for Novell--not in a lawyer to lawyer contest, and not in a developer to developer contest. I guess if Stallman wants his dream to die, he can choose to play with fire.

  105. Tortious interference? by rippa242 · · Score: 1

    As written, this make it sound as if the FSF were conspiring to commit tortious interference with Novell's extant praxis... I suspect they're a bit too savvy for it to be this simple. There does not appear to be any GPLv2 7 problem, because there's no license, just a covenant not to sue. Novell could, at this point, hand-on-heart say they are unaware of any royalties due on the code they distribute ( 2(b)). This gives rise to an interesting situation -- given the Novell/uSoft covenant, Novell, were Microsoft to bring successful suit against another and be awarded royalties, would become the ONLY entity that COULD distribute these works. Something tells me that with the lawyer count at uSoft and Novell not being small, they're only too-well aware of the value of the agreement as written, save the bad press (and costing Novell the services of one Jeremy Allison).

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

    1. Re:FUD, Really? F at best ;) by dorkygeek · · Score: 1

      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.

      No. The FSF is considering to modify wordage for the yet unreleased GPLv3 to prevent Novell or any other parties from selling code released under GPLv3 alongside such an agreement as Novell did with Microsoft.

      The FSF is not, I repeat, not trying or even thinking about stopping Novell from selling any code released under GPLv2. As RMS states:

      "... the Novell/Microsoft patent agreement is not in violation of the GPL version 2."
      --
      Windows is like decaf - it tastes like the real thing, but it won't get you through the day.
    2. Re:FUD, Really? F at best ;) by Anonymous Coward · · Score: 0

      Woah, woah, woah, dorkygeek. Don't use logic when talking to a fanboy that also thinks he understands law, but clearly does not.

      Who wants to bet that Famatra has used IANAL in one of his posts in the past, or that he has at least considered it?

  107. There is some clarification... by Anonymous Coward · · Score: 0

    ...in a e-mail interview with Eben Moglen at Linux Watch. The essence, as I understand it, is "Novell may not be able to distribute software released under GPL v3 because of the deal with Microsoft" wich is hardly any real news for us. Reuters is delivering business news and for them the reason is a little less important... what is important is the effect of a decision.

  108. This is the problem with the GPL by raddan · · Score: 1

    It's not really free. The whole point of free software is to allow people to do what they want with their machines. People may do unethical things with that software, and we may have a legitimate reason to stop that unethical behavior, but software's license should not be the tool to do that job. Software should just do it's job well, and allow us to modify it when we need to. It's like Stallman forgot why he got into this business in the first place.

    "But software which OpenBSD uses and redistributes must be free to all (be they people or companies), for any purpose they wish to use it, including modification, use, peeing on, or even integration into baby mulching machines or atomic bombs to be dropped on Australia." -- Theo de Raadt

  109. Buncha babies by Anonymous Coward · · Score: 0

    This is further proof (as though more were needed) that the FSF and OSS advocates in general are a bunch of immature little babies. Novell can't be "banned" from distributing Linux. How do you stop someone from distributing a FREE operating system?

    And Linux people wonder why nobody ever takes them seriously! This sort of political infighting is rampant in the OSS world, and it shows. Linux isn't going anywhere until the OSS "community" can stop stabbing each other in the back long enough to present a united front to the world. You bloody fools laugh and point fingers at Microsoft (making sure to slur the name somehow) for shipping as many as EIGHT versions of Windows Vista, but pray tell me, how many versions of Linux are there? And what are their differences? Hm? The fact that such schizophrenia exists at all tells me there are major, major problems with Linux. If the advocates can't even agree on a "distro" then how can I be sure ANYthing you say worth hearing?

  110. Spin doctoring by sacrilicious · · Score: 1
    Is this a measured response, or an over-reaction...?

    Or is even this response less than the response that is deserved, despite being perhaps the extent of what the FSF is legally capable of doing?

    --
    - First they ignore you, then they laugh at you, then ???, then profit.
  111. FSF got their antennas crossed. by RoadWarriorX · · Score: 1
    The FSF is starting to lose focus of the real issue. Companies are creating and buying patents as a strategy against their competitors. It's not only Microsoft. IBM does it. HP does it. Novell does it. Whether you like it or not, they are all competitors of free software. They may publicly promote free and open source software, but that is really only one of their business strategies. They have one goal: make money. Whether SUSE (notice I did not say "Novell"), Red Hat, Mandriva, etc enter into non-aggression aggreements is really irrelevent. The Linux distributors, the so-called "defenders of free software" also have a common goal: make money. They are little different though. The distributors ones making concessions that balance the business aspects of software versus the ethics of software to achieve their primary goal: make money. So, when the FSF and the community bitch and moan about these agreements, the tend to jump on some sort of bandwagon that distracts them from their goals. FSF: fight the real issue. Fight all of the obvious patents. Fight to copyrighting / patenting of public API's. Keep fighting real, tangable, and provable violations of the GPL.

    If the businesses that are promoting free and open source software are entering into non-aggression agreeements, so what? Nothing is preventing the FSF in entering agreements of their own. For example, maybe they can enter into agreements with distributors to help the FSF with lobbying funds to address the patent issue. I do not see many news stories on that, do I FSF? Look at your campaigns page. Nothing about patents there, either. Even the high priority projects show nothing about this issue. In this old eWeek article, Lawyers Weigh In on Linux Patent Threat, shows that the FSF has at least acknowledged the issue:

    [regarding the use of patent litigation insurance] Bradley M. Kuhn, executive director of the Free Software Foundation (FSF) added that the news "isn't a surprise."

    "The U.S. Patent Office has been granting patents at an alarming rate. In fact, it's likely difficult today to write any software program--be it free software or proprietary--from scratch that does not exercise the teachings of some existing software patent in the U.S.A."

    Moreover, the "FSF has long warned that software patents were very dangerous not only to free software, but to the software industry as a whole. We firmly believe that the world would be a much better place without software patents," Kuhn said.


    If that is the case, then why isn't the actually fighting patents the top priority of the FSF? It is the biggest threat to use of free software, don't you think?
    1. Re:FSF got their antennas crossed. by RoadWarriorX · · Score: 1

      Someone pointed out to me that the FSF does mention something about patents on their campaigns page. My bad. However, it is focus toward a petition in the United Kingdom. I personally do not believe in petitioning myself, so I may have selectively ignored it. I believe more in lobbying because that's what the politicians really listen to.

  112. 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! $-)

    1. Re:Section 7 and explicit claims by init100 · · Score: 1

      I wonder why GPLv2 isn't considered sufficient to block the Novell-Microsoft deal, while GPLv3 will be.

      I guess (IANAL) that it might be because the patent license is not given from Novell to their customers, but directly from Microsoft to Novell's customers. This does not seem to be covered by the patent license wording in the GPLv2, while it will be in the GPLv3.

    2. Re:Section 7 and explicit claims by DaveV1.0 · · Score: 1

      Because Novell can create new programs that it does not have to put under the GPL. That includes binary blobs for the kernel. If Novell make a new SMB compatible program that is not a derivative of SAMBA but rather Microsoft, then Novell does not violate the GPL.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    3. Re:Section 7 and explicit claims by Anders+Andersson · · Score: 1

      I guess (IANAL) that it might be because the patent license is not given from Novell to their customers, but directly from Microsoft to Novell's customers. This does not seem to be covered by the patent license wording in the GPLv2, while it will be in the GPLv3.

      That's what everybody (including RMS) seem to be saying. Yet, what exactly is that supposedly flawed "patent license wording" in GPLv2? Let's look at the first paragraph of Section 7 again (with its three sentences enumerated):

      1. 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.
      2. 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.
      3. 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 first sentence is not limited to "patent issues", but explicitely mentions also "any other reason". I believe the issue is the phrasing "conditions are imposed on you" (here referring to Novell). However, the sentence stops short of spelling out what you are required to do (or not to do); it merely says you are not "excused" from the conditions of the license.

      I believe the second sentence is the crucial one: "If you cannot distribute so as to satisfy [...] then as a consequence you may not distribute the Program at all." Here, "you" still refers to Novell, but this sentence doesn't even mention any patent issues.

      The third sentence merely provides a clarifying example involving a patent license, and it's thus not significant when interpreting the wordings of the first two sentences. However, I find it interesting that there is no mention of who receives the patent license, but the text instead reads "a patent license would not permit".

      It's of course good that the language will be clarified in GPLv3, but I'm not convinced that GPLv2 is dead yet. The text must have some meaning, and if it really means you are free to distribute GPL software to people who are unable to redistribute it legally thanks in part to your own actions, then there are problems besides patent law we should worry about.

      So, would it be ok for Novell to say to Microsoft "The GPL prevents us from enforcing any restrictions on copying against our customers' customers, but if you can find some restrictions to enforce on either your own or our behalf, you should be in the clear, since you are not party to the license agreement (and we will look the other way)"?

      Of course, nothing would have prevented Microsoft from going after Novell's customers' customers even without the deal with Novell, but in that case Novell's hands would have been clean. Novell might even have offered indemnification to downstream recipients of its code and challenged Microsoft's claims, something this deal appearantly prevents - or does it? Novell has dirty hands by getting into the deal, and therefore they cannot claim they have had no influence on Microsoft's assertions of patent rights in GPL software they distribute in accordance with the deal.

      If Novell distributes GPL software they believe cannot be freely redistributed by their recipients, is Novell distributing so as to satisfy its obligations under the GPL? This is, I think, what sentence 2 above requires of them.

      "Here is the source code - catch! - Oh, your hands were tied? That's just too bad, but we did provide the source to you, technically speaking..." ;-)

  113. Novell tried to get around the GPL. by Animats · · Score: 1

    Novell and Microsoft tried to find a way around the GPL, via a patent cross-licensing deal. This may backfire. "The stock is likely to trade down before the Foundation discloses its ruling as investors stay on the sidelines to avoid the worst-case scenario, analysts said."

    What will probably happen is that Novell agrees not to use Microsoft patents in GPL code. Which is what should happen.

  114. Legal wrangling. by ZwJGR · · Score: 1

    The FSF are not doing themselves any favours by making people nervous. They would be better off:
    a) Demanding to know details on the MS-Novell contract/agreement, specifically in terms of possible litigation/GPL-violation possibilities.
    b) Waiting for the some MS IP-restricted code to find its way into GPL code, and then demand that either MSs IP restrictions of that code are removed, or that it is removed.
    c) Warning Novell QUIETLY not to try any funny business. (Probably not going to happen and not very effective)
    As for the Open Source Community, they can simply ignore Novell and concentrate their efforts somewhere else. Projects like Samba, as quoted previously, aren't happy with Novell, they can simply forget about them and concentrate on writing good code instead.
    All of this legal wrangling is pointless unless somebody has actually, obviously and blatantly broken a properly big and binding legal agreement, and the ton of legal bricks are poised to fall and deprive them of a dimension.
    Ultimately, nitpicking over commas and implied subtleties in license agreements should be reserved for fat coorporations, who charge big money for bloated, expensive software. Not Linux. Not GPL. Not FOSS.

    --
    There is no psychiatrist in the world like a puppy licking your face - Ben Williams
  115. So much for "FOSS" by Illbay · · Score: 1

    Apparently, if you're a corporation despised by hippies, you don't have freedom.

    --
    Any technology distinguishable from magic is insufficiently advanced.
  116. Fine Line by gone.fishing · · Score: 1

    I'll freely admit that I have not paid much attention to the Novell/Microsoft agreement and what it means to the Free Software Movement in general or to Linux in particular. My observations here have less to do with the particulars of the agreement than they have to do with general observations about Open Source, Free Software, Novell and Microsoft.

    First, we all love to hate Microsoft while many of us generally admire the direction that Novell has taken in the past several years. Remember several years ago that Novell was a has-been company that was seen as being on the verge of death's door. Rather than doing the SCO thing, they decided to jump in to Open Source in a big way. The Novell brand on open source products was generally seen as a good thing. While Novell did not have the mega-bucks of someone like IBM, it did have a solid reputation to lend to the industry.

    Novell, as a company has profit as its motive, it has sharholders to satisfy and if it is to continue as an entity it has to find ways to position itself in the market in such a manner that it can make some money. Today very few companies in the computing industry can ignore Microsoft. At the very least they have to offer compatibility with the Microsoft products and at best, they want to offer true integration with Microsoft products while offering something that Microsoft itself isn't delivering. It is after all these niche markets where smaller companies can really deliver something of value to a market that will pay for it.

    Novell's "deal with the devil" was probably something that they felt compelled to do. In their eyes, they probably felt that the "something" that they got out of the deal was much better than the "nothing" that they would have gotten without the deal. I would imagine that they also probably hoped that the deal would allow them to be able to escape some direct competition from Microsoft if and when they deliver the products born from this rather odd union.

    Let us not forget that Microsoft itself has on occasion packaged open-source tools and utilities with their products and that the Open Source community has delevoped tools and utilities that have allowed Microsoft products to better integrate with things like Linux, Apache, and Samba.

    If Microsoft's arrangment with Novell in some way actually affects free software, I would hope it would be in a good way. If Microsoft uses some of Novell's code that uses some open source code, then by virtue of the licenses, it would seem to me that Microsoft would either be required to eliminate the open source code or, be required to incorporate the requirements of the license into their product. In other words, Microsoft would have to play by the GPL rules.

    While Linux and other open source operating systems pose a competitive risk to Microsoft's operating systems, it does not mean that it is always going to be in Microsoft's best interests to simply ignore the features the competition offers. Access to some of these features may very well be what Microsoft sees itself getting out of the Novell/Microsoft arrangment. I don't know, I have not paid that much attention but I would think that some tight closed-source Microsoft integration with things found in open source operating systems (and networking components) may prove to be a symbiotic benefit. How would it hurt Linux if Microsoft offered near-native access to the Riser file system or fully integrated with some other O/S and networking features? It seems to me that if they did this, it may make open-source more acceptable to a larger market.

  117. So? by Anonymous Coward · · Score: 0

    Novell can still participate in the Open Source revolution.

    They can start shipping the SuSE configs/software on top of FreeBSD.

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

  119. "haha" tag is right by The+Bungi · · Score: 1

    Of course these articles are always tagged with the "haha" in-joke, but in this case that's more than apropos. I really hope the FSF goes ahead with this, because that will be the end of whatever credibility it has left. "Free as in freedom", indeed.

  120. What GPL 2 only software are you talking about? by tepples · · Score: 1

    Not if it is a GPL3 license. GPL2 or even 1 is incompatible with a GPL3 licensed product.

    Apart from the Linux kernel, most popular software under GPL 2 is multi-licensed under GPL >= 2.

    It covers things a software license shouldn't cover, like what other software you use and th distribution of encryption and signing keys.

    If I want to develop bug fixes for the GNU software in my TiVo DVR, how do I test these bug fixes?

    1. Re:What GPL 2 only software are you talking about? by sumdumass · · Score: 1

      Apart from the Linux kernel, most popular software under GPL 2 is multi-licensed under GPL >= 2
      Sure. And that software can be taken to GPLv3 whether the copyrigth owner likes it or not. But GPLv3 code cannot be distributed with GPLv2 code. The two licenses are not compatible with each other. So most likely, what will happen is they will either continue to be dual licensed or forked. But without a kernel, i guess the question remaining might be why fork it if it can't be used any more?

      f I want to develop bug fixes for the GNU software in my TiVo DVR, how do I test these bug fixes?
      Is it GNU software or opensource software?I guess it doesn't matter for the pupose of this question.

      First, you download the source. Next, you patch it. Now thas simple isn't it? Ahh i know, your going to get uptight because you purchased a device that does a specific thing for a specific purpose in a specific way and was manufactured for those specific reasons and don't have the ability to change it easily. Well, buy something that can be changed. TIVO doesn't manufactur any of the parts so they are availible somewhere at some costs. If you want to save money, you could just replece the part that causes it to check for a signature. but then you wouldn't have a TIVO, you wouldhave a computer of some sorts using TIVO parts in it.

      You could also just make/buy/beg/barrow/steal an emulator of some sorts. Test your patches and then submit them to TIVO for inclusion in their next firmware upgrade. Either way, I see it as a non problem because you bought a devioce that does a specific thing in a specific way. A software license shouldn't regulat how hardware does something. That is just selfish and bullheadedness.

      More importantly, you knew all this when buying the device and I see your fracturing of the Free _Software_ comunity so you can force a manufacturer make a device and sell it your way instead of the companies way is stupid and childish. You and people like you are destroying the ability for a comunity to function and in effect are placing it years behind the competition because of your own personal greed. And this greed isn't based on any ideals or anything close, it is so you don't have to spend more money after getting something that is designed to work a certain way and for a certain purpose to work your way. I hope the cryes of "look at me now, I'm ubber kool" never get expressed near me. I don't think i could be held to civil reactions. I think some people need to grow up a bit. You could start too. You definatly wouldn't complain to the lightbulb manufacturer because you had an issue trying to get radio reception on the 100 wat soft white you just bought. .

      Good day!
    2. Re:What GPL 2 only software are you talking about? by mrchaotica · · Score: 1

      But GPLv3 code cannot be distributed with GPLv2 code. The two licenses are not compatible with each other. So most likely, what will happen is they will either continue to be dual licensed or forked. But without a kernel, i guess the question remaining might be why fork it if it can't be used any more?

      GPLv3 code cannot be distributed with GPLv2[-only] code in the same piece of software. In contrast, distributing separate GPLv2 and v3 software in the same package (as would be the case in a Linux distribution shipping a v2 kernel and a v3 GCC) is perfectly OK because it constitutes "mere aggregation."

      In other words, your last sentence is wrong because the forked software can be used. To further demonstrate your error, if you were right then stuff like Cygwin couldn't legally exist because its GPL license would conflict with the proprietary license of the NT kernel. Yet Cygwin does exist, so you must be wrong. QED.

      Ahh i know, your going to get uptight because you purchased a device that does a specific thing for a specific purpose in a specific way and was manufactured for those specific reasons and don't have the ability to change it easily. Well, buy something that can be changed.

      The fact that the software used in the TiVo is GPL is supposed to ensure that it can be changed. The intent of the FSF and most other people who license their software under the GPL is that if someone (like TiVo) wants to make a closed product, then they should write their own damn software without the benefit of the community.

      A software license shouldn't regulat[sic] how hardware does something. That is just selfish and bullheadedness.

      No, that's just the conditions under which the software is distributed. If TiVo doesn't like it, then TiVo can simply choose not to use GPL software!

      Here's the bottom line: if someone distributes GPL software, they're supposed to give everyone else the same rights they had. TiVo and Novell aren't doing this, so they should lose their right to distribute the software. It's that simple.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  121. FSF publicity department in a nutshell by DF5JT · · Score: 1

    1. www.fsf.org:

      Created by johns
    Last modified 2007-01-16 12:43 PM

    Why do we need read Reuters redacted newsfart instead of some hard information on their website? The whole website is pretty useless when it comes to finding out what current political affairs are hot within the scope of fsf's audience.

    2. Eben Moglen

    http://emoglen.law.columbia.edu/blog

    Last entry 26 Sep 2006

    Where is the place I can read his actual thoughts on this matter? Again, just Reuters?

    Sheesh.

  122. I have.....a cunning plan. And a turnip! by Real1tyCzech · · Score: 0

    Our subtle plan is unfolding exactly as predicted, Baldrick.

    You see, we join forces with the one who's done the most for the community, the community shuns them, and everything falls to pieces.

    This, Baldrick, is how we will destroy Linux once and for all. By offering them the interoperability they've always demanded.

    Muahahahahhahaa......

  123. To all of the FSF's advocates left on this site... by petrus4 · · Score: 1

    ...I hope you're paying attention.

    When what I've been saying about the FSF for years now is vindicated with them taking steps like this, I'm very interested in hearing how you claim that you were correct in telling me that contrary to my assertion, Stallman is in fact NOT a Stalinist megalomaniac.

    If the FSF go ahead with this, and if it sticks, that will end for certain anything I for one have to do with Linux permanently. I also hope to God that Linus is watching this, and that this prompts him to finally seek a way to cut all ties with the FSF once and for all.

    Everything that has been said...the account of Ulrich Drepper, the interview with Bradley Kuhn here...it has now been vindicated. The Free Software Foundation is finally laid bare as the genuinely evil, repressive organisation that I have long known it to be.

    Richard Stallman, some of us know who and what you really are. Free as in Do As I Say.

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

    1. Re:This would be atni-free-software, wouldn't it? by borgheron · · Score: 1

      Not really. The problem is that the Novell patent license guarantees that only people who are SuSE customers cannot be sued. According to the GPL, you must grant any patent rights to ALL users, not to a specific subset.

      In short, this has nothing to do with the fact that they made a deal with Microsoft and it has everything to do with the legal effect of the deal.

      GJC

      --
      Gregory Casamento
      ## Chief Maintainer for GNUstep
    2. Re:This would be atni-free-software, wouldn't it? by petrus4 · · Score: 0, Flamebait

      The whole point of Free Software is freedom - enforced by the GPL.

      There's a contradiction contained in that statement. See if you can figure out what it is.

      Perhaps there may be trademark issues, but restricting someone from doing what they want with GPL software would make Stallman quite the hypocrite.

      It wouldn't make him one...it'd simply reveal in less than the usually controvertible terms just how much of one he really is.

    3. Re:This would be atni-free-software, wouldn't it? by Geoffreyerffoeg · · Score: 1

      restricting someone from doing what they want with GPL software

      Like selling it in binary form only and refusing to provide the source or even acknowledge it's GPL'd?

      The GPL is a viral freedom license. It makes sure that all redistributions and derivatives are as Free as the original.

      In this case, the restriction would be that Novell would be trying to combine it with patented code and call the result GPL'd. This is kinda possible with GPLv2, but it won't be possible with GPLv3, and the new GNU utilities will be released under v3 only; therefore, Novell could only sell their patented additions to older, probably stagnant GNU code.

      Indeed, like the license wanted, the v2 code will always be free to redistribute under v2. But it's not going to be the latest.

  125. Don't Throw Out the Baby with the Bathwater by Anonymous Coward · · Score: 0

    Obviously, the FSF doesn't care about the commercial viability of Linux. The FSF is doing more to harm the commercial viability of Linux than is the Novell / Microsoft deal. Balkanization is obviously a potential problem, and it is the FSF rather than Novell/Microsoft that is the biggest danger.

    What is ethically wrong with a mutual agreement not to bring a lawsuit against each other's customers?

    For instance, were I to start a company, and I enter into a legal agreement which says "I won't sue your customers", what is ethically wrong with that?

    Somebody enlighten me please on the basis of a moral argument; that means without concrete reference to Novell or Microsoft.

    If GPLv3 prevents me from promising not to sue, I guess I won't use any GPLv3-licensed software. Hopefully I won't have to move away from Linux, but if I do, hello Solaris and/or BSD. Hopefully Linus will stick to his guns and ensure that the Kernel continues to be GPLv2. Hopefully there will be high-quality distributions that are not GPLv3.

    Floss advocates in general hate it when people raise legal uncertainty issues as an argument against Linux, saying it is just the product of anti-Linux fudsters.

    Linux has continued to flourish despite the SCO legal challenge, largely due to the skillful defense mounted by IBM and the general environment of credibility that goes along with that. Guess what, I don't think IBM or any other Linux friendly company with pockets of similar depth will be able to save Linux from the FSF.

    The largest impediment that exists right now to further adoption of Linux isn't a competing technology or a competing company, it is the legal issues surrounding Linux. The FSF will set Linux adoption in the enterprise back a long, long way, if not totally killing it, if they create major legal problems for a large and prominent Linux distributor. To bad the FSF creates legal problems rather than solves legal problems.

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

  127. Protection rackets, money flow, and inflation by Anders+Andersson · · Score: 1

    True enough that Novell has eliminated the risk only for their customers. The trouble is Novell can not negotiate for the whole community they can only negotiate for themselves and in this case for their customers.

    If my neighbour were to pay protection money to the mafia, I would want no part of it; I'd require him to leave my neighbourhood for putting the rest of us in danger. We don't want Novell or anybody else to pay protection money on behalf of everyone to somebody who doesn't deserve it, much like we don't want the government to give in to some airplane hijacker's demands and give him a million dollars plus a refuel; that only results in more hijackings. The community doesn't need collective "protection" from perceived legal threats, when we can simply ask our legislature to remove the ground from under those threats. You take out insurances against things neither you nor the insurance agent can predict, not against frivolous demands made by the insurance agent or against well-known consequences of the law.

    I still look at the flow of money. It is from MS to Novell. Why would MS pay Novell for Novell's customers right to use their patents? Seems that the "insurer" is paying the insured in this case. Not your typical "protection money" scheme.

    Who says "payment" has to be made in cash? Novell and Microsoft made a deal where both parties agreed to contribute. Among other things, Novell contributed a commitment not to sue Microsoft's customers, just as Microsoft promised not to sue Novell's. Why would those two commitments be valued to exactly the same price? Microsoft ended up giving Novell some change to cover the difference. If you return a malfunctioning TV set to the store within the warranty period, but agree to buy a cheaper model instead and receive the difference as a credit worth $20, would you say the "seller" pays you to accept the new TV?

    And the mafia guy could very well grant a hefty "rebate" to the first buyer of his fire insurance, simply to be able to point at one happy "customer" when selling the same insurance to his neighbours (without the rebate).

    To me the ideal solution would be for the Linux community to "buy up" or have contributed a number of patents for integration into Linux. Then the community has a patent portfolio to protect them against MS or other large companies who may want to sue for patent infringement. That is how the corporations use their patents in most cases, defensively.

    Patents are like paper money, in that there is a potentially infinite supply of them. Where the Federal Reserve (or your corresponding national entity) could find reason to print more banknotes, the Patent Office issues new patents at the request of businesses. However, if the "currency" thus issued doesn't match up with something of value being held by either office, the result is inflation. If we engage in a virtual landgrab, trying to buy the "rights" to everything that is scribbled down on a piece of paper, there will be no shortage of scribblings covering gradually tinier portions of this virtual territory. Some critics of the patent system argue that this is what we are doing already today. Since free software is usually being distributed without demands for monetary compensation, where are we going to find the money to pay for all those patents? Do you expect us to outspend big business, like the USA outspent the USSR in much the same fashion during the cold war?

    1. Re:Protection rackets, money flow, and inflation by pgk2 · · Score: 1

      You choose to use the inflamatory term "protection money". Most people would call it insurance or risk allocation. Most people pay for car insurance yet those who don't view those who do as increasing their risk or cost. Additionally, as a group there are many in the Linux community that already have patents that could/should be contributed. It would be best for the community to band together and in this effort. Though I am sure the issue is that different companies have different levels of patents in their technology. Novell, as an older company, has a whole bucket of them. To me the better path would be to lobby Novell to contribute their patents into the community and have the community counterclaim MS if and when they sue a Linux vendor or user. The community will just need to determine how to allocate the "insurance" among its members. I would note that MS is not invincible. Over the last 10 years many companies have gotten MS to settle anti-trust and patent claims. I just think it is a better path to keep Novell within the community and determine how to turn that into the broader community.

    2. Re:Protection rackets, money flow, and inflation by Anders+Andersson · · Score: 1

      Most people pay for car insurance yet those who don't view those who do as increasing their risk or cost.

      This is because car accidents usually happen for other reasons than insurance agents working overtime to disable the brakes of cars belonging to people who don't pay for car insurance.

      At least with fire insurance, there is a real possibility that a fire will happen due to a real accident rather than because of a paid arsonist who isn't caught or identified. This is not so with litigation. Nobody is ever sued "by accident", but it's always an intentional act on the part of an identified plaintiff. If the claims are unfounded, the plaintiff (rather than some insurance company) should bear the cost of litigation. If the claims are valid, however, the defendant should admit responsibility and pay up (if he has legal insurance, this is where it may kick in). In no way should the plaintiff be able to game the system to have the defendant pay "insurance" to him in order to protect against future litigation, without the claims ever being tested in court.

      Legally speaking, this is not an issue of what is "best for the community", but what the GPL actually means. Software authors have attached the GPL to their code in the hope that it will promote the sharing and further development of said code, and in doing so they have already decided what is best for the community, in their opinion. Novell does not have the right to change the terms of that license, and neither has the FSF nor anybody else, except the copyright holders. Even if the Microsoft-Novell deal were to be good for the community, its wording and implementation is not what the software authors are likely to have approved of, even if there may be a technical "loophole" in GPLv2.

      Novell is free to remain within the community, but it has chosen an unexpected path into unknown legal territory, and the community is unlikely to follow along just to keep Novell happy. If we accept Novell's position as "good", then we can expect a multitude of other companies to make similar deals, including those who have contributed nothing at all to the free software community, but simply want to make a quick buck out of the patent mess. The license must be interpreted in the same way regardless of who it applies to.

      I haven't contributed any significant code myself, so I have no right to ask for a reward. Still, if I identify a particular concept that is used in some software, patent it, and begin selling the "right" of using "my invention" to various commercial distributors of free software, would you advocate them paying up just to keep me within the "community"? I hope you would not, because if they were to pay, the community would be overrun by parasites like me in no time. Fortunately, I'm not that kind of a freerider. :-)

    3. Re:Protection rackets, money flow, and inflation by pgk2 · · Score: 1

      I don't understand your response about insurance agents disabling the brakes of other drivers. How is Novell disabling others brakes? All they have done is made their car safer and security sells, like a Volvo.

      Regardless, note my earlier comment about most large companies cross license patents. Often the ones that make out are smaller players that find a patent violation. A good example was the Soderblum(sp?) patent.

      I do not see where Novell has "changed" the GPL license one iota. They have done a separate agreement to protect their customers. Others are free to do the same or similar agreement. If you are arguing that they should not have done that and waited until MS sued one of their customers I respectfully disagree. The legal issue hanging over Novell, its customers and the whole community needs to be addressed to help drive adoption. Ideally the Linux vendors would go in to court and look for a declarative judgment on this whole ordeal. However, practically speaking, who would pay for this? That is my point, if there were lots of patents contributed to Linux and there was someone funding the legal process MS could not move.

      So, to me, Novell did the best thing they could, protect their customers. Unfortunately they can not protect the whole community.

    4. Re:Protection rackets, money flow, and inflation by SavvyPlayer · · Score: 1

      I don't understand your response about insurance agents disabling the brakes of other drivers. How is Novell disabling others brakes? All they have done is made their car safer and security sells, like a Volvo.
      I don't believe the protection racket analogy applies to Novell so much as Microsoft -- the concern of the Free Software community is this new precedent will raise the barriers to entry for smaller Linux vendors with smaller patent portfolios compared to that of Novell. Surely we can simply pretend the deal was never made, but once Microsoft cuts the brakes of one of RedHat's customers (in true MAFIAA style), the corporate board of virtually every organization running Linux will demand its vendors enter into similar arrangements with Microsoft. Well guess what, for those vendors that have no patent portfolio of their own, dollars will be flowing in the other direction vis-a-vis the Novell deal. Those vendors will be forced to raise the price of their respective offerings, which will have multiple repercussions:
      1. Those vendors with patent portfolios will be more attractively priced than those who don't.
      2. Those vendors without patent portfolios will be priced out of the market.
      3. Companies now investing in patent portfolios will have less incentive to lobby against a patent system from which they increasingly benefit.
      4. Members of the F/OSS community become increasingly disincented to contribute for fear they may in turn be held liable.
      None of these endgame scenarios are in the interest of the F/OSS community. This is of course uncharted territory and there may of course be options not yet understood that might prevent this (companies like IBM donating enough patents to the community that the community as a whole is 'protected' via MADD). The negative attention Microsoft might receive suing a F/OSS vendor might itself be enough to prevent it from following this path (perhaps I am being naive, but I can't imagine its best and brightest engineering talent tolerating such a move anyhow). Meanwhile, the charter of the FSF requires it to protect the interests of the community, which is exactly what it is doing (and what I pay it to do as a member).
    5. Re:Protection rackets, money flow, and inflation by pgk2 · · Score: 1
      That is my point, ideally the community would take this on and share the expense. That is what insurance is. The trouble is, insurance is something you pay to gain the protection it affords. Kind of violates the "free" principle.

      Conceptually it could be like real insurance, based upon the risk of a member needing its protection based upon a number of variables. Smaller companies would probably pay less with larger companies paying more in either expenses or contributions, i.e. patents contributed to the community.

      Regardless, I do not know how to solve this. I just do not think that Novell is bad and should be expelled for working to protect their customers. Of course this helps them sell more but the alternative is customers thinking that they would be sued.

    6. Re:Protection rackets, money flow, and inflation by SavvyPlayer · · Score: 1

      From what I've read this appears to have been an honest mistake and would agree that Novell should still be counted among the 'good guys'... but good guys can and do make mistakes. Novell entered into a contract that it can't simply walk away from considering contractual obligations, penalties etc. It needs to pull a rabbit out of a hat, soon.

  128. This isn't the end of the world - yet by Whuffo · · Score: 1
    If Novell loses the ability to distribute Linux because they've broken the terms of the GPL by including software with incompatible licensing - then so be it. There'd still be plenty of good Linux distributions available, and it wouldn't be hard at all to explain why their actions required the termination of their license to distribute.

    It wouldn't be sensible to allow them to continue. SCO isn't getting anywhere because they can't seem to find any of their code in Linux. But with Novell slipping Microsoft supplied IP into Linux little by little - when the next patsy sues the infringing code will be right there - right where they put it. They don't even need to insert the infringing code themselves; just roll out some useful / fancy bits of code (with undeclared Microsoft supplied IP inside) and let the community cross-pollinate them into multiple distributions.

    Microsoft is still holding onto their monopoly position - but there are some very smart people working there and they can see the writing on the wall. It's getting harder and harder for them to create new Windows versions and Linux distributions keep getting better and better. As their sales decline, they'll need to increase prices to maintain their margins - and more and more people will find the low / no cost alternative more to their liking. In the long term, Windows will fade away. Microsoft sees this and they're scared. They'll do ANYTHING they can to derail Linux, legal or not.

    They've tried FUD along with SCO and their ill-conceived lawsuits; it didn't work. This won't be the last attack against GPL software and they're watching and learning all the time. The next skirmish (Novell?) will pick up where SCO left off and they'll keep attacking until they win (highly unlikely) or die.

    What Microsoft can't overcome is that the Linux distributions are a joint product of the IT community. Not one company or one person but hundreds or thousands of programmers who have donated their time to the project. Not only are they outnumbered, but their enemy is also the target market for their products. It's a lose-lose situation - but they'll create much noise and distraction as they try to rewrite reality...

    1. Re:This isn't the end of the world - yet by petrus4 · · Score: 1

      If Novell loses the ability to distribute Linux because they've broken the terms of the GPL by including software with incompatible licensing - then so be it.

      You're assuming that they are infringing the GPL. That hasn't been proven. That isn't really all that important anyway.

      The real reason why the FSF want to do this is purely because Novell made a partnership with Microsoft, which the FSF doesn't like. I haven't seen any indication myself that Novell are any closer to violating the GPL now than they were before they made the agreement with MS; the issue that some people are having I think comes almost entirely from the Mafia-like noises Steve Ballmer has been making about Linux recently. The only reason why the FSF will want to allege that Novell *are* violating the GPL is because they need that in order to have grounds to ban (or try to ban, more specifically) Novell from distributing Linux.

      There is one fact of life that the Free Software Foundation is eventually going to have to accept...and that is that very few people among the non-autistic human population cares about what they think, and neither should they have to. The sole reason why they're really persuing this is because they want to be seen as an authority. The FSF want to force people to see them as important...because they well know that 99.9% of the population aren't willingly going to otherwise.

    2. Re:This isn't the end of the world - yet by arem-aref · · Score: 0

      without the free software foundation(richard stallman), there is no "linux", you god damned moron.

    3. Re:This isn't the end of the world - yet by petrus4 · · Score: 1

      I'm making arguments...sometimes fairly detailed ones. You're calling me names.

      I don't think I really need to say anything else.

    4. Re:This isn't the end of the world - yet by DaveV1.0 · · Score: 1

      This is false. Without Linus, there would be no Linux.

      Without RMS and the FSF, Linux would probably be Public Domain.

      Now, you ignorant dumbass, STFU and go read the history of Linux.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  129. Sue Me: +1, Helpful by Anonymous Coward · · Score: 0


    Read the GPL, morons.

    I can charge for the media in my distribution of ANY Linux as long as it has the GPL.

    Please do some research before you post these crap stories.

    Sincerely,
    Kilgore Trout

  130. The GPL ain't done... by Anonymous Coward · · Score: 0

    ...till Novell can't run.

  131. the deal, what it is by SQLz · · Score: 1

    Its a very long term plan to coral linux to just Novell, which will be bille as the "safe from IP violation verion of linux." Other distros/developers will be sued for patent violations, forcing large companies to adopt Novell. Once the dust settles, MS will turn on Novell and crush them, thereby eliminating linux from the market place.

  132. Sooo... by Creepy+Crawler · · Score: 1

    Its free..... Until you use it!!

    --
  133. Re:I'm Not Confused by Anonymous Coward · · Score: 0

    Under the GPL, if Novel releases MS IP, then Novel must Indemnify all recipients of that GPL'd code. This means that if MS takes you to court, Novel must defend you because if they don't, then you have the right to demand that Novel, the original violator, pay the settlement.

    Of course, at this point, Novel will loose any right to use any GPL'd software as the FSF can and should revoke the license due to Novel's stupidity in violating a basic element of the GPL to begin with.

    Note that there is no reason for Novel to release MS IP under anything except an MS Open Source License with the blessing of MS.

  134. Borrow what? by Anonymous Coward · · Score: 0

    What would Solaris borrow from the Linux kernel?
    IMHO, Linux would benefit more from borrowing,
    from Solaris: genuine realtime scheduling, for
    one thing; designed from the ground-up for SMP,
    so scales well.

  135. Caveat Emptor by KixAreForKids · · Score: 1

    Novell is merely engaging in a quaint, pre-GPL business practice; indemnifying their customers against potential legal issues even when they consider the probabilities remote. Novell hasn't licensed any particular MS IP for the distro, and nobody has claimed to find a specific potentially infringing Novell contribution, have they? So the risk is hypothetical for the moment. Outside of explicit agreements such as this, MS could claim that any other new contribution to open source software infringes on one of their patents, they don't have to do a deal with a contributor first. GPL doesn't indemnify its users for such action. All GPL will do is allow FSF to gang up on the same alleged infringer along with MS: can't you see the headline now? All Novell has done by this deal is add a bit of reassurance for their customers, and more power to them if they can get customers to pay for it. So I think that this whole brouhaha is open source community mass hysteria. No one who suspects Novell's contributions might be tainted needs to pick up their contributions -- let the buyer beware! Or maybe it's simply an attempt by the zealots to goad the mob into shunning a company which has traded with the enemy. Or maybe here's a glimpse of the iron beneath the FSF's velvet glove, asserting a right to regulate the business practices of commercial software licensed under GPL. Funny, they're not a bank, a national government or even the better business bureau. I thought it was "free" software. But, of course, IANAL.

  136. MOD UP!! by Bill,+Shooter+of+Bul · · Score: 1

    I think I might have to ignore any novel & microsoft stories. There is just so much bullSh*t about it flying around. Novell is not about to start putting in microsoft patents into its software. THEY cans still be sued by MS. Their customers can not. THe main point of the agreement from Novells perspective is the cooperation. MS has agreed to make its products more interopreable with novells. The current state of novell means that they can gpl these new interconectiosn to the Miscorsoft world. This whole deal will go down as MS biggest mistake. The new XML office version is the first product of this. think of it, an open standard that works with OO.org? I imagine the next step could very well be exchange. Exchange interaction would allow a company to slowly replace its Windows clients with linux. It would also make building a GPL exchange knockoff a lot easier. Too many people are hooked into this emotional pull of a potential MS lawsuit to see the real ramifications of this deal. MS cannot and will not sue anyone over linux. the EU still has them over a barrell and dems are comming back into power in the US. I'm sure the world governments would bring out the butcher knife if they attempted such a stunt. They have to play it safe. This is about the closest it can come to actually doing it.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  137. Re:To all of the FSF's advocates left on this site by arem-aref · · Score: 0

    you are an complete imbecile(: a person affected with moderate mental retardation).

  138. Re:Free software? Really? by arem-aref · · Score: 0

    maybe you should learn to read(4th grade english)

  139. quaint?! by Stu+Charlton · · Score: 1

    Novell is merely engaging in a quaint, pre-GPL business practice; indemnifying their customers against potential legal issues even when they consider the probabilities remote.

    Quaint?

    One of the major reasons that Linux is being adopted at an increasing rate is that large vendors such as IBM, HP, and Sun are offering blanket IP indemnity on Linux. They're not making specific deals with Microsoft, however, so I suppose it's less of a news item.

    --
    -Stu
  140. Indemnity is a big reason for FOSS adoption by Stu+Charlton · · Score: 1

    IBM, HP, Sun, etc. already offer broad IP indemnity for customers that use (vendor approved, often Redhat or Novell) Linux on their hardware. It wasn't news for them, and FSF isn't threatening them.

    It's ludicrous to punish Novell for doing a service for their customers that is intended to make them feel *safe* using Linux. The fact is that many large companies are frightened that they will be sued for patent infringment if they use OSS, especially Linux. Yes, a massive cry of outrage will happen if something like that ever occurs, but a) cornered software companies can be vicious and have tremendous staying power if they feel they have nothing to lose, see SCO; b) the more risk averse companies may fire the people that chose Linux and jettison it ASAP, dealing a blow to FOSS adoption in the enterprise.

    To mitigate their risks, some companies have very specific lists of approved OSS packages, vetted by lawyers for potential infringement claims. Open source Java toolkits may have less of a chance of patent infringement, so tend to be blessed more easily (and often are bundled with commercial app servers anyway, who may indemnify what's in the package, though only specific versions).

    The problem is that Microsoft claims patents on absurdly broad things -- filesystems (since disproven), memory management, etc. Non-technical legal departments may or may not explore these in detail -- the quick thing to do would to tell the CIO: "no Linux". Or they may scratch the surface of these patents and see them for the joke that many of them are. We know that Microsoft has already threatened large IT shops with possible patent suits in the future (under NDA, no les), and likely offered them indemnity. Few have taken them up on this, though it seems Novell was gullible enough to bite.

    --
    -Stu
  141. Novel != Linux by Anonymous Coward · · Score: 0

    When was it that Novel's sole reason for existance was selling linux. While there maybe no value to microsofts grant of patent immunity for Novels linux distribution. There is a lot of value for that immunity so far as it may affect the rest of novell's product line.

    Microsoft and Novell share a great deal of application space beyond base OS's.

  142. I was the parent and it would be narrowing "use" by Anonymous Coward · · Score: 0

    Use can mean
    1) running
    2) incorporating in your work
    EULAs claim they can restrict #1. GPL can't and says so explicitly. However, #2 is controlled by copyrights and if you lose your license you cannot do this. If you breech your EULA you may be able to get to court to get them to agree that #1 is not forbidden by copyright so is not controlled by the copyright holder. Nobody's managed to get that far yet. So we're only left (when concerning the breach of agreement) option 2.

    Novell can't do that.

    I don't see why you see a difference, though, once I explained that "running" isn't worth considering for two reasons: whether running code can be made illegal after purchase is undecided and for the purpose Novell need, running the code isn't what the want Linux for. Heck, they can use Windows Vista and STILL sell Linux. So that meaning of "use" isn't germane so saying they can still do this and are not bound to refrain is confusing the issue with irrelevancies.

    Aye?

  143. PLEASE MOD PARENT INSIGHTFUL by fritsd · · Score: 1

    I think I'm beginning to understand the issue now, and with us not having access to the actual text of the Novell-Microsoft deal, it's quite difficult to see through that thick fog :-)

    --
    To be, or not to be: isn't that quite logical, Slashdot Beta?
  144. Use the source, luke! by fritsd · · Score: 1
    Don't forget, you don't have to go for hearsay, because you have full access to the authoritative source:
    From the 2.6.15 source, file "COPYING":

    Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated. Linus Torvalds
    --
    To be, or not to be: isn't that quite logical, Slashdot Beta?
    1. Re:Use the source, luke! by kripkenstein · · Score: 1

      Yet, as mentioned elsewhere in this thread, Linus' statement that you quoted is of dubious legal standing. If a source file contains "GPL 2 or above", then which takes precedence - the license granted by the copyright owner of that file, or a claim made by Linus?

      IANAL, I don't know. But it seems to me that the copyright owner decides.

  145. Re:I was the parent and it would be narrowing "use by zotz · · Score: 1

    "Aye?"

    I know what you are saying, I can't agree with the wording and I think the three examples are different enough that you can object to the first two without objecting to the third.

    Well, in a nutshell. If you violate the GPL with respect to some particular code under the GPL, you lose the rights to do the things with the code that copyright law forbids but the license permits with respect to that same code.

    Is that clear enough and are we agreed on that?

    all the best,

    drew

    --
    FreeMusicPush If you want to see more Free Music made, listen to Free
  146. Total bung by Thomas+Charron · · Score: 1

    The FSF released this as a total FUD publicity stunt. The entire article SCREAMS fud. They seem to have the general opinion that anything released under the GPL is owned by the FSF, which it isn't. Some of it is, sure, but it sure as hell isn't Linux.

    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.

    SUPRISE! They already have a version of all of the FSF utilities they wish to use, and as they haven't violated the licence, you can't force feed them a change to the terms of the licence. Perfect way to setup the perfect fork situation.

    And the BIGGEST pile of DUNG in this FUDFEST by the FSF is!!!!

    There IS no version of Linux being released under the GPL3.

    --
    -- I'm the root of all that's evil, but you can call me cookie..
  147. Maybe this is what MS wants... by gmac63 · · Score: 1

    Has it occurred to anyone that a ban on Novell might be what MS wants: A weaker corporate Open Source alliance?

    "Jefferies & Co. analyst Katherine Egbert said Novell's business was likely to suffer if it was banned from using the new versions of Linux."

    Just a thought.

    --

    INSERT INTO comment VALUE('Doh!') WHERE user='you';
  148. I hate when this happens... by Vampyre_Dark · · Score: 0

    Linux just rolled a 6, but landed on a space that said take ten steps backwards!

  149. Operating system and aggregation exceptions by tepples · · Score: 1

    But GPLv3 code cannot be distributed with GPLv2 code.

    Yes it can, per the mere aggregation clause of both licenses. You just can't run GPL v2 code and GPL v3+ code in the same process. From GPL v2:

    In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

    See also the GPL and non-free software, clarification of "mere aggregation", and use of GPL software in a proprietary system from the GPL v2 FAQ. Likewise, from the latest draft of GPL v3:

    A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

    Furthermore, if you are referring to the combination of Linux with a GPL v3 application, then Linux itself is licensed under an explicit exception such that syscalls are not considered "combining" per the GPL. From the Linux license:

    NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work".

    The GPL v3 application is licensed under the operating system exception, which is worded as follows in the current draft:

    The "System Libraries" of an executable work include every subunit such that (a) the identical subunit is normally included as an adjunct in the distribution of either a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the object code runs, or a compiler used to produce the object code, or an object code interpreter used to run it, and (b) the subunit (aside from possible incidental extensions) serves only to enable use of the work with that system component or compiler or interpreter, or to implement a widely used or standard interface for which an implementation is available to the public in source code form.
    1. Re:Operating system and aggregation exceptions by sumdumass · · Score: 1
      And you are somewhat corect while at the same time wrong.

      The requirement for distibuting the source code under the GPLv3 includes

      Corresponding Source includes scripts used to control those activities, interface definition files associated with the program source files, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by complex data communication or control flow between those subprograms and other parts of the work.
      The GPLv3 is attempting to take ownership of the exception in the kernel license. But more importantly, IT is attampting to place GPLv3 restrictions on the system libraries. The gplv2 clearly states that you cannot place any further restrictions so you cannot cover them with the source code requirments of the GPLv3. Of course the GPLv3 attempts to get around it claiming "other licenses can exist" but it doesn't get around the fact that you cannot package the source for a GPLv2 product that is necesary for the covered work to run and distribute it witha more restrictive license.

      The GPLv3 is incompatible with v2. they havn't satisfied the ability for them to co exist and even though the GPLv3 defines an agregate program, it will still run into the same problem that Nvidia did when they first tried the linux driver thing. Placing GPLv3 code with GPLv2 and distributing it under GPLv3 violates the version 2 license and there is no way arouns it unless you remove it so far from the requiring functionality of the GPLv2 stuff that you basicly rewrote the program. Now, you probably could place the two on a cd and say "here you go, butyou couldn't fix them into a distibution that the user does one install an dends up with a co dependant version of both program.(co dependent is were one program won't function without the other)

      In the end, the kernel will stay v2, anything moving will be forked, trolls will come out from under the bridge with the sole purpose of litigating a fortune from anyone who dual licenses or forks for any reason. And they will be looking to see if the simularities of either version (GPLv3 or the forked v2) are simular enough to constitute copying and file a suite over it. We know one of these trolls very well, SCO and now we are trying to make enemies from another who just decided to be microsofts friend again. And if we look far enogh back, we will see that SCO would never have gone as far as theydid if it wasn't for MS funding. Now we are pissing off one of the other companies microsoft is funding. All because people want to use thier tivo as a general purpose computer.

      BTW, I see Tivo going into the court room over the GPLv3 too, They will content that they never sold a general purpose computer and the gplv3 states the reason for the anti tivo provisions is for a general purpose computer. when someone harrases them about GPLv3 violation. I'm looking forward to that one! the GPLv3 is just wrong.
    2. Re:Operating system and aggregation exceptions by tepples · · Score: 1

      Corresponding Source includes [...] interface definition files associated with the program source files, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by complex data communication or control flow between those subprograms and other parts of the work. The GPLv3 is attempting to take ownership of the exception in the kernel license. But more importantly, IT is attampting to place GPLv3 restrictions on the system libraries.

      O RLY? I saw the following (my emphasis):

      The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, except its System Libraries

      So as I read it, the System Libraries are explicitly excluded from the Corresponding Source.

      but it doesn't get around the fact that you cannot package the source for a GPLv2 product that is necesary for the covered work to run and distribute it witha more restrictive license.

      What you say is true, except when "a GPLv2 product that is necessary for the covered work to run" qualifies as System Libraries. The Linux kernel headers certainly qualify per my reading. Besides, GNU software should be written portably; Linux isn't "necessary for the covered work to run".

      The GPLv3 is incompatible with v2. they havn't satisfied the ability for them to co exist and even though the GPLv3 defines an agregate program, it will still run into the same problem that Nvidia did when they first tried the linux driver thing.

      That's because NVIDIA's driver code ran in the same process (that is, Kernel Mode) as Linux. Later NVIDIA drivers ran in a separate process.

      now we are trying to make enemies from another who just decided to be microsofts friend again.

      That depends on how the patent agreement (whose terms are a trade secret) defines "Novell's customers".

  150. 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 ]
  151. Re:Free software? Really? by init100 · · Score: 1

    They are going to say, "Why should some long hairs from Massachussets be able to disrupt my data center?

    Because you use their software, and your distributor have creatively sidestepped the license that this code is released under.

    I'm going to go with a product where there are market forces in place to give me some stability.

    Such as a monopoly. Fine, but don't come howling to me when Microsoft decides it is time for another round in the treadmill.

    FSF's goal is that no one sells code.

    Did you even read the license? Selling GPL software is fine, you just have to provide the source, and the source has to be licensed under the GPL too.

    But I've never thought GPL was "free". If your software is free, let me do whatever I want with it. Seriously. Don't tie in clauses preventing certain uses that go against your morals. If it's free, let it be free. Otherwise call it what it is, but don't use the word "free" to do that, since it's clearly not free in a "free to use however you want" way.

    And no country is free, because we are not free to kill other people. The GPL is free, in the sense that those restrictions it applies only serve to ensure the continued freedom of the program, including derivative works. The BSD is more free in that you can do almost anything you want with such code, but it is less free in that derivative works do not have to be free.

  152. About the words "Free" and "Freedom" by DaveV1.0 · · Score: 1

    "You keep using that word. I do not think it means what you think it means." - Inigo Montoya

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  153. super restrictions of the FSF by at1as · · Score: 1

    I want to know where those dicks at the FSF get off thinking they speak for the "community". Some of us in the community would like to see companies as well as individuals benefit from FOSS. Many of those companies invest a lot of resources back into the community, not only providing paid coders, but also a huge amount of marketting capital. Linux mind-share is an asset at much as code is. So Novell has a rather interesting new relationship with "the enemy" (which sounds very adolescent anyway). We have not seen any true evidence of negative impact nor does the agreement appear to go against the GPL. Stallman needs to chill the f*** out and stop thinking that the_community = RMS (assignment intentional). Sincerely, One of the Community

  154. How is RedHat any different. by HackerAce · · Score: 1

    RedHat has been selling a "value added" version of Linux for several years. Just because Novell has partnered with what some persons would consider the enemy does not make Novell any different than RedHat. And, at the end of the day what we all really want is to see a significant number of Linux installations on the desktop. So, if that means Microvele, or Novasoft, is installed why do I care?