Slashdot Mirror


Jeremy Allison Resigns From Novell In Protest

walterbyrd writes to alert us to word from groklaw.net that Jeremy Allison has turned in his resignation at Novell. "The legendary Jeremy Allison (of Samba fame) has resigned from Novell in protest over the Microsoft-Novell patent agreement, which he calls 'a mistake' that will be 'damaging to Novell's success in the future.' His main issue with the deal, though, is 'that even if it does not violate the letter of the license, it violates the intent of the GPL license the Samba code is released under, which is to treat all recipients of the code equally.' He leaves the company at the end of this month. He explained why in a message sent to several Novell email lists, and the message included his letter to management."

344 comments

  1. Excellent! by Scott+Lockwood · · Score: 4, Insightful

    Now if a few more people apply similar pressure. What I'd really like to see, is the Samba team officially pull support for Novell/SuSE, if not outright inform them they are in violation of the liscense, and their right to use the software is revoked.

    --
    But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    1. Re:Excellent! by dj961 · · Score: 0, Troll

      Uhg, people like you make me sad. Novell is not in violation of the GPL, sorry try again.

    2. Re:Excellent! by Attrition_cp · · Score: 3, Interesting

      I wonder if developers jumping ship was part of Microsoft's reason for wanting the deal. more disenfranchisement means less open source competition (you could say they'll move to greener pastures but some could just leave). I realize even if that was true it would be a huge monetary waste for Microsoft, but tin foil hats are cheap. No, not trolling. It's a boring workday and I can cook up any plots I like!

      --
      Touched By His Noodley Appendage.
    3. Re:Excellent! by Iphtashu+Fitz · · Score: 4, Insightful

      Can the Samba team do that? Samba is released under the GPL, and even though Novell may be violating the intent of the GPL it's not violating the actual license agreement itself. I don't think the Samba team can unilaterally tell Novell they no longer have the right to use Samba. I suppose they could release new versions under a modified GPL license that specifically excludes Novell, but Novell could still use the current version and modify it on their own. It'd just end up in a split of the Samba project - the full GPL'd version and the bastardized Novell/Microsoft hybrid.

    4. Re:Excellent! by GodInHell · · Score: 1

      Novell is not in violation of the GPL, sorry try again. Except many people (including Jeremy Allison) think they are.

      Have any argument to back up your bald asertion?

      -GiH

    5. Re:Excellent! by Scott+Lockwood · · Score: 2

      Knee jerk holier than thou reactions make the baby Jesus cry.

      You don't KNOW they're not in violation of the license. Intent is important. Clearly, they are not distributing the software any longer in a manor that is palatable to the people who write the code. That's a no-no. Also, they're trying for an end run around GPLv2, which is bad.

      Frankly, I'd like to see it go to court - I believe a case could be made that they are NOT fully compliant with the license. That, or I'd like to see Samba go GPLv3.

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    6. Re:Excellent! by omeg · · Score: 1

      They aren't violating the license. That's one of the key points of Allison's post; he says that even though Novell is not violating the GPL, under which Samba is released, it still is not upholding the true intent of the license. Whether or not you agree with that is up to you (I personally do), but nothing is really going to stop Novell from using it.

    7. Re:Excellent! by Anonymous Coward · · Score: 0, Flamebait

      Richard Stallman and Eben Moglen think they aren't. Since it's not going to end up in court... I win.

    8. Re:Excellent! by Billosaur · · Score: 1

      Well, they took a first step with this, but how much further will they be willing to go? What does SAMBA stand to lose if they lock out Novell?

      --
      GetOuttaMySpace - The Anti-Social Network
    9. Re:Excellent! by Anonymous Coward · · Score: 1, Insightful

      No, you are wrong. J. A. clearly says they are not. RTFA!

    10. Re:Excellent! by m0rph3us0 · · Score: 0, Troll

      The assertion is that Novell is in violation of the GPL. You can't assert or rather, can't prove that something isn't. JAINAL or more importantly JAINAJ (Jeremy Allison is not a Judge). If Novell is in violation of the GPL perhaps someone should setup something for resolving disputes of copyright and bring their case there.

    11. Re:Excellent! by AceJohnny · · Score: 2, Insightful
      It'd just end up in a split of the Samba project - the full GPL'd version and the bastardized Novell/Microsoft hybrid.


      The worst part is that the bastardized Novell/Microsoft hybrid would probably the best-working version. (Hey, who better than microsoft to know the backward-compatibility quirks of Samba/CIFS?)
      --
      Misleading titles? Inflammatory blurbs? Keep in mind that Slashdot is a tabloid.
    12. Re:Excellent! by bogaboga · · Score: 1, Insightful
      I wonder if developers jumping ship was part of Microsoft's reason for wanting the deal.

      It seems it was part of the strategy and so far, it appears to be working. Good for Microsoft.

      On the other hand, I wonder what Novell will ever to right with Open Source Software.

    13. Re:Excellent! by Eggplant62 · · Score: 5, Insightful

      Scott!!

      Yeah, I'm with you, pal. When I consider Steve Ballmer's comments regarding this deal, it stinks to high heaven. There's no way Novell or Microsoft will ever square this deal in my eyes in light of those patent threats made by the CEO of Microsoft. Novell's proper reaction should have been to turn right around and drop the deal once they heard what that creep was spouting. "Undisclosed balance sheet liability" my arse.

      No matter what Novell does, they still look to me to have been bullied into this agreement. Most likely MS came to Novell threatening legal action and this is how they settled it. We weren't inside, and we'll never know, but that's what this whole thing feels like to me.

    14. Re:Excellent! by GodInHell · · Score: 4, Insightful

      The assertion is that Novell is in violation of the GPL. You can't assert or rather, can't prove that something isn't. I didn't ask you to prove it, just to argue it. Arguments (as used in court) discuss questions of intent, meaning of text, possible conflicts, and proposed remedies.

      To the above ACs who feel that delcaring that Novell is not technically breaching the letter of the contract means that the contract is not breached, do some reading up on contracts. The words are open to interpretation - with the goal of divining the intent of the parties. Knowingly misconstruing the meaning of a contract to evade its obvious intent is a breach of contract - according to Englo-American juris prudence.


      -GiH

      Not a lawyer, just a student.

    15. Re:Excellent! by fudgefactor7 · · Score: 2, Insightful

      Novell now no longer needs Samba, with MS being their shiny new sugar-daddy. They'll just come out with something *like* Samba, but different, and proprietary (50% MS, 50% Novell), and it would probably work better than Samba does now...thus killing an otherwise excellent OSS program...and locking in more to MS's solutions...which is what MS wants. The only people that lose in this scenario is Samba and the OSS/GPL movement in general.

    16. Re:Excellent! by 10scjed · · Score: 1

      About Ballmer's statements, Novell has said, those balance sheet statements were "taken out of context"

      --
      --10scjed IANAL,AFAIK
    17. Re:Excellent! by Anonymous Coward · · Score: 2, Insightful

      What I'd really like to see, is the Samba team officially pull support for Novell/SuSE, if not outright inform them they are in violation of the liscense, and their right to use the software is revoked.

      Er, so basically, you want the Samba team to treat Novell differently to other recipients of the code... because Novell don't treat recipients of the code equally?

    18. Re:Excellent! by DragonWriter · · Score: 5, Insightful
      Can the Samba team do that? Samba is released under the GPL, and even though Novell may be violating the intent of the GPL it's not violating the actual license agreement itself.


      I'm not sure that's the case; certainly, Allison's position sounds as if it is that the deal violates at least the spirit and possibly the letter of the license. Certainly, a high profile group of suppliers of GPL software included in Novell's Linux offerings raising the specter of litigation and license violations over the deal would undermine the primary purpose and destroy the value of the deal, which was, after all, to help Novell sell its commercial Linux products by removing uncertainty associated with them stemming from the specter of litigation over the IP violations.

      If there is a cloud of GPL-related potential litigation seen surrounding Novell, all its done is traded one potential source of litigation for many potential sources of litigation.
    19. Re:Excellent! by Eggplant62 · · Score: 4, Interesting

      I don't care what Novell says. They're trying to smooth feathers is all. Go back and read the entire statement Ballmer made and tell me you didn't feel physically revolted by his words. I know I did.

    20. Re:Excellent! by Drantin · · Score: 1

      Would that even be a GPL compatible license with a restriction like that?

      --
      Actio personalis moritur cum persona. (Dead men don't sue)
    21. Re:Excellent! by m0rph3us0 · · Score: 0, Troll

      Thurgood Marshall just called, he'd wants to talk to you about the 14th Ammendment and the Southern Pacific Railroad.

    22. Re:Excellent! by 10scjed · · Score: 4, Insightful
      exactly, Novell is Microsoft these days, sharing PR and sales offices, and spreading FUD about potential infringement since they are in the unique position to benefit from it.

      Novell isn't using their patents/IP to FUD against open source, they are using their partner Microsoft's patents/IP to FUD against open source. A technicality perhaps, but still wholly unacceptable.

      --
      --10scjed IANAL,AFAIK
    23. Re:Excellent! by arth1 · · Score: 1
      No matter what Novell does, they still look to me to have been bullied into this agreement. Most likely MS came to Novell threatening legal action and this is how they settled it. We weren't inside, and we'll never know, but that's what this whole thing feels like to me.


      Hanlon's Razor[*] tells me that the Novell executives had no idea what they were doing.

      [*]: Never attribute to malice that which can be adequately explained by stupidity.
    24. Re:Excellent! by eno2001 · · Score: 5, Insightful

      This is what I predicted from the beginning. The goal here was fragmentation of the Linux development community. It looks like they could succeed. It's basic "divide and conquer" because there will be some developers who don't see much wrong with the deal and will support the Novell Microsoft deal and there will be others who will not. The ones who don't MAY start new forks/projects and join other distros, or... they may just move on to other things entirely. This ensures a two-tiered Linux world with crappy underdeveloped software in non-blessed distros (Gentoo, Debian, etc...) and second-rate (compared to Microsoft Windows solutions) software in the intentionally stunted Novell Suse Linux and anyone else who decides to sign on. Microsoft very likely wants Novell Linux to be as successful as Apple's Mac OS was pre-OS X. That is to say, "enough to stay alive and prove that there is competition but not alive enough to compete on Microsoft's turf in the profitable business markets".

      Microsoft couldn't care less if Apple Macs were all the rage in schools early on because that wasn't one of their markets. Schools aren't as comparatively profitable as businesses. Once Microsoft had conquered the business world, they then started paying attention to schools and libraries and took those markets away from Apple. If the Apple platform actually started to make major inroads in server rooms, office suites, groupware and provided a killer alternative to Exchange, MS would be actively trying to take them down a few pegs again. Many Linux distros are doing exactly that and that's why taking Linux down a few pegs is a necessity to MS. MS doesn't want Linux dead. They just want it to smell funny. Probably something like pee. (I keep doing that)

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    25. Re:Excellent! by lawpoop · · Score: 5, Insightful

      Now witness the genius of the GPL. If you distribute software you have derived from GPL'ed code, you must provide that source code to the public under the terms of the GPL.

      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code. Any improvements MS/Novell make to samba are guaranteed to become available to us, and they can never take it away.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    26. Re:Excellent! by 0xABADC0DA · · Score: 1, Insightful

      Sometimes in software like Samba the best code is written when developers don't know the exact specifications. If you say "make it share files and handle these special cases in Win2k, these ones in WinXP, these ones in Vista" then you are likely to get a solution that can only handle those bugs. But if you say "make it share files and oh yeah there are some special cases here's an example of some" then developers make the system with more flexibility.

      Programmers don't want to get stuck on some obscure file locking issue for instance and realize they have to rewrite 50k of code just to handle it. So the less they know about the gotchas the more error checking, hooks, and gestalt they put in. This gets really ugly though when there isn't a well-defined goal (ie 'filesharing with windows') because coders go crazy making it overly generic and flexible.

    27. Re:Excellent! by Amazing+Quantum+Man · · Score: 1

      As I recall, they specifically announced that they weren't pulling SCOX's license for Samba, so I doubt they'd do it for Novell, either.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    28. Re:Excellent! by Amazing+Quantum+Man · · Score: 3, Insightful

      he says that even though Novell is not violating the GPL, under which Samba is released, it still is not upholding the true intent of the license.

      No, that's not what he's saying. You're close, though. What he's saying is that even if Novell is not violating the GPL, under which Samba is released, it still is not upholding the true intent of the license.

      There's a difference. The actual statement is a hypothetical. Your version is an assertion.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    29. Re:Excellent! by garcia · · Score: 2, Insightful

      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code. Any improvements MS/Novell make to samba are guaranteed to become available to us, and they can never take it away.

      Then they'll just link to an external library that hides all the new functionality.

    30. Re:Excellent! by Scott+Lockwood · · Score: 1

      Fair is fair, after all. More importantly, I want to see them enforce the spirit of the agreement - treat them the SAME as you would anyone who violates the GPL.

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    31. Re:Excellent! by PinkPanther · · Score: 3, Informative
      you must provide that source code to the public
      Er....um...no.

      You must provide access to the source code to the person to whom you delivered your derived work. Nothing in the GPL says that you need to provide access to the public.

      You are correct that the genius is that distributing something that was under the GPL must be distributed under the GPL itself. Recursive genius, though some fudslingers call it viral genius.

      --
      It's a simple matter of complex programming.
    32. Re:Excellent! by Orange+Crush · · Score: 1
      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code.

      But would they even have to derive anything from Samba? MS already has a proprietary closed-source implementation of SMB in Windows. Is there any reason they couldn't port that to Linux themselves or shoehorn in some kind of compatibility layer/shim?

    33. Re:Excellent! by gclef · · Score: 1

      They did one thing right, which we should be thanking them for: they fought SCO.

    34. Re:Excellent! by bb5ch39t · · Score: 3, Interesting

      But that person then has the right to redistribute. And if they do, then they must supply the source code. That is also a part of the GPL. You cannot take a GPL'ed program and say: "Here is a modified version and the source. But you cannot give it to anybody else!" Once the modified program is distributed to ANYBODY, then it can be distributed to EVERYBODY. And that cannot be stopped.

    35. Re:Excellent! by Anonymous Coward · · Score: 0

      Please cite the specific packages and GPL clause that are being violated. All your complaints are moot until you do.

    36. Re:Excellent! by lawpoop · · Score: 1

      Sure, MS can make a Unix-compatable windows file-server/domain controller at any time they want to. They could have done it before the Novell deal; they could do it now. Who cares? Let MS do whatever they want.

      The only thing I would be concerned about is if MS were able to benefit from the Samba code without giving anything back. And the GPL prevents them from doing that.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    37. Re:Excellent! by ClosedSource · · Score: 1

      There's a difference between "benefiting" from Samba code and "using" Samba code. MS or anyone else can look at the Samba code and incorporate its ideas in brand-new code without violating the GPL.

    38. Re:Excellent! by Damastus+the+WizLiz · · Score: 2, Insightful

      The assertion is that they are in violation of the SPIRIT of the GPL not in violation of the letter of the license. He clearly states that though Novell is not in volation of the GPLs terms the agreement Novell is ignoring the intent of the GPL.

      --
      I often have trouble remembering which way is out of bed in the morning.
    39. Re:Excellent! by andreyw · · Score: 1

      There's a difference between "benefiting" from Samba code and "using" Samba code. MS or anyone else can look at the Samba code and incorporate its ideas in brand-new code without violating the GPL. /me wonders what MS can learn from a reverse-engineered hack with such a poor design it gets rewritten every major version increase? I mean... don't kid yourselves.
    40. Re:Excellent! by nuzak · · Score: 1

      The worst part is that the bastardized Novell/Microsoft hybrid would probably the best-working version. (Hey, who better than microsoft to know the backward-compatibility quirks of Samba/CIFS?)

      Novell, not being the copyright holders of Samba, cannot fork Samba under a different license, and would be obliged to release the source to any changes they make under the GPL. And I think you overestimate Microsoft actually -- there's actually not a lot of people there who really understand the quirks of SMB/CIFS. Much of the behavior that many clients depend on was simply never documented.

      --
      Done with slashdot, done with nerds, getting a life.
    41. Re:Excellent! by urbanradar · · Score: 1

      It's basic "divide and conquer" because there will be some developers who don't see much wrong with the deal and will support the Novell Microsoft deal and there will be others who will not. The ones who don't MAY start new forks/projects and join other distros, or... they may just move on to other things entirely. This ensures a two-tiered Linux world with crappy underdeveloped software in non-blessed distros (Gentoo, Debian, etc...) and second-rate (compared to Microsoft Windows solutions) software in the intentionally stunted Novell Suse Linux and anyone else who decides to sign on.

      Don't think so. Most of the people who really make an important difference to Linux development seem to be against this, even if quite a few other important developers are and remain Novell employees. If there is fragmentation -- if -- I think it will be in favour of the community just due to the sheer numbers.

      And even if not: Just because the "blessed" distros will have paid developers working on their projects full-time doesn't mean their programmes / versions of programmes will be superior. If there are enough dedicated people out there who have the talent and truly believe in the spirit of open source and community -- and I do believe there are -- they can easily keep up with the commercial developers, or even surpass them. That's part of the beauty of open source. A big budget does not guarantee high-quality software. Just compare Linux or BSD with Windows, or Firefox with IE.

      I'm a bit more worried about the possible IP claims against Linux on Microsoft's part, but even so - Linux is a big thing involving a LOT of people, and it's not easily destroyed.

    42. Re:Excellent! by Dracos · · Score: 1

      Maybe MS' plan was to fragment the community, but so far I've only seen two opinions about the MS/Novell deal: either "it's evil" or "hmm". I have yet to see anyone cheering the deal, much less defiantly declaring that they will stay at their jobs because this deal is a good idea.

      And if Novell wants to keep hyping the interoperability side of the deal, that lies solely in MS' hands. Only MS can provide the specifications to make interop with Windows happen. Interop with Linux is easy, because the specs and code are freely available. If MS really wanted interop, they could have done it themselves a long time ago without help from anyone.

      Trouble is, they've proven time and again that they don't want interop with anything. Such is the life of a convicted monopolist.

    43. Re:Excellent! by shaitand · · Score: 1

      Novell does not need the GPL to use Samba. They do need the GPL to distribute Samba however.

      Unfortunately, Novell is only in violation of the GPL if they try to distribute patent encumbered software under the GPL. If samba is patent encumbered now then nobody has the right to distribute it under the GPL, even the samba team themselves! If novell adds something patented to samba and attempts to distribute under the GPL THEN they will be in violation of the license. But they haven't done that yet, there is just a concern that they will.

      People do need to remember that the agreement itself doesn't magically make legitimate distribution by Novell illegitimate. It only means that Microsoft won't go after them or their customers if they violate the GPL by including contributions covered under MS patents. That doesn't mean they will ever actually do so.

    44. Re:Excellent! by Anonymous Coward · · Score: 0

      You're right. Microsoft have been doing that sort of thing a lot longer than the Samba team!

    45. Re:Excellent! by Achromatic1978 · · Score: 1, Insightful
      the software any longer in a manor that is palatable to the people who write the code

      And here I was thinking freedom included the freedom to do that which others might not approve of... instead, it's apparently "freedom to use this code in a manner in which we see fit".

    46. Re:Excellent! by samkass · · Score: 1

      I think the open source community is doing a good enough job fragmenting itself around GPLv3, and doesn't need any help from Microsoft. You think this little hubbub at Novell is significant? It will be a drop in the ocean compared to the fragmentation that's on the horizon over GPLv3. I suspect many at Microsoft are cackling with glee over GPLv3 rather than caring much about Novell.

      --
      E pluribus unum
    47. Re:Excellent! by ClosedSource · · Score: 1

      It wasn't my intent to comment on the quality of the code, just the fact that the GPL doesn't protect ideas, just the particular expression of those ideas in the code.

    48. Re:Excellent! by sd790 · · Score: 1

      There's a problem with this line of thinking though. If Novell adds code that intentionally infringes on Microsoft's patents, that code will be tainted so that no other projects or distributions can realistically use it.

      I don't know if that revokes the GPL for Novell in that case, but I've got that feeling that we'll all know soon enough.

    49. Re:Excellent! by shaitand · · Score: 1

      "If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code."

      Yup, unfortunately that code will implement functions that are patent encumbered. This means nobody without a patent agreement with Microsoft will be able to use them. Or be able to implement the functionality in that way.

      At best it would require one group reading the code and documenting previous undocumented apis and functionality and another reading that documentation and implementing completely unique functionality without ever having been tainted by patented solutions.

    50. Re:Excellent! by lawpoop · · Score: 1

      It sounds like there is potentially a conflict between the GPL and any patented code methods. This will probably be decided in court, and could very well be Microsoft's next move in destroying the GPL and open source.

      However, there is a good argument that could work in favor of the GPL:

      If you're a patent holder and you knowingly create derivative work from GPL'ed code, then you are implicitly giving license to recipients to use the patented methods. After all, you knew that you were entering into contract to re-distribute the code and allowing people to re-use it. If you knew that you were giving such permission when you started working on GPL'ed code, you are giving implicit permission for recipients of your code to use your patents.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    51. Re:Excellent! by Scott+Lockwood · · Score: 1

      Welcome to the real world. If we don't protect our own interests, who will?

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    52. Re:Excellent! by lawpoop · · Score: 1

      What do you think of this quasi-legal argument?

      The GPL specifically states that the author of any GPL'ed derivative work must release such derivative work under the same terms, namely the GPL. The GPL specifically permits a user to use the code in any way they want to.

      If MS creates code that is derivative of GPL'ed code, they understand that the terms of the contract are such that they must release code to others under the same terms. If they choose to use their own patented software methods in such code that they are knowingly releasing under the GPL, they are giving future users permission to use their software patents on account that MS is using such patented methods in code they are releasing under the GPL.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    53. Re:Excellent! by Anonymous Coward · · Score: 0

      Yes, good idea.

      Now all they need is something resembling a legal leg to stand on when they inform Novell they're not allowed to use Samba.

      I'm not sure GPLv3 can provide said legal leg without seriously compromising the commercial viability of linux.

    54. Re:Excellent! by Scott+Lockwood · · Score: 1

      Nor am I. However, I'd rather see it remain free, if the choice is eithercommercial viability or freedom.

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    55. Re:Excellent! by marcello_dl · · Score: 1

      > [Hanlon's razor]: Never attribute to malice that which can be adequately explained by stupidity. This razor doesn't cut: stupidity can adequately explain everything.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    56. Re:Excellent! by twistedcubic · · Score: 1

      If you are entitled to 90% of the tens of millions in license fees SCO has collected, you'd probably fight too.

    57. Re:Excellent! by Anonymous Coward · · Score: 0

      You are the problem, just standing on the other side of the fence.

    58. Re:Excellent! by Anonymous Coward · · Score: 0

      Hmmm... Novell already has a (closed-source) CIFS service that runs on NetWare that is more scalable than Samba :-O

    59. Re:Excellent! by larry+bagina · · Score: 2, Informative

      Now witness the genius of the GPL. If you distribute software you have derived from GPL'ed code, you must provide that source code to the public under the terms of the GPL.

      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code. Any improvements MS/Novell make to samba are guaranteed to become available to us, and they can never take it away.

      What you said is true... except that the GPL v 2 (which the hypothetical MicroSuse SAMBA fork would be licensed under) is incompatable with GPL 3 (which SAMBA will be licensed under). MicroSamba's improvements can't be merged back into SAMBA.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    60. Re:Excellent! by larry+bagina · · Score: 1
      Novell is not the hypothetical patent holder in these scenarios -- MS is. That argument is cute when applied to SCO, but irrelevant here.

      Due to patents, encryption, and other artificial limitations, many GPL and FOSS projects include "illegal for export" encryption code and "might be patented in your country" algorithms ("wink wink, only enable this functionality if it's legal for you to do so!").

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    61. Re:Excellent! by Anonymous Coward · · Score: 0

      When Novell produce an Enterprise ready deritive of Samba, it is not impossible that they can circumvent this by ensuring that their Samba does not deliver the entire solution; perhaps it uses another software component which is non GPL.

    62. Re:Excellent! by mrchaotica · · Score: 1

      Actually, not quite. The lawsuit that's most beneficial to Free Software is SCO vs. IBM, not SCO vs. Novell. Now Novell is trying to force SCO to drop the suit against IBM, which is actually not in our best interests (since it's virtually assured that IBM would win anyway). In effect, you could say that Novell is trying to rob IBM and us of having the GPL fully proven in court.

      --

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

    63. Re:Excellent! by mrchaotica · · Score: 1
      If the Apple platform actually started to make major inroads in server rooms, office suites, groupware and provided a killer alternative to Exchange, MS would be actively trying to take them down a few pegs again.

      By the way, that's happening now: MS is actively trying to kill Apple by ceasing development of its Mac software. Over the past two years, the following has been dropped: IE/Mac, Virtual PC/Mac, Windows Media Player/Mac, and now VB scripting for Office/Mac (I'll bet the only reason the whole suite isn't gone is the 5-year promise of support MS made a while back -- MS can't kill it entirely, so it'll just kneecap it instead). In addition, Microsoft is attacking the iPod by coming out with the Zune -- not by directly competing, though, but by setting a precedent of paying the RIAA royalties for music players. Microsoft is hoping the publishers will try to force similar deals out of Apple in the future.

      --

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

    64. Re:Excellent! by Anonymous Coward · · Score: 0

      GPL is contract. Patents are law. Law stronger than contracts.

      I live in country does not recognize software patents. I write GPL software (is good). Maybe it infringes on US patents. I do not worry. Is not my fault if you cannot use.

      My friend from US go to Amsterdam, smoke lots of marijuana, has sex with prostitute. Is not legal in US but he not care. He like! Just like GPL and patents.

    65. Re:Excellent! by starwed · · Score: 1

      Does it matter that the GPL is in no way a contract?

    66. Re:Excellent! by Pecisk · · Score: 1

      No, they don't have. It is another Urban legend that GPLv3 will solve anything. To force Novell to fork, either you have to destroy spirit of GPL you are so in need to protect, or turn it into so vague language that lawyers of Novell will say you just to fuck off.

      Sorry to say that, but we should seek another way to solve this, not plain and let's say, childish revenge.

      It is so, even when you say it isn't.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    67. Re:Excellent! by smilindog2000 · · Score: 1

      Yes, exactly! I must say my respect for Jeremy could not be higher. We here on /. should do well to live up to his example.

      --
      Beer is proof that God loves us, and wants us to be happy.
    68. Re:Excellent! by mrchaotica · · Score: 1
      If you're a patent holder and you knowingly create derivative work from GPL'ed code, then you are implicitly giving license to recipients to use the patented methods.

      And that's why Microsoft is doing this kind of thing by proxy (i.e., through SCO and Novell) rather than directly.

      --

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

    69. Re:Excellent! by mrchaotica · · Score: 1

      (I know I just answered this in response to your other post, but other people might only read this one so I'm doing it again.)

      If MS creates code that is derivative of GPL'ed code...

      Your argument fails because Novell is the one actually creating the code, not Microsoft. This could very well result in the destruction of Novell, but MS is squeaky-clean.

      --

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

    70. Re:Excellent! by shaitand · · Score: 1

      That is quite reasonable, although novell is creating the code in this case and not microsoft. Microsoft has the authority to give permission implicitly as you suggest but the agreement Novell has does not grant them permission to do so.

      Under the terms of the GPL if there if you have any reason to believe you do not have the authority to release under the terms of the GPL then your right to redistribute under the GPL is revoked. It seems to me that you aren't 'passing the same rights granted under this license' if you know that those you distribute to will be in violation of patents that impede them from having those rights.

    71. Re:Excellent! by shaitand · · Score: 1

      "GPL is contract. Patents are law. Law stronger than contracts."

      A patent agreement is a contract as well. The GPL is contract regarding copyright (law), a patent agreement is a contract regarding patents (law). Both are the law and strength is not an issue.

      "I live in country does not recognize software patents. I write GPL software (is good). Maybe it infringes on US patents. I do not worry. Is not my fault if you cannot use."

      That is fine, the GPL grants you permission to distribute ONLY if you both have the authority to grant those rights to those you distribute to AND you do grant those rights. If you do not have that authority then you yourself do not have permission to distribute under the GPL.

      You operate in a country without software patents, in the juristiction where you are producing that software you have the right to fulfill the terms of the GPL by granting those you distribute to all the same rights you have under the GPL. Including the right to redistribute.

      I operate in a country WITH software patents, in the jurisdiction where I am producing software I do not have the right to fulfill the terms of the GPL by granting those I distribute to all the same rights I have under the GPL (if someone else owns the patent). Including the right to redistribute.

      Novell does not have the authority to pass on the rights their contract with Microsoft grants them and Novell operates in a country that DOES have software patent laws. Therefore Novell can't give me GPL'd software that includes functions covered by a Microsoft patent, because they can't grant me the right to redistribute and therefore lose their own rights under the GPL.

    72. Re:Excellent! by lawpoop · · Score: 2, Interesting

      Oh, now I get it. So that means that since it isn't MS developing GPL derived code, they aren't giving any implicit permission to use patented methods. Novell has an agreement with MS to use the patented methods, and they can develop GPL-derived code, but the recipients of Novell's GPL-derived code *don't* have an agreement with MS to use MS' patented software methods in the GPL code that Novell produced.

      Now I get it.

      However, this doesn't seem to be any kind of death knell for the GPL. If this were happening in the early nineties, it might be a problem, but we seem to have a critical mass of GPL software so that you can have an entire system that's GPL.

      I predict that this patent-encumbered Samba can only boost Linux adoption. The customers for MS/Novell Samba will have Linux servers and windows desktops. There's no reason to use this if you don't have Linux servers. And if you have Linux servers already, you must use Linux on the server for reasons other than it's cheaper than a Windows license. Why migrate to Windows servers if you can have Linux servers with no software cost?

      This type of software-patent work-around for proprietizing GPL code would seem to only work if there were an existing, well-developed GPL app that solely functions as a replacement or emulator for a proprietary program, and then, the proxy developer has to have an interest in creating and selling it. Sure, you can pay someone to create patent-encumbered GPL code using your patents, but then you have to get people to use it. That means that they have to have an agreement with you. So, just use the already free, already available alternative.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    73. Re:Excellent! by Tiger4 · · Score: 1
      The GPL IS a contract. Between the people the provided the code and the people that want to use it. "We give you this software, in return for which you promise to use and distribute it in the following ways..."

      Assuming the things exchanged and the actions promised are not illegal, it should be a valid contract. There are some legal cases out there testing whther this kind of license is legal in certain countries, but in common law nations it is all but settlled.

      --
      Behold, this dreamer cometh. Come now, and let us slay him... and we shall see what will become of his dreams.
    74. Re:Excellent! by bertramwooster · · Score: 1

      Many Linux distros are doing exactly that and that's why taking Linux down a few pegs is a necessity to MS. MS doesn't want Linux dead. They just want it to smell funny. Probably something like pee. (I keep doing that)

      Keep doing what? Smell like pee?

    75. Re:Excellent! by awehttam · · Score: 1
      Why not?

      NMAP did it

    76. Re:Excellent! by Anonymous Coward · · Score: 0

      Then Microsoft still has not learned its lesson. There is no divide and conquer. The only Victim here will be novell, as users and coders alike walk away. Despite a Novell/Microsoft sponsored survey indicating the opposite. How many linux flavors have come and gone, the pile is deep, it just grows by one more today....and the band plays on.

    77. Re:Excellent! by Anonymous Coward · · Score: 0

      Then Microsoft still has not learned its lesson. There is no divide and conquer. The only Victim here will be novell, as users and coders alike walk away. Despite a Novell/Microsoft sponsored survey indicating the opposite. How many linux flavors have come and gone, the pile is deep, it just grows by one more today....and the band plays on and on

    78. Re:Excellent! by eno2001 · · Score: 1

      Great comic timing. Superb. No really.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    79. Re:Excellent! by lpq · · Score: 1
      What I'd really like to see, is...pull support for Novell/SuSE, ...inform them they are in violation of liscense, and revoke usage

      Geez, and then maybe their president and board be covered in honey and staked to a fire-ant hill, and all their customers go bankrupt!... Oh yeah, don't forget castration, mutilation and other pleasant forms of spiteful vindictiveness.

      I applaud your sense of logic and balance.
    80. Re:Excellent! by andreyw · · Score: 1

      My comment on the quality itself was rather unnecessary... I am more stressing the - WHY Microsoft would bother looking at a reverse-engineering product of THEIR OWN SOFTWARE. I mean...

    81. Re:Excellent! by WNight · · Score: 1

      Perhaps then the OSx86 project streamlines installation a bit more, you'll install OS X on your PC. Piracy was Microsoft's big distribution channel, now Apple can take it away with a vengence.

    82. Re:Excellent! by Anthony · · Score: 1

      My understanding was that MS turned to the Samba documentation at one stage because it was a more complete description of the protocol.

      --
      Slashdot: Where nerds gather to pool their ignorance
    83. Re:Excellent! by Anonymous Coward · · Score: 0

      Novell may be violating the intent of the GPL it's not violating the actual license agreement itself

      That's not true, it definitely is in violation of the GPL.

  2. I applaud him! by 10scjed · · Score: 1

    Hopefully, Novell will keep Stafford Masie's promise to be GPL v3 compliant, fix the deal, and then maybe they can hire him back, with a raise and promotion of course. Best of luck to Jeremy.

    --
    --10scjed IANAL,AFAIK
    1. Re:I applaud him! by arth1 · · Score: 1
      I'm not to sure how to interpret this rapture from Stafford Masie:

      Now, as GPL version 3 matures, and Stallman has said we're not in violation of GPL version 2 at the moment, now we're not with the current agreement, but he believes in GPL3 he will put verbiage in there to ensure that we are.


      Stallman will put verbiage in GPL3 to ensure that Novell is in violation? That's what he said, but obviously not what he meant. So what did he mean? That Stallman will kowtow and ensure that the GPL is amended to ensure that Novell isn't violating it? That sounds even less likely - RMS is an upright guy, no matter what else you think of him (and he also isn't the only person in charge of creating the new GPL).

      So what, exactly, did Maisie mean, if anything?

      Regards,
      --
      *Art
    2. Re:I applaud him! by SuiteSisterMary · · Score: 4, Funny

      "GPL3 ain't done till Microsoft and Novell won't run"?

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    3. Re:I applaud him! by evil_Tak · · Score: 1

      Stallman will put verbiage in GPL3 to ensure that Novell is in violation? That's what he said, but obviously not what he meant.

      That's exactly what he meant. He believes that the creators of GPL3, specifically RMS, will make sure that GPL3 specifically forbids actions like Novell's. Which it should, since, as has been mentioned approximately 1.21 gigatimes in these comments, even if the Novell/MS agreement doesn't violate the letter of the GPL2, it certainly violates the spirit and intention.

    4. Re:I applaud him! by vz3phyre · · Score: 1

      I sit beside you and do the same thing

    5. Re:I applaud him! by Anonymous Coward · · Score: 0

      GPL v3 will contain clauses that will prevent the kind of thing novell did here - where they are in compliance with the letter of the GPL but not the intention/spirit.

      once code begins to be released under the GPL v3, people like novell will have to fork off their own distribution with the older GPLv2 code, because they won't be able to intermingle the GPLv3 code into it. as more and more code is released under GPLv3 the "support load" will get higher and higher for novell, until there is so much load either novell will find themselves eating up a lot of resources just to keep up with developments in the rest of the linux sphere, or find themselves using "old" stuff.

      the most critical component would be the kernel, but here linus is acting as a spoiler for this kind of strategy since he doesn't seem to want the kernel to be GPL v3. if future versions of the kernel were GPL v3, novell would have to fork off their own kernel, and THAT would be a lot of work (and plenty of compatibility issues).

      the only interesting alternative possibility here (to me anyways) would be - what if that was microsoft's intent? they actually would have the resources to maintain a fork of a linux kernel. then there would be two "linuxes" - one a continuation of the current kernel development process, another under the auspices of novell and - whether explicitly or not - microsoft.

  3. Intent doesn't matter by Dynedain · · Score: 1

    You don't think that MS and Novell have had teams of lawyers going over everything for this deal, including the GPL. When it comes down to it, it's the letter of the contract that matters, not the intent that was in the minds of the writers.

    If I write a contract to deliver a dozen roses, but for some reason I think that carnation is called a rose and instead deliver a dozen carnations, I will be held in breach of contract. It doesn't matter what my intent was if I framed the contract improperly to ensure my intent.

    --
    I'm out of my mind right now, but feel free to leave a message.....
    1. Re:Intent doesn't matter by eln · · Score: 2, Insightful

      It sounds to me like he released Samba under the GPL with the idea that the GPL somehow reflects some sort of utopian ideal where everyone is equal, and the GPL just doesn't say that. I wonder if he decided to use the GPL because it was the best-known Open Source license, without actually reading it (or better yet, having his lawyer read it), and is now caught off guard when he sees that the license he chose is not as reflective of his idea of the "Open Source Ideal" as he thought.

      He chose to release his software under a license that permitted this sort of behavior, and now he's complaining when people actually engage in this sort of behavior.

    2. Re:Intent doesn't matter by $RANDOMLUSER · · Score: 1

      Yes. And Microsoft's record in following consent decrees and contracts with others (Sun) is inviolate.

      --
      No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    3. Re:Intent doesn't matter by tdos20 · · Score: 1

      It does if your intentions cause all your employees to resign

    4. Re:Intent doesn't matter by radarsat1 · · Score: 1
      When it comes down to it, it's the letter of the contract that matters, not the intent that was in the minds of the writers.


      Well, it matters when everyone gets pissed off at you, you begin losing market share, and you start losing your best developers...

      Fortunately we still live in a world where people can make choices, and people are affected by intent. (People... as opposed to Lawyers, I guess. swish!.. heheh.) So yes, it matters.
    5. Re:Intent doesn't matter by Schue · · Score: 1

      That isn't entirely true. Honoring the "spirit of the agreement" has played an increasing role in courts as an effort to reduce the complexity of litigation and suppress frivolous suits. After all, if you purposefully convince someone to execute an agreement that legalistically conceals its true meaning and you misrepresent your intent then what you are doing is rooted in deceit and, therefore, fraud.

    6. Re:Intent doesn't matter by arth1 · · Score: 4, Funny
      You don't think that MS and Novell have had teams of lawyers going over everything for this deal, including the GPL. When it comes down to it, it's the letter of the contract that matters, not the intent that was in the minds of the writers.

      If I write a contract to deliver a dozen roses, but for some reason I think that carnation is called a rose and instead deliver a dozen carnations, I will be held in breach of contract. It doesn't matter what my intent was if I framed the contract improperly to ensure my intent.


      Fortunately, YANAL, and you're dead wrong. Using your example, if you deliver Kevin Rose and 9 members of his family, you've fulfilled the letter of the contract, but will still be held in breach of it because you violented the intent of it.

    7. Re:Intent doesn't matter by 10scjed · · Score: 1

      especially since you're still 2 'rose's short, but mint example.

      --
      --10scjed IANAL,AFAIK
    8. Re:Intent doesn't matter by Anonymous Coward · · Score: 1, Funny

      Actually, when you deliver humans, it's called a "cannibal's dozen". Historically speaking, you eat two on the way. So, there's only 10.

    9. Re:Intent doesn't matter by Anonymous Coward · · Score: 0

      The two qualifying grandparents wilted...

    10. Re:Intent doesn't matter by Anonymous Coward · · Score: 0

      IANAL, but I believe that contracts are case sensitive: "Rose" != "rose". Do you have a better example? IMO, contracts are supposed to describe the intent and nothing else. I've read the GPL and always assumed that its intent was what was written. If the intent is something else, is there any document online that explains it? If so, why haven't they used that document as the license?

    11. Re:Intent doesn't matter by everphilski · · Score: 1, Redundant

      If your employees don't understand the license (Here's a hint: both Eben Moglen and RMS can't find anything wrong with the deal) then there is something wrong with the employees, not the employer.

    12. Re:Intent doesn't matter by jedidiah · · Score: 1

      "idea that the GPL somehow reflects some sort of utopian ideal where everyone is equal"

      That's EXACTLY what is says. That's the explicitly stated intent of the thing, even if
      the legal language hasn't quite succeeded in allowing that ideal to be enforced.

      The only question is if Moglen wrote the thing air-tight enough to cover Novell's actions or not.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    13. Re:Intent doesn't matter by Austerity+Empowers · · Score: 1

      You just need the right lawyer, let's get Cochran in here. Bring Shakespeare back from the dead, along with half a dozen english lit professors, and apply the following defense:

      "That which we call a rose by any other name would smell as sweet, and thus we did deliver 12 carnations, according to the terms of our contract". Three weeks, a dozen expert testimonies later, and a carnation would legally be considered a rose, and no one will touch it with a 100ft pole for fear he might speak again.

  4. well no they won't by Anonymous Coward · · Score: 0

    because they treat all people equally. That is important to them. Novell don't stop being "all people" just by being a bunch of Just like there was talk of SAMBA 'revoking' SCO's license for being a bunch of . They didn't.

  5. What really happened by autophile · · Score: 3, Funny

    Executive #1: Hey, I just got an Internet!
    Executive #2: Who from?
    Executive #1: Some guy named Jeremy. Isn't this caviar good?
    Executive #2: Sure is. Who's Jeremy?
    Executive #1: I think he's some greasy coder.
    Executive #2: Ha ha, they are *so* *guh-ross!*
    Executive #1: You said it! Here, have a small, autonomous Micronesian island, complete with 143 nubile slaves and an offshore account.

    Ha ha only serious?

    --Rob

    --
    Towards the Singularity.
  6. I don't understand this... by PenguinBoyDave · · Score: 0, Troll

    Let's see here...

    * Novell gets a BIG chunk of money for this deal
    * Microsoft says it will not file any lawsuits against developers over any patent issues
    * Companies can use SUSE Linux and Windows and know that total interoperability is the goal of both Microsoft and Novell
    * HP, Goldman Sachs, IBM and others have called this a very positive thing for IT, Linux and Open Source
    * The only people who are complaining are those who are true *idealists* when it comes to Linux and Open Source

    I don't know why this guy is leaving. This is a good thing all the way around for the Linux community. I have large customers (people who spend money on software AND use Open Source) who run Windows and Linux side by side. Their NUMBER ONE complaint has been lack of interoperability. They say that they will definitely continue to run Linux in their environment and will probably switch to SUSE Linux because of this agreement.

    This agreement gives them the support they need to run their businesses...period. It does nothing more than that. I'm sorry to see him leave Novell, but this project will go on without him, and Linux, Open Source, and the IT community will be better off for this agreement. Hopefully he'll find a god place that can use his talents.

    --
    I'm not a troll, but I play one on Slashdot.
    1. Re:I don't understand this... by mccalli · · Score: 3, Insightful

      * The only people who are complaining are those who are true *idealists* when it comes to Linux and Open Source

      ....or in this case, the people that actually produce the software being used.

      I have large customers (people who spend money on software AND use Open Source) who run Windows and Linux side by side. Their NUMBER ONE complaint has been lack of interoperability.

      Precisely. Users will think this is great, but it's not users who are writing the software being abused. Large users in particular (I work for a very large corporate user of Linux) will think this is great, because they're already paying for their support contracts and are basically seeing Linux as a commercial OS anyway - that's true in their case, because they're paying for support and restricting themselves to supported configs etc.. But it's the people writing the code that are objecting to their labour being used in this way, not the end users.

      Cheers,
      Ian

    2. Re:I don't understand this... by Enderandrew · · Score: 2, Interesting

      Part of this agreement involves Novell paying Microsoft not to sue them.

      It makes the Linux world look guilty of stealing from Microsoft.

      And the second Novell gave Microsoft money, Novell ceased development on products that would compete with Microsoft.

      Do you think that Novell isn't forever compromised by this deal?

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    3. Re:I don't understand this... by MysticOne · · Score: 2, Insightful

      From what I understand, it doesn't protect any developers unless they work for Novell. Aside from that, it only protects Novell's customers from patent lawsuits. If you're using a different Linux distribution, you're not going to be covered.

      The problem here is that it does violate the spirit of the GPL. Rather than granting all users freedom, they're granting users freedom only if they've purchased a specific distribution. The GPLv3 will more than likely fix this, but for now we're stuck with the GPLv2 allowing actions such as this.

      Oh, and just how is Microsoft going to be fostering interoperability? I haven't seen yet where they've adopted any of our open protocols or open formats. I don't see them working with developers of free software products to help them inter-operate with Microsoft software. All I've seen so far is that Novell is going to be making an OpenXML plug-in for OpenOffice, and OpenXML is a standard in name only, also completely avoiding the intent of what it means to be a standard.

    4. Re:I don't understand this... by ctid · · Score: 2, Insightful
      * Microsoft says it will not file any lawsuits against developers over any patent issues

      MS said they won't file suit against hobbyist developers. They didn't say anything about developers who are paid to work on Linux by companies other than SUSE.
      * Companies can use SUSE Linux and Windows and know that total interoperability is the goal of both Microsoft and Novell

      Jeremy Allison has been quoted many times about some of the problems of making SAMBA work with Microsoft's SMB. Many of these problems have been because Microsoft do not (perhaps that should be "did not") want operability between Windows and Linux. As the founder of the SAMBA project, he's in an invidious position for precisely the reason you state when you talk about customers who complained about interoperability and who now want to switch to SUSE.

      --
      Reality is defined by the maddest person in the room
    5. Re:I don't understand this... by mrsbrisby · · Score: 5, Insightful
      * Microsoft says it will not file any lawsuits against developers over any patent issues
      Maybe this is where you're confused.

      Microsoft says it will sue users of Samba, but not if they give Microsoft money by being a customer of Novell (because a portion of the SUSE warantee agreement goes to Microsoft directly).

      By doing this, Novell is violating my copyright and the copyright of every contributor to free software by redistributing my software to people who do not have the ability to redistribute my software (with all rights they received therein). The GPL expressly forbids this, both in intent and in letter.

      Novell is now saying that when I said anyone they distribute my software to must be given the same rights to redistribute that Novell has, and be told as such, that I really didn't mean it. While the GPL says this means Novell no longer has the right to redistribute my software, I strongly suspect they think it doesn't say that either.
    6. Re:I don't understand this... by Rob+T+Firefly · · Score: 1
      I don't know why this guy is leaving.
      Read his post, the one that starts off "I have decided to leave Novell. [...] As many of you will guess, this is due to..." Whether or not you personally agree with his reasoning, that's why this guy is leaving.
    7. Re:I don't understand this... by PenguinBoyDave · · Score: 1

      "Oh, and just how is Microsoft going to be fostering interoperability?"

      Go visit http://port25.technet.com/

      Take some time and actually read what they are doing over there. Note that Microsoft and Firefox folks have been working together...

      It isn't all bad folks.

      --
      I'm not a troll, but I play one on Slashdot.
    8. Re:I don't understand this... by MysticOne · · Score: 1

      I know they've done a few things that are at least somewhat "open", but I don't see this as being a significant part of Microsoft's strategy. It's probably more something to garner "good will" in the community, so we're more complacent. With all that said, they can *still* exert control over their patents if an open solution they've developed is used or extended by somebody else.

      I just don't see them doing anything that's going to weaken their stranglehold on the PC community.

    9. Re:I don't understand this... by pscottdv · · Score: 1

      The only people who are complaining are those who are true *idealists* when it comes to Linux and Open Source

      Like it or not, many of those "true idealists" are also the people writing the code. So maybe their opinion matters.

      --

      this signature has been removed due to a DMCA takedown notice

    10. Re:I don't understand this... by PenguinBoyDave · · Score: 1

      Their opinion absolutely matters. And while I applaud Allison for standing up for his convictions, I think they are poorly placed with this particular move.

      Look...he can do what he wants, as can any other coder. They is his, and your right. However, it is my prediction that in two years, this agreement will be seen as the best thing to happen to Linux in the Enterprise. If I'm wrong, I'll gladly come back here to Slashdot and publicly state that I was foolish with my assessment.

      --
      I'm not a troll, but I play one on Slashdot.
    11. Re:I don't understand this... by PenguinBoyDave · · Score: 2, Interesting

      I might be dead-wrong here. I might be so wrong that I'll lament ever supporting this. But I look at this as Microsoft finally admitting that Linux and Open Source are here to stay, and since they can't and won't beat it, why not see how to best work with it. The formation of the Port25 website and the Open Source lab is a good step in the right direction.

      --
      I'm not a troll, but I play one on Slashdot.
    12. Re:I don't understand this... by neaorin · · Score: 2, Insightful

      How is Novell violating your copyright because of something another company said?

      If there were no deal and MS said 'we'll sue everyone, but not Novell 'cause we like their funky green lizard', would Novell still violate the GPL by redistributing?

      Now if MS comes out and points out copyright violations in GPL code, Novell can't legally distribute it regardless of the deal...

      I've RTFA and I think the guy is saying he feels marginalized by the community because the company he worked for 'made a deal with the devil'.

      "We can pledge patents all we wish, we can talk to the press and "community leaders", we can do all the right things w.r.t. all our other interactions, but we will still be known as GPL violators and that's the end of it."
    13. Re:I don't understand this... by Anonymous Coward · · Score: 0

      Those *idealists* are the ones who wrote the code in the first place (or atleast some of them, there's always a band of trolls following everything - that can't be avoided). I think they have a right to voice their oppinion about the matter.

      Also, have you read all the complaints about how impossible it is to understand the OpenXML specification and implement it right? I bet that Novell has run over their budget received from Microsoft quadruple times before they have an OpenXML implementation for OOo that is anywhere near usable for MS Word compability. //fatal

    14. Re:I don't understand this... by tokul · · Score: 1

      There is nothing about interoperability in that agreement.

      Microsoft, on behalf of itself and its Subsidiaries (collectively "Microsoft"), hereby covenants not to sue Novell's Customers and Novell's Subsidiaries' Customers for infringement under Covered Patents of Microsoft on account of a such Customers' use of specific copies of a Covered Product as distributed by Novell or its Subsidiaries (collectively "Novell") for which Novell has received Revenue (directly or indirectly) for such specific copies; provided the foregoing covenant is limited to use by a Customer of Novell (i) of such specific copies that are authorized by Novell in consideration for such Revenue, and (ii) within the scope authorized by Novell in consideration for such Revenue.
    15. Re:I don't understand this... by MysticOne · · Score: 1

      Well, I'll give it to you for being optimistic. :) It'd be nice if they were going to adopt a lot of these open practices and move forward towards a level playing field. But, we're talking about the largest software company in the world, whose monopoly allows them to pretty much do whatever they please. I don't see them giving that up easily, and I don't think the FOSS community is big enough for them to really care. It might be their way of conceding and working together more on the server front, but I don't see it moving over to the desktop. But, time will tell. We'll see.

      They're still violating the spirit of the GPL, though.

    16. Re:I don't understand this... by Anonymous Coward · · Score: 0

      So, your customers will be switching to SUSE because Novell found a clever way around the GPL2, and will be able to give their customers exclusive patent protection on the free software developed by the community, while knowing full well that this goes against the intent of the GPL and the entire free/open-source community... Congrats?

      Like Jeremy said in his letter: "Do you think that if we'd have found what we legally considered a clever way around the Microsoft EULA so we didn't have to pay for Microsoft licenses ... that Microsoft would be silent about it[?]"

      With the GPL stating: "We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all."

      It will be interesting to see what Novell does without a C compiler and library, or is Microsoft going to help them out with that too? If you really think this is a good thing for your clients and that Microsoft is out to help a competitor, you're in for quite a surprise.

    17. Re:I don't understand this... by pscottdv · · Score: 1

      Alright, I'll make my prediction with the same pledge. I predict Novell will do the same thing to Suse Linux as they have done with every other product they have ever touched, which has been described as spinning gold into toxic waste. But that isn't really relevant to my post.

      I must say, it grieves me, too. Novell has been a really solid community partner. Really! They seemed to "get it" when it came to the GPL community. I just don't understand it.

      I should also point out that it is perfectly possible for the agreement to be the "best thing to happen to Linux in the Enterprise" and also be the worst thing for Free Software depending on your goal for "Linux in the Enterprise". I strongly suspect that Allison's primary goal is not increased market share. After all, he's obviously one of those "true idealists".

      --

      this signature has been removed due to a DMCA takedown notice

    18. Re:I don't understand this... by ravenoak · · Score: 1

      Here...go listen to this netcast. It just *happens* to be Jeremy Allison being featured on FLOSS weekly. Pay close attention to the bits (somewhere around 35 min. into the netcast) where he mentions MS's intentions on interoperability, specifically what changes they made to the Sever Message Block protocol in Windows 2003/Vista. Yah, they might say that they want to play nice, but I have a hard time beleiving that MS has changed their tune since the creation of SMB2.

    19. Re:I don't understand this... by Anonymous Coward · · Score: 0

      The only people who are complaining are those who are true *idealists* when it comes to Linux and Open Source

      As in.. the people who originally started/created the software and the movement? Ah.

    20. Re:I don't understand this... by Anonymous Coward · · Score: 0

      Try finding the source for SLES 10.

      You can't. Novell does not provide any coherent means of getting its source. Redhat does, right there on ftp.redhat.com. Screw Novell, SLES is only good for now because they haven't had time to totally fuck it up. Who cares about their deals with MS, those of you who thought Novell was in any way going to handle suse competently are sadly mistaken. In 10 years, they will be struggling to totally reinvent themselves once again. Look at their handling of netware, UNIX, now SuSE. Sad for SuSE.

      Show me a community sponsored open distro of SLES, such as CentOS for redhat. Thats because THERE ARE NO SOURCES FOR SLES 10.

    21. Re:I don't understand this... by jalet · · Score: 1

      > Their NUMBER ONE complaint has been lack of interoperability.

      Did you ever ask yourself WHY there were interoperability problems ?

      --
      Votez ecolo : Chiez dans l'urne !
    22. Re:I don't understand this... by PenguinBoyDave · · Score: 1

      It's not my place to ask. These are large, Fortune 500 or larger companies. They want something that works...period. If it doesn't work, they will look for something else that does.

      --
      I'm not a troll, but I play one on Slashdot.
    23. Re:I don't understand this... by jalet · · Score: 1

      Precisely, but you can say it both ways : GNU/Linux is not interoperable enough with Windows, or the other way around : Windows is not interoperable enough with GNU/Linux.

      Why do your customers always seem to look the same way ? Just explain them, they should understand : If Windows doesn't work, they just have to move to something else that does.

      --
      Votez ecolo : Chiez dans l'urne !
    24. Re:I don't understand this... by MikeBabcock · · Score: 1
      By doing this, Novell is violating my copyright and the copyright of every contributor to free software by redistributing my software to people who do not have the ability to redistribute my software (with all rights they received therein). The GPL expressly forbids this, both in intent and in letter.


      I mean this in the nicest possible way, but you're on crack.

      Nothing prohibits any Novell customer from giving any non-Novell customer the source code and binaries to any GPL product contained in that distribution. Nothing in the GPL even begins to deal with things outside of the boundaries of Copyright law. That is to say, Copyright normally takes your rights away and the GPL allows you certain freedoms in contradiction to Copyright should you agree to uphold those ideals.

      Those ideals are very simple, and none of them include giving away something that is normally expected to be paid for, like a warrantee. In fact, most GPL products expressly disclaim any warrantees to users in the first place, so I'm still not sure why you're upset.

      You do realize that's all this is right? -- a warrantee agreement between Novell and its customers with permission from Microsoft.

      None of my or your precious GPL freedoms are being taken away at all, and this hoopla is very confusing to me. Yeah yeah, the evil Microsoft signed an agreement with a Linux distributor, so what? I hate Microsoft as much as the next guy with six Linux PCs at home, but really, who cares? What matters is how the software is distributed and your rights to do whatever you want with the sources (which you would still have as a Novell customer).

      You may not be able to transfer any additional warrantee Novell gives you w.r.t. Microsoft lawsuits that may or may not ever happen, but you wouldn't have had that without the agreement either.

      Please, informed replies only. Flames are not helpful.
      --
      - Michael T. Babcock (Yes, I blog)
    25. Re:I don't understand this... by PenguinBoyDave · · Score: 2, Insightful

      We could go back and forth like this all day long...point for point. But I'll break it down like this:

      1. Windows was in the Data Center first (except for mainframe and Unix...but hang with me for a minute)
      2. Linux is the newcomer to the corporate world.
      3. Companies are not going to dump their Windows environment for Linux, just because Microsoft has, admittedly, made no effort to integrate with Linux. We would be foolish to believe Gates / Ballmer would say "you know, it would be great if we could make our OS work with this new, free OS that is our direct competition." If they did, they would have their shareholders up in arms. My last company made great strides in integrating Linux into their corporate environment, but when you have a gazillion Exchange servers, you're not going to dump that. Just isn't going to happen. Same with SQL servers...not going to win that one either.
      4. Now, Ballmer decides he can't beat Linux or Open Source decides that perhaps it is time to work together, because the customers are telling them they need to do so. Great. But don't expect him to change over night. Sure...he can say "all Linux users are fair game..." but what are the odds of that happening? Surely he's seen the fiasco that is the SCO lawsuit. He's not that stupid.

      Look...if it were up to me, everyone would run Linux on the desktop and the server. I've done it for years, and with the exception of my work laptop, I'm either running Linux (Debian & SUSE) or Mac OSX. But it isn't up to me. IBM said they were going to switch everyone to a Linux desktop. They didn't. Novell said everyone was going to use a Linux desktop. A lot do, but not everyone. The plain and simple fact is that Microsoft is the world's largest software manufacturer. Ballmer is charged with protecting its interests. The Open Source lab and the deal with Novell are a good step. But as I said, we can't expect him and the ship that is Microsoft to change course over night. It takes time. Companies and individuals will also change over time, and more Linux will show up on the desktop and server. When I work with friends setting up businesses I recommend and help them implement Open Source software. But that is from the ground up. Trying to get bigger companies to make that change isn't easy, and they will stay with what they have because of what it would take to switch.

      Come up with a tool that will seamlessly migrate Windows desktops and server to Linux with little to no down-time, and you'll be a Billionaire...guaranteed, and this discussion won't happen, because everyone will run Linux, because they can, and it won't hurt in the process of changing over.

      --
      I'm not a troll, but I play one on Slashdot.
    26. Re:I don't understand this... by jalet · · Score: 1

      Thanks for this answer.

      --
      Votez ecolo : Chiez dans l'urne !
    27. Re:I don't understand this... by symbolset · · Score: 1
      This is only my opinion, but...
      I might be dead-wrong here.

      You are

      I might be so wrong that I'll lament ever supporting this.

      You will be.

      The benefits you see are the bait. The patents are the hook. The line is currently four years and ten months long. The death of Novell is the sinker.

      If people trust this deal, they're going to feel a lot of pain getting uncommitted.

      --
      Help stamp out iliturcy.
    28. Re:I don't understand this... by Anonymous Coward · · Score: 0

      Hey Ian - you are out off work today:) lucky bastard!

    29. Re:I don't understand this... by mrsbrisby · · Score: 1
      How is Novell violating your copyright because of something another company said?
      They're violating it regardless of what Microsoft says.

      I've RTFA and I think the guy is saying he feels marginalized by the community because the company he worked for 'made a deal with the devil'.
      You're right, that's Jeremy's problem with Novell, but parent said they didn't understand the problem, so here it is:

      Novell made a deal that promises protection for their customers. That's a big part of why they made it, and along comes Microsoft and says as much. Novell could say You know, we really meant that to protect our customers for Novell products, not for third-party products and yet they didn't. They said trust us, we're the good guys remember?

      The simple fact is that Novell doesn't have the right to enter into that deal with Microsoft using SUSE because Novell doesn't have the right to guarantee their customers those rights (under the deal with Microsoft). If they did, Microsoft probably wouldn't have entered into the deal.
    30. Re:I don't understand this... by PenguinBoyDave · · Score: 1

      Thanks for the debate. Right or wrong, it was fun, and I think it's good for everyone.

      Happy holidays to you.

      --
      I'm not a troll, but I play one on Slashdot.
    31. Re:I don't understand this... by mrsbrisby · · Score: 1
      Nothing prohibits any Novell customer from giving any non-Novell customer the source code and binaries to any GPL product contained in that distribution. Nothing in the GPL even begins to deal with things outside of the boundaries of Copyright law. That is to say, Copyright normally takes your rights away and the GPL allows you certain freedoms in contradiction to Copyright should you agree to uphold those ideals.
      From the Preamble to the GPL:

      For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
      You may not be able to transfer any additional warrantee Novell gives you w.r.t. Microsoft lawsuits that may or may not ever happen, but you wouldn't have had that without the agreement either.
      I'd say that the GPL just said otherwise.

      You do realize that's all this is right? -- a warrantee agreement between Novell and its customers with permission from Microsoft.
      Because Novell is licensing thse patents for the use of their customers (presumably with SUSE), they are denying their customers the rights to use the software for any purpose (they can only use it on machines with paid-up SUSE licenses). They can't give someone else the rights to use the software (assuming the patents are valid), so if Linux really does contain patented algorithms that aren't freely licensed for everyone's use, Novell loses the right to distribute Linux at all since the recipients cannot transfer those rights to others.

      Please, informed replies only. Flames are not helpful.
      You accuse someone of drug use "but in the nicest possible way", lecture an argument on a single broken assumption, and then say, "only people who agree with me can reply-"

      Software and its use is supposed to be Free: Free to run, Free to change, Free to share, and Free to improve. US Copyright law guarantees the first two, so the GPL really is about Free to share the software, and improved versions of that software. Anything that produces inequalities in its users, or its use is contrary to the spirit of the GPL, and I really do think anyone informed about Free Software knows this.

      The real question is whether a Judge will honor the spirits of the GPL, and the authors of Free Software, or the twisted freedom hating interpretation of Microsoft.
    32. Re:I don't understand this... by Kjella · · Score: 1

      Here's the long and short of it: Novell is redistributing all the rights it has. Novell has no patent license, a promise not to sue is nothing at all in IP law. Does Microsoft even need any formal agreement at all to sue everyone but Novell's customers? No. All Novell needs to do is to pay Mircosoft somehow, and mysteriously enough they don't get sued. And I doubt very much there's anything the GPLv3 could do about it.

      --
      Live today, because you never know what tomorrow brings
    33. Re:I don't understand this... by mrsbrisby · · Score: 1
      And I doubt very much there's anything the GPLv3 could do about it.
      Why? Are you a lawyer?

      The GPL forbids distribution that is patent encumbered; from the preamble:

      Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. This means that if those programs are patent-encumbered, then Novell doesn't have a right to redistribute them, no matter what Microsoft says. In order for Novell to have the right to redistribute GPL software, then Microsoft cannot have the right to use anyone (not Novells' customers, not anybody) for those patents.

      Now ordinarily, we could simply agree to disagree- and wait for a Judge to say if Microsoft is right or not, but the problem here is that Novell is saying that these files are encumbered with patents and so therefore Novell is saying expressly that Novell is violating copyright law.

      Of course, it's possible that contract isn't legally binding, and that neither Microsoft nor Novell had the right to offer what they did in the contract, but you seem to forget that the parent poster was asking why anyone is bothered about this and here it is: Either Novell is an asshole to GPL developers and sold something Novell didn't own, or Novell is an asshole to GPL developers and violated their copyright.
  7. Red Hat Opportunity? by Erwos · · Score: 1

    Well, here's a nice hiring opportunity for Red Hat - let's see if they take advantage of it.

    --
    Plausible conjecture should not be misrepresented as proof positive.
    1. Re:Red Hat Opportunity? by Anonymous Coward · · Score: 2, Interesting
      Well, here's a nice hiring opportunity for Red Hat - let's see if they take advantage of it.

      To be honest I think I would rather see IBM pick up Samba and Jeremy. Not because I don't have anything against Red Hat because I don't. IBM has a lot more good lawyers should Microsoft start threatening lawsuits and IBM would be better equipped to stand up against any attack from Microsoft. Not to mention the fact that SMB originated at IBM.

  8. If developers want to do it, sure by saikou · · Score: 1

    I think his decision is what was expected. People can argue all they want about "technical compliance" and "spirit" of the license. In this case decision seem to be based on a simple fact: employer did something, that goes against employee's beliefs. Employee decided not to "live with it" and quit, as changing of employer's mind seems to be impossible.
    I hope he will find another job soon. I also hope that other people that may be unhappy about the situation will find courage and chance to do something about it.

  9. Putting your money where your mouth is by astrashe · · Score: 5, Interesting

    Whatever you think about what Allison has done, you have to repsect him for living up to his convictions. This sort of thing can't be good for your career, or for your bank account.

    I really admire people who choose to live by their principles, even when it's hard or costly to do so.

    1. Re:Putting your money where your mouth is by seanellis · · Score: 1

      Seconded, wholeheartedly.

    2. Re:Putting your money where your mouth is by epiphani · · Score: 1, Redundant

      Agreed.

      Now, lets make sure that he gets picked up quickly by someone else. If we can start saying without question that leaving Novell in protest of the patent deal will get you a few job offers off the bat will be quite good.

      Keep these people employed!

      --
      .
    3. Re:Putting your money where your mouth is by Daemonstar · · Score: 0, Redundant

      I agree. Money is important, but being happy with your job is also important. Besides, I doubt he will have much trouble finding work.

      I used to work for the local city government, but quit because of the way my co-workers (especially supervisors) did their job, the way they treated others around them, and because they gave little to no flexability in scheduling. By voicing my opinion and leaving, I later found out that it had inspired someone else there to leave for the same reasons. She found a better job and is much happer. Me, it took a while, but I finally found work. I really liked the position I had, but when you can't stand the way things are run, you have to do what you feel is right.

      --
      I don't reply to Anonymous posts; if you have something to say to me, identify yourself or I won't reply.
    4. Re:Putting your money where your mouth is by PinkPanther · · Score: 3, Insightful
      This sort of thing can't be good for your career, or for your bank account.
      I will admit that this sort of move is risky, but I strongly suspect that this will be good for both his career and his bank account.

      So this leader of a popular software development project goes and gets his name splattered all over the web tied to an account of how strong his integrity is?

      You can't buy marketing like that :-)

      --
      It's a simple matter of complex programming.
    5. Re:Putting your money where your mouth is by Anonymous Coward · · Score: 0

      Yeah... It's even easier when you have enough money in the bank account to walk when you want. I'm not saying that resigning his post on principle is bad (or that he didn't do it)... it's just a lot easier when you're sitting on a pile of money to make these type decisions... plus, it looks good for him to do so (good press). I walked from a job on principle before and it was pretty difficult since my bank account wasn't loaded and I had to spend time unemployed.

    6. Re:Putting your money where your mouth is by Heir+Of+The+Mess · · Score: 2, Insightful

      I wouldn't feel too bad for him. He's moving to google http://blogs.zdnet.com/microsoft/?p=170/ which I'm sure isn't too bad for his career or his bank account. It's easier to have strong principles when you have a safety net. I've always found a job offer from a competitor to be the perfect opportunity to get things off my chest followed by a resignation.

      --
      Australian running a company that does C# / C++ / Java / SQL / Python / Mathematica
    7. Re:Putting your money where your mouth is by Anonymous Coward · · Score: 0

      Whatever...he had a Google job lined up. Resigning "on principle" doesn't mean much when you're moving to a cushier job.

  10. If it's a matter of principle.. by Anonymous Coward · · Score: 0, Interesting

    ..why didn't he resign immediately?

    It's easy to be courageous with another job waiting.

    1. Re:If it's a matter of principle.. by Anonymous Coward · · Score: 0

      usually it makes sense to take some time to figure out if what happened is really what you think happened, instead of jumping to conclusions when it comes to making a major decision like quitting your job. once it becomes clear it really is the worst case scenario of what you feared, you then leave.

      your implication is the kind of sniveling worm-like response usually made by people who don't have the guts to live up to their principles and are envious of people who do, and can't bring themselves to admit it so they make snide comments about "oh he should have done it immediately" and crap.

  11. Probably Not by codepunk · · Score: 2, Funny

    However, nobody is saying samba has got to be easy to compile, run or maintain on Novell's distro.

    --


    Got Code?
  12. What are you smoking? by Scott+Lockwood · · Score: 1

    Ok, I'll bite. You DO realize that the chances of J A going without a job are about the same as the likelyhood of being killed by falling airplane parts, in a submerged submarine, right?

    --
    But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    1. Re:What are you smoking? by nbannerman · · Score: 1

      No fair, my sub was written off this morning by a Trent engine manifold...

    2. Re:What are you smoking? by Hyram+Graff · · Score: 1

      Is this counting airplane delivered torpedos as falling airplane parts?

      --
      0*0
      00*
      ***
    3. Re:What are you smoking? by Scott+Lockwood · · Score: 1

      lol - OUCH! Sorry to hear that!

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    4. Re:What are you smoking? by Scott+Lockwood · · Score: 1

      No, those are parting gifts.

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    5. Re:What are you smoking? by Anonymous Coward · · Score: 0

      I'll bite too. You DO realize that the chances of Jeremy Allison to find another job where they pay him to work on Samba 100% of the time are about the same as the likelyhood of being killed by falling airplane parts, in a submerged submarine, right?
      In the past, I've seen hundreds of cases of developers being forced to dramatically scale down their participation on FOSS projects, or to abandon them completely because their employers needed them work on some other, revenue-generating, non-FOSS-related stuff.
      If in his new job Jeremy Allison can't find the time to update Samba to be compatible with Vista's SMB2, or even to fix bugs or add new features to the current version, who do you think will benefit most from that? Linux or Microsoft?

    6. Re:What are you smoking? by Scott+Lockwood · · Score: 1

      I disagree. I have no doubt at all that he'll find another position with someone. IBM for example.

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    7. Re:What are you smoking? by Anonymous Coward · · Score: 0

      And I have no doubt that Santa Claus really exists, and lives up there on the North Pole.

    8. Re:What are you smoking? by Scott+Lockwood · · Score: 1

      Confirmation that you're an idiot just came through on the Samba mailing list:

      -----Original Message-----
      From: samba-bounces+xxxxx=xxxxxxxxxx.com@lists.samba.org [mailto:samba-bounces+xxxxx=xxxxxxxxxx.com@lists.s amba.org] On Behalf Of Jeremy Allison
      Sent: Monday, December 25, 2006 12:03 AM
      To: david rankin
      Cc: samba; opensuse
      Subject: Re: [Samba] Re: [opensuse] Open-source leader leaving Novell forGoogle

      On Sun, Dec 24, 2006 at 11:11:18PM -0600, david rankin wrote:
      > Jesus,
      >
      > I hope it isn't true. But if it is, we will miss him dearly, both
      > here and very much so on the Samba list. However I can under stand and
      > respect the decision. Good luck and God speed Jeremy. Jerry, can you
      > pick up the slack?? An ill wind blows for us all as a result of the MS deal....

      It's true I'm leaving Novell, but why do you think this means I'm not going to be on any Samba lists ? I'm joining Google on 2nd Jan, and believe me when I tell you they're *very* interested in me spending all my time on Samba :-) :-).

      As Herb once said to me, "Same job, different office" :-) :-).

      Jeremy.
      --
      To unsubscribe from this list go to the following URL and read the
      instructions: https://lists.samba.org/mailman/listinfo/samba

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
  13. Doesn't it? by sammy+baby · · Score: 1
    Warning: IANAL.

    You're wrong.

    There are many instances in the law where intent does matter very much, especially in regard to contracts. If it can be shown that Novell and Microsoft colluded to violate the terms of the GPL, you can bet it would be worse for them than if they had been found to be "accidentally" in violation. Plausible deniability is nice to have.

    Related to intent is understanding - the concept of the "meeting of the minds," which is central to contract law. This excerpt is taken from a site about health care, but it's still applicable. Emphasis mine:

    The parties to a contract must reach a meeting of the minds--that is, both parties must have the same understanding of the agreement and of their respective obligations and rights under the contract.

    This concept has a number of implications. Meeting of the minds requires that both parties have good faith. Good faith on the part of a party means that the party does not have the intention of deceiving or taking unfair advantage of the other party. Without good faith, the parties do not truly have the same understanding of the agreement and so a meeting of the minds has not been reached. Therefore, if it can be shown that either party was not acting in good faith, the contract can be declared invalid and rescinded (cancelled).

    Sometimes there is no meeting of the minds because important information is missing or incorrect, meaning that through no fault of his own one of the parties does not have an accurate understanding of the terms of the agreement...


    And of course, in criminal law, the intent to commit a crime is hugely important. Google "mens rea" sometime... or, wait, I'll do it for you. Of course, any case coming out of this would likely be civil rather than criminal, but you get the picture.
    1. Re:Doesn't it? by Anonymous Coward · · Score: 0

      Related to intent is understanding - the concept of the "meeting of the minds," which is central to contract law. This excerpt is taken from a site about health care, but it's still applicable.

      The GPL is a license, not a contract.

    2. Re:Doesn't it? by arth1 · · Score: 1
      The GPL is a license, not a contract.

      So? The license agreement is a contract.
    3. Re:Doesn't it? by Anonymous Coward · · Score: 0, Troll

      Warning: IANAL.

      You're wrong.


      Fucking priceless. Your opinion here isn't worth shit. If you're not a lawyer, quit trying to state what a law does and doesn't mean - because you have no fucking idea.

    4. Re:Doesn't it? by SpaceLifeForm · · Score: 1
      No, it's not a contract. You do not have to agree to the GPL in order to use GPL software.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    5. Re:Doesn't it? by Anonymous Coward · · Score: 0

      This is a discussion about a license, the GPL, not EULAs. If you wish to discuss EULAs, please find another forum.

    6. Re:Doesn't it? by GodInHell · · Score: 0
      1) Law students wander these halls too.

      2) Law is all about opinion. (what do judges write again?)

      3) He's right, grab any book on contracts and look for "meeting of the minds."

      4) Impressive Trolling.


      -GiH

    7. Re:Doesn't it? by sammy+baby · · Score: 1
      This is a discussion about a license, the GPL, not EULAs. If you wish to discuss EULAs, please find another forum.


      Don't be dense.

      An End User License Agreement is a license that the End User most Agree to before using the software.

      The GNU Public License is a license that a recipient of the software must Agree to if they intend to distribute or modify the software.

      The difference is that the former is limited to End Users, and there is rarely an option to redistribute or modify the software. But they are both certainly licenses, and acceptance of the terms of a license constitutes agreement.

      Side note, and unrelated to this discussion: has anyone noticed that the same people who defend the GPL's validity as a legally binding agreement tend to deny the validity of EULAs? I mean, there are some practical reasons why it's unreasonable to assume that someone is going to wade through 10 pages of legalese in order to install a security patch, but otherwise...
    8. Re:Doesn't it? by ffrinch · · Score: 1

      "Side note, and unrelated to this discussion: has anyone noticed that the same people who defend the GPL's validity as a legally binding agreement tend to deny the validity of EULAs?"

      The position isn't inconsistent.

      If a book comes with a license agreement allowing the recipient to freely distribute copies (and modified copies) according to certain conditions, they don't have to agree to the license. They can believe that it's invalid, and are still entitled to use (i.e., read) the book to their heart's content. If they want to distribute copies, however, they either agree to the license or commit copyright infringement.

      That is, claiming that they accepted the license would be a defense against a charge of copyright infringement. The distributor had offered the terms and they had agreed to them, receiving the additional rights granted by the license agreement.

      If the book came shrink-wrapped with an EULA claiming that it was prohibited to use as a fly-swatter, it would be (deservedly) ridiculed. It's ridiculous that software EULAs purport to impose similar conditions, like not publishing benchmarks or criticism. If you publish a benchmark and claim that the EULA was invalid, what do they sue you for? Even if you didn't agree to the terms -- and clicking "agree" really doesn't cut it -- you haven't done anything that a reasonable person wouldn't believe you already had the right to do as a result of buying the software.

  14. Pretty simple actually by codepunk · · Score: 2, Insightful

    He did not like how his employer was circumventing the spirit of the license by which his code is developed. You see it does not matter what you, Novell, MS, HP etc thinks this is about developers. In a FOSS development model those commercial entities mean absolutely nothing at all, the developer who licensed the code steers the ship, not the other way around.

    Good on him, it is his code!

    Not like he has to work very hard at finding a new job anyhow.

    --


    Got Code?
  15. In short by Anonymous Coward · · Score: 0

    In short they didn't approve his raise and bonus.

  16. Winnowing The Herd by mpapet · · Score: 2, Insightful

    I think someone at Microsoft understands that most paid OSS developers choose their salaries over the many principals violated with the deal. I'm not discrediting the developers who make this choice. I've sacrificed my principals in exchange for feeding my family many times and I'm not alone.

    As has been said before, Microsoft is trying to narrow its Linux competition to one or two then eliminate them later. The influx of corporate politics and big money/power stands to poison the whole notion of bazaar-style development. Big-Money has a way of doing that. Look at Debian and dunc-tank. That's hardly big money and it's already affected volunteerism at that project.

    As is often the case, there are just a couple of people who carry such a strong sense of principals, that they choose a more uncertain path over a more predictable one that is the result of having more flexible principals.

    I for one admire his sense of conviction.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Winnowing The Herd by Tx · · Score: 2, Funny

      I'd sacrifice my principals for lots of cash, but not my principles.

      --
      Oh no... it's the future.
  17. Of course they can by bonefry · · Score: 3, Interesting

    A software's author that licensed the project under the GPL or any other license STILL RETAINS THE COPYRIGHTS of that project. Thus ... the author of a software project can specifically forbid a certain individual or company from distributing that software. If the Samba team holds the copyrights of Samba ... go figure, they can.

    1. Re:Of course they can by rhombic · · Score: 1, Informative

      Except that if the team wants to continue to use the GPL, the FSF doesn't allow modification of the wording of the GPL license, which is what they'd have to do. Inserting a clause like, "All of the above doesn't apply to MS or Novell, they are teh sux and they can't use it" would put the team in violation of the FSF's copyright on the license itself.

      Oh yeah, and MS/Novell could just fork off of a version that's already out there. The Samba team controls the copyright, but they've already released versions under the GPL. They can't pull that back in, it's already out and specifically says MS/Novell along w/ everyone else can use and abuse it, as long as they comply w/ the license. One of the "problems" w/ the GPL, that's "fixed" in v3.

      --
      1984 was supposed to be a warning, not an instruction manual.
    2. Re:Of course they can by Anonymous Coward · · Score: 0

      This would only be for only future versions. Novell can take anything currently released and use that as long as they don't violate the license. That's how the GPL works. Once you release a version that version is bound to the terms of that license. You can't stop someone from using the software just because you don't like them or whatever. That again is the whole point of the GPL. Anyone is free to use the code as long as they stick to the terms of the license.

      If there is no license violation there is nothing they can do other than make all new releases exclude Novell. They can't keep Novell from using the already released versions because those are under the GPL free and clear as long as Novell doesn't violate the GPL.

    3. Re:Of course they can by drinkypoo · · Score: 1

      Nope. The GPL says you have the right to distribute if you get it. If you instituted a license which said that certain people wouldn't be able to distribute it would conflict with the GPL. If your other license conflicts with the GPL the GPL version cannot be distributed. If you cannot distribute the software under the GPL then your sole remedy is to stop distributing the software. Thus a clause like that would cause you to be unable to distribute the software - unless you substantially rewrote the license, to the point at which it would not be GPL - and thus it would be incompatible with OSI-approved licenses. Also you would need permission from any contributors, or to rewrite their portions of the program...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:Of course they can by bonefry · · Score: 1, Informative

      No, you don't get it ... its not about the GPL license ... its about the right to do whatever you want with your copyrights. A copyright holder can prevent an individual or a company from having access to the GPL license. If Novell doesn't have the right to use the GPL license of Samba, Novell cannot redistribute it.

    5. Re:Of course they can by bentcd · · Score: 1

      The thing is that the samba team has at one time said "yeah, sure you can use this, no problem" (I paraphrase). For them to then, a couple of years later, say "ah, no sorry, what we said earlier doesn't apply now, you can't use that anymore" is a particularly nasty variant of bait and switch that I doubt will go down well with the courts.
      I expect that, in a nutshell, once licensed you stay licensed.

      --
      sigs are hazardous to your health
    6. Re:Of course they can by Skjellifetti · · Score: 1

      Except that if the team wants to continue to use the GPL, the FSF doesn't allow modification of the wording of the GPL license...

      How did Linus get away with modifying the GPL? The GPL states that:

      This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

      And yet Linus has added:

      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.

      The GPL allows me to redistribute the kernel under v3, but Linus seems to be trying to prohibit redistribution using the any later version clause if I am reading his words correctly.

    7. Re:Of course they can by Znork · · Score: 1

      "A copyright holder can prevent an individual or a company from having access to the GPL license."

      Yes, the copyright holder could refrain from licensing the code to Novell. However, with the bog standard GPL someone else could give it to Novell instead, as the rights follows the redistribution, so without a license change you couldnt accomplish much.

      However, what you _could_ do would be, for example, to include some potentially protected non-GPL code owned by, for example, RedHat, into the codebase and then sign a deal with RedHat on behalf of your first-line recepients (and/or anyone but yourself and Novell) where RedHat promises not sue them.

      Thus you'd be doing exactly the same vile thing Novell has done, right back at them (and incidentally destroying more or less the whole point of opensource/free software at the same time).

    8. Re:Of course they can by T-Ranger · · Score: 2, Informative
      Well, he diddn't change the text of the license. He added a clarifying statement to before the text © FSF. And he didn't change the license, either, as the license explicityly allows for such clarifying statements.
      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.
      If you are going to be commenting on licenses, it may be a good idea that you actually read them.
    9. Re:Of course they can by Linegod · · Score: 2, Informative

      >>Except that if the team wants to continue to use the GPL, the FSF doesn't allow modification of the wording of the GPL
      >>license...

      > How did Linus get away with modifying the GPL? The GPL states that:

      Because that is not the license. It is a paragraph that tells you which license you can use. It is not a part of the GPL. Many people use the same paragraph, but it is not a part of the license.

      --
      -- I care not for your foolish signatures.
    10. Re:Of course they can by Viking+Coder · · Score: 1

      You've lost me. As soon as someone ELSE contributes to a work, there is no longer a sole author. The "original author" can no more change the copyright than the "new author" could. They would have to agree.

      If Novell is one of the contributors, they would have to agree exclude themselves...?

      The GPL cuts both ways. It prevents "users" from modifying and hiding their changes, and it prevents "authors" from changing the license out from under the "users." ...right?

      --
      Education is the silver bullet.
    11. Re:Of course they can by nuzak · · Score: 1

      > How did Linus get away with modifying the GPL?

      You cannot violate your own license.

      He may very well be incorrectly calling it the GPL and not "a modified GPL", but even the FSF doesn't seem to want to raise a fuss over the term, since they've never aimed at making it a servicemark.

      --
      Done with slashdot, done with nerds, getting a life.
    12. Re:Of course they can by maxume · · Score: 1

      I don't think that the GPL allows them to do it retroactively. Basically, once you GPL something(that you hold the copyright for...), you can't 'un' GPL the specific version that you GPLed, and anybody can do anything allowed in the GPL with that code, which I believe is the whole point of the GPL in the first place.

      --
      Nerd rage is the funniest rage.
    13. Re:Of course they can by Skjellifetti · · Score: 1

      If you are going to be commenting on licenses, it may be a good idea that you actually read them.

      Um, I was asking a question about something that puzzled me, not commenting on a license. If you are going to reply to other's comments, it may be a good idea that you first read the comment to which you are replying.

    14. Re:Of course they can by Millenniumman · · Score: 2, Insightful

      It's stupid to let a third party change your license at will. You're essentially giving the FSF full control of your software with that clause.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    15. Re:Of course they can by Kjella · · Score: 2, Insightful

      Except
      a) It doesn't work retroactively and far more important
      b) It will no longer be GPL

      There's no such thing as "GPL with my extra requirement", then it's not GPL or even GPL-compatible. If you're lucky it's still OSI-definition "open source", but I think that would even disqualify it as that.

      --
      Live today, because you never know what tomorrow brings
    16. Re:Of course they can by ppanon · · Score: 1
      If you are going to be commenting on licenses, it may be a good idea that you actually read them.
      The same could be said for you. :-)

      Let's look at that again shall we.

      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. So either the author can specify a version of the GPL licence and the recipient can redistribute with any later release of the GPL, or...

      If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. The author can omit specifying a version number and the recipient can redistribute with any version of the GPL, even 1.0 if that's what they desire.

      By specifying a specific version of the GPL, and only that version, Linus is changing the GPL. You can call it GPL/Linus if you want, but it's no longer the GPL v2.0 and it's arguable that the inconsistency as a result of his change weakens the licence as a result.
      --
      Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
    17. Re:Of course they can by Dave2+Wickham · · Score: 1

      Note the "and" in your first block of quoted text. It's saying that if both of the conditions are true (i.e. the author explicitly allows the use of any later GPL version), then you can use it under the terms of the specified GPL version or any later one. This is the preferred wording of the FSF, but I'm fairly sure it's not required.

  18. The GPL is no longer sufficient for many coders by pscottdv · · Score: 5, Insightful

    From TFA

    "Do you think that if we'd have found what we legally considered a clever way around the Microsoft EULA so we didn't have to pay for Microsoft licenses and had decided to ship, oh let's say, "Exchange Server" under this "legal hack" that Microsoft would be silent about it - or we should act aggrieved when they change the EULA to stop us doing this?"

    I think this sums up both the reason why the GPL community is mad at Novell even if they didn't technically violate GPLv2 and why there is a need for GPLv3.

    Some are saying that the community has no right be mad at Novell because they aren't technically in violation of the GPL. Fine for them. But many of those that contribute code to GPL projects do so because they believe in the intent of the GPL, which is that all who receive the code are to be on the same legal footing as all others regardless of how they receive it. If the GPLv2 is no longer sufficient to provide this guarantee, then changes are needed. And it is perfectly valid for Eben Moglen to craft the changes to plug specific legal-loophole, zero-day exploits in the GPLv2 such as this Microsoft-Novell deal.

    Novell keeps trying to make this deal smell rosy by talking up the interoperability part of the agreement. Are they really so stupid that they do not see that the interoperability part of the deal is not what has GPL supporters upset? They could have made any number of deals with Microsoft to work on interoperability without trying to destroy the foundation of the GPL.

    --

    this signature has been removed due to a DMCA takedown notice

  19. You clearly know nothing about contract law by Anonymous Coward · · Score: 1, Informative

    Intent is a vitally important part of contracts. Essentially, whenever there's any dispute over a contract, unless a term is specifically and excruciatingly spelled out, the intent of the parties making the contract is what the judge will use to make a decision.

  20. This makes me a sad Panda by rudeboy1 · · Score: 3, Interesting

    SUSE 10.2 is my preferred flavor of Linux, and with all that is currently going on, I feel guilty for liking it as much as I do. I see it as a potential windows alternative down the line, once XP is sufficiently outdated, if 10.x keeps improving, cause I'm sure as hell not pissing money away on Vista. Now I feel like I'm being sucked back to the Microsoft teet even as I make plans to break away.

    --
    Raging in an online forum won't do anything for the world around you. To see change, you must take action.
    1. Re:This makes me a sad Panda by rkhalloran · · Score: 2, Insightful

      I've run SUSE for a few years now, through 10.1, but with the Novell deal I've reimaged with Kubuntu 6.10 and I don't plan to look back.

      Ballmer promptly started spewing once this deal was signed that customers of other Linux distros were at risk [somebody shut him up shortly afterwards]. This provides MS a wonderful FUD opportunity now that the SCOX farce is winding down. This implies that Linux actually infringes on Microsoft patents somehow without openly admitting it, and that Novell paid them off to stay legit. All of which is anathema to the FOSS movement that created this code to start with.

      If Stevie B actually thinks there's patent violations in Linux, let him bring them forward. If not, he should STFU and try competing on the merits of his company's products. Oh wait...

    2. Re:This makes me a sad Panda by Anonymous Coward · · Score: 0
    3. Re:This makes me a sad Panda by avanaardt · · Score: 1

      Here's your answer: http://www.ubuntu.com/ I dumped Novell last week for Ubuntu. Go ahead, it will make you feel miles better.

  21. Probably a good thing ... by cjjjer · · Score: 1

    The only thing that holds a company / product back are the people who manage the company or who make the product not the competitors around it. In this day and age if a product or service is as good as people rave about it sells it's self.

  22. ZO)MIGOSH by Anonymous Coward · · Score: 0

    Zealots should think outside the box...
    Unless the box had a MS product in it and we're all gonna die because of that... /sarcasm

  23. Question. by Anonymous Coward · · Score: 0

    Will this new respect for 'intent' extend to respecting the intent of all future anti reverse engineering laws?

  24. Won't revoke rights; Samba team too good for that by KWTm · · Score: 4, Insightful
    Because Samba is distributed under the GPL, they won't be able to revoke the rights to Novell as long as Novell stays within the (letter of) the agreement.

    Besides, in the past, the Samba team has demonstrated a professionalism that has put their detractors to shame, and I hope they can continue to uphold their standards. Witness what they said to SCO when SCO accused the evil Samba team of spreading the deadly plague of Open Source (all the while distributing Samba with their SCO Linux). Here's the letter from Samba to SCO:
    Samba is developed and distributed under the GPL, in exactly the same manner as the Linux kernel code that SCO has been criticising for its lack of care in ownership attribution.
    Because of this, we believe that Samba must remain true to our principles and be freely available to use even in ways we personally disapprove of.
    Even when used by rank hypocrites like SCO.

    Translation: "Up yours, SCO." But they say it in such a way that it will carry weight in business circles. In the same way, Allison's resignation makes a clear statement.

    It would be a mistake to do otherwise; if the Samba team says, "Well, then I *un*-give you the code! Nyaah nyaah!", it would epitomise in the minds of executive decision-makers that Open Source is run by a bunch of immature J.Random Hackers From China who will revoke your license at the slightest provocation.

    One only hopes that Novell will show some more understanding of how much turd they have now placed their foot in, and make some public gesture to show the IT world that OSS is alive and well. Sort of like what EV1 did. Novell's done a lot of good for OSS. I hope they continue.
    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  25. is he tainted now? by wardk · · Score: 1

    having been on the payroll at the time of the contract signing with MS....does this mean he's got any sort of restrictions now dangling on his neck, at least from the point of view of microsoft?

    1. Re:is he tainted now? by rkhalloran · · Score: 3, Insightful

      EXACTLY the sort of consideration this deal generates, all to MS' gain.

      And why the developer community is so seriously dead-set against it. Any code contribution by Novell at this point has to be considered suspect against MS claims of infringement that Novell/its customers are supposedly safe from, but the rest of us are wide-open to.

  26. Re:Don't let the door hit you on your way out. by sparkane · · Score: 0, Flamebait

    Worst troll EVAR.

  27. Intent matters in contract law. by GodInHell · · Score: 2, Interesting

    You don't think that MS and Novell have had teams of lawyers going over everything for this deal, including the GPL. When it comes down to it, it's the letter of the contract that matters, not the intent that was in the minds of the writers. You are about 170 degrees off true (mostly wrong, but not all wrong). A written contract is always subject to interpretation of meaning, definition of words, etc. The more complex the terms used in a contract the more likely it is to be open to interpretation. In American Jurisprudence, the normal goal in interpreting a contract is to reach a true understanding of the intent of the parties to the contract. Here, the parties are the GPL community and Novell/MS. The GPL includes several clear statments of intent - to create freely available open source software, to encourage contribution, and to prevent abuse by parties who would seek to seize that software and claim it for their own.


    I'm not going to take the time to teach class in contracts, but the long and short is that judges (usually) interpret for intent, punish those who seek to abuse ambiguity, and interpret toward a useable contract (if an interpretation makes the contract void, they go with a different interpretation).

    If I write a contract to deliver a dozen roses, but for some reason I think that carnation is called a rose and instead deliver a dozen carnations, I will be held in breach of contract. It doesn't matter what my intent was if I framed the contract improperly to ensure my intent. That's actually not true. If the mistake is unilateral (only the other party made a mistake and you were not aware of it) then they are probably in breach - however, if any element of the contract suggests that the mistake was apparent at the time of contract (the price is far too low, there is evidence that you were show a picture of the final product, etc) you're boned. Judges will tend take a narrow view of parties who attempt to abuse contract language to enforce and unfair deal. If it is clear that the given interpretation is decidedly one sided, or that an interpretation requires ignoring common use of language and interpreted meaning of the contract - they will see it for what it is, abuse of the legal system, and rule accordingly.

    Wikipedia has some information on mistake, and also interpretation: Mistake / Interpretation of Tems.


    -GiH

  28. Mod Up! by Archangel+Michael · · Score: 1

    BINGO!

    Clearest, most concise description of the FUD we as Open Source supports should be saying. Period, end of story.

    Fight FUD with FUD. They made their bed, now is the time to make them sleep in it.

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    1. Re:Mod Up! by Anonymous Coward · · Score: 0

      You're a fucking moron.

      Seriously.

    2. Re:Mod Up! by Archangel+Michael · · Score: 1

      I can see, by your well chosen use of vocabulary, that you are quite intellectual.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  29. Novell would be the one with the fork. by khasim · · Score: 4, Interesting
    This is what I predicted from the beginning. The goal here was fragmentation of the Linux development community. It looks like they could succeed.

    Okay.

    It's basic "divide and conquer" because there will be some developers who don't see much wrong with the deal and will support the Novell Microsoft deal and there will be others who will not.

    But that does not seem to be happening.

    So far it is just Miguel who supports it ... and everyone else who opposes it.

    The ones who don't MAY start new forks/projects and join other distros, or... they may just move on to other things entirely.

    I think you're confusing those items.

    If the legendary Jeremy Allison moves to Red Hat or Canonical, he'll probably still be working on Samba. And when the GPL v3 comes out, it will probably be adopted by Team Samba.

    So in that specific case, it would be Novell who would have to fork the project and do all the work without the help of Team Samba.

    This ensures a two-tiered Linux world with crappy underdeveloped software in non-blessed distros (Gentoo, Debian, etc...) and second-rate (compared to Microsoft Windows solutions) software in the intentionally stunted Novell Suse Linux and anyone else who decides to sign on.

    Huh? So Red Hat (where Alan works) is "second-rate"?

    Or is it that Ubuntu is "crappy"?

    I don't see that happening. Instead I see a company flailing at its declining marketshare and signing an agreement to FUD everything else Linux related.

    Just like SCO did.

    And Novell will die, just like SCO is dying.
    1. Re:Novell would be the one with the fork. by Anonymous Coward · · Score: 0
      So far it is just Miguel who supports it ... and everyone else who opposes it.

      You forgot about Hubert Mantel

      Seems more mixed to me with different developers having different views. http://www.linux-watch.com/news/NS6962961128.html

    2. Re:Novell would be the one with the fork. by eno2001 · · Score: 2, Insightful

      It's all hypothetical, but I'm speaking strictly from the vantage point of a non-technical person (I am an IT person, I'm just playing non-tech's advocate.) and that is likely the way they will see things. "Oh... I heard that you shouldn't use RedHat in the server room because it can't run on the latest servers since they didn't go with the Trusted Computing option that Novell did". Or... "Yeah, I could use Debian to run a web server but this review I read said that Novell's Apache based web server has full IIS compatibility and is able to essentially duplicate the previous version of IIS". To those people, Novell is going to seem like the easy choice and the others will be fairly irrelevant. Of course to those same people anything that isn't "Big name/corporate backed" isn't relevant anyway. My bosses keep trying to convince me that we should have paid support for EVERYTHING we run in the server room so they really want Redhat or Novell. With the latest, they are starting to lean towards Novell and away from Redhat. Not wise, but that's the typical impression of non-technical folks.

      Personally Gentoo rocks my world and I run it on all the boxen at home as well as on a few Xen VMs here doing some fairly important stuff (syslog for our network switches routers and firewall for example). The only thing that makes me run "supported" Linux distros are product requirements. Oracle's management package MUST run on RedHat Linux Enterprise for example. Can't get away from that... So if these companies eventually start dictating that only the "one true" Novell Linux is the only supported one, I'll be stuck. And you know there are going to be people who will see the Microsoft "blessing" of a Linux distro as meaning that it's got a higher level of quality over non-blessed distros regardless of the truth.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  30. It's not about copyright by Anonymous Coward · · Score: 5, Insightful

    The issue with the Novell deal isn't copyright. It's patents. In countries dumb enough to allow software to be patented (ie, the US), Microsoft could make Samba 100% compatible with Windows and 100% GPL. They'd be able to say, though, if you're not a Novell user they'll sue you for patent infringement.

    1. Re:It's not about copyright by novus+ordo · · Score: 1

      Bravo! It's about you creating GPL code and releasing it, but then MS suing you for patent violations. This is clearly forbidden in Section 7 of the GPL but MS has gotten around it(?) thanks to Novell. Thanks Novell!

      --
      "You're everywhere. You're omnivorous."
    2. Re:It's not about copyright by Anonymous Coward · · Score: 0

      In countries dumb enough to allow software to be patented

      Dumb enough! Right. None of the power elite (you know, the people with that special "right" to employ coercion as their means) benefit from being in the business of software patents, let alone the patent business in general! Give them a break -- they're just dumb!

      Right. It never occurred to you that maybe, just maybe, the people who control government operate in self-interest just like you, me, and every other human being on this planet?

  31. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  32. Would GPLv3 protect against this? by mpcooke3 · · Score: 2, Interesting

    I'm interested to know if the GPLv3 would help stop this kind of deal.

    My understanding is that under GPLv3 Novell would have their rights to redistribute samba terminated if they themselves tried to enforce a patent claim against Samba.

    Under GPLv3 would Novell have their right to redistribute Samba terminated if they knowingly introduced code that was patented by Microsoft into Samba? Also how could it be proven?

    1. Re:Would GPLv3 protect against this? by Anonymous Coward · · Score: 0

      There is no knowingly or unknowingly about it. Novell is allowed to distribute code under GPL3 only if they are able to give to all third parties all rights that they themselves have in the code. If Novell has some rights to a patent in the code but they cannot sublicense all third parties with those same rights, then they do not have permission to distribute the code under the GPL.

    2. Re:Would GPLv3 protect against this? by novus+ordo · · Score: 1

      This is already in GPLv2 under Section 7. However this deal "by proxy" is not explicitly covered and Moglen has said this will be rectified in GPLv3.

      --
      "You're everywhere. You're omnivorous."
    3. Re:Would GPLv3 protect against this? by mpcooke3 · · Score: 1

      Novell have no rights to the patents. That is the issue.

      Microsoft has indemnified them against prosecution, that is all.

  33. Respect, by PinkyGigglebrain · · Score: 1

    He has mine for now. Anyone who will put there convictions above their paycheck gets high marks from me. I have seen too many people keep silent because they don't have the guts to speak out against something that is wrong or just plain stupid, and I'm not just talking about the M$/Novell deal.

    One of the greatest Evils is when the Good stand by and do NOTHING.

    1. Re:Respect, by 10scjed · · Score: 1

      To sin by silence when they should protest makes cowards of men. (Abraham Lincoln)

      --
      --10scjed IANAL,AFAIK
    2. Re:Respect, by DaMattster · · Score: 1

      I could not be in more agreement. When the good stand silently by, they become a part of the problem.

    3. Re:Respect, by Anonymous Coward · · Score: 0

      You know what? People who still try to quote Boondock Saints are pathetic fuckers. That means you.

  34. Divide and.. beat the crap out of Red Hat. by GodInHell · · Score: 1

    I don't know why this guy is leaving. This is a good thing all the way around for the Linux community. I have large customers (people who spend money on software AND use Open Source) who run Windows and Linux side by side. Their NUMBER ONE complaint has been lack of interoperability. They say that they will definitely continue to run Linux in their environment and will probably switch to SUSE Linux because of this agreement. Here's the problem 1) MS has only made this deal with Novell - with whom it has a long history of competitive co-operation to Novell's detriment. 2) Ballmer has already started struting about how this is "only fair" and using it as a club to suggest to linux users that not running SuSe leaves them liable for patent infringment - attempting to beat them away from the much more popular Red Hat, a company which also happens to be far more comitted to the open source development format.

    This is a bribe to one company, intended to set a precedent which MS will then use on the others. I predict based on my reading of the documents and MS's past behaviour that MS is preparing suits now, to file against Red Hat's customers, and the company itself.

    Eliminating the party who is stubbornly opposed to you makes conquering the rest so much easier.


    -GiH

    1. Re:Divide and.. beat the crap out of Red Hat. by PenguinBoyDave · · Score: 1

      If they do, I'll publicly admit I was very wrong in my assessment of the situation. I don't have any mod points, but if I did, I'd give you an "insightful" rating right now. Good post...very thought provoking.

      --
      I'm not a troll, but I play one on Slashdot.
  35. Utter rubish by Anonymous Coward · · Score: 2, Insightful

    Pardon me, but you sound like a Novel apologist, trying to sow memes of acceptance of Novell.

    Allow me to disprove your contention; it's quite simple. This deal has been such an utter P.R. disaster for Novell that they have had several P.R. opportunities to try to explain themselves. Not once has there ever been any hint of a statement that this deal was either a mistake, or that they were forced into it.

    Your "feelings" about this deal are seriously misguided. If this were indeed the case, Novell would have at least dropped some hints in this direction. Please quite trying to justify this deal by making excuses for Novell.

    My impression of Novells' actions and statements is that this deal is all about greed, not fear.

  36. Others can do a better job. by GodInHell · · Score: 2, Informative

    I'm not involved in coding for the project or in GPL litigation.. however others who are have posted below. Check it out.

    Here's one argument on how Novell is breaching the GPL: sample

    I'd do more linking.. but it's lunch time.. [runs off to meet fiance]

    -GiH

  37. You miss the point by Eric+Damron · · Score: 5, Interesting

    You miss the point. Novell and Microsoft are saying that they can release code under GPL v2 that is encumbered by patents. If this is the case FOSS CANNOT use that code without denying the freedoms that were the intent of the GPL.

    Microsoft could, for example, help Novell inject their IP and later tell users that they must pay or be sued for patent infringement.

    I didn't support GPL v3 in the past but I do now. Let's close this loophole and shun Novell until they straighten up and fly right!

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:You miss the point by lawpoop · · Score: 2, Interesting

      Let me see if I understand what you are saying. They are creating works derived from GPL'ed code, but they claim that their contribution is covered by patents, so even if they were to distribute the code, end-users would have to deal with patented processes, ideas, etc. in that new code.

      So there would be a kind of built-in conflict of the resulting code -- on the one hand, it's GPL'ed, but on the other hand, it's covered by patents. Is that about right?

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    2. Re:You miss the point by giminy · · Score: 2, Interesting

      Thank you. A few years ago I got flamed on slashdot for suggesting that patent encumbrance could be an issue for the GPL. This deal is making people "get it." Yay!

      I recommend taking the GPL Quiz for anyone that questions anyone else's understanding of copyright and patent issues. It's a great starting point to understand some of the issues, and slashdot would be a better place for it.

      --
      The Right Reverend K. Reid Wightman,
    3. Re:You miss the point by oohshiny · · Score: 1

      You miss the point. Novell and Microsoft are saying that they can release code under GPL v2 that is encumbered by patents

      I don't get your point. How has anything changed?

      Microsoft has been asserting for years that Linux infringes on their patents. The Novell deal doesn't change that.

      Nor does the Novell deal protect Novell's users. Microsoft can promise not to sue Novell users, but the second Microsoft actually attempts to assert any of their patents against a piece of software, everybody, including Novell, has to stop distributing that software, no matter what deal Microsoft and Novell have. Furthermore, if Novell knowingly distributed software that was patent encumbered, then they are violating the GPL and may be sued by the authors of the software in question.

      I just don't see how anything has changed.

      I didn't support GPL v3 in the past but I do now. Let's close this loophole and shun Novell until they straighten up and fly right!

      I think the GPL v3 will do some good in terms of clarifying these issues further. Still, I don't see a significant problem even under GPL v2.

      In terms of "shunning Novell", come on, are you buying any of their stuff anyway? I'm not. If this deal gets more open source software into corporations by giving them a warm and fuzzy feeling, all the better. The more Linux gets its foot in the door, the better. If Microsoft thinks this deal will help them in any way, they are sadly mistaken.

    4. Re:You miss the point by lp_bugman · · Score: 1

      Yes.
      The code is GPL but a company can claim the algoritms are infinging in their patented technology. This is exaclty what every body is afraid of with the Microsoft deal.

      --
      BSD licensed software can't be stolen....
  38. Re:Won't revoke rights; Samba team too good for th by Scott+Lockwood · · Score: 1

    That is the first, intelligent and well reasoned response I've seen yet. You make some very good points.

    However, I think there is a fundamental difference between SCO and Novell. SCO was worthless from the word go. Novell was, and could again be, a good partner. It's going to be necessary to wack them with a clue stick repeatedly until they wake up.

    --
    But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
  39. au contraire by toby · · Score: 1

    I don't see that this would do any harm to his career at all.

    He's just proven himself to be a highly ethical person. Some employers like that.

    --
    you had me at #!
  40. Don't make deals with MS by plopez · · Score: 1

    I just have to wonder if the Novell management was high that day. If you look at what tends to happen to MS 'partners' you should know *not* to deal with MS. Example include: Sybase, thier 'plays for sure partners', Orange, IBM, and I'm sure others could come up with more.

    I predict in a year or two Novell will be an empty shell of a company, not unlike SCO. Also, IIRC, doesn't Novell hold Unix copyrights and patents? If Novell needs to liquidate assests would MS get first refusal on these copyrights and patents? What exactly was in their deal?

    It maybe tinfoil hat thinking on my part, but it could get scary.

    --
    putting the 'B' in LGBTQ+
  41. Novell on your Resume is becoming a negative thing by Anonymous Coward · · Score: 0

    Indeed.

    Already, people with recent SCO experience on their Resume are treated like pariahs. I know I won't work with anyone who has that. I certainly won't hire them.

    Unless Novell makes a U-turn here, anybody who's got Novell on their Resume is going to get similar treatment.

  42. It's not LGPL by mangu · · Score: 5, Insightful
    they'll just link to an external library that hides all the new functionality


    The beauty of the GPL is that they cannot do that. That's why I support the GPL over all other licences, its track record to this day has been perfect in keeping free source free.

    1. Re:It's not LGPL by Sloppy · · Score: 2, Insightful
      they'll just link to an external library that hides all the new functionality
      The beauty of the GPL is that they cannot do that.
      Really? They'll get sued and injuncted like Nvidia and ATI did?
      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:It's not LGPL by kamome · · Score: 1

      The GPL will keep free code free, but not (necessarily) prevent unfree code from being used to work around this "problem" - see binary linux modules.

    3. Re:It's not LGPL by nuzak · · Score: 1

      Linus does not consider these modules to be "derived works". See http://kerneltrap.org/node/1735 (he doesn't mention the graphics drivers specifically, but it does make his general stance clear). Obviously it's a grey area, and he even says so, but it's (nominally) still his kernel and still up to him.

      I suspect however that adding new and necessary interop functionality to Samba, a piece of software specifically made for interoperability, would be interpreted pretty damn quickly as a "derived" work, in which case it doesn't really matter how you attach it to the original work -- the GPL will still come into force.

      --
      Done with slashdot, done with nerds, getting a life.
    4. Re:It's not LGPL by Znork · · Score: 2, Interesting

      Do note that many Linux vendors do not ship proprietary drivers because of that exact GPL requirement. You're entirely free to ship the components apart (like NVidia and ATI), letting the end user do the combination, but shipping the combined work is a violation.

      Supposing a loadable module functionality for Samba that would allow a reasonably 'separate' entity to exist without incursions into the Samba sourcecode it might be possible for a third party to ship such a module and let the end users do the combining. But it would fairly painful to manage.

    5. Re:It's not LGPL by deKernel · · Score: 0

      That is where you are incorrect. The GPL does not cover the use of dynamic libraries. If Novells code does not link against the .so (either static or dynamic), and then the .so is loaded manually at runtime, the GPL is not violated. You might not like it, but it is true.

      If this weren't the case, then the Linux kernel would be in violation.

    6. Re:It's not LGPL by Sloppy · · Score: 1

      Linus can decide what to permit in derivations of his works. But he can't define what a "derived work" is. Congress and courts do that.

      The fact that Linus permits ATI's behavior (or for that matter, the fact that FSF despises ATI's behavior and would sue if they had standing), is not evidence for/against drivers being derived works of the kernel.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    7. Re:It's not LGPL by OriginalArlen · · Score: 4, Insightful
      Right, but I think you underestimate the skill of the lawyers and engineers Microsoft will have poring over this problem. How's this for a scenario. Microsoft release a new product specifically for SuSE interop - not just for SMB, but the real value of the Microsoft LAN stuff which is Active Directory. The product contains two main components. A client-side blob runs on the SuSE client and includes ready-to-go config files (note: not software, just configs) to set various stuff up - Kerberos or OpenLDAP, Samba, PAM, CUPS perhaps, and so on. All that software can be made to work well with AD, but anyone who's tried to learn it from the man pages will have also spent a lot of time searching mailing lists for config tips. The software probably has a wizard, it prods the local network and DCs to see what is likely to be well received, makes "intelligent" guesses to recommend default settings, builds the config files and HUPs the required services / daemons. The whole thing would appear in the SuSE installer as something like "Microsoft Network InterOp Kit". The MS-blessed configs would just eliminate the hell of trying to make everything work OK. (I've been using Linux as a workstation and for security and web development work for eight years now, and it's as much as I can do to make icons on the desktop that open smb:// URLs in Konquerer. A keen web dev tried to get his LAMP wiki to use AD authentication, he was messing about with mod_auth_kerb for weeks, every few days he'd get excited & come over asking me to try it again, again without success. The Microsoft-blessed config files can of course be easily read and copied, but they're (c) Microsoft and no other distribution can use them. They can't even read them , go "Aha! I need to set signing to NTLMv2 AES-128 *only* for NMB lookups, not Samba SMB traffic itself" (or whatever it may be) and then write the appropriate lines into their own custom config files. And if anyone looked like getting close, MS would I am sure be happy to kick off a decade or two of lawsuits, draining tens of millions of dollars from the victim distributions and vigorously smearing FUD over the whole GNU world. The end result is that SuSE Linux interoperates beautifully with a Windows AD based network, has a "Microsoft Approved" sticker on the front, and comes with file & print, mail & whatnot all working really slickly. No other distribution can ship the same thing because Microsoft own the copyright on the configs and client-side agent binary. Other distros can attempt to find their own magic configs, but let's face it, we've been working on Windows interop technologies for ten years and although huge amounts of excellent work have been done, Microsoft will always easily be able to FUD corporates by saying it's unsupported -- "Unlike Microsoft's new "Services for Linux" product, included with our selected Linux Partner Vendor, Novell. Here's their number, tell 'em Bill sent you..." No linking to GPL'd software required, no source released, Microsoft succeed in partially subverting Free software. Score: Microsoft 1: Free Software community 0.

      I personally think it's a tactic that shows signs of desperation; you can bet they've spent a lot of lawyer-years brainstorming ways to attack Free software, but it looks like they've got something here in the short term. It would be a dangerous move to be seen to endorse Linux even slightly, and shipping software to run on it would certainly do that -- but most of all I think it'd increase the exposure of Windows admins to Linux / Free software, which just increases the rate of attrition of MS mindshare. So in a couple more decades, OSes will be seen as far more of a commodity, and minimal, streamlined feature sets with straightforward modular components. And will include an old .au file of a man saying "My name is Linus Torvalds, and I pronounce it 'Lee-nuhx' :)

      --

      Everything I needed to know about life, I learnt from Blake's Seven
    8. Re:It's not LGPL by shaitand · · Score: 1

      The linux kernel does NOT use the standard GPL. Everyone knows this at this point so stop trolling by trying to claim foul on kernel modules everytime this discussion comes up.

      If external libraries are allowed it is because they can be considered seperate works under the provisions of the GPL. The GP is reversing the situation anyway, the controversy comes in when a non-GPL application links a GPL Library, not a GPL application linking a non-GPL library. Libraries are by definition independent of the applications that link to them. You can't violate the GPL at runtime because the GPL does not cover usage, you can only violate the GPL when you distribute. So it doesn't matter if the code intermixes in memory. If it did then you could never write a GPL'd windows app since they all intermix with microsoft libs at some point.

    9. Re:It's not LGPL by mrchaotica · · Score: 1
      You're entirely free to ship the components apart (like NVidia and ATI), letting the end user do the combination, but shipping the combined work is a violation.

      The FSF would disagree with you -- it believes that NVidia and ATI are violating the GPL. The problem, though, is that only the copyright holder (i.e., Linus) can sue, and he doesn't care.

      Supposing a loadable module functionality for Samba that would allow a reasonably 'separate' entity to exist without incursions into the Samba sourcecode it might be possible for a third party to ship such a module and let the end users do the combining. But it would fairly painful to manage.

      Unlike Linus, the Samba copyright holders apparently do care, so this wouldn't fly.

      --

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

    10. Re:It's not LGPL by Tommy_S · · Score: 1

      Interesting idea about copyrighting config files, however I'd think any config files would would have to be considered a "derivative work".

    11. Re:It's not LGPL by tokul · · Score: 1

      configuration files can provide better interoperatibility only when programs are compatible. I think Samba is not fully compatible with Microsoft CIFS implementation and Active directory stuff. Lots of gotchas, closed stuff and hacks that make it work. Novell would have to provide specifically compiled and patched samba version in order to maximize compatibility with microsoft and reduce number of issues. Patches and compilation options are part of source rpms.

    12. Re:It's not LGPL by avanaardt · · Score: 1

      Very good description of the problem. I sent it on to Groklaw. Maybe you should consider posting it there too?

    13. Re:It's not LGPL by dodobh · · Score: 1

      I don't notice Nvidia and ATI distributing Linux kernel binaries.

      --
      I can throw myself at the ground, and miss.
  43. ...and besides by toby · · Score: 1

    I don't think you have much to fear when your resignation immediately makes positive front page coverage on both Slashdot and Groklaw. 100 million people just found out Jeremy Allison's looking for work.

    I'd feel better about my own career if I had that kind of visibility. PS. I'm looking for a job. :)

    --
    you had me at #!
    1. Re:...and besides by Anonymous Coward · · Score: 0

      I here the Bugar King is New Orleans is still looking for people.

  44. I Salute Jeremy Allison For His Guts! by xutopia · · Score: 1

    Too few people let things go by just because their job depends on them shutting up. I'm glad this guy has the power to say no.

    1. Re:I Salute Jeremy Allison For His Guts! by Anonymous Coward · · Score: 0

      It probably helps that any number of companies will gladly hire him... RedHat, IBM, EVault...

  45. They would run Windows, not Linux. by khasim · · Score: 4, Interesting
    It's all hypothetical, but I'm speaking strictly from the vantage point of a non-technical person (I am an IT person, I'm just playing non-tech's advocate.) and that is likely the way they will see things.

    I'm not seeing that. If people question Linux, they'll choose Windows instead.

    Just like Novell's CEO saw when he tried to go head-to-head with Microsoft ... and kept losing the deals.

    "Oh... I heard that you shouldn't use RedHat in the server room because it can't run on the latest servers since they didn't go with the Trusted Computing option that Novell did". Or... "Yeah, I could use Debian to run a web server but this review I read said that Novell's Apache based web server has full IIS compatibility and is able to essentially duplicate the previous version of IIS". To those people, Novell is going to seem like the easy choice and the others will be fairly irrelevant.

    No, the "easy choice" will be Windows. The "easy choice" in IT is always to go with a single vendor. That way there's no finger-pointing about why something won't work that way the salesperson said it would.

    Why would anyone be looking for "full IIS compatibility" from a different vendor when they can have IIS itself? Migrations are expensive and the customers know that deals between IT companies can go sour. It's safest to involve the fewest companies and that means buying from the vendor selling the product itself. Not from someone promising "compatibility" with that product.

    Linux has a few advantages over Microsoft products. And licensing is one of the biggest advantages for the end user. Once that is gone (and it is under Novell's deal), there really isn't any reason for the end user to consider "compatibility" with Microsoft's products when they can just go with Microsoft itself.

    Particularly when Novell has to maintain its own "forks" of projects such as Samba because Team Samba has gone with GPL v3.
    1. Re:They would run Windows, not Linux. by jimicus · · Score: 1

      Linux has a few advantages over Microsoft products. And licensing is one of the biggest advantages for the end user.

      Don't underestimate that. If Microsoft start sic'ing their licensing dogs on more companies, it will become more of an issue.

      The reason why is this: I've looked into the various licensing options and concluded that you aren't expected to understand them or comply with them. There's no way anyone could be reasonably expected to comply with licensing like that without seeking professional legal advice with every mouse click. The whole system is designed to set you up for failure, presumably so that if they send the BSA around for an audit, they're bound to find something that's not up to scratch.

  46. It won't matter by ClosedSource · · Score: 1

    Once somebody has the adjective "legendary" applied to them they become more of a symbol than a key player. If there's such a thing as an FOSS Fellow (like an Apple Fellow) he should appy for it.

  47. v2 already does that by Anonymous Coward · · Score: 0

    What v3 will do is automatically indemnify *everyone* against a patent threat if you offer it to *anyone*. That will basically make M$'s stake in this deal worthless, so naturally they will pull out (as they always have in the past).

    1. Re:v2 already does that by mpcooke3 · · Score: 1

      So as a developer I have to indemnify everyone for all the bits of the software i didn't write?

  48. Storm in a teacup by JJC · · Score: 0

    I find it very difficult to see how the patent agreement hurts anyone. If you're a Novell customer, then you enjoy the warm, snug feeling that Microsoft won't sue you for using SUSE. If you're not a Novell customer, then your life is exactly the same as it was before. Is there some subtlety I'm missing here?

    1. Re:Storm in a teacup by jonnyelectronic · · Score: 1

      It's FUD. The fact that they have an agreement in the first place suggests to people that Novell (read Linux) infringes on Microsoft's IP.

      This means that people start to think "Linux infringes, maybe we should steer clear until it sorts itself out", as it's better to be safe.

      I doubt highly that Linux infringes on any legitimate IP of Microsoft's, but Microsoft what the general public (and managers that don't know any better) to think that it does.

      As was said with the SCO case (or if it wasn't then it should have been), "Show us where we infringe, and we'll happily take it out". Microsoft can peruse all of the source, so why would they choose not to simply sue anyone/everyone who makes money from Linux?

    2. Re:Storm in a teacup by Anonymous Coward · · Score: 0

      but if we show them, they'll take it out! We just want them to stop!

  49. Where's the -1 wrong? by rhombic · · Score: 1

    Dude, I do get it. You seem to misunderstand how copyright & licenses work. The samba team definitly owns the license, and they released a version with a license that says that anyone can copy it and reproduce it and change it, as long as they release whatever changes to the code they make. In doing so, they lost the ability to retroactively go back and say, "I take it back, that's not free anymore".

    Any NEW versions they release, they can release under whatever license they want. But they can't retroactively go back and undo the GPL'ing of their earlier code. If you could retroactively un-GPL code, I can guarantee a huge number of minor projects, that became successful, would have been un-GPL'd by their authors and be commercial software today. New version, whatever license you want, but once it's been released under the GPL license, you can't go back & undo that.

    --
    1984 was supposed to be a warning, not an instruction manual.
  50. The spectre of litigation by GodInHell · · Score: 2, Insightful

    If there is a cloud of GPL-related potential litigation seen surrounding Novell, all its done is traded one potential source of litigation for many potential sources of litigation. There is an essential difference between a threat of litigation from Microsoft, and a similar threat from any grassroots community. MS has the cash on hand to fund litigation until they've emptied the pockets of nearly any opponent - they can file motion after motion which you must reply to or face the very real possibility that the judge will summarily rule in MS's favor (since you failed to respond). The resulting legal bills are extremely cost-prohibitive.


    An honest litigant dosen't need to use these tactics, they are the techniques of the abuser and the oppressor company, but they work, and there are lawyers who will do this for Microsoft, RIAA, and other sources of pain and suffering.


    Microsoft would be willing to bear these costs, because they see a need to confront the open source movment NOW before Google shows the world how to get run everything through a web browser, and open office winds up sitting in front of technical evaluators at middle sized companies. Putting the stink of this kind of litigation - branding open source software as an illegal movment which steals and cheats the system, will drive buisiness back towards main stream solutions. As of right now, MS is the only show in town that qualifies.


    This is another in a long chain of life altering moments that you should probably write about in your diary - today I saw MS launch the second stage of its war on linux.

    -GiH

    1. Re:The spectre of litigation by DragonWriter · · Score: 1
      There is an essential difference between a threat of litigation from Microsoft, and a similar threat from any grassroots community. MS has the cash on hand to fund litigation until they've emptied the pockets of nearly any opponent - they can file motion after motion which you must reply to or face the very real possibility that the judge will summarily rule in MS's favor (since you failed to respond). The resulting legal bills are extremely cost-prohibitive.


      OTOH, a diverse pool of litigants can have the same effect in aggregate by filing lawsuit after lawsuit to which you must respond or risk summary judgement, further, prevailing on a particular issue of against one does not guarantee prevailing on the same issue against another. (Or, when the claims are common, they can institute a common action and pool resources.) And its a lot harder to make a deal with a diverse pool to completely remove the threat of litigation once its perceived in the marketplace and becomes a drag on your product.
    2. Re:The spectre of litigation by GodInHell · · Score: 1

      OTOH, a diverse pool of litigants can have the same effect in aggregate by filing lawsuit after lawsuit to which you must respond or risk summary judgement, further, prevailing on a particular issue of against one does not guarantee prevailing on the same issue against another. (Or, when the claims are common, they can institute a common action and pool resources.) And its a lot harder to make a deal with a diverse pool to completely remove the threat of litigation once its perceived in the marketplace and becomes a drag on your product. My gutt tells me there isn't enough money in the OSS community to protect customers from Microsoft - they will gladly spend too much in a bid to maintain dominance.

      -GiH
    3. Re:The spectre of litigation by DragonWriter · · Score: 1
      My gutt tells me there isn't enough money in the OSS community to protect customers from Microsoft
      That's not really the question; the question is whether there is enough of a combination of money and legitimate grounds in the community to replace the litigation threat that spawned the Novell-MS deal with a reactive threat to discourage more such deals.
    4. Re:The spectre of litigation by ConceptJunkie · · Score: 1

      Maybe you don't realize just how rich Microsoft is.

      --
      You are in a maze of twisty little passages, all alike.
    5. Re:The spectre of litigation by GodInHell · · Score: 1
      MS can sue those who uses linux. This isn't normally a problem for software owners because the EULA indemnifies (takes on legal responsability) for the software's content. Those users who buy SuSE need not worry, but those who use either free (as in beer) GPL software will bear that liability personally. I don't know if Red Hat indemnifies its clinets, but I would like to believe they do.


      This means that while MS can bring coercive preasure on clients to cease using those versions of Linux which remain true to the GPL intent, and therefore opposed to MS's proprietary "open" schemas, there isn't much that the open source community can do back except counter sue MS directly. This is a good and noble thing, but it dosen't shelter the users. This whole buisiness smells very foul, it has a familiar stench of "leverage and burn" that MS has used before.

      -GiH

  51. Ballmer: "We will sue Linux". Get it now? by KWTm · · Score: 1
    * Microsoft says it will not file any lawsuits against developers over any patent issues

    I don't know where you get that, especially since, two weeks after Novell shook hands with Microsoft over their deal, Steve Ballmer specifically said that non-Novell Linux was a target.
    In short, it is not good for Linux because it is not good for anyone outside of Novell. If Microsoft wanted interoperability, they didn't need Novell to do it. Why do you think they did need Novell?
    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  52. Said it before and I'll say it again by HalAtWork · · Score: 1

    Duplicate Please bear with me as I refer to the open source community by using generalizations, and also as I tack on my thoughts on MS. But hey, it's only what I think. It's not payback for SCO, it's divide and conquer. In one move, MS has eliminated Novell as a competitor. Novell has confused and/or pissed off a lot of the open source community by entering into this agreement behind closed doors; That is, without the open approval of the majority of SuSE customers, users, and supporters involved with SuSE, and yet they are claiming otherwise. Now everyone in the community is paranoid about code touched by Novell post-agreement. Now Novell is no longer of any use to the community as a whole (i.e. those not directly involved with SuSE but still involved with OSS) since they can no longer be trusted by a large portion, which will lead to arguments which will lead to either forks or simply no integration of Novell code and therefore a lot of work that was lost on something that doesn't benefit those who helped build up SuSE or the other OSS projects that share code with SuSE in the first place (by using GPL-compatible licenses and by not restricting them with patent law). This move has also caused the community to slow down by everyone putting so much attention on Novell instead of building better code, and to fight amongst each other as we decide what to do with Novell code and the SuSE platform. Now Novell is building its software to be compatible with Windows so that businesses can easily migrate from the Novell platform by slowly phasing out their linux boxes and replacing them with Windows ones. This is a move that attempts to funnel Novell customers to MS (I'm just saying now there is a much bigger chance of it happening than before, and MS may have some other moves/FUD/threats/patents/whatever up its sleeve to make this much more likely). This is also a move that attempts to cause in-fighting and to put chinks in the armor of the OSS movement/community/whatever. MS is trying to figure out how to battle OSS and they are getting more and more successful with every attempt -- even if they are just throwing shit up on the wall to see what sticks, they're tenacious and they're building a strategy around the results of their actions. Slowly and steadily they are figuring out how to "deal with" OSS. MS is easily forgiven as long as money and other flash are thrown around, but OSS has its integrity and the fruit of our sweat and blood. Let's show them which is most important.

  53. Talk about your viral license.... by The+Monster · · Score: 1
    having been on the payroll at the time of the contract signing with MS....does this mean he's got any sort of restrictions now dangling on his neck, at least from the point of view of microsoft?
    #include <ianal.h>

    A contract to which Novell and Microsoft are parties cannot bind him personally. It can obviously affect him in his capacity as a Novell employee. I suspect that he has not committed any changes to the Samba tree since the agreement was enacted, nor will he until next month, just to be sure that he isn't opening that particular door. He probably is familiar with how Gerald Combs had to change the name of Ethereal to Wireshark because his former employer had legal claims over the prior name. This one isn't a trademark issue, of course, but the same principle applies.

    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

  54. What about Nat Friedman? by Bruce+Perens · · Score: 5, Insightful
    I've publicly told Nat Friedman, whom Novell is using as the public apologist for the patent agreement, that I think his ethical position stinks, Jeremy's resignation (which I applaud, of course), should reinforce this. Nat should leave too.

    Please sign the Open Letter to Novell. I'd like to get that over 3000 signatures at least today. It's at about 2950 now.

    Thanks

    Bruce

    1. Re:What about Nat Friedman? by Scott+Lockwood · · Score: 1

      For you? Anything. Loved you in Revolution OS by the way!

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    2. Re:What about Nat Friedman? by Bruce+Perens · · Score: 1
      Thanks!

      Bruce

    3. Re:What about Nat Friedman? by Rimbo · · Score: 2, Interesting
      Bruce --

      If I were a Novell executive, upon reading your second sentence, I would immediately think: "That's correct. This is in our best interests financially!" I would stop reading beyond that point; you just made my point for me, so any disagreement expressed would not be in my interests to investigate.

      Novell doesn't care about betrayal, unless it affects their bottom line. Now, you and I both know that Novell's decision will affect their bottom line. So instead of patting Novell on the back for their wise financial judgment in the first paragraph of this letter, let's start the letter with a sentence that connects the dots for them?

      I would recommend the following first paragraph:

      The Open Source community would find little to criticize in your agreement with Microsoft, had it remained a strictly technical agreement. As the agreement stands today, it betrays the authors of the software you re-market and their users worldwide for a potential short-term gain that will lead to a certain long-term loss, as betrayed authors and users discard Novell's products and services in favor of those provided by Novell's competitors and partners.


      That last sentence could be broken up, as it's a bit wordy, but you hopefully see my point. We have to get their attention, and that means showing them the money. Telling them that their agreement is for their own financial benefit will just steel their resolve.

      Make that change, and I'll sign your letter.
    4. Re:What about Nat Friedman? by Bruce+Perens · · Score: 2, Interesting
      If I were a Novell executive, upon reading your second sentence, I would immediately think: "That's correct. This is in our best interests financially!" I would stop reading beyond that point; you just made my point for me, so any disagreement expressed would not be in my interests to investigate.

      I see. You believe that the phrase "it betrays ... for Novell's sole financial benefit" would be percieved as "we screwed someone to make money, great!, no need to read any more of this, there can't possibly be any negative consequences".

      If that degree of cynicism applies, and it may well, there's little hope of convincing them of anything. Our only choice would be to follow a similar strategy to SCO - deprecate them and direct customers elsewhere until there's no business left. And that's what we're doing, because there never was very much hope that they'd "get" it, and we've handled situations like this enough times to know that yes, we'll be rid of them eventually.

      I hope you can understand that I am wary of editing the document after 2973 people have already signed it.

      Thanks

      Bruce

    5. Re:What about Nat Friedman? by Stephen+Ma · · Score: 1
      Novell doesn't care about betrayal, unless it affects their bottom line. Now, you and I both know that Novell's decision will affect their bottom line.

      Don't worry. Novell's survival hinges on being able to make money from Linux services; in other words, they will live or die by the Red Hat business model. However, you need credibility to succeed in the services game, and Novell has just flushed theirs down the toilet. Expect them to be hit with the mother of all boycotts. They will start whimpering soon.

    6. Re:What about Nat Friedman? by Rimbo · · Score: 1
      I hope you can understand that I am wary of editing the document after 2973 people have already signed it.


      It's a matter of the phrasing, more than anything else. It's just a matter of restating the beginning so that the letter doesn't begin by implying, "You're doing something for your own benefit! You assholes!"

      It's perfectly natural for someone to do something that's in his or her own best interests; if what Novell has done is truly the best for their company, then what hope do we have of convincing them that they've made a mistake?

      That's not what's happened, of course. Novell's created for themselves a huge amount of ill will. That will impact their bottom line, now or later. And that's the first thing that should be brought to their attention.

      It's not a very big change, and it's not changing the spirit or intent of the letter, to which nearly 3000 people (so far) agree. Just a few words removed a few added so that Novell understands that we don't really believe that this is for their benefit at all.
  55. politics make that unlikely by Anonymous Coward · · Score: 0

    tridge works for IBM.

    IBM wants Novell/SuSE to succeed.

    It would look bad for IBM if tridge took action against one of IBM's partners in such a way.

    I think it's more likely to see a broader movement against Novell from within Novell.

  56. Leaving at the end of this month by Nom+du+Keyboard · · Score: 1

    Most IT companies I've seen have you escorted out the door at the end of the next hour after they find out you're quitting. Why is he special?

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
    1. Re:Leaving at the end of this month by Alizarin+Erythrosin · · Score: 1

      Considering that there are only 4 days until Christmas, and he will not likely work the weekend, and use some vacation time for the end of the year, I think he won't be back. Hell, I'm off all next week, and this being Thursday, my workplace is pretty much a ghost town.

      --
      There are only 10 kinds of people in this world... those who understand binary and those who don't
  57. I think that THAT is the reason for this "deal". by khasim · · Score: 3, Insightful
    The whole system is designed to set you up for failure, presumably so that if they send the BSA around for an audit, they're bound to find something that's not up to scratch.

    EXACTLY. And if you'll look at the SCO case, you'll see the exact same thing. SCO sued a couple of its own customers NOT because they were using Linux but because they did not comply 100% with the contract they had signed with SCO.

    When Microsoft comes in for an "audit", they're not doing it to help you. They're doing it because they want more money out of you. And the only way to get more money out of you is to "find" that you are not "in compliance" with the agreement you signed.

    Which is why it would be smarter for people to avoid Novell products which Novell is paying a ROYALTY to Microsoft for if you're looking to reduce your exposure to Microsoft lawsuits and/or reduce your costs to Microsoft.
  58. Actually, you have to give source to anyone. by Bruce+Perens · · Score: 1
    GPL 3(b) applies if a commercial distribution doesn't include the source along with the binary. That requires the distributor to include an agreement to provide source to any third party.

    Bruce

    1. Re:Actually, you have to give source to anyone. by Constantine+Evans · · Score: 1

      However, am I correct in interpreting that section as meaning that the distributor is only obligated to provide the source to any third party that the party receiving the binary chooses? The part in question is:

      b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
      c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

      As can be seen, the offer is written, and only needs to be given to the receiving party. The intent is clearly to allow the actions in (c) - so that the receiving party can distribute copies of their binaries without having a copy of the source while still fulfilling the obligations and spirit of the licence.

    2. Re:Actually, you have to give source to anyone. by Bruce+Perens · · Score: 1
      Who is the offer to? Really two parties, I think. The first is the recieving party, who can enforce compliance with the offer only on the basis of contract law, because they aren't the copyright holder. The second is the copyright holder, who can enforce on the basis of copyright law. Can the party offering the binary keep the offer secret from the copyright holder, if the copyright holder asks to see it? I doubt it.

      Who can get the source? Any third party, not just the one that the party recieving the binary designates. And the copyright holder can enforce that if ever a binary has been distributed.

      So, I think it ends up that you have to give source to anyone.

      A lawyer could probably do a better job at this.

      Bruce

    3. Re:Actually, you have to give source to anyone. by mvdwege · · Score: 1

      I read section 3 as follows:

      1. You give source along with the binary, your obligation ends. The receiving party is now in possession of the source, and if it redistributes, it becomes the original distributor and has the choice in which form of section 3 it will use.
      2. You give a written offer for the source along with the binary. The receiving partner may still redistribute the binary, but if it hasn't taken you up on the written offer yet, it may pass on the offer and all those it distributes binaries to may ask the source from you.

      Of course, once your original partner accepts the written offer and gets the source, you can now point to section 3(a) and refer all third parties to the second party, as you have discharged your obligation. This is where the lawyers come in: is it at all possible to invalidate the written offer under 3(b) by retroactively complying with 3(a) and referring third parties to the second party? And more practically, is it not easier to just comply with 3(b) and give third parties the source anyway?

      At first blush one would say no, as the written offer is to all third parties, and they are not parties to your agreement with the second party. What if the original first party has divested its activities though, and does not want to keep the source? Or what if the second party agrees to take over the obligations under 3(b)? This might get hairy fast, especially considering that the second party may be considered a party to all further recipients downstream, as it is their decision as to which section to use to redistribute.

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
  59. Licenses are contracts. by GodInHell · · Score: 1
    Licenses are an agreement between two or more parties which are enforceable under the law. The classic definition of a contract.


    Contracts do not require a signature or even a writing - spoken promises can suffice for most purposes. Every sale you've every completed is a contract with certain assumed responsabilities (default warranties) and rights (exchange of property). A Licesnse is a contract to allow another access to your property for a stated purpose/duration, etc. Tickets are also licenses - most often the terms are spelled out on the back.


    This is all contracts 101 stuff.

    -GiH

  60. Bad director by PermanentMarker · · Score: 0, Redundant

    So you work for a company. And leave it for an excuse of your past company before novell... ????? Damn forget who is paying you ..... ? Wass your sallery to low .... ? Or ehm mentaly ill ... ? Well i hope he does resign himself, and wont perform a buyout for those novell employees. Resigning for poor reasons is bad behaviour and not liked by employees in general. Such people must better think if their bad-leadership is needed in the company who pays their sallery, well its good that he somehow knows he understand he should leave. Such leaders are overrated in a company, i've got no good words for it. (And Bill if you like a joke wel hire him for a good salery but give him an ugly terrible job whoehahahahah it would give a nice twist to this novel $$$ person )

    --
    I know you're out there. I can feel you now. I know that you're afraid. You're afraid of us. You're afraid of change.
  61. In the US we apply the Objective Theory by glrotate · · Score: 1
    "The parties' intentions are, first and foremost, determined by the language used in their agreement. Thus, when the parties express their intentions in writing, the language used by the parties will generally be construed in an objective, not in a subjective, manner. In other words, the law assumes not only that words have an objective meaning, but that it is this meaning that is intended when particular words are used in a contract.
    Williston on Contracts 32:2
    1. Re:In the US we apply the Objective Theory by GodInHell · · Score: 1
      At the risk of being a little too tounge-in-cheek:

      Yes, but what do you mean when you say "objective," or more importantly, what does the author of your quote mean? That's what I was getting at when I spoke of guiding theories for interpretation - courts will favor interpretations in the sense that the industry would use them. The objective standard does not use a reasonable person test. The judge or (rarely) jury will interpret the meaning of the words as they would be used in that form of contract. I don't assume that the "Rails" mentioned in a contract for transport would be the same if I ask you to author a web-site.

      There still remains an assumption that Microsoft and Novell have found a loop-hole which would even pass an "objective person" test. This is an issues which (as I read it) is open to interpretation either way. If one reads the contract toward the original intent (again, as stated in the writing) then any loop-hole will be an accident of language and clearly opposite to the written text, if I go with a legal realist interpreation (or Law and Economics) I'll likely come out on Microsoft's side arguing that the intent statements are pre-amble and unnessential to the contract - that the contract is fair as written only if it is interpreted in favor of allowing coproations to build tools on top of GPL tools without GPLing the result, and that these hippy scum don't belong in a court of law. Okay, I tacked that last bit on just for fun.

      -GiH

  62. Linux for the foreseeable future! Hooray! by mandelbr0t · · Score: 1

    Straight from the devil's (Ballmer's) mouth:

    ...we understand there's going to be Unix on Intel, and therefore Linux, for the long foreseeable future.

    Hooray! Microsoft has acknowledged the survivability of Linux! Who'd-a-thunk-it?

    mandelbr0t

    --
    "Please describe the scientific nature of the 'whammy'" - Agent Scully
    1. Re:Linux for the foreseeable future! Hooray! by Slashcrap · · Score: 1
      Straight from the devil's (Ballmer's) mouth:

      ...we understand there's going to be Unix on Intel, and therefore Linux, for the long foreseeable future.

      Hooray! Microsoft has acknowledged the survivability of Linux! Who'd-a-thunk-it?

      He then went on to say "But of course everyone knows we're a very shortsighted company".
  63. Objective Theory by DragonWriter · · Score: 1

    This is one of those things that is "true, but simplified to the point of being misleading"; even under the so-called "objective" approach to interpretation, usages in trade, the course of dealing between the parties, and all kinds of other things that would to anyone but a lawyer be considered evidence of subjective intent rather than objective meaning of the words will be considered in determining intent.

  64. Re:Good by t0rkm3 · · Score: 1

    I, for one, do not _need_ any job. I will make my way through the world as I can with or without you.

    I pity anyone who _needs_ their job, rather than wanting it.

    Good for Mr. Allison. He can reap the benefits of being good at what he does and contributing to a highly recognized body of work.

  65. That is correct by Eric+Damron · · Score: 4, Insightful

    Yes, that pretty much sums it up. Novell has always maintained that it hasn't infringed on Microsoft's patents but Microsoft has openly stated that Samba and Mono and other software does infringe.

    So what you have is Microsoft offering .NET to the world as an "Open Standard" and then claiming that whoever implements it are using Microsoft's IP that are protected by the patent laws.

    Microsoft has never been known for playing fair and it's time for the entire world to work hard to simply make them irrelevant. Don't implement standards that are not truly open. Don't support Microsoft in ANYTHING they do. Demand that they be held accountable for their continued antitrust violations. Microsoft needs to be broken into at least three separate companies in order to level the playing field. This can easily be justified by their continued lawless actions and the effects those actions have on the IT world.

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:That is correct by oohshiny · · Score: 1

      Novell has always maintained that it hasn't infringed on Microsoft's patents but Microsoft has openly stated that Samba and Mono and other software does infringe.

      Yeah, and so what? Lots of companies are making lots of outrageous patent claims. Are you going to stop any sort of open source software development whenever Microsoft claims it infringes on their patents?

      So what you have is Microsoft offering .NET to the world as an "Open Standard" and then claiming that whoever implements it are using Microsoft's IP that are protected by the patent laws.

      Probably. But they could make just the same assertions about GNU g++, "D" or Python or Perl or Ruby. There is simply no way of running away from Microsoft's IP claims: Microsoft is going to assert patent claims (bogus or real) against any innovative open source software. And it's not only Microsoft--other companies are going to do the same. That's the way the real world works.

      The only way of dealing with such patent claims is to know about the patents that Microsoft and other companies actually have, write software in such a way that it doesn't infringe, and defend against patent claims in court if they make them.

      Trying to avoid patents by listening to claims or trying to second guess legal agreements simply is not going to work.

  66. Samba's fine by sacrilicious · · Score: 1
    [Novell will] come out with something *like* Samba, but different, and proprietary (50% MS, 50% Novell), and it would probably work better than Samba does now...thus killing an otherwise excellent OSS program

    I really doubt this would be a threat to Samba, let alone kill it. Samba is GPL'd, so even if Novell somehow "owned" the Samba team (which AFAIK they do NOT) then it would still be likely that people would pick up the code and run with it. It does seem likely that Novell itself will stop using Samba, but that won't kill Samba any more than Novell disregarding the GPL will kill the GPL.

    --
    - First they ignore you, then they laugh at you, then ???, then profit.
  67. No matter who forks out first it is still division by louzer · · Score: 0

    Whether Novell forks out first or some one else forks out first it is still division of effort which could otherwise be used against MS.

    So MS is winning.

    --
    Heroes die once, cowards live longer.
  68. Re:Won't revoke rights; Samba team too good for th by Achromatic1978 · · Score: 1
    Apropos of anything else, I'm still trying to reconcile how:

    the Samba team has demonstrated a professionalism

    with:

    Even when used by rank hypocrites like SCO.

    I'm sorry, I'm lost. Ad hominem attacks are "professional"?

  69. Re:Won't revoke rights; Samba team too good for th by Omnifarious · · Score: 2, Insightful

    Except, that's not ad hominem because it's directly related to the issue at hand. Pointing out that even SCO doesn't really agree with their own arguments if you look at their behavior doesn't create the standard logical fallacy of an ad hominem attack.

  70. rooted in deceit by symbolset · · Score: 1

    Thereby violating various methods patents owned by everybody's favorite megacorp.

    --
    Help stamp out iliturcy.
  71. M$ wins again by Droid+Rot · · Score: 1

    This is what Ballmer wanted to happen!

    Divide and conquer people!

  72. get over it! by oohshiny · · Score: 1

    This is what I predicted from the beginning. The goal here was fragmentation of the Linux development community.

    It makes no difference whether the Samba team likes Novell or SuSE; the software is released under an open source license. The ability by people you don't like to use software that you release under an open source license is an essential part of open source.

    Many Linux distros are doing exactly that and that's why taking Linux down a few pegs is a necessity to MS. MS doesn't want Linux dead. They just want it to smell funny. Probably something like pee. (I keep doing that)

    That's what Microsoft does. So what? Whining about it isn't going to change it.

  73. stop spreading FUD by oohshiny · · Score: 2, Insightful

    If the legendary Jeremy Allison moves to Red Hat or Canonical, he'll probably still be working on Samba. And when the GPL v3 comes out, it will probably be adopted by Team Samba. [...] So in that specific case, it would be Novell who would have to fork the project and do all the work without the help of Team Samba.

    There is no rational reason anybody has demonstrated why SuSE shouldn't be able to ship Samba under GPL v3. So, please, stop spreading FUD.

    1. Re:stop spreading FUD by NickFortune · · Score: 1
      There is no rational reason anybody has demonstrated why SuSE shouldn't be able to ship Samba under GPL v3.
      Short memory, huh?

      Never mind, let's recap the important point: Stallman has promised to make the incorporate wording into GPLv3 that will explicitly forbid deals such that between Novell and Microsoft.

      This doesn't seem to have sunk in from last time, so just to be clear: Novell will not be able to ship any GPLv3 versions of anything under the terms of their deal with MS, because Richard Stallman has promised that the GPLv3 will forbid them from doing so.

      If he does this, and I can't for the life of me see why he would not, then that would prevent SuSE from shipping any subsequent versions. The standard GPL boilerplate would still give Novell the option of distributing the last GPLv2 version, but as the GP points out, that would leave them with a fork.

      Rational enough? Or do I have to go through it again using smaller words?

      So, please, stop spreading FUD.
      "You keep saying that word; I don' think it means what you think it means"

      I don't know whether you're trolling, stupid, wilfully ignorant or just plain in denial, but please stop spreading falsehoods.

      --
      Don't let THEM immanentize the Eschaton!
    2. Re:stop spreading FUD by oohshiny · · Score: 1

      This doesn't seem to have sunk in from last time

      Yes, because you're wrong.

      so just to be clear: Novell will not be able to ship any GPLv3 versions of anything under the terms of their deal with MS, because

      Where does the GPL v3 say "you can't ship this code if you have have an agreement like the MS/Novell" agreement? In fact, it doesn't. Novell can ship the code under the GPL v3 all they like, despite having whatever agreements they have with Microsoft.

      Richard Stallman has promised that the GPLv3 will forbid them from doing so.

      No, what Stallman has "promised" is that the GPL v3 will make agreements like the MS/Novell agreement ineffective. It will, and that's a good thing.

      But making those agreements ineffective is not the same as prohibiting Novell from shipping the software; Novell will likely choose to continue to ship the software under the GPL v3 and live with the fact that their agreement with MS then doesn't mean anything. That puts the ball back in Microsoft's court, and Microsoft's actions are then limited to suing or shutting up.

      The standard GPL boilerplate would still give Novell the option of distributing the last GPLv2 version, but as the GP points out, that would leave them with a fork.

      Novell also has the option of distributing the code under the GPL v3 and living with the consequence that they are then back to having the same legal status wrt Microsoft patents as any other Linux vendor. Most likely, that's exactly what's going to happen.

      I don't know

      You obviously don't know a lot of things, and your thinking is fuzzy. That's why you should shut up and stop spreading hearsay and innuendo, instead of facts and sound analysis.

    3. Re:stop spreading FUD by NickFortune · · Score: 1
      so just to be clear: Novell will not be able to ship any GPLv3 versions of anything under the terms of their deal with MS, because
      Where does the GPL v3 say "you can't ship this code if you have have an agreement like the MS/Novell" agreement? In fact, it doesn't. Novell can ship the code under the GPL v3 all they like, despite having whatever agreements they have with Microsoft.
      The final version of GPLv3 has yet to be drafted. Perhaps you could show me the line where it says Novell can continue to ship GPLv3 code while continuing with their patent agreement? I'd be interested, if for no other reason than it would show you at least understand the hyperlink syntax.

      No, what Stallman has "promised" is that the GPL v3 will make agreements like the MS/Novell agreement ineffective.
      You still haven't actually read what he said, have you?

      It turns out that perhaps it's a good thing that Microsoft did this now, because we discovered that the text we had written for GPL version 3 would not have blocked this, but it's not too late and we're going to make sure that when GPL version 3 really comes out it will block such deals.
      Sounds like a clear commitment to me. Also notice that he doesn't say "make ineffective" but rather "block".
      now that we have seen this possibility, we're not going to have trouble drafting the language that will block it off. We're going to say not just that if you receive the patent license, but if you have arranged any sort of patent licensing that is prejudicial among the downstream recipients, that that's not allowed.
      Which bit of that sounds like "distribution will still be permitted" to you? I'm genuinely curious.

      Novell will likely choose to continue to ship the software under the GPL v3 and live with the fact that their agreement with MS then doesn't mean anything.
      So the minute the GPL becomes incompatible with the deal, they'll break their agreement? It doesn't reflect well on Novell, but given that their business model is somewhat dependent on distributing Free Software, it would be a rational response, if a little cynical and unprincipled.

      Of course that rather assumes that Novell's legal exposure would negligible. I find that a little hard to swallow, if only because Microsoft's lawyers, at least have a reputation for competence, and I would expect some sort of provision to stop Novell backing out so trivially. Of course, since the details of the deal are NDA'd we'll never know, but it's far from a safe assumption.

      Still, you seem to accept that planned changes to the GPLv3 will make it illegal for Novell to distribute GPLv3 software while they partake in patent agreements such as the one they recently made with Microsoft. And you seem to think that Novell will break such agreements, albeit only when forced to do so by the imminent collapse of their business. Fair enough, I agree. So why do you keep yelling "FUD" every time someone else says it?

      Maybe you'd like to join with us in urging Novell to repudiate the deal without further delay? Then Novell get to emerge with some shred of integrity, and we'd have nothing to argue about. A win-win scenario, except perhaps for Microsoft.

      I don't know
      You obviously don't know a lot of things, and your thinking is fuzzy. That's why you should shut up and stop spreading hearsay and innuendo, instead of facts and sound analysis.
      You're right. There are lots of things that I don't know, and my thinking could always be clearer. Nevertheless, I'm the one linking to references to support his arguments, while you are apparently so hard up for facts that you're reduced to quoting out of context to set up cheap shots. I think that speaks for itself, really.
      --
      Don't let THEM immanentize the Eschaton!
    4. Re:stop spreading FUD by Anonymous Coward · · Score: 0

      Which bit of that sounds like "distribution will still be permitted" to you? I'm genuinely curious.

      Despite your handwaving, in fact, there is no language either in the GPL v3 drafts or in RMS's comments that says that Novell can't ship code under the GPL v3.

      So the minute the GPL becomes incompatible with the deal, they'll break their agreement? It doesn't reflect well on Novell, but given that their business model is somewhat dependent on distributing Free Software, it would be a rational response, if a little cynical and unprincipled.

      Novell has been saying again and again that there is no patent infringement, so I don't see anything "unprincipled" about it. Furthermore, if they distribute under the GPL v3, it doesn't mean that they are "breaking" their agreement with Microsoft, it means that they are giving additional, transferable guarantees to their customers.

      The only people who might end up "breaking" their agreement are Microsoft, who face the choice of distributing GPL v3 software or breaking their distribution agreement with Novell.

      Still, you seem to accept that planned changes to the GPLv3 will make it illegal for Novell to distribute GPLv3 software while they partake in patent agreements such as the one they recently made with Microsoft.

      First of all, even if the two agreements are in conflict, it wouldn't be "illegal", it would be a breach of contract. But how would distribution breach their contract with Microsoft anyway?

      Nevertheless, I'm the one linking to references to support his arguments, while you are apparently so hard up for facts that you're reduced to quoting out of context to set up cheap shots. I think that speaks for itself, really.

      You're linking, just not to anything that supports your points. In fact, your problem is that you apparently don't even understand the issues involved.

      Let's be clear: Novell is taking advantage of a loophole, and that loophole needs to be closed. Furthermore, Microsoft is clearly on a campaign of attacking open source through patents. But those problems are not going to get addressed by your kind of hysterics and denunciations of specific companies, they are going to be addressed by getting the GPL v3 adopted quickly and by scrupulously avoiding patent infringement. Novell may not be a nice company (I never liked them), but if open source only works if all the companies using it are nice, then we might as well give up right now. Fortunately, what matters for the success of open source is the licenses and actual patents, not likes and dislikes of individual companies.

    5. Re:stop spreading FUD by ccp · · Score: 1
      I don't know whether you're trolling, stupid, wilfully ignorant or just plain in denial,

      I'd vote 5: all of the above.

      Cheers,
      CC
    6. Re:stop spreading FUD by NickFortune · · Score: 1

      there is no language either in the GPL v3 drafts or in RMS's comments that says that Novell can't ship code under the GPL v3.

      No there isn't, and I don't believe I've said there was. That particular piece of hand-waving was ooshiny doing some creative misinterpretation of my earlier posts, but frankly it seemed too juvenile a ploy to be worth correcting.

      But the responsibility for clear communication lies with the communicator, so let me restate my position. Richard Stallman has declared his intention to include language in the next GPLv3 draft that will make the new Licence incompatible with cross patent deals such as that which currently exists between Novell and Microsoft. It is highly unlikely (IMHO) that the licence text will mention Novell or Microsoft by name. However, since Stallman refers to the Novell-Microsoft deal as an exemplar of class of deals he intends to block, it seems unlikely that Novell will be able to comply with the terms of GPLv3 while continuing their deal with Microsoft.

      To put it another way: Novell is not being targeted, but the same cannot be said for their deal with Microsoft. The only functional difference is that Novell have the option of being able to comply, but only by discontinuing their patent agreement. If they choose not to do so, and they've given no indication that they will, then they will not be able to distribute GPLv3 software under the terms of the licence.

      Novell has been saying again and again that there is no patent infringement, so I don't see anything "unprincipled" about it.

      mmm... did you read Jeremy Allison's comments in TFA? I know they've been quoted many times in this discussion, but just to make sure we're all on the same page:

      In case anyone might think I gave up too easily, here is a copy of a letter I recently sent to management on this matter.

      [...]

      For people who will point out to me we don't "technically" violate the GPLv2 here's an argument I recently made on the mailing lists.

      "Do you think that if we'd have found what we legally considered a clever way around the Microsoft EULA so we didn't have to pay for Microsoft licenses and had decided to ship, oh let's say, "Exchange Server" under this "legal hack" that Microsoft would be silent about it - or we should act aggr[i]eved when they change the EULA to stop us doing this?"

      So, this strongly suggests that a dominant faction in Novell management is quite aware that the agreement contravenes the intent of the GPL, and seem to think that's ok because they have only violated the spirit of the licence but not the letter.

      Their behaviour may be legal, but it is hardly ethical.

      They could mend a lot of fences by discontinuing the deal before the new GPL forces their hand. Then they could claim to have reconsidered. Otherwise, it reinforces the impression of a company with nothing but contempt for the free software community; one which is cynically willing to abuse the trust of others in pursuit of a private agenda.

      I'll stick with "unprincipled", thank you.

      if they distribute under the GPL v3, it doesn't mean that they are "breaking" their agreement with Microsoft

      No. It will mean that unless they do "break" , "cancel", "abrogate" or somehow otherwise "cease to participate in" their patent deal with MS, they will be distributing the software without a licence to do so, since the patent deal will put them in violation of the terms of GPLv3.

      It's really not that complicated:

      • Stallman says he will make GPLv3 incompatible with deals such as the Novell-MS patent pact
      • Thus Novell will not be able to comply with the GPLv3 while said pact remains in force
      • Unless Novell comply with GPLv3, they will have no legal right to distribute GPLv3 software.
      • Therefore Novell must either cease distribution, or discontinue their patent
      --
      Don't let THEM immanentize the Eschaton!
  74. what's the problem? by oohshiny · · Score: 1

    Microsoft either derives code from something that's GPL'ed or they don't.

    In the first case, they have to provide source code to their stuff under the GPL, plus transferable licenses for all necessary patents.

    In the second case, they are effectively simply releasing a piece of proprietary software--no different from lots of other proprietary software that SuSE, RedHat, and other distros are already shipping.

    Either way, I don't see what the big deal is. Microsoft could always distribute proprietary stuff, and Microsoft could always sue people of patent infringement. Nothing has really changed, other than that they are a couple of hundred million dollars poorer.

  75. what happened by Anonymous Coward · · Score: 0

    novell was going down the tubes financially, go back and look, handwriting->wall. MS saw an opportunity to shaft open source for cheap, while appearing to the suits and the wall street ticks that they weren't and were still shrewd businesscreeps. And they know linus is just a coder and beyond that rather lame, obnoxious and uncaring, that he don't care one way or the other (really, way back in the day he appears to have been just a cheapskate more than anything else, not in any way enamored with open source freedom as it is known), so they bought winning a big battle by bribing off a few generals and coopted one of the major linux players for lunch money to them. Novell's suits needed the cash to keep their fat-ass cushy jobs and because "stockholders" demand an emphasis on quarterly filings and profits, and 99% of most stockholders never think beyond that time limit, and even more of them have no idea how open source works in the long run, they just don't "get it" at all. So the cash was spread around.

    Screw novell, double screw MS, triple screw wall street. Ignore them and work around the damage those entities caused.

  76. GPL3 is expressly incompatible with Novell deal by OmniGeek · · Score: 2, Insightful

    So, if Novell is distributing under a nontransferable "patent umbrella license" from MS, wouldn't that put them in violation of the GPL3 with any GPL3-licensed package they were to distribute? That's the crux of the whole GPL3 issue, IIRC; that Novell would need to do its own support and updates under GPL2 'cause they couldn't distribute anything under GPL3 and still offer the "patent protection." I don't seem to recall there being any wiggle room in that deal for Novell to distribute Open Source software outside the "umbrella," and that's the only way they could still be in compliance.

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
  77. Re: Interface Control by Tiger4 · · Score: 1

    The only "IP" Ballmer could be referring to is the Interface definition needed to properly talk to a Microsoft box. MS has the right to keep it proprietary, but trade secrets are not protected by copyright or patent. If they publish and patent it, then to the extent that MS keeps that information proprietary, then any attempt to hack and market it (reverse engineer a properly working interface and sell it) is theft of MS IP.

    Everything else on the Microsoft side of the interface is part of the Windows OS or some other MS style product. The only way they are owed compensation for that is if that particular copy of the OS is pirated.

    --
    Behold, this dreamer cometh. Come now, and let us slay him... and we shall see what will become of his dreams.
  78. Quitters Never Win by Anonymous Coward · · Score: 0

    and Winners Never Quit -

    Except Heroin Addicts...

  79. It's not about laws. by Anonymous Coward · · Score: 0

    "They'd be able to say, though, if you're not a Novell user they'll sue you for patent infringement."

    Quoth the slashdot lawyer. Let's just say no, and leave it at that.

  80. That is correct-no it's not. by Anonymous Coward · · Score: 0

    "So what you have is Microsoft offering .NET to the world as an "Open Standard" and then claiming that whoever implements it are using Microsoft's IP that are protected by the patent laws."

    Ladies and germs this is why I don't use slashdot as a legal source (or a source period). MS/HP/Intel are offering C# (C-sharp) and the CLI as an "open standard". Not NET. Second I doubt the ECMA would approve both and allow a patent bomb.

  81. Let me be clear by Eric+Damron · · Score: 1

    What Novell and Microsoft are claiming is that they CAN incorporate patent encumbered IP into GPL v2 software. I believe that that claim is being examined by a FOSS lawyers. If the GPL v2 license doesn't prevent that (as Novell and Microsoft assert) then we have a real problem using that license.

    The mere fact that Novell entered into a patent agreement does several things:

    1.It tells the world that Novell does not care about the intent of the GPL.
    2.It casts doubts about any projects that they may contribute to the FOSS community.
    3.It will be a major FUD source for Microsoft.

    And yes, any corporation that uses GPL'd software but does not abide by the intent of the GPL needs to pay a heavy price. I really hope that Novell realizes their mistake and comes back to the community but until then I won't use their products. It really hurt to wipe Suse off my PC. It was one of the best distros I have ever used but I'm adjusting to Ubuntu.

    The last thing we should do is let this pass.

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:Let me be clear by oohshiny · · Score: 1

      What Novell and Microsoft are claiming is that they CAN incorporate patent encumbered IP into GPL v2 software. I believe that that claim is being examined by a FOSS lawyers. If the GPL v2 license doesn't prevent that (as Novell and Microsoft assert) then we have a real problem using that license.

      In a limited sense, they probably can, and that's why the GPL is being clarified.

      And yes, any corporation that uses GPL'd software but does not abide by the intent of the GPL needs to pay a heavy price.

      If the GPL is unclear or contains loopholes, then the GPL needs to be clarified; if we start ostracizing companies that comply with the letter of the GPL just because we don't like how they're complying, then free software will be perceived as untrustworthy. (And, in any case, I think there are bigger violations of the spirit of the GPL than Novell.) Since we have the mechanisms for fixing the GPL, I don't see the problem. This year, projects are going to start moving to the GPL v3, and, no matter what ambiguities may exist now, then Novell needs to make a decision.

      No, the real problem with the reaction to the Novell/Microsoft patent deal is that people are losing sight of the core problem: Microsoft's patent portfolio and their threats of asserting it against open source distributors and users. Nothing Novell does or doesn't do changes that threat.

      I really hope that Novell realizes their mistake and comes back to the community but until then I won't use their products. It really hurt to wipe Suse off my PC. It was one of the best distros I have ever used but I'm adjusting to Ubuntu.

      Personally, I have always found SuSE's excessive fondness of proprietary software irritating and I made the switch away from SuSE a few years ago. The MS/Novell deal doesn't particularly surprise me, it's in character, but I also don't think it changes a lot. Perhaps the reason why many people react to this deal so strongly is because they had an unrealistic notion of what kind of company Novell/SuSE actually is.

  82. Correction: It was Andew, not Jeremey by tlambert · · Score: 1

    It was Andrew Tridgell, not Jeremy Allison who founded Samba.

    Jeremy has been an amazingly important contributor to the project, but it was Andrew's "AT&T LANMan compatibility code" that started the project .

    I know, because I brow-beat Andrew on Usenet until he released it after mentioning it once in a post to one of the news groups, and once it was released, I suggested that he start a mailing list for it (we had a bunch of AT&T WGS boxes that AT&T had donated to the University, they all had LANMan, and I wanted to hook them up to the Ultrix box we had).

    Also, I used to work in the cublicle across from Jeremy when he was working at Whistle communications before it was bought by IBM. 8-)

    -- Terry

  83. Playing right into Microsoft's hands by petrus4 · · Score: 2

    If anyone in the community had bothered to stop and think about this, they might have realised that it is possible that causing such division is exactly what Microsoft intended with this agreement. As those of you who've read ESR might remember him saying, the greatest (and ultimately only) strength FOSS people have is their programming ability.

    If Allison had stayed with the company, he might have been able to keep securing funding for the Samba project, which in turn would mean that code would continue to get written...presumably GPLed code which Microsoft thus would have been unable to co-opt.

    Throwing a tantrum and leaving accomplishes nothing. It will not hurt Microsoft in the slightest, nor is it likely to impress anyone watching with Allison's "moral stand." The only thing it will accomplish is possibly throw the future of the Samba project into question, at least with regards to his ability to continue maintaining it.

    A number of people involved in FOSS need to read Machiavelli and get a clue about how the real world works. Isolated exceptions like Gandhi aside, "principled" martyrdom generally accomplishes exactly nothing. 99.9...% of the population are only ever going to care about FOSS purely on the basis of how doing so benefits them. They DO NOT CARE about moral abstractions of any kind. I wish I knew why so many people associated with Linux had such difficulty comprehending this.

    Please try and understand one simple concept. Windows became the dominant system purely because it gave people what they wanted. No other reason. If the people who develop Linux want it to become the dominant system, then they are ultimately going to have to abandon any other consideration; technical superiority, "principle," whatever. If Linux's developers want it to take over the world, the *only* thing that can matter is that it does what people want.

    If principle is something that Linux's developers care more about than relevance, that's fine...but people need to start recognising that the two are mutually exclusive. If you want one, you're going to have to let go of the other. In terms of gaining the type of popularity for Linux that many of its' developers seem to want, Hobbesian ethics are far more likely to be of assistance than the Lockean philosophy that such groups as Debian claim to adhere to.

    This more than anything else is how I know that people are naive when they believe that Stallman is the being of light that they do, while still having managed to gain the marginal degree of influence that he has. Power doesn't work that way. It comes from giving people whatever pleasant mirage they want to see. In Stallman's case, the Prophet, St Ignucius, is the image some people want, and which with a certain demographic, Stallman has managed to rate pretty highly...but again, it's purely because by following along with his crusade, people expect to either be able to get free software, or make money from it...straight back to the "what's in it for me?" principle.

    As an example of this, it nearly made me vomit the other night when, in a reply to one of my posts here, someone from India in particular had the gall to quote the FSF's party line on morality and principle.

    I know exactly why Stallman is so popular in India; it's because Linux is one of the primary elements enabling India to do a role reversal with the US as an economic member of the Third World. If you think it's because contemporary Indians take after Gandhi in being pillars of virtue and caring about the FSF's "principles", then please, pass me some of what you're smoking.

  84. Novell will be exhibiting at SCALE 5x in LA by Anonymous Coward · · Score: 0

    Novell will be exhibiting at SCALE 5x in Los Angeles on Feb 10-11, 2007. SCALE will have over 40 seminars and 70 exhibitors on Linux and Open Source software.

  85. Oops. by ctid · · Score: 1

    You're right of course. How could I make so stupid a mistake?! Thanks for the correction.

    --
    Reality is defined by the maddest person in the room
  86. The wording is a contract by Anonymous Coward · · Score: 0

    It's because language can't disambiguate ALL meanings of a word.

    The GPL is a license because you are allowed to do things you would not otherwise be able to do.

    If Novell used SAMBA in internally only, then they do not beach the GPL NO MATTER WHAT THEY DO.

    However, in order to sell those changes or distribute them, they must abide by the contractual obligations.

    NOTE: Unlike an EULA, the restrictions are to do with copyright controlled actions (not, for example, reverse engineering, which isn't a copyright issue) and those rescrtictions are inherent as part of acceptance (so you do not agree to let someone else audit your company, which again has nothing to do with copyright).

  87. Key Words: "Reasonable And Non Discriminatory" by NickFortune · · Score: 1
    I doubt the ECMA would approve both and allow a patent bomb.
    That's not a well founded assumption.

    According to the ECMA Code of Conduct in Patent Matters there is no requirement that any relevant that patents pertaining be opened, merely that they are made available for licence under Reasonable And Non Discriminatory (RAND) terms.

    The problem here is that RAND is not further defined, meaning that a company like MS can charge a peppercorn licence fee, and still place the licences out of the reach of FOSS projects who can't pass on the overheads to their customers.

    Additionally, ECMA don't seem require the patents to be actually licenced, they just require a statement of policy from the patent holder. If the patent holder later declines to issue the patent, they may be excluded from further participation in that committee, but by that stage you could still have a whole hell of a lot of deeply entrenched patent violations, so I don't take much comfort from that provision.

    Oh, and if they ask the patent holder if they have any undisclosed patents, and the holder doesn't respond, the technical committee is free to vote on adoption, and therefore presumably adopt, the standard anyway.

    So, as it turns out, there's absolutely nothing in the ECMA procedures prohibiting patent bombs, at least in so far as Free Software is concerned.

    IANAL, Groklaw has a bunch of them who examined this in detail at the time of the Massachusetts ODF flap. Check it out!

    --
    Don't let THEM immanentize the Eschaton!
  88. Windows became the dominant via vendor lock by walterbyrd · · Score: 1

    No other reason. It was the only upgrade path from ms-dos.

    Msft is absolutely masterful at the vendor-lock game.

    1. Re:Windows became the dominant via vendor lock by petrus4 · · Score: 1

      The Mac existed at the time, as did OS/2 and commercial UNIX. Come to that, so did the Amiga.

      Yes, Microsoft are good at trying as hard as they can to keep people locked in...and their ability to intimidate OEMs went close to ensuring it...but people still had options.

  89. Jeremy Allison to join Google by hritcu · · Score: 1

    This ZDNet blog entry has more details: The ultimate revenge? Novell's Allison to join Google.

    --
    If you don't fail at least 90 percent of the time, you're not aiming high enough. (Alan Kay)
  90. besides the point by oohshiny · · Score: 1

    that Novell would need to do its own support and updates under GPL2 'cause they couldn't distribute anything under GPL3 and still offer the "patent protection."

    Well, that statement is misleading. In fact, Novell has a choice: either they fork and offer patent protection, or they simply ship under the GPL v3 and don't offer patent protection. So, statements like "Novell [...] would have to fork the project and do all the work without the help of Team Samba." are incorrect, since such statements already assume that Novell would not choose to go with the GPL v3.

    In fact, Novell keeps saying that they don't think the FOSS they are shipping is infringing. So, most likely, when GPL v3 software comes out, they'll simply ship that under GPL v3 and live with the fact that there will be no patent protection from Microsoft claims. At that point, Novell will be in the same boat as all other Linux vendors again, except that they have gotten some money out of the deal.

    In any case, the sooner the GPL v3 gets out and adopted, the better for everybody, including Novell, because the GPL v3 will clarify these issues and let us focus on important questions again.

  91. Re:Make that change, and I'll sign your letter. by wilec · · Score: 1

    I just signed the document and as of then : 3109 people have added their signatures to this document. I can understand why Bruce would hesitate to edit it now. Hey he has provided a space for your comments, just use it to present your IMHO rather excellent logic. Myself, I noted the parable of the scorpion and the eagle as being most topical.
    Wabi-Sabi
    Matthew

  92. Not really by wilec · · Score: 1

    "Windows became the dominant system purely because it gave people what they wanted. No other reason."

    Not really, Windows became what it is from a combination of several factors. Number one is preloads, that Microsoft managed to persuade IBM to tie a MSDOS license to each CPU clone was an outstandingly brilliant business move. That it can manipulate vendors into preinstalls today is due to failures of the legal system to act. Some of the success is due to simple good fortune of being at the right place and time. Some is due to vision of seeing the possibilities. Much more is due to ruthless practices, ethical flexibility in regard to acquisition of others persons ideas, even IP as they themselves define it. Somewhat more than most expect a lot is due to MS being rather soft on the piracy of Windows in the early years. In the later years it has been more about manipulation, deception and marketing, oops sorry those are kinda of the same thing. I will concede that compared to commercial versions of UNIX, DOS and especially Windows was rather cheap and easy, read dumbed down and limited to make is so. Since IBM PC cloned hsrdwsre was also much cheaper than Apples MS scores again.

    It may very well be that many here need to be better informed of natural philosophy. However a Wikipedia linked mini dissertation on how "Hobbesian" or "Lockean" philosophical base principles are related to software development and the marketplace is pointless in such a construct and I can easiy twist such an argument around on you. As brilliant as these men were they or no other person has ever nailed down the human condition well enough to support such an argument. Yes there are "Machiavellian" persons about in the world and there are those who strive to the ideals of Gandhi, however the vast majority of persons fall into the vast grey center. These opposing philosophical views often work out in the real world in ways you might not expect.

    An example is called for here: Modern Linux distributions are much closer to what the vast majority of people would choose as per your definition of "Hobbesian values". That it is cheap, and dependable are attributes that most people want is due mostly to the merits of the FOSS "Lockean" type of ideals. Linux is getting easier to use and more dependable with each generation. Microsoft indeed realizes all these trends and this is why they are being as aggressive as possible in the deals they cut, the manipulation, deception, collusion and the FUD they spew forth.

    On the other hand Windows is getting more expensive, less easy to use in many ways, and its relevance is being diminished by the greed of MS the RIAA and others.

    Wabi-Sabi
    Matthew

  93. The legendary Jeremy Allison by d_54321 · · Score: 1

    Ah yes of course, the legendary Jeremy Allison, whom I have never heard of before and the reason why I have no interest in reading past the first 4 words of the summary.