Slashdot Mirror


Microsoft Excludes GPLv3 From Linspire Deal

rs232 writes to tell us that Microsoft is excluding any software licensed under the new GPLv3 from their recent patent protection deal with Linspire. "Microsoft has since been treating GPLv3 software as though it were radioactive. 'Microsoft isn't a party to the GPLv3 license and none of its actions are to be misinterpreted as accepting status as a contracting party of GPLv3 or assuming any legal obligations under such license,' the company said in a statement released shortly after GPLv3 was published on June 29. In addition to excluding GPLv3 software from the Linspire deal, Microsoft recently said that it wouldn't distribute any GPLv3 software under its SUSE Linux alliance with Novell, even as it maintains in public statements that the antilawsuit provisions in the license have no legal weight. "

342 comments

  1. The GPLv3 works by A+beautiful+mind · · Score: 3, Interesting

    Microsoft has since been treating GPLv3 software as though it were radioactive.
    Great news!
    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
    1. Re:The GPLv3 works by TheRaven64 · · Score: 4, Funny

      You say that now, but wait until Microsoft gets bitten by a radioactive license and turns into SuperEULA. You won't find it so funny then.

      --
      I am TheRaven on Soylent News
    2. Re:The GPLv3 works by Dracos · · Score: 4, Funny

      SuperEULA: able to transform customers into pirates with a single click!

      (Ninjas of the world, beware)

    3. Re:The GPLv3 works by kripkenstein · · Score: 5, Interesting

      Great news!
      As you and others said, if Microsoft is so worried about the GPL3, then the GPL3 must be on the right track. However, that isn't the real story here, as I see it.

      The real story is how Microsoft changed its patent covenant, after the deal with Linspire was already finalized. Is Microsoft free under that deal to alter the patent covenant however they want - making it useless?

      Not that the deal was useful for anything previously either. It doesn't cover 'clone products' - which perhaps includes OpenOffice and Wine, and it doesn't cover 'video game applications designed to run on a computer', nor 'unified communications', nor a long list of other things. Does it cover anything at all?
    4. Re:The GPLv3 works by Zantetsuken · · Score: 1

      I guess robots don't count all of a sudden because they already have an OS? Prejudice!

    5. Re:The GPLv3 works by bberens · · Score: 0, Troll

      The real story is how Microsoft changed its patent covenant, after the deal with Linspire was already finalized. Is Microsoft free under that deal to alter the patent covenant however they want - making it useless? IANAL but I do know that you can't make a contract that is contradictory to the law. For example, if I make you sign a waiver before bungee jumping but then replace your regular bungee cord with chain linked pretzels you can still sue me (assuming you survive the fall) because I have illegally created an unsafe environment. If Suse, Linspire or another company breaks the law, Microsoft is within their rights to sue them. A contract stating "I won't sue you for patent infringement" is not necessarily the same as "You are licensed to utilize all of my patents at no charge."
      --
      Check out my lame java blog at www.javachopshop.com
    6. Re:The GPLv3 works by random0xff · · Score: 0

      "Does it cover anything at all?" Their asses

    7. Re:The GPLv3 works by Vexorian · · Score: 1

      I, as many people don't seem to actually understand why would Novell or Linspire make this deal since so far there seems to be nothing convenient about it, I am not able to take those 2 seriously as bussiness since they seem to make these lame-ass covenants that certainly don't seem to give them any good. I laugh at Kevin Carmony's implying that linux needs "bussiness thinking" considering he signed such a dumb deal that doesn't seem to give his company any actual advantage besides the status of MS work drone.

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    8. Re:The GPLv3 works by january05 · · Score: 1

      Well, it's cause MS paid them to be idiots. Money's funny that way... Too bad the trust-busters aren't around anymore.

    9. Re:The GPLv3 works by f8l_0e · · Score: 1

      Hurray!! Global warming will finally have a solution.

    10. Re:The GPLv3 works by LaminatorX · · Score: 3, Funny

      BALMER: I am altering the deal. Pray I don't alter it any further.

    11. Re:The GPLv3 works by jimicus · · Score: 1

      Oh, so you've read the EULA for SQL Server then?

    12. Re:The GPLv3 works by Anonymous Coward · · Score: 0

      ...Pray I don't alter it further.

  2. Stallman by timeOday · · Score: 3, Insightful

    he must be doing something right if Microsoft is shunning it.

    1. Re:Stallman by AndyCR · · Score: 1

      Exactly. If it "carries no legal weight", why are they so afraid of it?

      --
      If there's anyone I hate more than stupid people, it's intellectuals.
  3. So what? by Frosty+Piss · · Score: 4, Insightful

    Look, Microsoft is not an "Open Source" software company. Neither they, nor anyone else (including "Open Source" software companies), are obligated to distribute software under GPLv3. Indeed, contrary to popular beliefs, GPL is not the only real "Open Source" license.

    --
    If you want news from today, you have to come back tomorrow.
    1. Re:So what? by RiffRafff · · Score: 4, Interesting

      True, but it would seem to me to undercut much of the Novell deal if a large percentage of the software in the distribution went to GPL3.

      --
      "I might have made a tactical error in not going to a physician for 20 years." -- Warren Zevon
    2. Re:So what? by Ohreally_factor · · Score: 3, Interesting

      GPL 3 is going to be "radioactive" to a lot of companies. Hell, even the main Linux Kernel guys consider it malignant. Developers that want to see their code adopted and used by the mainstream, whether they are in it for profit or not, might want to avoid GPL 3, especially if their software has runs on specialized or proprietary hardware. GPL 3 creates what in essence is a walled garden. If you GPL 3 your code, you're putting it into that garden. It might be a very beautiful garden, but your code will never get out.*

      *Assuming others are contributing to it. If you're the sole copyright holder for your project, you can always do whatever the hell you want.

      --
      It's not offtopic, dumbass. It's orthogonal.
    3. Re:So what? by FinchWorld · · Score: 2, Interesting

      True, but it was my understanding (which may be wrong), that small, yet important parts of say the Linux Kernel will be emerging under GPLv3, which isn't going to play nice with the likes of Novell or certain proprietry software, which shafts them when it comes to upgrading.

      --
      "I may be full of crap about this game, and I may be wrong, and that's fine." -Jack Thompson
    4. Re:So what? by Ohreally_factor · · Score: 3, Insightful

      Unless there's been a radical change in the last week, the Linux Kernel developers are eschewing GPL 3, saying it's a much worse license than GPL 2, which they consider to be a pretty good license. Most of their objections are due to the GPL 3's attempt to control hardware design and usage. The FSF has sent some squads to the LKML (Linux Kernel Mail List) to argue why the kernel developers "misunderstand", but so far I don't think they've convinced anyone, made any solid arguments, or overcome the kernel developers objections.

      All the FSF can do is take the GNU/ userland GPL 3, but all the GNU/ tools up to that point are still GPL 2 and can be forked. On top of that, the BSD userland can be adapted to the Linux kernel. So I really don't see Linux going GPL 3, in whole or in part.

      --
      It's not offtopic, dumbass. It's orthogonal.
    5. Re:So what? by maxwell+demon · · Score: 2, Interesting

      Since GPLv2 and GPLv3 are incompatible, and parts of the kernel are GPLv2 only, it's not possible to have just a few parts of the kernel to be GPLv3. The resulting kernel would not be distributable at all.
      IANAL however.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    6. Re:So what? by petrus4 · · Score: 1

      So I really don't see Linux going GPL 3, in whole or in part.

      Give it time. Alan Cox has been chipping away at Linus about it more or less ever since the GPL 3 was first thought of, and the FSF sends its' minions to apply pressure on a fairly regular basis, as well.

    7. Re:So what? by Anonymous Coward · · Score: 5, Insightful

      The GNU/ tools up to that point are still GPL 2 and can be forked.

      At enormous cost. Linux itself is just a kernel. The GNU toolchain outweighs it by a huge factor in terms of what actually makes a linux distro a linux distro, and the BSD userland is laughably inadequate compared to it.

      I personally hope that as much as possible of the average linux distro goes GPLv3 as soon as possible. The mere fact microsoft is reacting so vehemently to it is an indication the GPLv3 gets something right.

    8. Re:So what? by BlueParrot · · Score: 5, Informative

      GPL 3 creates what in essence is a walled garden. If you GPL 3 your code, you're putting it into that garden.
      That is exactly the point. If you don't like it you can always use a license like the X11 license and permit anyone to do whatever they want with your code. The GPL is all about protecting the rights of the user by limiting the restrictions a developer may impose. This includes copyright, DRM, patents etc... The restrictions apply only if you choose to accept the license, which you only have to do if you want to modify or redistribute the program. In fact, the license explicitly gives you the permission to use the program without recognising the license.

      9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
      The bottom line is that if you want other developers to be able to prevent users from doing this or that with the program, the GPL is not for you. The GPL is NOT about giving developers the greatest freedom possible ( that would be public domain or BSD-style licensing ) the GPL is about defending the USER. In particular it is about defending his/her right to run, study, modify and redistribute the program. Patents and DRM-style lockdowns are attacks against these rights, which is why they are dissalowed.
    9. Re:So what? by alph0ns3 · · Score: 2, Funny

      Hi Mr. Microsoft Employee!

    10. Re:So what? by flyingfsck · · Score: 1

      So I take it that you are not using Samba?

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    11. Re:So what? by Znork · · Score: 3, Insightful

      "On top of that, the BSD userland can be adapted to the Linux kernel."

      Did you know, the BSD userland actually has a BSD kernel too (a whole bunch of them, in fact)?

      I think we can safely conclude that anyone who wanted the BSD userland and BSD licensed kernel would, in fact, already be using BSD. And looking at the history of the unix wars we can draw some further conclusions about how the anything-goes approach plays out. The only ones who'd be interested in a repeat of that would be Microsoft or some aspireing semi-proprietary vendors who arent familiar with the pile of proprietary unices that fell at the roadside.

      The fact is, the bigger participants in that round have been staunch supporters of the FSF's approach on GPLv3; both Sun and IBM appear to have learned the lessons of fractured markets and IP warfare. It creates many more losers than winners, and it damages the market as a whole - better then to live with an enforced level playing field where you compete on being the best, as opposed to being the best backstabber, where you compete on being the quickest, not the quickest to lauch lawsuits.

      In the end, even tho the ability to deny others freedom can lead to short term benefits for one or a few players, in the long term the enforced market freedom creates a bigger pie for all players.

    12. Re:So what? by jZnat · · Score: 2, Informative

      Or GNOME or KDE for that matter. Hell, he probably doesn't even use any open source systems because you still need some GPL-licensed program (GCC) to make it work, even with systems like OpenBSD.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    13. Re:So what? by Ohreally_factor · · Score: 2, Insightful

      I think you're mixing up GPL 2 and GPL 3 there. Admit it, they are two very different licenses. GPL 2 is a quid pro quo license. You get, but you have to give back (if distributing binaries; if a user wants to modify the code for private use, there is nothing protecting other users from this "stinginess").

      GPL 3 reaches past this (some would say overreaches), and controls attempts to control the hardware designs of the user. The GPL 3 is much more focused on the rights of certain users, shifting those rights away from other users and developers.

      I totally agree with you that any given developer should careful examine all his licensing options and choose the license that is right for his or her project. GPL 3 is not going to be the right license for some GPL 2 projects and vice versa. For some, neither will be right, and perhaps the BSD is better suited.

      Also, perhaps calling the GPL 3 a walled garden is unfair of me. A garden sounds like it's going to be small no matter what, and the GPL 3 doesn't and won't have any such physical constraints. Yet there is a wall there between it and GPL 2. A GPL 3 fork cannot be merged back with GPL 2 code.

      --
      It's not offtopic, dumbass. It's orthogonal.
    14. Re:So what? by NickFortune · · Score: 4, Informative

      Look, Microsoft is not an "Open Source" software company. Neither they, nor anyone else ... are obligated to distribute software under GPLv3

      Which is true as far as it goes. The missing detail is the vouchers MS have been selling for SUSE Linux which have no expiry date. This means that, in principle, if anyone redeems such a voucher for a copy of SLES, and if that collection contains any code licenced under GPLv3 at the time they redeem the voucher, then there's a chance MS may be held to account under the terms of GPLv3.

      Now whether that will stand up in a court of law or not is another matter. Eben Moglen and RMS seem to think so, since they wrote the new licence to allow the MS-Novell pact specifically for this reason. But like I say, we won't know for sure until it's tested in court.

      On the other hand it seems reasonably certain that Microsoft sees some legal exposure there, or they wouldn't be making such a fuss. Because for all they talk as if the licence poses no threat to them, they are nevertheless backing away from it at every opportunity.

      The thing is that if the GPLv3 does apply, then anyone they sue for patent violation hereafter is going to be able to claim that Microsoft licenced the patent for their use - else they had no right to distribute in the first place. That too will need to be tested in court, but again it seems that Microsoft are taking the threat seriously.

      So that's "so what". It's not Microsoft don't use GPLv3 and we think they should.

      It's more a case of MS may already be using GPLv3 which makes them a lot less scary.

      Hope that helps, have a nice day.

      --
      Don't let THEM immanentize the Eschaton!
    15. Re:So what? by Ohreally_factor · · Score: 0, Troll

      Those are part of the kernel now? My goodness, technology changes quickly!

      --
      It's not offtopic, dumbass. It's orthogonal.
    16. Re:So what? by dosius · · Score: 1

      I've ported a bunch of BSD stuff myself, and I'd have no issue porting more if there were 36 hours in a day.

      Nothing to do with GPL, everything to do with GNU bloatware.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    17. Re:So what? by Anonymous Coward · · Score: 0

      This is just FUD.

      GPL 3 is going to be "radioactive" to a lot of companies. Hell, even the main Linux Kernel guys consider it malignant. Developers that want to see their code adopted and used by the mainstream, whether they are in it for profit or not, might want to avoid GPL 3, especially if their software has runs on specialized or proprietary hardware.

      Why are you using "specialized or proprietary hardware" as a justification for the mainstream avoiding the GPLv3? By definition, the mainstream doesn't use specialized hardware, and proprietary hardware is extremely rare too. Even if you ignore that, specialized and proprietary hardware aren't incompatible with the GPLv3.

      GPL 3 creates what in essence is a walled garden.

      Nonsense. The GPLv3 is compatible with a hell of a lot of different licenses. In some respects, it's more compatible than previous versions of the GPL.

      It might be a very beautiful garden, but your code will never get out.*

      Not true. Are you at all familiar with copyright law?

    18. Re:So what? by mikelieman · · Score: 4, Insightful

      SAMBA. Not being able to package Samba is the kiss of death.

      --
      Technology -- No Place For Wimps! Grateful Dead and Jerry Garcia Chatroom -- http://www.wemissjerry.org
    19. Re:So what? by shura57 · · Score: 3, Insightful

      What good is the naked kernel? For any user, kernel is a must, but so are the applications. If applications all go GPLv3 then good luck selling naked kernel.

    20. Re:So what? by Tony+Hoyle · · Score: 2, Informative

      Old versions of samba exist. It'll just fork. There's already a fork - samba-tng - and we don't know what's happening to that yet.

    21. Re:So what? by Tony+Hoyle · · Score: 1

      No that's true.

      Kernel is GPL2 only.
      GPL3 license states GPLv3 or late.

      They're incompatible licenses - a wholesale change to GPL3 is about as likely (and as feasable) as a change to BSD... in fact BSD would be easier as you could do it piecemeal.

    22. Re:So what? by Burpmaster · · Score: 2, Insightful

      The GPL 3 is much more focused on the rights of certain users, shifting those rights away from other users and developers. Huh? What 'other users'? A user is the person using the software/device. GPL3 protects the rights of owners. The manufacturer is not a owner once they sell it, and they certainly aren't the user.
    23. Re:So what? by DRJlaw · · Score: 1, Insightful

      "Which is true as far as it goes. The missing detail is the vouchers MS have been selling for SUSE Linux which have no expiry date. This means that, in principle, if anyone redeems such a voucher for a copy of SLES, and if that collection contains any code licenced under GPLv3 at the time they redeem the voucher, then there's a chance MS may be held to account under the terms of GPLv3."

      No. The missing detail is that the vouchers do not specify the version of SUSE Linux that must be distributed, nor do they specify that it must be the latest version. Microsoft and Novell are free to amend the agreement between them, if it was at all ambiguous in the first place, to only cover versions of SUSE in existence prior to June 29, 2007, and/or versions of SUSE created after June 29, 2007 and not subject to GPLv3, and those buying the vouchers are out of luck.

      Microsoft's public stance is quite rational. Customers buying vouchers prior to June 29, 2007 do not have a strong claim to fulfillment using newer versions of SUSE, and customers buying vouchers after the public announcement can no longer claim that they made the purchase with a reasonable belief that they would receive a version subject to GPLv3. Moreover, even if Novell ships a version of SUSE subject to GPLv3 in fulfilling a voucher request, Microsoft has virtually assured that such a distribution will not affect its patent rights, as Novell lacks both the actual and apparent authority to distribute GPLv3 code under the voucher program.*

      GPLv3 zealots are hoping for a hook buried in the crunchy middle (the intervening 2-3 weeks since the introduction of GPLv3). While I'm not familiar with the operation of the voucher program, I would speculate that the probability of such code having worked its way into the distribution and actually been distributed through the voucher program prior to the announcement is very very low.

      *This assumes that the private agreement between Microsoft and Novell, if it was at all ambiguous, was amended in response to GPLv3 to exclude patent indemnification for GPLv3-associated code.

    24. Re:So what? by HAKdragon · · Score: 1

      For what it's worth, the current version of SAMBA and subsequent bug fixes will still be distributed under GPLv2 while the new version will be distributed under GPLv3.

      --
      "Our opponent is an alien starship packed with atomic bombs. We have a protractor."
    25. Re:So what? by ArtDent · · Score: 1

      You're objecting to FUD and not spreading it? Are you sure?

      Could you please point out any published comment by RMS in which he describes non-GPL free software licenses as dishonorable? Any published comment to the effect that developers should not have the freedom to use a license of their choosing?

      He believes that the user's freedom is paramount and that the GPL v3 is the best license to defend that freedom. He strongly advocates that position. Apparently, you disagree with it, and that's fine. But do you think you're doing yourself any favours by calling him a communist and claiming that he advocates laws that would obligate you to use his preferred license?

      Oh, the Free Software Foundation has an extensive list of licenses, too. It lists 66 free software licenses (your OSI link lists a similar number, 60).

    26. Re:So what? by Anonymous Coward · · Score: 0

      Yeah, if every open source software would go under GPLv3 M$ would actually need to write code! Though stealing isn't beyond them, so i don't really believe they wouldn't touch GPLv3 stuff. They'll just shut their jaw about it.

    27. Re:So what? by AvitarX · · Score: 1

      You would obviously move the kernel piecemeal to GPLv2 or later, just as easy as BSD. Then move to GPL3 or later.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    28. Re:So what? by vrimj · · Score: 1

      Nonsense. If you don't accept the license (GPL) you have no right to use the program. Why? Because the work is implicitly protected by copyright law which makes the copy illegal (i.e., you have no right to use it).
      At least your post is properly labeled.
      Copyright limits your abilty to make copies. Unless you made a copy of the program (and are thus a distributor as well as a user) it simply doesn't apply. It takes more then use to trigger copyright protections.
    29. Re:So what? by RobBebop · · Score: 3, Insightful

      GPL 3 reaches past this (some would say overreaches), and controls attempts to control the hardware designs of the user.

      If you consider the company that makes Tivo to be a "user", and not the people who are actually watching their digitally recorded television programs, then you would be correct in stating that the controls are over-reaching.

      I prefer to view somebody who is using the device a user, though. The company making money off of it is simply a vendor.

      And GPLv3 doesn't say "You cannot make money from selling your product" to the Tivo people. They say, "Play fair and share the innovative features that you added to the core software that you paid no money for."

      The Tivo company has every right to keep selling hardware with its tailored software on it... as long as they give users the rights to change and continue to innovate it.

      This makes it easier for Tivo competition, which would only need to design their own hardware and then run the same software as Tivo. This competition arises not from a "control" of the GPLv3, but because it isn't right for Tivo to "control" the 2% of code that they made to produce their box.

      --
      Support the 30 Hour Work Week!!!
    30. Re:So what? by Anonymous Coward · · Score: 0

      It specifically differentiates between "consumer products" and other (i.e. industrial) products. A DRM-enabled Tivo is bad under the GPLv3, but a DRM-enabled assembly line controller is just fine.

    31. Re:So what? by jtn · · Score: 1

      Laughably inadequate? What does this even mean? Way to back up your broad statement.

      This much rabid "debate" (more like cobras spitting at each other) by people INSIDE the open source community is an indication that maybe GPLv3 gets something wrong?

    32. Re:So what? by Otto · · Score: 1

      No, you're wrong. Tivo already gave back the 2% of code changes they made. A Tivo competitor could indeed create their own hardware and run Tivo's code on it. What a Tivo competitor could NOT do would be to write their own code and replace it on Tivo's boxes, thus cutting Tivo off from their revenue stream.

      In essence, the GPLv3 makes it impossible for anybody to sell blades after giving away the razor.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    33. Re:So what? by NickFortune · · Score: 1

      Microsoft and Novell are free to amend the agreement between them, if it was at all ambiguous in the first place,

      Which raises, I think, an interesting point. Because while we don't know the full details of the agreement, Eben Moglen does. He was allowed (IIRC) to look over the agreement so he could satisfy himself that it didn't contravene the GPLv2. And while he's barred by NDA from discussing the terms of the agreement, that wouldn't necessarily stop him from exploiting a flaw in the agreement had he noticed one in his review.

      Now, I've read your profile, and I have to respect your legal credentials. I'm a coder, not a lawyer, and I'm not about to argue the law with you. But I think we also have to respect Moglen's credentials here, and he had plenty of time to think about how he was going to address the MS-Novell pact.

      So like I said earlier - we won't really know unless and until this gets tested in court. But I think we have to allow the possibility that Microsoft might be in trouble here.

      --
      Don't let THEM immanentize the Eschaton!
    34. Re:So what? by Anonymous Coward · · Score: 0

      Excuse me, but this seems to be cut and pasted from when the GPL2 was adopted.

    35. Re:So what? by init100 · · Score: 1

      That was a compromise to enable some possibly beneficial uses of DRM. The FSF still thinks that it is a bad idea though, it is just that businesses have more bargaining power than a consumer, so they do not require the same level of protection against abuse.

    36. Re:So what? by Crayon+Kid · · Score: 5, Interesting

      Old versions of samba exist. It'll just fork.


      It's not as simple as saying, "fine, we'll just ditch anything GPLv3". Who's gonna maintain the fork? 'Cause you gotta maintain it, you can't just fork it and let it rot. Will Microsoft pick up the fork? Will any of the Linux distro's that made a deal with Microsoft? Will they fork and maintain all projects that go GPLv3?

      See, it's not just a matter of forking the code. The license still sticks. OK, it's not GPLv3, it's good old GPLv2, but I think they'll have a lot of trouble dealing with just GPLv2 too. Remember, v3 made patent protection explicit and took it globally. But the stuff was still there, albeit implicit and USA-centric.

      All in all, I absolutely love seeing Microsoft publicly stating it won't touch GPLv3 with a ten foot pole. This is it, folks, this is THE shit. FSF got the holy Grail. It tells the corporate assholes "take it or leave it", and they gotta choose. And neither option comes easy.

      I think it's a knee-jerk reaction of Microsoft's to simply dismiss everything GPLv3, but they're probably frantic to get out of the Novell deal with clean face. It turned worse that they could've ever dreamed.
      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    37. Re:So what? by RobBebop · · Score: 1

      I am not an expert on the Tivo situation, so if I got something wrong, I would like to understand why.

      I was aware that Tivo did eventually concede and publish their source code on their website (and they should be commended for that), so if I wanted to I could build a "Tivo" system.

      I don't understand what is preventing people from writing software and running it on the Tivo box. Is this control of there own hardware what should upset me?

      Personally, I have no interest in Tivo (because I don't watch much TV)... but I would want control of other specialized computing devices to do innovative things with.

      I expect the Linux SmartPhone that was discussed here within the last week to lead to innovation in this area...

      Oh - nevermind - I understand now... Tivo is bad because I can't change the software on it. If Blackberry or iPhone ran Linux, but didn't allow you to change the software on it... they would be just as bad.

      Thank you for pointing out where I was wrong... and telling me why I was wrong so that I could understand what is actually going on the in example I tried to cite. Kudos.

      --
      Support the 30 Hour Work Week!!!
    38. Re:So what? by init100 · · Score: 1

      This much rabid "debate" (more like cobras spitting at each other) by people INSIDE the open source community is an indication that maybe GPLv3 gets something wrong?

      No, it's not. This is just a rehash of the eternal BSD vs GPL debate, with BSD substituted with GPLv2 and GPL substituted by GPLv3. There are people, like BSD proponents, that think that it is fine for companies to take their code and make it restricted, just like there are people that don't like this.

      A debate is a sign of a healthy community. I'd be more worried if there were no debate at all.

    39. Re:So what? by Crayon+Kid · · Score: 1

      It takes more then use to trigger copyright protections.


      Technically, that's not right. They are a select few ways of use that will NOT trigger copyright protection. Almost everything else is the author's right to decide how it happens.
      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    40. Re:So what? by mdielmann · · Score: 1

      Keep in mind that "handles the MS-Novell deal" could be interpreted as "marginalizes the MS-Novell deal". Most vouchers have a certain amount of wiggle room in them, to allow for vendors to substitute similar items or restrict the voucher for similar items that they refuse to carry. If I were running MS, I would avoid the GPL v3, too. Not because I'm sure that the restrictions are legally sound, but because it's not going to be cheap to test that and putting pressure on the competing community is good for business. So, allow GPL v2 stuff, disallow GPL v3 stuff, and risk having to refund vouchers. MS isn't going into unknown territory and GPL v3 is still accomplishing its purpose. Everyone wins, except perhaps the end user.

      --
      Sure I'm paranoid, but am I paranoid enough?
    41. Re:So what? by Crayon+Kid · · Score: 1

      They still screw themselves if they start introducing modifications to the terms now. Who's gonna take them seriously after that? Gotta ask yourself, who wants to make business with someone who changes deal terms to suit themselves whenever they feel like it?

      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    42. Re:So what? by init100 · · Score: 1

      calling him a communist

      Well, he also called Steve Ballmer a fascist, so it evens out. :)

    43. Re:So what? by Chandon+Seldon · · Score: 1

      Nonsense. If you don't accept the license (GPL) you have no right to use the program.

      There's a whole *section* in GPLv3 to cover this. From section 9:

      You are not required to accept this License in order to receive or run a copy of the Program.

      Stop spreading misinformation.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    44. Re:So what? by Chandon+Seldon · · Score: 1

      You would obviously move the kernel piecemeal to GPLv2 or later, just as easy as BSD. Then move to GPL3 or later.

      Knowing the kernel guys, you'd get a lot of people moving their code to "GPLv2 or GPLv3" rather than "GPLv2 or later" - which is fine.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    45. Re:So what? by bl8n8r · · Score: 1

      > GPL is not the only real "Open Source" license.

      No, but it's the only one beating microsoft at it's own game right now.

      --
      boycott slashdot February 10th - 17th check out: altSlashdot.org
    46. Re:So what? by Secrity · · Score: 1

      I seriously doubt that any of the managers of any project that use GPLv3 give a rat's ass if MS distributes their software or not.

    47. Re:So what? by mrchaotica · · Score: 4, Informative

      There's already a fork - samba-tng - and we don't know what's happening to that yet.

      Uh, yeah we do. According to its Wikipedia entry, it's pretty much dead. It's at version 0.4.99, which was released almost two years ago, and apparently hasn't had more than "minimal" development since it was forked:

      Samba TNG was forked in late 1999...

      Since 2000, development on Samba TNG has been minimal...

      --

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

    48. Re:So what? by mrchaotica · · Score: 1

      A Tivo competitor could indeed create their own hardware and run Tivo's code on it.

      But that wouldn't do any damn good! Ever since the beginning, the point of the GPL was to enable users to control their own property. For example, the whole Free Software movement started because of RMS's printer. Would RMS have been satisfied getting that source code to his printer if he couldn't modifiy it and make it run on the original device? Obviously not! By that example, it follows that TiVo's strategy has been unethical from day one -- it's not just contrary to the GPLv3, but to v2 and even v1 as well.

      --

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

    49. Re:So what? by mrchaotica · · Score: 0, Flamebait

      the GPL 3's attempt to control hardware design and usage.

      QUIT SPREADING THE FUCKING FUD ALREADY!

      Name one "hardware design" that the GPLv3 "attempt[s] to control", and I'll concede your point. Otherwise, quit lying!

      --

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

    50. Re:So what? by mr-niloc · · Score: 2, Funny

      They'll just have to whip up "Microsoft SMB Services for Linux" in a couple of weeks and post it as a complimentary download for Novell customers (to be offered to others for the same price as a copy of Windows.)

    51. Re:So what? by themusicgod1 · · Score: 1

      "GPL 3 reaches past this (some would say overreaches), and controls attempts to control the hardware designs of the user."

      Where does this myth keep coming from? You've posted at least two posts on this thread saying this. The GPL3 does no such thing. Have you even read the license? You can do whatever you want with your hardware that you distribute with the GPL3. If you're going to restrict the use of your hardware to signed software, you must take addition measures, but those measures do not have anything to do with the hardware side. There's absolutely no change to the hardware involved, whatsoever.

      --
      GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    52. Re:So what? by VGPowerlord · · Score: 1

      I'm not a lawyer, but in the US at least, Microsoft is probably protected from retribution from the FSF by the doctrine of first sale. The same one that allows me to sell a copy of Microsoft Windows I bought because I disagreed with its license terms.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    53. Re:So what? by a.d.trick · · Score: 1

      GNU/BSD is a lot more viable than Linux with BSD userland tools. However, I don't really see what the point of the mess is (apart from the problems with the GPL2). Why can't we have a GPL3 userland with a GPL2 kernel?

    54. Re:So what? by suckmysav · · Score: 1

      "In essence, the GPLv3 makes it impossible for anybody to sell blades after giving away the razor."

      You know, I'm struggling to imagine why anyone would consider this to be a bad thing. I for one am sick of companies who employ this tactic. (Yes HP, Lexmark et al, I am looking at you guys) These guys should sell their products (razors, printers) at a profitable level and then compete fairly for sales of the consumables. This practice of luring consumers into buying into your locked-in brand through selling the initial item at a loss with the expectation of making it up through grossly inflated consumable pricing is disgraceful.

      In the case of TiVo then they should expect to make a profit selling their boxes, and then offer an ongoing service that is attractive and competitive in the marketplace. If people don't like what TiVo offers them as far as services why shouldn't they be able to choose who/what to run on their hardware? TiVo made a profit selling them the box, they then need to work to keep their customers connected to their service.

      Would you buy a Sony TV with the expectation that you could only watch Sony produced programming?

      --
      "You can't fight in here, this is the war room!"
    55. Re:So what? by micpp · · Score: 1

      There is no reason why the average user can't do just that. There's already quite a mix of licenses in the average Linux distro.

    56. Re:So what? by Anonymous Coward · · Score: 0

      Hi Mr. Microsoft Employee!.

    57. Re:So what? by Ohreally_factor · · Score: 1

      So, according to your definition, only end users qualify as code users? A vendor isn't a user of code? How narrow a definition do you want? When does it get too narrow? The FSF sets the definitions and exceptions arbitrarily? What happens if the definition becomes: A user is any enduser except Burpmaster?

      --
      It's not offtopic, dumbass. It's orthogonal.
    58. Re:So what? by Anonymous Coward · · Score: 0

      Good point, but for an average linux "distro" (there are over 160), look at how much of the 'base system software' is under GPLv.3? The operating system is GPLv.2 (Linus gets his way on that). Everyone else who contributed the mountains of software including a whole whack of applications can pick the license they wish, and many with GPLv.3. If even a bit of a distro is GPLv.3, then it taints the whole distro as being 'at least partly GPLv.3'. This makes it very hard for microsoft to touch any mainstream Linux distro.

    59. Re:So what? by NickFortune · · Score: 1

      Keep in mind that "handles the MS-Novell deal" could be interpreted as "marginalizes the MS-Novell deal".

      True enough. RMS and Eben Moglen might have just decided it was a more elegant solution to allow the deal, and then let Microsoft run away screaming than it would have been to try and kill the agreement outright. If nothing else, it certainly lends credibility to the new licence. Short of overturning GPLv3 in court, I think that possibility represents the "best case" outcome for Microsoft here. I just don't suppose it to be the only possibility.

      If I were running MS, I would avoid the GPL v3, too.

      They don't have much choice, really. If they ever try and sue for patent infringement (and I'm not holding my breath BTW) then they are going to have to be able to show that they are not bound by the terms of the GPLv3, or the defendant can reasonably claim by conveying covered software, Microsoft grant them a licence for those patents. Which ought to be enough to get the case thrown out.

      Everyone wins, except perhaps the end user.

      How does the end user suffer? I still get to run Linux. One more flame war on LKML, maybe a couple of projects get forked... I don't see this affecting me in the long term.

      --
      Don't let THEM immanentize the Eschaton!
    60. Re:So what? by NickFortune · · Score: 1

      Microsoft is probably protected from retribution from the FSF by the doctrine of first sale.

      So then if I buy a copy of Windows, don't install it, and then start selling copies... no, that can't work. Of course, I'm copying a CD there which puts it into fairly well defined territory.

      So how about if I bought a copy of a game from one of the online distributors. Can I then decide I don't like the licence and sell the electronic copy onwards? Can I do it multiple times?

      I don't think MS will fall back on the first sale doctrine if they can avoid it. If they strengthen the doctrine as applied to software, they weaken their own licencing in the process or so it seems to me.

      --
      Don't let THEM immanentize the Eschaton!
    61. Re:So what? by Vintermann · · Score: 1

      And you got to wonder what happens if Solaris goes GPL3. Will we see a Debian GNU/Solaris before long?

      --
      xkcd is not in the sudoers file. This incident will be reported.
    62. Re:So what? by trifish · · Score: 1

      You are not required to accept this License in order to receive or run a copy of the Program.

      Ok, then GPL3 is more unusuable shite than I initially thought. As a "mere" user, I don't have to accept the GPL. So the following section is not legally binding for me (and the section is obviously intended to protect the free software authors from users suing them for damages arising out of their use, which it fails to do):

      [The following part is entirely in upper case letters, however, the Slasdhot filter doesn't allow it, so I converted it to lower case:]

      15. Disclaimer of Warranty.
      there is no warranty for the program, to the extent permitted by applicable law. except when otherwise stated in writing the copyright holders and/or other parties provide the program "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. the entire risk as to the quality and performance of the program is with you. should the program prove defective, you assume the cost of all necessary servicing, repair or correction.

      16. limitation of liability.
      in no event unless required by applicable law or agreed to in writing will any copyright holder, or any other party who modifies and/or conveys the program as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use the program (including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the program to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.

      The above is redundant, because I don't have to accept it. Silly, ridiculous, and unusable license.

    63. Re:So what? by trifish · · Score: 1

      I just found out that GPL indeed explicitly allows the user to NOT ACCEPT the license if he doesn't modify the program! Unbelievable legal mockery. So the following section is not legally binding for me (and the section is obviously intended to protect the free software authors from users suing them for damages arising out of their use, which it fails to do):

      [The following part is entirely in upper case letters, however, the Slasdhot filter doesn't allow it, so I converted it to lower case:]

      15. Disclaimer of Warranty.
      there is no warranty for the program, to the extent permitted by applicable law. except when otherwise stated in writing the copyright holders and/or other parties provide the program "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. the entire risk as to the quality and performance of the program is with you. should the program prove defective, you assume the cost of all necessary servicing, repair or correction.

      16. limitation of liability.
      in no event unless required by applicable law or agreed to in writing will any copyright holder, or any other party who modifies and/or conveys the program as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use the program (including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the program to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.

      The above is redundant, because I don't have to accept it. Silly, ridiculous, and unusable license.

    64. Re:So what? by hdparm · · Score: 1

      But what are they going to distribute once really important pieces all become GPLv3 licensed, like samba is already. Don't tell me that Novell and Linspire are able to maintain GPLv2 fork of everything.

    65. Re:So what? by WNight · · Score: 1

      In essence, the GPLv3 makes it impossible for anybody to sell blades after giving away the razor.
      ... with someone else's razor that they got for free.
    66. Re:So what? by Burpmaster · · Score: 1

      You're confusing the issue. There is no broad or narrow definition. The user of a device is the person using the device! If a vendor wants to lock a device down while they still own it, fine, but as soon as they distribute a device to a user, under GPL3 the manfacturer has to give that user the same ability they had to install software on the device.

      GPL3 protects certain listed rights of users, one of which is to install/update software. In doing this, it in no way removes that same right from the manufacturers.

    67. Re:So what? by mdielmann · · Score: 1

      I said "except perhaps the end user". I'm not sure they would lose, but I haven't thought about that part of the equation, just the corporate elements.

      --
      Sure I'm paranoid, but am I paranoid enough?
    68. Re:So what? by Chandon+Seldon · · Score: 1

      Those aren't license terms. Those are notices. You don't have to accept them - they simply are.

      Whole teams of lawyers spent almost two years on this license. If there were blatant mechanical problems with it, they'd have noticed long ago.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    69. Re:So what? by sumdumass · · Score: 1

      Who's gonna maintain the fork?

      Samba will fork the code. And they will do this after facing a situation where they fear becoming irrelevant. Samba is in a unique position where they rely on Microsoft in order to even have a product. And this reliance combined with the GPLv3 will cause them more problems then they know or appear to care about.

      You may like the GPLv3 as you have that right. I don't like it for several reasons and here is one of them. Any Software provider can place a discriminatory patent license in with their product and offer the same software without it for ten times the amount the software normally costs and the GPLv3's Anti Novell deal will kick in making anyone who buys that software with the license a Mini Novell who can't distribute GPLv3 covered works. And it will be the GPLv3 disallowing the use of the GPLv3 not MS or whatever third part software vendor who does this. I can see it happening to stop the development of a competing OSS product. Gimp and a lot of others can be effected in the same ways.

      I suspect Microsoft will wait until the GPLv3 gains momentum and then pull this. Too many people are dependent on Microsoft software because it does something itself that FOSS software won't do or they depend on some other third party app that only works with MS OSes. This means that a lot of people, especially companies which is where Samba's development is pointing to will be locked out the the GPL by the GPLv3 itself. Samba will start loosing contributers, users will lose one of the more important reasons for using Samba and there just won't be too much interest after a while. Further more, If they offer the same software at 10 times the cost without the deal, then the Samba developers will have to pay ten times the amount of money for development when MS changes something and they need to create the compatibility. I also think this will cause a big divide in the Samba community because the switch back from the GPLv3 isn't automatic like the changes going up. There will be holdouts on the copyright who don't think it is necessary or are standing on principle and all that. It will get ugly for the Samba team.

      Of course some companies will use this as an excuse to go MS free while other won't be able too. Still others will look at this and decide there is just too much risk to use GPLv3 covered worked because of the same reasons MS is shying away from it. MS is acting like they are afraid of it so people like you will go around and say things like "I absolutely love seeing Microsoft publicly stating it won't touch GPLv3 with a ten foot pole" and "this is THE shit. FSF got the holy Grail. It tells the corporate assholes "take it or leave it", and "they gotta choose. Neither option comes easy" which allows Microsoft to go on about how viral the new license is, about how it will destroy everything you own, including your investors first born child and everything that is just a rehash of all the other FUD they have been Spewing out for years. But this time, instead of the FOSS community saying "what a load of crap", they are saying "yea, take it baby" "we screwed you".

      I think it's a knee-jerk reaction of Microsoft's to simply dismiss everything GPLv3, but they're probably frantic to get out of the Novell deal with clean face. It turned worse that they could've ever dreamed.

      No, I think it is a very calculated maneuver they are taking here. they aren't worried about the GPLv3 in one bit. And they aren't bound by it to the point people think either. There is a lot of ifs in making them subject to the GPLv3 in a meaning full way. You would have to make sure that whatever is considered infringing on their patents that they won't disclose is published under the GPLv3 license. You would have to make sure it got distributed in someway by MS and that they know it was being distributed by them. And you would have to do all this without showing that you know what is in violation of their claims so i

    70. Re:So what? by Otto · · Score: 1

      I was aware that Tivo did eventually concede and publish their source code on their website (and they should be commended for that), so if I wanted to I could build a "Tivo" system. No, there's no "eventually" about it, they did this even before the very first box was ever sold. They actually went so far as to print the text of the GPLv2 in the User Manual as well as a link to their site to download the code.

      Tivo didn't get bullied into doing this. They did it from the very beginning, period. They did the right thing all the way down the line.

      I don't understand what is preventing people from writing software and running it on the Tivo box. The Tivo hardware verifies that the copy of the Linux kernel it boots is signed using Tivo's own private key. So while you can compile Tivo's kernel changes and run them on another box, you can't put the changes on the Tivo box, because you do not have the ability to sign it with their private key. If you do so, the Tivo refuses to boot.

      This can be hacked around, BTW. But that's beside the point.
      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    71. Re:So what? by sumdumass · · Score: 1

      But the GPLv3 only has this provision to the extent that it effects the GPLv3 covered software or works. Strangely enough, Tivo can still lock out the hard drive, tuner cards and display output leaving you with a fancy terminal if none of the code ruining those devices are using GPLv3 covered code.

      What I don't like about the GPLv3 is that it opens so many more problems then it fixes. And when it does fix something, it does it so narrowly that it only effects a small subset of the people. Even the discriminatory patent clause can be circumvented by Microsoft directly. They create a separate entity who carries a license from MS to insure someone from a lawsuit against them. Then this separate entity offers insurance and when MS pulls a stunt, they say here is my get off Scott free card. The FSF said insurance is specifically not covered so as long as the license isn't from an entity who distributed software, that clause is ineffective.

    72. Re:So what? by Otto · · Score: 1

      Obviously not! By that example, it follows that TiVo's strategy has been unethical from day one -- it's not just contrary to the GPLv3, but to v2 and even v1 as well. Linus Torvalds, who actually owns the copyright to the code in question, disagrees with you and says that Tivo has fully complied with the GPLv2, in his viewpoint.

      Since it's actually his code that they used, your opinion means exactly zero.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    73. Re:So what? by Otto · · Score: 1

      You know, I'm struggling to imagine why anyone would consider this to be a bad thing. I for one am sick of companies who employ this tactic. And because you're sick of it, you want to make it impossible for them to do it? Gee, strongarm much?

      You know, you could just *NOT BUY* these products that use this tactic. Some of us don't mind it too much, since it gives us affordable products at reasonable prices for the expected lifetime of those products.

      The lifetime of the average consumer video device is 5-6 years, maximum. Spending a huge amount of money up front vs. paying for it by buying a service over that period of time... Well, each person can make that choice for themselves, can't they?

      TiVo made a profit selling them the box, they then need to work to keep their customers connected to their service. Tivo never would have made a profit selling the boxes. They sold them at a loss. If the price was high enough to make a profit on the things, they would have been $500 instead of $200. And then they would not have sold nearly as many of them. Certainly not enough to reach profitability. Furthermore, at the time, they required phone lines to connect back to the service (broadband was not quite as widespread then, so they didn't put ethernet in them), so there was an ongoing maintenance cost as well, for use of the phone lines.

      For a simple contrast, look at ReplayTV. ReplayTV did exactly what you suggest. They sold their boxes at a slight profit. They also went out of business in just a few years. Tivo, on the other hand, is still around.

      Would you buy a Sony TV with the expectation that you could only watch Sony produced programming? These are not even comparable.. Tivo's "service" is to provide TV Guide information, which is the same regardless of who provides it. Now, more recently, they've expanded into web control of the box, Tivo Mobile, Amazon Unbox downloads, etc, etc.. However that doesn't change the fact that they were selling something that would be largely the same through any provider. Their goal was not to shut out competitors, their goal was to shut out people from getting the information off the web for free (via scrapers) and eliminating their service entirely while they were still trying to get off the ground and achieve profitability. They sold the hardware at a loss in order to reach more people and didn't want unscrupulous people taking advantage of them for it. That doesn't seem all that unethical to me.
      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    74. Re:So what? by trifish · · Score: 1

      Those are sections of the license. Section 9 says that "I don't have to accept this license" if I only want to use the unmodified program. So, an average Joe user stops reading further sections (including sections 15 and 16, which are the disclaimers and limitations of liabilities).

    75. Re:So what? by trifish · · Score: 1

      If there were blatant mechanical problems with it, they'd have noticed long ago.

      That is as stupid as saying that if there were blatant mechanical problems with Windows, people would've noticed long ago. GPL is not a lawyer's work, but a politician and zealot's work.

    76. Re:So what? by Ohreally_factor · · Score: 1

      No, I think you (and the FSF) are confusing the issue. We were talking about users of software. Now you're bringing in hardware, and trying to control how some software users design their hardware. You're taking away a freedom to protect a freedom that isn't really being threatened by the hardware makers.

      There is nothing physically stopping you from using a device as you see fit, assuming you have the desire, the time, and the technical ability to do so. The argument that all device makers must make it easy for anyone to do so just doesn't fly. If the DCMA is your problem, then you should address that by changing the law or committing civil disobedience or just ignoring the law.

      On top of that, if you really want to hack your DVR, you can choose to buy an open DVR, such as products from Neuros. You're actually doing a disservice to open hardware makers by choosing a Tivo and hacking (or attempting to hack) it, because you're not supporting them with your dollars.

      I'm starting to think that the FSF doesn't really think that open platforms are superior to closed ones and that open ones have no chance of success. Otherwise, why would they seek to cripple closed platforms instead of putting all their energy into supporting the open ones? I suspect that this has to do with RMS's socialist anti-property bias. Under a socialist system of the sort we saw in the Soviet Union, competition is bad. Choice is bad. You take what the state gives you and you better like it if you know what's good for you. Oh, yeah, let a thousand flowers bloom! (OK, that's Maoist rather than Stalinist, but it's the same principle.)

      --
      It's not offtopic, dumbass. It's orthogonal.
    77. Re:So what? by Ohreally_factor · · Score: 1

      Yelling and swearing and accusing me of lying make your point brilliantly, Mr. Chaotica. Good show! Let me know when you'd like to discuss this without the emotion (or religion).

      --
      It's not offtopic, dumbass. It's orthogonal.
    78. Re:So what? by mrchaotica · · Score: 1

      Good job evading the question!

      --

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

    79. Re:So what? by Ohreally_factor · · Score: 1

      If you were intellectually curious, rather than an apologist for the the FSF, you might do your own research rather than ask others to do it for you.

      How was that for evasive?

      Why do I need to find you an example? Are you arguing that a hardware designer can use GPL 3 code and not worry about whether his hardware design fits today's FSF requirements?

      --
      It's not offtopic, dumbass. It's orthogonal.
    80. Re:So what? by VGPowerlord · · Score: 1

      So then if I buy a copy of Windows, don't install it, and then start selling copies... no, that can't work. Of course, I'm copying a CD there which puts it into fairly well defined territory.
      The doctrine of first sale doesn't give you permission to make additional copies. Fair use might, but copyright law prohibits you from selling said copies.

      So how about if I bought a copy of a game from one of the online distributors. Can I then decide I don't like the licence and sell the electronic copy onwards?
      Personally, I'd say yes. However, courts seem to think that EULAs can take away rights rather than give them (which is what a license is supposed to do). I have yet to see a for-pay electronic download not have some sort of EULA attached to it. Of course, these EULAs undoubtably remove your right to sell said game.

      As a side note, if companies tell you that you're don't have the right to install software on your computer without needing a license, they're lying to you. Title 17 117(a)(1) explicitly authorizes you to make a copy or adaptation if the software won't run without a copy being made... i.e. you're given a blanket license to install and run (because this also covers copies in memory) software without needing a license to do it.

      Can I do it multiple times?
      Title 17 (US Copyright Law) 117(b) prohibits you from keeping exact copies of a computer program if you sell the original. It also forbids you from creating an adaption without the copyright owner's consent (so you can't get around the "exact copies" rule). As noted above, you are permitted to make said copies or adaptations if it's required to run the program, but you're not allowed to do anything but use such a copy. I will note that the Title 17 definition of "computer program" appears to exclude data files, such as mp3s.

      I don't think MS will fall back on the first sale doctrine if they can avoid it. If they strengthen the doctrine as applied to software, they weaken their own licencing in the process or so it seems to me.
      You have a good point there.
      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    81. Re:So what? by Burpmaster · · Score: 1

      No, I think you (and the FSF) are confusing the issue. We were talking about users of software.

      I use Ubuntu on my machines. That means I'm an Ubuntu user. I have the right to run 'sudo rm -rf /' on those machines if I want to. Let's say you install Ubuntu on your machine. We are both Ubuntu users now, but that does not give you the right to 'sudo rm -rf /' on my machine. Your user rights are not violated by this restriction because your user rights only pertain to the property you have the right to use.

      If you want to talk about the manufacturer in the capacity that they are a user, it can only refer to the hardware that is still theirs. When they sell a hardware/software combo, that is distribution, not use, and from that point on, they cease to be the user of both the device AND the copy of the software on that device, even if they still have an identical device in their possession that they ARE a user of.

      Now you're bringing in hardware, and trying to control how some software users design their hardware.

      I guess Microsoft is trying to stop everyone from even making hardware at all, then, considering that their software can't even be used or distributed for free.

      Reality check: All manufacturers can design their hardware however the hell they want. They aren't bound by the GPL until they distribute the software. Distribution carries certain responsibilities under GPL. Always has and always will. One such responsibility is the requirement to hand over the source code. New to GPL3 is the requirement to hand over the key to unlock the device.

      You're taking away a freedom to protect a freedom that isn't really being threatened by the hardware makers.

      Are you opposed to copyright in general? At this point, you have to be to stay consistent, because the sole purpose of copyright is to allow authors of creative works to put conditions on their use and distribution, which takes away freedom. GPL is very liberal in that there are practically no restrictions on use, and distribution is restricted as minimally as possible. The only requirements for distribution that do exist were designed specifically to maximize what the end user can do as a user.

      There is nothing physically stopping you from using a device as you see fit, assuming you have the desire, the time, and the technical ability to do so. The argument that all device makers must make it easy for anyone to do so just doesn't fly.

      But there is something physically stopping me: the design of the device! Now, it may ultimately be possible, with great effort, to unlock most devices available today, but there's no reason that will remain true. With further miniaturization, devices could be made completely unhackable, and be designed so that any attempt to open them up destroys them. Would you then say "nothing is physically stopping you from modifying the device's software, it just happens to be physically impossible"?

      If the DCMA is your problem, then you should address that by changing the law or committing civil disobedience or just ignoring the law.

      How do you feel about the DMCA? I think by now, you have to be opposed to it. Then are you OK at least with the clause in the GPL3 that requires the distributor to waive the right to sue users for DMCA violations? Or is blocking an unjust lawsuit another restriction on freedom?

      On top of that, if you really want to hack your DVR, you can choose to buy an open DVR, such as products from Neuros. You're actually doing a disservice to open hardware makers by choosing a Tivo and hacking (or attempting to hack) it, because you're not supporting them with your dollars.

      And I wouldn't want a Tivo (I'm already using my desktop PC as a DVR anyway). But I also don't want any software I write to be distributed w

    82. Re:So what? by mrchaotica · · Score: 1

      Are you arguing that a hardware designer can use GPL 3 code and not worry about whether his hardware design fits today's FSF requirements?

      Yes! I assert that there is no possible arrangement of transistors that the GPLv3 does not allow, including arrangements that function to enable DRM. Prove me wrong!

      --

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

    83. Re:So what? by Ohreally_factor · · Score: 1

      Transistors? Why didn't you ask me about tubes? You're playing with definitions and trying to play a gotcha game. Get over your Tivo fetish and buy a neuros, for God's sake.

      --
      It's not offtopic, dumbass. It's orthogonal.
    84. Re:So what? by mrchaotica · · Score: 1

      I'm not "playing a gotcha game," I'm trying to make a point. And anyway, quit trying to weasel out of the question! You were the one who started this by spreading FUD! Let me remind you of what you said:

      Most of their objections are due to the GPL 3's attempt to control hardware design and usage.

      Also, let me remind you of what else you said:

      The FSF has sent some squads to the LKML (Linux Kernel Mail List) to argue why the kernel developers "misunderstand", but so far I don't think they've convinced anyone, made any solid arguments, or overcome the kernel developers objections.

      So, hypocritical much? It seems to me that you're the one failing to make any solid arguments!

      So, how's about it: will you finally stand behind what you say, and substantiate your claim? Or will you continue to whine, and whinge, and spread FUD like the coward and shill you are?

      Put up or shut up, damnit!

      --

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

    85. Re:So what? by Ohreally_factor · · Score: 1

      There you go again, Chaotica, calling names as if it's going to make your argument. I decline to participate if that's how you're going to conduct yourself. The best way to deal with a bully is to ignore him, my mom used to say. I think she was right, as far as posting comments on the internet goes.

      Unless you have something more compelling to offer than shoddy and rhetorical debate tactics and tired insults, consider me done with our little branch of this thread.

      --
      It's not offtopic, dumbass. It's orthogonal.
    86. Re:So what? by mrchaotica · · Score: 1

      Fine. Substantiate your claims, please. That is all.

      --

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

    87. Re:So what? by suckmysav · · Score: 1


      "You know, you could just *NOT BUY* these products that use this tactic. "

      Uhh, which brand of razor/printer would you suggest genius? Where I shop, ALL the razors are pretty much the same price, and all the blades are pretty much the same inflated price. It's inevitable that once one or two manufacturers start using this lockin pricing strategy all the others have to follow as most consumers are brainless sheep who think that cheap razor + expensive blades makes for "affordable products at reasonable prices".

      "Some of us don't mind it too much, since it gives us affordable products
        at reasonable prices for the expected lifetime of those products."

      I rest my case. Anybody who thinks that getting a cheap item as a one off purchase with ongoing consumable items at inflated prices is a good thing is clearly too stupid to be taken seriously.

      --
      "You can't fight in here, this is the war room!"
    88. Re:So what? by RobBebop · · Score: 1

      I saw that my post last week got modded Insightful, and thought I'd circle-back on this dead thread...

      I agree with you that Otto seemed to be Trolling, though with semi-thought out arguments. When he tried to say "Pay $200 now and $10 per month..." is cheaper than "Pay $500 now" he was wrong.

      What is more wrong is that the device isn't worth $500. With any level of technical expertise, you be able to pay $200-300 to get the hardware and then Flash a Kernel with a File System onto the box and having a functioning Tivo. Is it be worth it to most people to let Tivo do this at a $200-300 premium? Yes, TV without commercials is worth that much. Satellite Radio bases their business model around the fact that people will pay to avoid commercials. What I think is wrong is that Otto seems to feel that "evil companies/individuals" are going to undermine Tivo by producing the $200-300 boxes and distributing them without the built-in "subscription" that Tivo charges.

      As far as razors go... a better analogy is needed. For the last 3 or 4 years I've been buying the throw-away 3-blade ones that come 4 in a pack for like $7. I get about 2 months out of each razor before it becomes to abrasive for me. Mind you, I shave every other day, unless professionalism demands otherwise, but I think spending $10-15 per year on razors is completely affordable.

      What gets me is cellular telephone vendors selling you a phone and then telling you that you need to pay $0.15 every time somebody wants to send a text message, and if you don't like it... the solution is to add a $5/month "plan" so that receiving/sending more than 30 of these tiny messages per month is "affordable". That adds $60 to my bill per year... so screw that. I asked them to turn off the damned service on my phone, and they can keep it off until they understand that 500 text messages on their network takes up the same bandwidth as 1 or 2 minutes of talk time... and it should be priced that way.

      --
      Support the 30 Hour Work Week!!!
    89. Re:So what? by Otto · · Score: 1

      I agree with you that Otto seemed to be Trolling, though with semi-thought out arguments. You need to look up "trolling" again, because I was doing no such thing.

      When he tried to say "Pay $200 now and $10 per month..." is cheaper than "Pay $500 now" he was wrong. No, I'm not. Figure depreciation into it as well. That $500 box today will only be worth $200 tommorrow. If you upgrade on a regular basis, then it may be well worth it to spend lower now and a small monthly rate.

      Or are you one of those people who doesn't grasp why people lease cars either?

      What is more wrong is that the device isn't worth $500. Well, not NOW it's not. When it was new, the build cost of it was over $1000.

      What I think is wrong is that Otto seems to feel that "evil companies/individuals" are going to undermine Tivo by producing the $200-300 boxes and distributing them without the built-in "subscription" that Tivo charges. No, that's not it at all. You're more than welcome to build your own box and use Tivo's software on it. That's the purpose of the GPL. What "Tivoization" is is for Tivo to prevent you from putting your own software on the box that Tivo built and sold to you on the cheap. In other words, to take Tivo's box, sold at a discount, and cut off their revenue stream by hacking it to, say, not have to call home to get guide data. That's why Tivo locked down their boxes. And that's what the GPLv3 is trying to prevent.
      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  4. Why isn't there a "noshit" tag? by xxxJonBoyxxx · · Score: 3, Insightful

    Why isn't there a "noshit" tag? The whole idea behind GPL3 was to keep Microsoft from license-protecting customers from lawsuits. Microsoft's main contention is that GPL2 allows them to do what they're doing. Why not just save room by posting a story that says "some old story, different day"?

    1. Re:Why isn't there a "noshit" tag? by Anonymous Coward · · Score: 0

      Why not just save room by posting a story that says "some old story, different day"?

      Cmdr Taco: You must be new here. Please reserve your comments for the dupe next week.

    2. Re:Why isn't there a "noshit" tag? by Anonymous Coward · · Score: 0

      The primary purpose of v3 was to slow the erosion of v2 protection in embedded devices where GPL software was used, could be modified, but could not be run in modified form on the device. But, you're right: since March 19, v3 has explicitly inhibited deals such as the Microsoft-Novell deal in what seems to be a secondary implementation of rights reinforcement.

    3. Re:Why isn't there a "noshit" tag? by kinglink · · Score: 1

      I think there's none because half the stories published on here would be marked that.

      The submission quality has been meaningless hype piece (see E3 info for the last week in games), non-Slashdot Politic pieces to push the liberal agenda (there's some conservative pieces too but not that many, most of the political crap is edited by Kdawson, but he's hardly the only one), summary reading too far into the story (see the comcast/firefox article, comcast is lazy, go figure) and "DUH" articles, such as this one.

    4. Re:Why isn't there a "noshit" tag? by magus_melchior · · Score: 1

      A better question might be, why post the story at all? They could just put the headline text at the top of the page for a day.

      BTW, don't let the nonexistence of the tag prevent you from making your own. I use "captainobvious" myself.

      --
      "We are Microsoft. You shall be assimilated. Competition is futile."
  5. An other example of GPL3 suckyness by jellomizer · · Score: 1, Flamebait

    It took over a decade for a lot of major corporation to adjust to Open Source and the GPL as a business model. A lot of this time was finding the right loop-holes in it that would make it work with their business model... With these loopholes both sides won. These company contributed to the Open Source Community as some level and the Company made money. Now a few people who to the most part are anti-capitalistic. decided to change the rules because they see that the a few companies found a hole in the GPL that allowed them to do things not in the Spirit of the original GPL. So they go and change it make it more rigid for corporations and incompatible with their business model. So yes they will block GPL 3 Code and Contribute less to Open Source and Hire Developers to make in house software. (Both Sides loose) Now it may take an other decade for Business to find how to make GPL3 work for them, but in the meantime it is back to priority software. By going to far in one direction you loose more people who are in the middle. The Utopian vision of totally free information and code will never happen, The best you can do is maximize it. GPL 3 in my opinion is trying to force the Utopian vision thus minimizing the use of open coding. I know we all hate Microsoft and all. But can you blame them, they are just starting to kinda sorta maybe just a little bit become open source friendly then the rules change.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:An other example of GPL3 suckyness by Anonymous Coward · · Score: 0

      What is the difference of spurring on debate and Flamebait. A lot of supporters of Open Source are also big oponents of GPL 3. For a group of people who feel that information should be free and open you are sure quick to moderate down any information you don't agree with.

    2. Re:An other example of GPL3 suckyness by kebes · · Score: 5, Interesting

      With these loopholes both sides won.
      Strange, I don't remember feeling a satisfying sense of victory when Microsoft tried to undermine our software by claiming that it infringed their patents. I don't remember feeling that we had "won" when Novell signed a deal with Microsoft to protect themselves and leave the rest of the community out in the cold.

      The loopholes were just that: sneaky ways to evade the intentions of most of the most important contributors in the realm of FOSS. I have no problem with businesses making money using FOSS, and many of them do it in a way that is not only compatible with the intentions of the GPL, but actively promotes the cause of free software. However, those businesses who were exploiting loopholes in the GPL knew that they were not promoting our interests, and therefore should not be surprised when the community shifts to close those loopholes. Such a shift will only alienate businesses who were not helping "the cause" anyways.

      The GPLv3 is not perfect, and is not a perfect license. I don't think that every project should switch to GPLv3... for some the GPLv2 may be a better match. However GPLv3 was crafted to address a very real problem, and judging from Microsoft's reaction, it is doing a great job in that regard.
    3. Re:An other example of GPL3 suckyness by eclectro · · Score: 2, Insightful

      just a little bit become open source friendly then the rules change.

      I think the rules changed when Microsoft (or the companies before them) started shaking down everyone with their patent portfolio. I would be more willing to take your side if Microsoft had the courtesy to tell everyone what patents linux was violating. As it stands, Microsoft is the king of suck, and I do not see this zebra changing it's stripes anytime soon.

      --
      Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
    4. Re:An other example of GPL3 suckyness by 71thumper · · Score: 4, Interesting

      More importantly, GPLv3 serves as a reminder that choosing Open Source with the idea that "you'll never get left behind" is not a true position -- that all any given Open Source project really represents is the right to have the source code AS IT EXISTS NOW. In the future more restrictive licensing could be released that could impact you.

      In short, GPLv3 really made "Open Source" more like "Closed Source" by clearly pointing out that what you may be allowed to do now you may not be allowed to do later (unless you fork and thus lose the community aspect that made it interesting in the first place).

      After all, who's to say GPLv4 won't say "you must release any changes back to the community whether you distribute or not" ?

      GPLv3 is the best possible thing that could have happened to Closed Source vendors because it just kicked the chair out from under most of the arguments in favor of Open Source.

    5. Re:An other example of GPL3 suckyness by ZeroPly · · Score: 4, Insightful
      I'm afraid you have a fundamental misunderstanding of how open source development happens.

      Specifically, you are getting the cart before the horse. Company XYZ doesn't pick an arbitrary project from SourceForge and, strictly out of the goodness of their heart, task several paid programmers with working on it - with the goal of someday using it. Rather, they start using an existing product which is established (Linux, Apache, etc), and after heavy use realize that contributing to it is in their own best interest. Linux was successful BEFORE IBM invested a dime in it. Apache was successful before any corporation officially contributed a single line of code.

      How exactly do you think corporations are going to "block" GPLv3 code? By the time the sofware is worth blocking, it has either gained a following or failed. If it already has a following, the only choice the corporation has is whether to jump on the bandwagon. 90% of corporations are USERS, not developers. GPLv3 makes absolutely no difference to my boss since he's not planning on redistributing any of the code. If 7Zip comes with GPLv3 rather than GPLv2, you really think he's going to skip on it and pay $40/license for WinZip?

      --
      Support microSD: in a post 9/11 world, it is unwise to carry your data on media that you cannot comfortably swallow.
    6. Re:An other example of GPL3 suckyness by Anonymous Coward · · Score: 0

      Now a few people who to the most part are anti-capitalistic

      Pure capitalism doesn't have copyright. The GPL tries to force a free market system using copyrights. If there were no copyrights, the GPL wouldn't be necessary.

    7. Re:An other example of GPL3 suckyness by Dan+Ost · · Score: 1

      After all, who's to say GPLv4 won't say "you must release any changes back to the community whether you distribute or not" ?

      Copyright law is what gives the GPL teeth. Copyright law says that you can't distribute at all without permission. The GPL says you can distribute as long as you meet certain criteria.

      Now do you understand why the GPL can't place requirements on people who don't distribute?

      --

      *sigh* back to work...
    8. Re:An other example of GPL3 suckyness by glwtta · · Score: 1

      It's "lose", the word is spelled "lose".

      Oh yeah, and "blah blah I don't get the point of the GPL blah blah" - protecting free software from MS's "embrace and extend" strategies is quite high on the FSF's list of priorities, and rightfully so.

      --
      sic transit gloria mundi
    9. Re:An other example of GPL3 suckyness by Dog-Cow · · Score: 1

      The GP didn't say such a clause wouldn't work. He's pointing out that the GPL (and FSF) encourages the addition of restrictions as long as those restrictions meet their philosophical goals. In other words, they aren't interested in open code. If all they were interested in is open code, GPLv2 would have been fine and v3 not needed at all.

    10. Re:An other example of GPL3 suckyness by tkrotchko · · Score: 4, Insightful

      "that all any given Open Source project really represents is the right to have the source code AS IT EXISTS NOW."

      What gives you any better choice?

      When you buy Windows Vista, and you agree to the EULA, what exactly is it giving you the right to, except the license to run the binaries AS IT EXISTS NOW?

      I "get" the purpose of GPL3. I "get" why companies like MS object to it. What I don't "get" is why this is an issue. The GPL2 is still there. BSD is still there. Apache is still there. Use those.

      But implying that the GPL3 is taking something away from users is pretty silly. You know the score before you start... you get the candy for free, but you have to always share it with anybody who asks. If that's not okay, then don't use it! It doesn't limit your rights in any way.

      --
      You were mistaken. Which is odd, since memory shouldn't be a problem for you
    11. Re:An other example of GPL3 suckyness by dosius · · Score: 1

      At risk of being called a troll... GNU does embrace/extend too. But it's "free software", so it's all right, I guess?

      I prefer BSD precisely for that reason, they try to do it by the book, THEN they try to improve. That's why their binaries are easily half the size of GNU's.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    12. Re:An other example of GPL3 suckyness by jayw · · Score: 1

      I like your candy analogy. But it would be more correct to say:

      You get the candy for free, but you if you share it with others, you have to leave the wrappers on so they don't get sticky fingers.

    13. Re:An other example of GPL3 suckyness by Tony+Hoyle · · Score: 1

      Now do you understand why the GPL can't place requirements on people who don't distribute?

      Actually it does.

      If you link to a GPL library *even if you never distribute that library* your application becomes bound by the terms of the GPL.

      That's the whole Mysql business model in fact.

    14. Re:An other example of GPL3 suckyness by Tony+Hoyle · · Score: 1

      gpl3 opens up patent issues. If you compile an app with a gpl3 gcc does it nullify your patents? Probably not.. but for a manager it's a valid question - are you willing to bet your business on that? Of course not - you'll go to your lawyers who will look at the license and tell you what it safe to do.

      Now you're using a nice LGPL library. It goes LGPL3 (which I presume will exist at some point) - same question. Back to the lawyers.

      All of this cost time, money and uncertainty. Most businesses will take the easy way out and just blanket ban gpl3 until they absolutely have to pay lawyers to look at it. Heck even we have and we're a very small company.

    15. Re:An other example of GPL3 suckyness by twistedcubic · · Score: 1


      gpl3 opens up patent issues. If you compile an app with a gpl3 gcc does it nullify your patents? Probably not.. but for a manager it's a valid question - are you willing to bet your business on that? Of course not - you'll go to your lawyers who will look at the license and tell you what it safe to do.

      And of course, you when you use Visual Studio, Adobe XYZ, etc... you have to pay your lawyers to reads the EULAS, since they are a zillion times more onerous than GPL3. But in reality, since you didn't have your lawyers read the EULA for Visual Studio, you're in BIG TROUBLE!!!

    16. Re:An other example of GPL3 suckyness by Dan+Ost · · Score: 1

      Linking a GPL library makes your code a derivative of the GPL code. Therefore, in order to not break the law if you try to distribute your code (as a derivative of the GPL'd code), you must meet the criteria of the GPL.

      The Mysql business model is dependent on businesses wanting to distribute software, but not be required to satisfy the GPL requirements. Businesses that strictly use Mysql internally have no need to send any money to Mysql (unless they want to purchase support, but that a different business model).

      --

      *sigh* back to work...
    17. Re:An other example of GPL3 suckyness by init100 · · Score: 1

      GNU does embrace/extend too.

      Oh? Of what? The only one I can think of is BSD software, but those guys want their code to be embraced and extended. Otherwise, they wouldn't have used such a license.

      I prefer BSD precisely for that reason, they try to do it by the book, THEN they try to improve. That's why their binaries are easily half the size of GNU's.

      I really don't see what you mean. Care to elaborate?

    18. Re:An other example of GPL3 suckyness by DandyRandy · · Score: 0, Troll

      >>However GPLv3 was crafted to address a very real problem, and judging from Microsoft's reaction, it is doing a great job in that regard.>> Excellent operation, Professor! Your techniques are magnificent! Professor, your intelligence... that's top level! We are so-ooo-o impressed... only, could we ask you, why did your patient die??? /in memoriam, to FOSS etc, 'saved' by GPLv3 and pinkies/commies/.

    19. Re:An other example of GPL3 suckyness by Anonymous Coward · · Score: 0

      Most businesses did not do anything that would be in conflict with GPLv3, but not with GPLv2. Using DRM to lock users out was the exception before GPLv3 existed. Also, while a few businesses used patents to make GPLed software non-free, they where a very small minority. So for 99% of the community, whether it is GPLv2 or GPLv3 does not matter. For the remaining 1%, I'd be happy if they left our community and worked with proprietary vendors.

    20. Re:An other example of GPL3 suckyness by dosius · · Score: 1

      The standard is implemented by systems such as Solaris, AIX, HP/UX, and the BSDs basically have an attitude of "if we can, we ought to", as opposed to GNU's "generally copy the look and feel but add features" that results in significantly larger, slower (GNU's bash is a LOT slower than the public domain version of ksh, despite them being very similar), etc., and all the GNU extensions make compatibility with non-GNU unices like OSX a bit harder.

      I for one would rather have something that's GPL2 or BSD, and acts like Solaris's userland (CDE and all that jazz), something that if it were submitted to Open could get use of the UNIX trademark, before it were to get extended.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    21. Re:An other example of GPL3 suckyness by Anonymous Coward · · Score: 0

      I, OTOH, HAVE read the EULA of Visual Studio. It expressly says, RIGHT IN THE LICENSE, "You may not use this software to write programs using an open-source license."

    22. Re:An other example of GPL3 suckyness by init100 · · Score: 1

      I for one would rather have something that's GPL2 or BSD, and acts like Solaris's userland (CDE and all that jazz)

      Do you seriously mean that you like CDE?

    23. Re:An other example of GPL3 suckyness by dosius · · Score: 1

      Actually I do like CDE. But that's beside the point: CDE's a Unix standard, Gnome and KDE aren't, therefore CDE's what I want my "Unix" to have.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
  6. Why care about something with no legal weight? by Anonymous Coward · · Score: 0

    I read the summary as "Microsoft is being very careful ... to avoid stepping in the GPLv3 ... even though the GPLv3 has no legal weight". I realize that enough lawyers gives you infinite shades of grey, but it still seems like it's one or the other: if GPLv3 has "no legal weight", why bother excercising any due caution with your partner agreements?

    1. Re:Why care about something with no legal weight? by Volante3192 · · Score: 2

      The GPL has potential weight (as opposed to kinetic weight), and they hope if they keep repeating that "No, it doesn't" they'll make enough decision makers believe it.

      Microsoft really doesn't want to test the GPL because there's a good chance it will get kinetic weight from a legal standpoint, which would be bad.

    2. Re:Why care about something with no legal weight? by Kjella · · Score: 1

      It's a completely voluntary license and the terms are quite clear and not unreasonable. In general I don't think you can say "you're not allowed to sue me", but in this case it's a direct consequence of "By distributing this you grant me a patent license, thus you can't sue me for patent infringement" which is just spelling it out. Of course Microsoft will say it has no legal weight, SCO also claimed the GPL is unconstitutional...

      --
      Live today, because you never know what tomorrow brings
    3. Re:Why care about something with no legal weight? by Anonymous Coward · · Score: 0

      One has to wonder how many of the more vocal GPL3 detractors who endlessly post on Slashdot are paid Microsoft, SCO, or Apple shills looking to create a divide in the free software community. One need only see how they played up the mostly positive feelings Linus has about the GPLv3, by quoting him out of context, into a controversy. There has always been a significant number of well funded and well positioned people who would like to see the GPL destroyed due to the protections it affords end users, and it would not surprise me in the least if they are the ones swarming around slashdot and other places now ceaselessly attacking it.

    4. Re:Why care about something with no legal weight? by plague3106 · · Score: 1

      Microsoft really doesn't want to test the GPL because there's a good chance it will get kinetic weight from a legal standpoint, which would be bad.

      Or perhaps MS is respecting the licensing choice of developers, as it would like others to do.

      Or perhaps both of us really don't know why MS is acting as it is, since neither of us know the people making the decisions or were in meetings regarding the actions.

    5. Re:Why care about something with no legal weight? by Volante3192 · · Score: 1

      But speculation is half the fun!

    6. Re:Why care about something with no legal weight? by dgatwood · · Score: 1

      I, for one, am no shill. I'm sure the GPLv3 will probably inconvenience my employer at some point in the future, but that's somebody else's problem as far as I'm concerned. They couldn't pay me enough to spread FUD about the GPLv3. :-)

      Honestly, I think that the ideals the GPLv3 is trying to promote are noble ones. However, I think that the way they have pushed those ideals is harmful to the free software community. I feel that the right way to achieve their goals is through legislation, not licensing. I think that laws should prevent "Tivoization" of any device, period, without regard to what software is used on the device. If I want to rewrite the firmware of my printer, I should have that right. I paid for the device. It is mine, and once I have handed over my check/credit card/cash, the manufacturer should no longer have any say about what modifications I perform (beyond their right to disclaim warranty coverage if I break the device).

      I think the Tivoization clauses in the GPLv3 are completely wrongheaded, though. They harm the free software community as a whole by creating artificial divisions over what amounts to a very frivolous issue that bothers maybe all of a thousand people worldwide. It's on the same level of cuckoo-bananas as putting in a clause that says you can't use a particular piece of software on a whaling ship or a non-dolphin-safe tuna boat. It is standing up for ideals that really aren't worth standing up for. If you protest everything---if you don't choose your battles, you just end up looking like a loonie nut.

      It's also almost entirely academic anyway. Whenever somebody locks down hardware, it is either something that people wanted to hack or it isn't. If it isn't, then it doesn't matter. If it is, then the free software community has a tendency to write a replacement (MythTV, Freevo, etc.) that is usually significantly better in most ways and is free. The community senses damage and routes around it. I doubt that very many people even care about TiVo hacking at this point. As hackable devices go, it simply isn't that interesting because it has been supplanted. By locking things down so much, they basically sealed their own fate, and I would not be surprised to see them bankrupt in the not too distant future. One can reasonably hope that other companies will learn a lesson from that---a lesson that is far more powerful at making the point about closed hardware than any mere GPL licensing change could ever be.

      In short, I refuse to buy any TiVo because of what they have done, but I will vigorously defend their right to commit suicide if they choose to do so....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  7. Does Linspire have any market share? by jkrise · · Score: 3, Interesting

    So many firms have merely pretended to be at war with Microsoft - only to cave in later and become partners - Novell and Linspire being recent cases. Have any significant no. of customers actually signed up with Linspire for patent protection? I don't think so.

    Microsoft's Covenant to Customers (Linspire's customers it would seem - not Microsoft's) hardly makes compelling business sense to consider Linspire for the business desktop. Few home users would consider themselves vulnerable to patent lawsuits by Microsoft, if they used Linux.

    So this announcement merely indicates that GPL3 has won, and Microsoft has been compelled to publicly qualify their pre-negotiated deals with business partners, and customers gain more from GPL3 than covenants from Microsoft.

    --
    If you keep throwing chairs, one day you'll break windows....
  8. I, for one, welcome our... by Will+the+Chill · · Score: 3, Funny

    bullet-dodging FUD-slinging bloatware overlords!!!

    -WtC

    --
    Creator of RPerl, Scouter, Juggler, Mormon, Perl Monger, Serial Entrepreneur, Aspiring Astrophysicist, Community Organiz
  9. Success! by kebes · · Score: 5, Insightful

    Well, given that the GPLv3 was written specifically to make those "patent protection deals" untenable, this is a huge success for the GPLv3. Microsoft is essentially admitting that, legally, the GPLv3 does what it intends to do.

    So, anyone who was bothered by the MS/Novell deal (and its variants) can and should encourage usage of GPLv3. Coders who want to prevent MS from using patent threats to splinter the community should consider adopting the GPLv3.

    Since a certain number of important projects have already switched to GPLv3, this means that within a year or two the MS/Novell deal (and variants) will essentially disappear. As someone who was not happy with those deals in the first place, I say good riddance.

    1. Re:Success! by plague3106 · · Score: 1

      The deals may stop, but then MS may begin actively sueing companies that distribute gpl3 software. Do you think it'd be good if Redhat's legal now tookup 110% of revenue?

    2. Re:Success! by trolltalk.com · · Score: 3, Informative

      Microsoft will never sue - they know that the only thing they can do is amke noises. Actually suing would be the equivalent of a first strike in a MAD - Mutually Assured Destruction - scenario, which they would ultimately lose.

      The resulting positive publicity for linux would further erode their already slipping grip on their customer base. Like it did with allthe SCO BS.

    3. Re:Success! by tkinnun0 · · Score: 1

      Microsoft will never sue - they know that the only thing they can do is amke noises. Actually suing would be the equivalent of a first strike in a MAD - Mutually Assured Destruction - scenario, which they would ultimately lose. Well, does Red Hat have the clout to bring the big boys to their side? You see, MAD only works when both sides have an arsenal.
    4. Re:Success! by thethibs · · Score: 2, Interesting

      Well, given that the GPLv3 was written specifically to make those "patent protection deals" untenable,...

      There's another way of seeing this if we can assume that the effect is proof of the motive: that GPLV3 was written specifically to encourage developers to build products that would not be indemnified by those "patent protection deals". Richard stuck a spear in the ground and assumed Microsoft would run into it. What's comical is the number of people surprised or upset that they went around it instead.

      Writing code under GPLV3 is about to become a great deal like putting your head in the lion's mouth while guessing that he won't like the taste of your hair cream or that he doesn't have any teeth. After all, it could be that Microsoft doesn't really have any actionable software patents.

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
    5. Re:Success! by trolltalk.com · · Score: 1
      RedHat only needs to make some motions in discovery to get Mr. Softie to STFU. "Identiy with specificity the patents that you claim are infringing, by patent number and claim number, and source code file and line number in the infringing implementations, how these supposedly infringing pieces of code are prohibited under current doctrines, the names of the original patent holders (for more discovery) and anyone else who has seen the source code for the patented materials, what damages have been incurred, and what Microsoft has done to mitigate damages."

      That last bit - the obligation of the injured party to mitigate damages - will kill Mr. Softie, since they have gone out of their way NOT to mitigate damages by disclosing any infringing patents. The doctrine of laches means they are f$cked.

    6. Re:Success! by fm6 · · Score: 1

      The MAD scenario only applies when both sides are capable of obliterating each other. If it applies to software litigation, than there has to be an OSS company with the resources to out-litigate MS. Which is absurd. Red Hat (for example) has annual revenue out of about $60 million. Microsoft makes twice that much in one day.

      You seem to suffer from the quaint notion that litigation is always decided on its merits. Just not true. Litigation is expensive, especially when you're up against somebody who can afford to hire hundreds of lawyers to nitpick every filing you make. Unless you have the resources, you haven't a prayer, no matter how good your case is in theory.

    7. Re:Success! by trolltalk.com · · Score: 1

      Do you really expect everyone who has a stake in linux NOT to join in the case so as to protect their own interests? Would IBM sit on the sidelines and let a judgement go through without unleashing a few of the nazgul?

      Also remember, its a LOT cheaper to defend than to pursue.

    8. Re:Success! by Chandon+Seldon · · Score: 2, Interesting

      There is a player you're forgetting about: IBM.

      They aren't the good guys. In fact, they are the biggest patent abusing bastards in the world. But... they'd take a revenue hit if people were afraid of deploying their favorite commodity UNIX (i.e. GNU/Linux), so they're likely to step in and maul anyone who actually attacks it with software patents.

      And yes, they can win a patent war against Microsoft.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    9. Re:Success! by mrchaotica · · Score: 1

      Microsoft will never sue - they know that the only thing they can do is amke noises. Actually suing would be the equivalent of a first strike in a MAD - Mutually Assured Destruction - scenario, which they would ultimately lose.

      Not to mention that it would be like Alas, Babylon, where near the end of the story it talks about the US getting aid from places like Latin America: this kind of fight would destroy the computing industry in countries that upheld software patents but wouldn't affect anywhere else.

      --

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

    10. Re:Success! by trolltalk.com · · Score: 1

      It looks like we might be heading towards a different sort of singularity than was previously envisioned. A world where the US self-destructs (just look at the debt clock), ripped apart by capitalizm mixed with profiteering and greed among the well-connected, and the RotW (Rest of the World).

      Some of the economic projections for later this century are downright ugly - with a US with a population of up to half a billion, but a permanently wrecked economy, as we hit the upper limits of what's possible, and the rest of the world catches up, then surpasses the US in terms of GNP. Both China and India will have larger economies by the middle of the century - and less debt.

    11. Re:Success! by zsau · · Score: 1

      Ah --- quite the opposite. The desired effect was to discourage companies from doing business with Microsoft. And what's happened is that Microsoft's losing its power. If these patent protection deals don't cover GPLv3 software, then there's no point in signing up to one, if all (or most) of your software is GPLv3: and an increasing amount is. Stallman has put down a solid and essentially impenetrable defense around his castle. Now he's hoping to extend it round the entire kingdom.

      Microsoft are shooting themselves in the foot now. But it was that, or shoot themeselves in the heart. The GPLv3 was an excellent move.

      --
      Look out!
    12. Re:Success! by Anonymous Coward · · Score: 0

      Red Hat doesn't need to "bring the big boys to their side". They're already there.

      You do know about the Open Innovation Network, right? http://www.openinventionnetwork.com/

      They've already said they'll be involved with any attempt by Microsoft to enforce patent rights on Linux, and OIN has a much much larger patent stockpile than Microsoft has.

    13. Re:Success! by I'm+Don+Giovanni · · Score: 1

      So are you saying that as a practical matter, GPL3 gives devs carte-blanche to violate patents? I seriously doubt that. If a closed source dev sees OSS devs blatantly and wantonly violating their patents and publicly sticking their toungues at the closed source dev saying, "nyah nyah nyah - we violate your patents with impunity because GPL3 says we can!!", then that closed source dev will indeed take legal action.

      Historically, companies would pay for patent licenses or make cross-licensing deals, or whatever. For some reason Red Hat refuses to do this. It is only now that particular software companies like Red Hat feel that they can violate patents at will because a particular license allows such. Well GPL3 doesn't trump patent law.

      You guys are under the belief that MS's patent claims carry zero weight. We've seen courts uphold the most ridiculous of patents. Do you really believe that ZERO of Microsoft's 250 patents will be upheld? This is a very dangerous game you guys are playing. Remember that RMS is an anti-capitalist who has nothing at stake himself. Dancing to his tune is not very prudent, especially when it's so easy to make the patent-licensing deals that have been made for years between companies. THe old system worked well and seems more proper than some companies decided to violate patents at will.

      --
      -- "I never gave these stories much credence." - HAL 9000
    14. Re:Success! by I'm+Don+Giovanni · · Score: 1

      The desired effect was to discourage companies from doing business with Microsoft.


      Ever heard of the concept that making laws specific to particular case makes for bad law? If GPL3 was made with regards to one company, you can be sure that it's a bad license too.
      --
      -- "I never gave these stories much credence." - HAL 9000
    15. Re:Success! by Vintermann · · Score: 1

      Conveying GPL3 code now constitutes a sort of cross-licensing deal with the open source community - only we have no actual patents, only copyrights. So yes, if someone distributes GPL3 code...
      There is one thing they could do. Say company A distributes some GPL3 code. Then a feature is added by someone else, and A feels this infringes their patent. I wonder if they may have some legal standing if they say "Hey, stop, stop! We don't want to distribute anymore! We don't want to license THAT patent! Can we go back please?". But if the infringing feature was already present, their chances are zero.

      --
      xkcd is not in the sudoers file. This incident will be reported.
    16. Re:Success! by thethibs · · Score: 1

      Given this is the real world and not a graphic novel, if you are right then what happens is this:

      GPLV3 discourages companies from dealing with Microsoft, but if your organization is bigger than the Five Man Electrical Band, or if computers are incidental to your business, choosing not to deal with Microsoft would be choosing to shoot yourself in the foot. So you remain part of the vast market for Windows-compatible products (open-source or otherwise) whose demand will be supplied by ISVs and OEMs.

      If I'm an ISV or OEM in that marketplace I have a number of choices:

      • I can build solely for Windows. In return for no licensing nonsense I give up less than 10% of the market—maybe even less if it's a stand-alone product and the customer doesn't care what's inside.
      • If it's embedded, I can build on one of the many excellent platforms (e.g. QNX) available with great developer support, low unit cost, and no licensing nonsense. This is Tivo's best response.
      • If support is not an issue and I don't care what happens to my code, I can build on BSD with its excellent toolbase, zero unit cost and no licensing nonsense.
      • I can also build on a platform of GPLV2 software if I don't mind supporting a fork or if I think GPLV3 will become irrelevant. Licensing nonsense is minimal.
      • I can build my product with the code under GPLV3, tied up with licensing conditions so that anyone who wants to use my code in another product will need a lawyer to help decide whether or not it's safe to do so. I get the social benefit of membership in an elite group (the Fosseratti) while minimizing the risk that a competitor will use my code.
      The Tivo issue didn't happen in a vacuum. Other OEMs are watching and more than one development manager is being told by the people with money that they don't want to be the next Tivo. An OEM is not going to invest in a technology that preempts all future decisions regarding product and patent licensing models.

      GPLV3 interferes with doing business. That by itself will probably render it and GPLV3 products irrelevant in the long run. World domination schemes don't work, because they depend on the tacit approval of their victims.

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
    17. Re:Success! by trolltalk.com · · Score: 1

      Patents for software or business methods are bogus. They have zero to do with the original patent language, and are a "feature" of the USPTO that attests more to the bugginess of the process than anything else.

      Copyrights for software make sense. It is code, it is copywriteable. But patented? Its not an invention.

      Besides, you fail to address my main point - that because Microsoft has done nothing to reduce its alleged losses, specifically by identifying the alleged infringements, the doctrine of laches means they can't succeed with a claim any more. If they were to file a lawsuit tomorrow, they would have to prove that the lawsuit was over a patent OTHER THAN THE 235 "allegedly infringed" patents that are now lawsuit-proof. So they would ahve to name 236 patents, point to the first 235 and say, "it was not one of those", etc.

      They will never successfully sue. They know it. They blew any basis for a successful leagal claim by milking it for fud value, rather than disclosing what it was (since it never existed anyway, they couldn't ...).

      It doesn't matter in the long run, because in the long run (20 years), Microsoft will be a niche player, probably bought out by Apple, since they can no longer produce competitive products.

  10. What amazes me is this... by bogaboga · · Score: 1

    What amazes me is the fact that most pundits warned Linspire about Microsoft's actions while citing its past actions. They did not listen and even went ahead to defend their position. I wonder how they (Linspire folks) feel now.

    1. Re:What amazes me is this... by Anonymous Coward · · Score: 0

      I imagine that Kevin "used car salesman" Carmony feels richer. As for everyone else, oh well, too bad so sad.

    2. Re:What amazes me is this... by Dan+Ost · · Score: 1

      I guess it depends on how much money they were paid to sign the agreement. Was that ever made public?

      --

      *sigh* back to work...
  11. So Torvalds and MS agree on one thing by Brad_sk · · Score: 2, Funny

    On the other side - Theres atleast one thing both Linus Torvalds and MS agree on. They both disagree to GPLv3!!

    1. Re:So Torvalds and MS agree on one thing by vertinox · · Score: 1

      From my understanding, most of issues that Linus brought up with GPL3 were on a early draft. He did warm slightly when he saw the final draft.

      http://www.linux.com/articles/114336

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
  12. Stupid Microsoft by Anonymous Coward · · Score: 1, Informative

    Do they still not get the optional "later versions" clause that covers most GPL2 software?

    Worse for Microsoft, they were being clever-dicks and trying to work around existing license terms. All that GPL3 does is make GPL2 these terms implicit; all of which a court would take into consideration.

  13. Darth Gates by sconeu · · Score: 2, Insightful

    I have altered the deal, pray I don't alter it any further.

    --
    General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    1. Re:Darth Gates by Constantine+XVI · · Score: 2, Insightful

      The same could be said about GPLv3
      (see also: your own sig)

      --
      "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
    2. Re:Darth Gates by Anonymous Coward · · Score: 0

      I have altered the deal, pray I don't alter it any further.
      IANAL, but wouldn't changing the licenses of the software involved in the deal essentially break the contract if not renegociated? If Microsoft continued to distribute the vouchers without this disclaimer it could be termed as acceptance of the change, similar to the periodically changing EULAs that force a click through every time you go to use some companies software. With their disclaimers they are essentially saying that they only offer their promise not to sue to users of software distributed as originally licensed at the time of the agreement, ie if the license has changed then the deal has changed and they won't hold up their end of the bargain because they never agreed to the conditions invoked by GPLv3.

      Essentially they say they will hold up their bargain re: GPLv2 distributed by companies they have made deals with but any GPLv3 software you get that way is like getting a toaster from the bank with your new account, it is free, but the bank doesn't guarantee it. Tossing in the GPLv3 ex post facto like this is primarily the same as tossing a note into shipping containers that says "by taking delivery of this product you agree not to sue us if it is harmful to you in any way and you agree to pay us double for the delivery, prior contract not withstanding".

      Again, IANAL and I could be wrong about any part of the above or all, but IMO Microsoft is laying the groundwork for evidenciary proof that they never intended to extend their guarantee not to sue to anyone that did not have a contractual agreement with them stating so. I also believe that they will fight any GPLv3 attempts to remove their rights to sue under grounds similar to those used by the courts to hold parking lots and others liable despite their signs and agreements on parking lot stubs which essentially say "if you use our services on our property you agree that the company is not liable for any damage or loss to your property while under our 'care'", which would be amusing considering the wording of their own EULAs.

      Would certainly welcome a real lawyer's analysis/comments on the above or from someone with more knowledge/experience in such matters then myself. Of course the lawyers will probably have to include disclaimers such as "this is not free legal advice/opinion".
    3. Re:Darth Gates by sconeu · · Score: 1

      The difference is that MS is unilaterally saying "Oh, our deal will not apply to ***".

      Had *both* MS and Linspire said it, then fine.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    4. Re:Darth Gates by init100 · · Score: 1

      IMO Microsoft is laying the groundwork for evidenciary proof that they never intended to extend their guarantee not to sue to anyone that did not have a contractual agreement with them stating so.

      IMO, Microsoft is laying the groundwork for a lawsuit against Novell, as Novell has publicly stated that they think that their agreement permits shipping GPLv3 software, and that they will do so. Microsoft states the opposite. And the GPLv3 prohibits distribution if you also have contactual obligations or other requirements that cannot be fulfilled if you distribute. In other words, other contracts, court orders, etc, does not remove any of the requirements of the license.

      So if Novell distributes GPLv3 software, claiming that it is protected by the covenant not to sue, Microsoft may sue their "beloved" business partner.

      IANAL though.

    5. Re:Darth Gates by domatic · · Score: 1

      Not really. Code obtained under GPLv2 terms can still be used under those terms and even further developed.

  14. The shit hits the fan ... by Anonymous Coward · · Score: 0

    Let's see now how MS realizes that it can't exploit GPL and or any other kind alike conscienceless company (which is redundant, I know).

    I had the idea, sometime in the future MS will adapt Linux Kernel (a snapshot of it, essentially fork it) and run MS Windows on top of it, not yet excluded, right? Like Apple took *BSD fragments making MacOS-X ... at the end all use OSS software, but run their nifty (closed source) GUI on top of it . . . and all are happy: stable OS, great GUI, almost all open source, except the GUI layer ... this will happen, it's a matter of time (5 years). Of course, it will be interesting how FSF with handle it . . . GPLv4 or v5 preventing to use the kernel in a closed-source setup? Let's see.

    1. Re:The shit hits the fan ... by edwdig · · Score: 1

      Why would MS do that? The NT kernel is fine, it's the layers above it that's crap.

      If they were going to use another kernel, they'd take one of the BSD kernels so that they could retain more control.

    2. Re:The shit hits the fan ... by Anonymous Coward · · Score: 0

      The advantage over *BSD development: Linux will become even more active with more corporate support (IBM, SUN etc) and the coming features will make Linux per-se a kernel "must-have". If MS were smart, they would fund a start-up porting next version of MS Windows on top of 2.6 kernel, knowing at 3.x they fork - MS cannot afford to develop their own kernels, and I wouldn't be that surprised Sun ends up with a Linux kernel on Solaris as well, when all the features they donate now make the Linux kernel as versatile as their current.

      *BSD, even I prefere it myself, will remain what it is now, a niche, important one, and companies doing embedded stuff will use *BSD kernels to keep their secrets - but MS will, which I think, see Linux kernel is superior when the backing from IBM and Sun and others will keep up and more donations of "features" are happening.

      I know, it's a lot of speculation, but I also speculated of Apple switching to Intel, and having maintained a x86 source-tree in secret for a quick change (I would have if I were Apple) - if I were MS, putting aside all resentment I do have, they must think long-term ... and realize, how "cheap" it is to harvest almature kernel full of features from IBM, Sun and who knows - they don't become OSS friends, they will be convinced by the way they can profit, as banal as this.

    3. Re:The shit hits the fan ... by huckamania · · Score: 1

      I've wondered for a while if MS could pull off forking everything that is "GPLv2" and "GPLv2 or Later". The trick would be to do shadow development, never release a thing, until they have replaced all of the code that is controlled by the FSF and others. Think tool chains, compilers, libraries, etc. Once they have those pieces in place, they can start distributing and keep everything GPLv2, since the guts of the GPLv3 stuff will have all been replaced.

      Basically, it is similar to the "we'll rewrite any code covered by patents" defense everyone was so enamored with when MS first started huffing about patents. Which, BTW, is probably not a good idea, as it would basically show that the patent was infringed upon. That would allow MS to sue for the period of infringement, which could be a long time.

      Speculation is so much fun...

    4. Re:The shit hits the fan ... by Anonymous Coward · · Score: 0

      There's no problem in MS or any other company building on linux so long as they play by the rules - something Microsoft has been consistently incapable of doing.

      The patent threats and Novell deal are a stink-bomb from the nasty, malicious employees of a nasty, malicious company. A pathetic company too, they're absolutely terrified of being forced to compete on fair terms.

    5. Re:The shit hits the fan ... by edwdig · · Score: 1

      How can you say MS can't afford to develop their own kernel? They've been getting along just fine for decades with that approach. They even developed two different kernels (9x and NT) at the same time for good chunk of time. They obviously have the ability to do it.

      And for the cost aspect, Windows makes them incredible amounts of money. Enough so that it, combined with Office, subsidizes everything else the company does. They make enough that they can lose a billion dollars a year from the Xbox division and not even blink.

      Again though, the kernel is by far the best part of the Windows codebase. Why would they scrap that and keep the rest?

    6. Re:The shit hits the fan ... by Anonymous Coward · · Score: 0

      Linux kernel will leave most other developments far behind, because not even MS will catch up - look at the pace features are added the last months, if IBM and Sun keep up, MS will not able to afford to keep up. The quality the Linux kernel is reaching will be, so my speculation, grown beyond even MS ability. When Sun already makes the Linux kernel ready to be married, MS will not able to withstand within the next 5 years...

      To afford means: develop an alike kernel, with same features - the Linux kernel has become very big, and the knowledge embedded is immense - if the pace remains, and I don't see why it should change, the Linux kernel becomes a standard by itself. Of course, the change of API and lack of backward compatibility is a major drawback on this all .... this has to change.

      At some point, MS will realize, to embrace the Linux kernel, because it's more reliable, supported and feature-rich, it will (not now but later) excels MS ability to maintain an alike stable and feature-rich kernel. I would recommend MS to think in 5 to 10 years to adopt the linux kernel, and actually start to leave the old position to demonize FOSS (and vice-versa) - what most FOSS fans don't realize, the contributions of companies like IBM and Sun are far more significant than other hyped things. It really means, big companies realize the community is able to bring forth something they alone cannot afford in the long term - there are things which require long term commitment - only big companies, like IBM & Sun - who have long term strategies. And who else? MS.

      Anyway - I would recommend MS to start to invest 2-3 years work into the possibility to fork and/or adapt a 3.0 linux kernel, e.g. writing wrappers to reuse Vista drivers - that would be donated later to FOSS - it will make a lot of people happy - yet, the majority will still use MS, and MS control the layers in between, GUI level, like Apple does today.

      I speculate the FOSS be successful in the FS and Kernel arena, but fail in the GUI level - it may succeed in GUI arena too, but I don't foresee this in the near future of 10 years.

      Enough speculation! :-)

    7. Re:The shit hits the fan ... by Anonymous Coward · · Score: 0

      Yeah, it's not like the BSD license, which is probably what Microsoft would use for any Open-Source stuff of theirs, ISN'T compatible with GPLv2. Nor does Tivo have to use GPL stuff, when BSD stuff is available. There is no arguing on this point. Why would a company use GPL code when they could use BSD code? Could the fact that BSD code can become be part of closed source projects the reason why BSD code is less popular than GPL code, which forces the person to give modified code out under the same license if it is given to the public?

  15. Another Info World Fud Link by Filter · · Score: 1

    I guess this is what we get for not buying subscriptions to Slashdot.

    This Info World sure seems hell bent on trolling, really driven, I wonder why they are so interested?

    --

    "better ways of doing things eventually just replace the inferior things" - Linus Torvalds 09-08-07

  16. pleading in the alternative by oliphaunt · · Score: 4, Interesting

    I'm not a lawyer, yet.

    In a lawsuit, it is possible to argue multiple theories of liability, or multiple theories of innocence. As long as each theory is internally consistent, they don't all have to be consistent with each other. It's the legal version of throwing stuff at the wall to see what sticks... and when you're just getting started, you don't want to leave stuff out by mistake, becuase there might be a chance that if you don't bring it up at the beginning you won't be allowed to bring it up later.

    The classic example is: Your buddy says, "You bastard, you slept with my wife!" If this was a lawsuit, you might respond

    a. No I didn't!
    b. You said that I could!
    c. She wasn't your wife!
    d. I thought she was someone else!
    e. I was insane!

    This would be OK, becuase even though (d) seems to contradict (a), that doesn't automatically mean that (a) is invalid, even though BOTH statements can't be true at the same time. These are all alternative theories of how you might avoid blame/liability for the act, and in filing or responding to lawsuits, this practice is known as alternative pleading.

    In that context, Microsoft's GPLv3 statement doesn't need to be consistent- although it is unusual to see this kind of logical construct outside of a court document. The press release reads like they're anticipating a lawsuit, and they're trying to get their story straight ahead of time... In this situation, their story is plausible deniability. and it doesn't matter which alternative theory ends up working, as long as one of them does the job.

    So it's perfectly legit for MS to use alternate theories to justify their actions- it just reeks of bad faith when their public position is so openly contradictory. It does seem pretty odd that Microsoft is using legal tactics to write their press releases- almost like they've got something to hide.

    --




    Humpty Dumpty was pushed.
    1. Re:pleading in the alternative by querist · · Score: 1

      I hate to be pedantic, but please consider either reading your posts more carefully or taking a refresher in logic.

      (a) and (d) can be true at the same time provided that the woman in question was not the plaintiff's wife. It is entirely consistent. The woman in question was not the plaintiff's wife, and the defendant did not _think_ that the woman in question was not the plaintiff's wife.

      None of the arguments presented are contradictory to each other. (a), (c), and (d) can support each other. (c) and (d) can be considered the same thing, only to differing degrees. (c) is making an assertion about the identity of the woman while (d) is stating the defendant's beliefs regarding the woman's identity at the time of the incident in question.

      (b) is all on its own. The utility of (b) lies in (1) diffusing the suit through commity (that is, the plaintiff knew about it and agreed to it, therefore cannot sue later) and (2) the fact that (b) does not accept guilt - it is simply a statement that the defendant was given permission by the plaintiff. It does not state that the action occurred.

      An analysis of (e) and its interconnections with the other four arguments is left as an exercise for the reader.

      IANAL, but this is simple logic.

      That said, I suspect that there are people (including juries) who would agree with the original post due to their lack of understanding of formal logic. Unfortunately, until we have a system of trained, professional jurors we will not be able to avoid this issue. I believe that this is why it is possible to appeal decisions.

    2. Re:pleading in the alternative by oliphaunt · · Score: 2, Informative

      avast!

      Did I say that all of the statements were contradictory?

      no.

      (a) and (d) can be true at the same time provided that the woman in question was not the plaintiff's wife. It is entirely consistent. The woman in question was not the plaintiff's wife, and the defendant did not _think_ that the woman in question was not the plaintiff's wife.

      speck, eye, log, misplaced double negative- if the defendant thought the woman he slept with was the plaintiff's wife, he could not make statement (d). You're not allowed to change the facts to fit your argument.

      So I'll assume the second bold "not" is a typo, and address that argument instead. While it is possible to construe a situation where (a) and (d) could be true, that situation does not comport with the context I gave in my original post. (d) implies that defendant actually slept with plaintiff's wife by offering an excuse or justification for the alleged transgression. To read it otherwise is to engage in unnecessary parsing.

      I hate to be pedantic

      So don't do it. You'll feel better. I'll freely admit that the wikipedia dog example is a more clearly defined example of contradictory statements [P: Your dog bit me! D: (a) my dog was tied up (b) I don't believe you were bitten (c) I don't have a dog], but that's not the way I heard the story.

      --




      Humpty Dumpty was pushed.
    3. Re:pleading in the alternative by Anonymous Coward · · Score: 0

      Yes, you are being way too pedantic. Answers (b), (d), and (e) have the implicit assumption that, yes, he did sleep with the guys wife. As in:

      b. Yes, I slept with your wife but you said that I could!
      d. Yes, I slept with your wife but I thought she was someone else!
      e. Yes, I slept with your wife but I was insane!

    4. Re:pleading in the alternative by gstoddart · · Score: 3, Insightful

      I'm not a lawyer, yet. .... This would be OK, becuase even though (d) seems to contradict (a), that doesn't automatically mean that (a) is invalid, even though BOTH statements can't be true at the same time. These are all alternative theories of how you might avoid blame/liability for the act, and in filing or responding to lawsuits, this practice is known as alternative pleading.

      Well, thank you for demonstrating why legal stuff seems so damned asinine to the rest of us.

      Sure, we can argue five different things, no two of which can be self-consistent, but as long as we can get someone to give us the go ahead on one of those, then we'll act like that was the truth and our position the whole time.

      The press release reads like they're anticipating a lawsuit, and they're trying to get their story straight ahead of time... In this situation, their story is plausible deniability. and it doesn't matter which alternative theory ends up working, as long as one of them does the job.

      Or, when you put conflicting statements in front of anyone but a bunch of lawyers, everyone else will call shenanigans and point out you were full of crap from the get go?

      I mean ... "We're not bound by that license, and if we were, we're negating the terms of the deal which would make us bound by it, and by the way, you're all doody heads, and, hey, look, a unicorn". WTF?

      I'm sure someone could post a boring explanation as to WHY you can argue several contradictory points. It would only serve to reinforce to me that law in this realm isn't so much about truth, as being able to convince someone that something might not actually be false (even though it clearly is). Sadly, I'm sure there's very good reasons why we need to have this in law. It just seems so ... bizarre!!

      Cheers
      --
      Lost at C:>. Found at C.
    5. Re:pleading in the alternative by hawk · · Score: 2, Insightful

      >I'm not a lawyer, yet.

      But I am :)

      This isn't legal advice. If you look to slashdot for legal advice, you need a shrink far worse than a lawyer.

      The logical end of pleading in the alternative is referred to as "the Cheshire Cat" defense. Similar tol your list, it's to the effect that, "I wasn't there. If I was, I didn't do it. If I did, it was really my cat. But it wasn't my cat, it was the Cheshire Cat . . ."

      Anyway, there's nothing inconsistent between microsoft's positions here. "That's nonsense, it doesn't bind us, and we're staying far enough away to avoid the costly litigation that this mess is going to bring up."

      And as for the folks expecting them to be caught up by future versions of SUSE: the wild and free licensing of ms patents as a result of a fundamental post-contract change made by the other party (SUSE) just won't happen. That is *so* far outside of the *reasonable* expectations of any of the parties, and so drastic, that it just won't be the case.

      hawk, esq.

    6. Re:pleading in the alternative by hawk · · Score: 1

      This still isn't legal advice . . .

      Very simple case of pleading in the alternative:

      Tweedle Dee & Tweedle Dum, identical twins, work for the Jabberwock security firm, which was hired to protect Alice. Both are seen entering the single door to the room she is in. When they leave five minutes later, the White Rabbit discovers that she has been strangled. DNA evidence shows that one of the twins did it. Either way, their employer is liable.

      This could be plead in the alternative in the civil case (and possibly the criminal, but that's trickier).

      Generally, if there's two (or more) ways that something could have happened, and one must have happened, they should both make it to the pleadings. One or more may indeed be struck later, if discovery shows that it was the other, but both may be kept around until what really happened is discovered--possibly during the trial itself.

      hawk, esq.

    7. Re:pleading in the alternative by Kuciwalker · · Score: 1
      Sure, we can argue five different things, no two of which can be self-consistent, but as long as we can get someone to give us the go ahead on one of those, then we'll act like that was the truth and our position the whole time.

      It's a logically valid method of argument. Consider if you were trying to make a mathematical proof for some theorem, but it was hard to predict ahead of time whether a given proof is valid. You construct several proofs which have a decent chance of being valid, even if they're inconsistent with each other, and if any of them are correct, the statement is true.

      Consider another case: you are accused of trespassing on someone else's land, except the location you are accused of trespassing on is your propert and you weren't there anyway. You could say "1) it's not your land so I wasn't [or wouldn't be] trespassing and 2) I wasn't even there in the first place, so I wasn't trespassing" and there's nothing sketchy or wrong about it.

    8. Re:pleading in the alternative by oliphaunt · · Score: 1

      For the Dobbs gold-standard alternative liability case, see Summers v. Tice, 199 P.2d 1 (Cal.1948).

      --




      Humpty Dumpty was pushed.
    9. Re:pleading in the alternative by gstoddart · · Score: 1

      This still isn't legal advice . . .

      No worries. The day I take any posting on Slashdot as actual legal advice I'll have been around too long.

      Tweedle Dee & Tweedle Dum, identical twins, work for the Jabberwock security firm, which was hired to protect Alice. Both are seen entering the single door to the room she is in. When they leave five minutes later, the White Rabbit discovers that she has been strangled. DNA evidence shows that one of the twins did it. Either way, their employer is liable.

      Bah, Dee and Dum were framed. They tried to administer life-saving measures after an unknown assailant which appeared to be a a cat disappeared from the room even though it was locked, hence the presence of their DNA. The police should be out looking for him. Besides, the company can't possibly be liable -- Dee and Dum were subject to intensive background screening before any of this happened, and Alice signed a waiver saying we're not actually responsible for her life or our employees behaviour.

      This is a fun game, can we play again? =)

      This could be plead in the alternative in the civil case (and possibly the criminal, but that's trickier).

      I should hope this is less successful in criminal cases where there seems to an actual focus on what is demonstratably true, as opposed to what we feel strongly happened.

      Generally, if there's two (or more) ways that something could have happened, and one must have happened, they should both make it to the pleadings.

      Again, in a court of law, maybe that is the case. I question the validity of "must have happened", but that's neither here nor there. I get the point.

      I'm just saying that from a PR stand-point when you're explaining to lay-people, saying "I didn't do it. But if I did do it, here's how I did it" comes across as utter horse-shit.

      Thanks for the good layman's analogy as to why this has to be this way. It doesn't make the idea of simultaneously espousing several contradictory positions feel anything less like legal wrangling and obfuscation though -- especially when it's not actually being presented to a court where such things apparently make sense. :-P

      Cheers
      --
      Lost at C:>. Found at C.
    10. Re:pleading in the alternative by gstoddart · · Score: 1

      It's a logically valid method of argument. Consider if you were trying to make a mathematical proof for some theorem, but it was hard to predict ahead of time whether a given proof is valid. You construct several proofs which have a decent chance of being valid, even if they're inconsistent with each other, and if any of them are correct, the statement is true.

      It's a valid method of reasoning out the solution to a problem you don't know. Or, for exploring different philosophical points of view. Or trying to determine which of two positions is valid.

      IMO, it's far less valid when you're explaining why you're not bound by a license, or even if you were, why you're not bound by a license.

      Publicly rationalizing two opposite points of view doesn't go very far to convincing people you were right. It sounds like you're trying to see which of two conflicting points of view you can get people to buy, but by presenting them both, you undermine the value of either of them.

      I mean, if you said to me "why, I'm not a racist at all. But, since I am, I'm perfectly justified because inane theory here."

      We're not talking about a mathematical theorem or an mental experiment to attempt to deduce the truth. We're talking about acting like two opposite statements are both the truth. In the end, one of them will have been a lie (and you knew that up front), and you're hoping that once we figure out which one (if not both) was a lie, I'll conveniently forget the other.

      Other than mathematics and metaphysics ... I don't think this method is really applicable to most 'real world' scenarios. But, I guess people never seem to learn to treat such things with enough skepticism. So, in the long run, my objections probably don't amount to much.

      Cheers
      --
      Lost at C:>. Found at C.
    11. Re:pleading in the alternative by nagora · · Score: 1
      These are all alternative theories of how you might avoid blame/liability for the act, and in filing or responding to lawsuits, this practice is known as alternative pleading.

      And is immoral and corrupt, just like the rest of the legal system.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    12. Re:pleading in the alternative by twistedcubic · · Score: 1


      And as for the folks expecting them to be caught up by future versions of SUSE: the wild and free licensing of ms patents as a result of a fundamental post-contract change made by the other party (SUSE) just won't happen. That is *so* far outside of the *reasonable* expectations of any of the parties, and so drastic, that it just won't be the case.

      Not necessarily, Mr. Esquire. The point of the MS/SuSE deal is to circumvent the license of a third party, so I don't think it's unreasonable to expect the third party to sue when its (separate) agreements are violated. The *reasonable* expectations only apply to the deal between SuSe and MS-- they don't get a free pass with respect to licenses (the GPL) with third parties just because, and only an inept lawyer would advise them not to worry. There is no "post contract" change when the third party is not even involved in the contract. If MS's lawyers are silly enough to write a contract that doesn't account for unfavorable licenses, then they better revise their contract with SuSE. Any contract which states that MS won't sue for patents in code that hasn't been written is obviously a stupid contract. I seriously doubt their agreement is this broad.

    13. Re:pleading in the alternative by init100 · · Score: 1

      the wild and free licensing of ms patents as a result of a fundamental post-contract change made by the other party (SUSE) just won't happen.

      Sounds reasonable. My question (and hope) though: I assume that this will make Novell unable to distribute GPLv3 software, as they cannot simultaneously comply with the GPLv3, comply with the Microsoft agreement, and dole out patent licenses to only a select few. Right or wrong?

    14. Re:pleading in the alternative by Bloater · · Score: 1

      The classic example is: Your buddy says, "You bastard, you slept with my wife!" If this was a lawsuit, you might respond

      a. No I didn't!
      b. You said that I could!
      c. She wasn't your wife!
      d. I thought she was someone else!
      e. I was insane! I thought it was more like:

      a. Please realise I've done nothing wrong because I didn't sleep with anyone
      b. Please realise I've done nothing wrong because, although I didn't sleep with her, you said I could so it would have been okay had I done
      c. Please realise I've done nothing wrong because if I slept with anyone it couldn't have been your wife
      d. Please realise I've done nothing wrong because, if I slept with anyone, it could only have happened during "lie about who you are" day so I would have thought it was someone else.
      e. Please realise I've done nothing wrong because I was insane on the only day I could have slept with anyone so no act of sleeping with someone would have been wrong had they happened at all.

      But I thought that if you told the court A, but then you also say that you slept with somebody else (in order to exclude the possibility of it being the wife) to prove C then one of the two things you've told the court is a lie. And lying to the court is a no-no.

      So while you can say my A-E since they don't contradict each other, the course of events that you assert to prove each of them must not contradict. Your A-E contradict each other right from the off since some of them tell the court that you *did* sleep with the wife yet some of them tell the court that you didn't - either way lying to the court is contempt and you have to be more careful to do it how I have done.

      In my A-E, if you can prove that it was "lie about who you are" day on the day of the alleged act then you've defended yourself and you don't have to prove any of the others. If you can prove that you didn't sleep with anyone then you don't have to prove that it couldn't have been their wife. But nothing stated to the court can be shown to be untrue because all the things I've said could all be true in this world at the same time.
    15. Re:pleading in the alternative by hawk · · Score: 1

      I really don't know. They could certainly use the existing GPL 2 or inevitable forks. [Wild image: MS supporting the Samba fork :)]. They could modify the deal with Microsoft.

      What *won't* happen is Novell's decision opening the MS vaults. Possibly, their deal with microsoft will force them not to distribute GPL 3 stuff . . .

      hawk

    16. Re:pleading in the alternative by hawk · · Score: 1


      >No worries. The day I take any posting on Slashdot as actual legal advice I'll have been around too long.

      Definitely. But attorney's have been sued for less

      >This is a fun game, can we play again? =)

      sure. Please deposit 25c in the slot . . .

      >I should hope this is less successful in criminal cases where there seems to an actual focus on what is
      >demonstratably true, as opposed to what we feel strongly happened.

      It would be rare in criminal cases. As I spun it, though, it would sure sound like a conspiracy (or even just some other felony) or some such in which both would be guilty, regardless of who strangled.

      >I'm just saying that from a PR stand-point when you're explaining to lay-people, saying "I didn't do it. But if
      >I did do it, here's how I did it" comes across as utter horse-shit.

      Just watch for OJ book sales :(

      >Thanks for the good layman's analogy as to why this has to be this way.

      No problem.

      >It doesn't make the idea of
      >simultaneously espousing several contradictory positions feel anything less like
      >legal wrangling and obfuscation though -- especially when it's not actually being
      >presented to a court where such things apparently make sense.

      Actually taking contradictory positions would indeed usually backfire. In this case, though, I think it's a "you're wrong, but we're still not touching it because litigation is expensive."

      hawk, esq.

    17. Re:pleading in the alternative by hawk · · Score: 1

      I actually ran into that case for something other than the joint and several issue early in my practice--but I forget why.

      hawk

    18. Re:pleading in the alternative by Anonymous Coward · · Score: 0

      Publicly rationalizing two opposite points of view doesn't go very far to convincing people you were right. It sounds like you're trying to see which of two conflicting points of view you can get people to buy, but by presenting them both, you undermine the value of either of them.


      Which two opposite points of view are you talking about? It seems to me there is only one point of view at the time WHILE the idea was being written down. But how you would like to interpret it LATER from another point of view is something comepletely different.

      Kindly elaborate the two points of view that you think are troubling you, please. I will do my best to understand what you think.
  17. Microsoft agrees with Linus by Anonymous Coward · · Score: 0

    Me too am with Linus on this one. GPL v3 is a bad idea.

  18. MS and FOSS by falconwolf · · Score: 1

    Look, Microsoft is not an "Open Source" software company. Neither they, nor anyone else (including "Open Source" software companies), are obligated to distribute software under GPLv3.

    True but software currently under GPLv2 vary well may be moved to v3. As Linus had said he doesn't like v3 he may keep Linux licensed under v2. If so then MS could still distrbute Linux itself.

    Falcon
  19. I know how they feel by flyingfsck · · Score: 1

    The are laughing all the way to the bank! MS paid them for nothing...

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  20. Re:15 years ago: by Em+Ellel · · Score: 4, Interesting

    The GPL is going to be "radioactive" to a lot of companies. Hell, even the main BSD guys consider it malignant. Developers that want to see their code adopted and used by the mainstream, whether they are in it for profit or not, might want to avoid GPL, especially if their software has runs on specialized or proprietary hardware. GPL creates what in essence is a walled garden. If you GPL your code, you're putting it into that garden. It might be a very beautiful garden, but your code will never get out.*

    *Assuming others are contributing to it. If you're the sole copyright holder for your project, you can always do whatever the hell you want. Yep thats pretty much explains why BSD is the product of choice over Linux in many of the above cases. 15 years later BSD made it into mainstream products from large manufacturers (F5, OS/X and iPhone, etc) And the companies that try Linux (Tivo, Cisco) are treated as the enemy by GPLv3. Has GPL been like GPLv3 from the get go, would Tivo or Linksys ever consider using Linux or would those be BSD products?

    -Em

    --
    RelevantElephants: A Somatic WebComic...
  21. Pretty good, much worse.... what???? by Anonymous Coward · · Score: 0

    You say:

    "are eschewing GPL 3, saying it's a much worse license than GPL 2, which they consider to be a pretty good license."

    So if GPL2 is "pretty good" and GPL3 is "much worse" does that make GPL3 just mediocre?

    I don't get what you're saying. Can you please explain it with some hint of coherence?

    1. Re:Pretty good, much worse.... what???? by Ohreally_factor · · Score: 1

      So if GPL2 is "pretty good" and GPL3 is "much worse" does that make GPL3 just mediocre?

      I don't get what you're saying. Can you please explain it with some hint of coherence? Why not read the LKML yourself and decide what you think the kernel developers are saying about GPL 3?
      --
      It's not offtopic, dumbass. It's orthogonal.
  22. Re:15 years ago: by vux984 · · Score: 5, Insightful

    It might be a very beautiful garden, but your code will never get out.

    Not quite. You can take code out of the garden and modify it for personal/internal use, and you don't have to share those changes. You only have to put your modifications back into the garden if you redistribute them, and putting them back in the garden is the only way you are allowed to redistribute those changes.

    This ensures that changes that are redistributed are available to the original authors, and the community at large. That 'walled garden' is always open, and anyone can use it.

    Other licenses allow you to take code improve it, and then redistribute it in proprietary walled gardens that may restrict who can use it. Why would I want to contribute code to be used in someone elses proprietary walled garden... where one day I might be required to pay a license covering the code I wrote and contributed.

  23. Novell must remove samba? by pavera · · Score: 1

    Since samba is going GPLv3, and the whole "point" of the MS/Novell deal was interoperability, and Samba is pretty much THE windows/linux integration point...

    Obviously Novell doesn't have to remove samba, but I would imagine that the "vouchers" that MS has are for standard Suse distros which include samba. So, does Novell now have to create a "special" distro just for MS so they don't distribute GPLv3 software?

  24. Re:15 years ago: by ahxcjb · · Score: 3, Informative

    Sorry, but I have to correct you. F5 BigIP now runs, and has for quite a while now, RHEL 3. That's GNU/Linux for the avoidance of any doubt - not BSD.

  25. The only real objection Linus has... by Anonymous Coward · · Score: 5, Insightful

    The only serious objection Linus has is over TiVo-ization. He thinks it should be OK.
    He says he is angry that FSF is claiming to protect freedom while taking away a certain freedom from companies like TiVo.

    But the freedom that FSF is taking away is the freedom to take away freedom from users of the software. Thanks you Linus, great protector of ... wha??

    But keep in mind the politics that Linus has to deal with. There are many developers who would have to sign off on GPLv3. One of the biggies is Greg Kroah Hartmann of Novel, who owns the USB subsystem. Novel no doubt takes GPLv3 personally. Greg has actively tried to discourage even the "or any later version" clause from being included in kernel patches.

    On top of that, even if everyone wanted to go GPLv3, they would have to track down hundreds of developers. So it's just easier for Linus to say no to GPLv3 in any case.

    1. Re:The only real objection Linus has... by Ohreally_factor · · Score: 1

      But the freedom that FSF is taking away is the freedom to take away freedom from users of the software. Thanks you Linus, great protector of ... wha?? That's a very common mischaracterization of the objections to the hardware over reach of the GPL 3. If you want to really understand the kernel developers objections (and it's not just Linus), you need to read the relevant portions of the LKML.
      --
      It's not offtopic, dumbass. It's orthogonal.
    2. Re:The only real objection Linus has... by Anonymous Coward · · Score: 1, Informative

      Maybe you can distill the objections for us? I read the entire thread. I can't point to any logical objection. As I recall, the principle 'objection' was that GPLv3 places restrictions on hardware. It doesn't. It only restricts distribution of GPLv3 code. If you take away the freedom of the users, whether it be through patents, with-holding source code, or technical restrictions (tivoisation), then you cannot distribute.

      The rest was a bunch of straw-men and red herrings (c.f. Linus' bizarre assertion that the FSF wasn't letting him choose his own license). I was stunned by the misology. Alan Cox seems to be the only one with a level head.

  26. Re:15 years ago: by Em+Ellel · · Score: 1

    Sorry, but I have to correct you. F5 BigIP now runs, and has for quite a while now, RHEL 3. That's GNU/Linux for the avoidance of any doubt - not BSD. Really?? Guess its been a while since I used latest F5 gear. Last I used it it was BSD. Sorry, I stand corrected.

    -Em

    --
    RelevantElephants: A Somatic WebComic...
  27. Doesn't this fork *.everything? by davek · · Score: 3, Insightful

    I still haven't made up my mind on GPLv3, but I was under the impression that it was designed to unite, not to fork.

    If most F/OSS goes GPLv3, and simultaneously Microsoft denies GPLv3 bug still has a vested interest in Novell Linux, won't that just mean that MS will fork every open source project at the point where it switches to GPLv3? They'll create their own faux-communities loyal to the regime and play them off as open source, and the public will eat it up since they don't know any better. Those who believe in F/OSS as a philosophy and accept GPLv3 will be branded pinkos and commies by "commercial friendly" open source, and die a slow death...?

    I sure hope I'm wrong.

    --
    6th Street Radio @ddombrowsky
    1. Re:Doesn't this fork *.everything? by vertinox · · Score: 3, Insightful

      I still haven't made up my mind on GPLv3, but I was under the impression that it was designed to unite, not to fork.

      It was never that intention. GPLv3 was created solely to close the loopholes that many of the companies that were taking advantage of the GPLv2 in order to prevent their customers from gaining access from modifying the source. (aka "tivo-ization") in which vendors would simply deny modification of the source they were to provide by using another developers code under GPLv2 by adding hardware DRM.

      Or in Microsoft's case by means of patents.

      From my understanding there is nothing that compels any developer to upgrade from GPLv2 to GPLv3 unless you desire to use someone else's code that is being upgraded to GPLv3 with code changes (you are still free to hold on to their GPLv2 code without updating)

      And the other main beef that people have is the "and later versions" clause in GPLv3, but you are free to remove that if you want as a developer of your own code (Not so much if you are using someone else's code! But no one is forcing to use other people's work instead of making you own!)

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    2. Re:Doesn't this fork *.everything? by james_pb · · Score: 1

      You vastly underestimate the amount of effort it would take to create those communities. No one has the kind of resources it would take to "fork every open source project at the point where it switches to GPLv3."

    3. Re:Doesn't this fork *.everything? by alexgieg · · Score: 1

      This would solve nothing. The anti-patent clause is already present in GPLv2. As soon as Microsoft itself did any work on any GPLv2 software, and distributed it, it would ipso facto be licensing all patents it own present in that piece of software to all its recipients, as well as to anyone those recipients redistributed the software, and so on and so forth. Failure to do so would forbid it from distributing any GPLv2 software at all, forked or not.

      --
      Conservatism: (n.) love of the existing evils. Liberalism: (n.) desire to substitute new evils for the existing ones.
    4. Re:Doesn't this fork *.everything? by DandyRandy · · Score: 0, Troll

      >>Those who believe in F/OSS as a philosophy and accept GPLv3 will be branded pinkos and commies by "commercial friendly" open source, and die a slow death...?>>
      Don't worry, you are already branded as pinkos and commies! What do you expect if you accept such a bulls**t as GPL3? Which kind of credibility you expect for Mr. Stallman in the eyes of any self-respecting businessman?

    5. Re:Doesn't this fork *.everything? by a.d.trick · · Score: 2, Informative

      Actually, that was one of the intentions, and the GPL 3 is more compatible with other open source licenses. It's incompatibility with itself is an essential part of the license, otherwise it would be like a submarine with a screen door. That's why the FSF recommends you allow re-licensing of the work under later version of the GPL, then compatibility is not a problem.

    6. Re:Doesn't this fork *.everything? by noidentity · · Score: 1

      "I still haven't made up my mind on GPLv3, but I was under the impression that it was designed to unite, not to fork."

      It creates a small fork in the road for authors currently using GPLv2: do they close the loopholes (GPLv3) or preserve them (GPLv2)? Some things can't go forward at all because the authors are too numerous to contact.

    7. Re:Doesn't this fork *.everything? by Anonymous Coward · · Score: 0

      Ummm, microsoft has a hard enough time with its own software. Microsoft is only about 40,000 people total, and not all of them are programmers. The Linux community (at least on SourceForge) is at least 1,638,346 developers. Sure, they are part timers, but its still 41:1. As it is, microsoft has a hard time acquiring new staff. Retention is also a problem. Even if they doubled in size, it wouldn't be enough.

    8. Re:Doesn't this fork *.everything? by I'm+Don+Giovanni · · Score: 1

      GPL3 goes after Tivo and MS for violating the spirit of GPL, by closing certain loopholes, but leaves fully in place the web-app loophole allowing Google to use GPL code in its multi-billion dollare operation, distribute their web-apps for use to the public but not release their own code because they distributed the app as a web-app rather than a local binary.

      Why is Google allowed to violate the spirit of GPL? Google is the biggest violator of GPL spirit in history yet they get a pass?

      --
      -- "I never gave these stories much credence." - HAL 9000
  28. Re:I say by Dog-Cow · · Score: 1

    I've never understood that phrase in relation to some party that isn't liked or is doing bad stuff. Why in the world would you want to have sex with them?

  29. Why is this surprising? by Jamie.Barrows · · Score: 1

    Considering that a lot of the GPLv3 was designed to specifically target the actions of companies like MS, is it so surprising that MS would be avoiding them? Yes I know MS is claiming those sections don't apply to them, but that really hasn't been proven in court yet. For now its still a bit nebulous. I'm not saying that MS is in the right about those sections. All I'm saying is that MS's lawyers think they might be able to convince the courts that they are right. FSF lawyers say it does apply to MS. Until a few court cases settle the issue, it only makes sense for MS to avoid GPLv3 code if at all possible.

    --
    For a list of all the ways technology has failed to improve the quality of life, please press three. -- Alice Kahn
  30. is GPLv3 Successful? by falconwolf · · Score: 1

    So, anyone who was bothered by the MS/Novell deal (and its variants) can and should encourage usage of GPLv3. Coders who want to prevent MS from using patent threats to splinter the community should consider adopting the GPLv3.

    I'm not so sure. One of the things I've heard is that GPLv3 will create hardware vender lockout. Because of clauses in v3 they won't move to v3. It's hard enough the get hardware venders to release drivers for Linux, with v3 they won't period.

    Falcon

    All I know is that I know nothing!
    1. Re:is GPLv3 Successful? by Chandon+Seldon · · Score: 1

      I'm not so sure. One of the things I've heard is that GPLv3 will create hardware vender lockout. Because of clauses in v3 they won't move to v3. It's hard enough the get hardware venders to release drivers for Linux, with v3 they won't period.

      The GPLv3 doesn't actually contain any clauses that would make that response appropriate. The only reason we'd see behavior like that is if they believe the anti-GPLv3 FUD. Companies with software patents may want to avoid distributing GPLv3 code, but that doesn't prevent them from releasing drivers or specs in any way - they can simply license their drivers permissively, with a proprietary license, or with the clever "GPLv2 or later".

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    2. Re:is GPLv3 Successful? by init100 · · Score: 1

      One of the things I've heard is that GPLv3 will create hardware vender lockout. Because of clauses in v3 they won't move to v3. It's hard enough the get hardware venders to release drivers for Linux, with v3 they won't period.

      That's funny, since the kernel will stay GPLv2 for the foreseeable future, and hardware drivers are usually in the kernel, so why would drivers be affected by the GPLv3?

  31. Ignore it at your peril by asphaltjesus · · Score: 1

    The point is they will be using their bully pulpit to sodomize the Linux market by conveniently ignoring whatever rule of law applies in this situation.

    They will change tactics when ignoring the rule of law as they see fit is no longer tolerated.

    --
    Got Trader Joe's? friendwich.com RSS feeds work now!
    1. Re:Ignore it at your peril by thethibs · · Score: 1

      I wonder what comic book adventure that came from.

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
  32. Linspire Deal with the devil by obergfellja · · Score: 0

    I vaguely remember something about Microsoft suing Lindows (currently Linspire) for name infringement. Now M$FT (The Devil) wants to metaphorically "make a deal with the devil" so to speak with Linspire? this just doesn't feel right at all.

  33. re: SuperEULA by macraig · · Score: 1

    Somebody's been playing a bit too much Nuclear War. I don't think I have that card in my decks....

  34. copyright and license by falconwolf · · Score: 1

    Why would I want to contribute code to be used in someone elses proprietary walled garden... where one day I might be required to pay a license covering the code I wrote and contributed.

    Legally if you write code for yourself you own the copyright. Nobody can force you to pay a license fee to use that code unless you sell the rights to the code. Now you might of noticed I said "write code for yourself". That's important because if you write the code on someone else's (the owner's of that walled garden) dime, it's work for hire, then whoever hired you owns the code unless otherwise specifically stated in a contract.

    Falcon
    1. Re:copyright and license by vux984 · · Score: 1

      Legally if you write code for yourself you own the copyright. Nobody can force you to pay a license fee to use that code unless you sell the rights to the code.

      Technically, but in practice they can effectively accomplish it:

      Suppose you release a project under, say, a BSD license and someone modifies it - fixes a couple bugs, adds couple features, etc.

      Its true they can't force you to pay for your unaltered original code, but they can charge as much as they want for the 'improved' code... even if its 99.99% your original work, and if you want to use the improved code you'll have to pay.

      And you might not even be able to take your original unaltered code and reinvent the fixes and features they added if they've patented them.

    2. Re:copyright and license by falconwolf · · Score: 1

      Its true they can't force you to pay for your unaltered original code, but they can charge as much as they want for the 'improved' code... even if its 99.99% your original work, and if you want to use the improved code you'll have to pay.

      You're paying for the improvements, what was added by the others, for which they own the copyrights. They can not however prevent you from using your own code, nor can they make you pay for it. At least not legally.

      And you might not even be able to take your original unaltered code and reinvent the fixes and features they added if they've patented them.

      This is one of the reasons I oppose patents on copyrights. Copyrights are alright but not patents. If a person comes up with another way of doing the same thing they shoudn't be barred from selling or using it period.

      Falcon
    3. Re:copyright and license by vux984 · · Score: 1

      You're paying for the improvements, what was added by the others, for which they own the copyrights.

      In theory, maybe. If I give you a car for free, you repaint it, and change the tires and then offer to sell it for $15,000, you aren't charging for the improvements, you are selling the car for what its 'worth'. And that's fine.

      Except, really, what is the point of me giving you cars for nothing if this is what you do with them? What's in it for me? I contribute to the GPL, because I know that any improvements made will be usable by me and anyone else.

      What's in it for ME to release under a 'free' license that doesn't provide any benefit back to me?

      I don't support the GPL because I'm a communist hippie who wants to make the world a better place. I support it because its a good value proposition to ME. I have access to piles of code for free. I can modify it to make it do what I need. And If I contribute code, I know that I will have access to further improvements other people make.

      What do I get from a 'BSD' style license? Squat. Code that's already out there under BSD I can use, modify and sell, and potentially make a few bucks that way... and that's obviously a benefit to ME, and I can see why companies like that system. However, how many of those companies that TAKE from that code pool put anything into it? They don't HAVE to, and they don't necessarily get anything back if they do... and thus very few of them do.

      The only mystery is where BSD code is coming from in the first place? Who are the 'altruistic hippies' who keep contributing to it without getting anything back? Lets see... University projects mostly. And for demo/sample code.

      Universities? no surprise there, they should be used to being mined for anything valuable by corporations by now. And as for demo/sample code -- again the BSD license actually makes sense - the authors of that stuff explicitly just want people to be able to use the code, and don't want/need/expect anything back for it. Its teaching material, etc. Although, just sticking it in the public domain would be pretty nearly as good for that sort of code.

      Copyrights are alright but not patents.

      Which is partly why the GPLv3 is so hostile to patents. Patents can be used to effectively deny users the very rights the GPL purports to give. So its only common sense that the GPL contain provisions to ensure patents cannot be used in this way.

    4. Re:copyright and license by falconwolf · · Score: 1

      I don't support the GPL because I'm a communist hippie who wants to make the world a better place. I support it because its a good value proposition to ME.

      Fine, if you're satisfied then go for it.

      What do I get from a 'BSD' style license? Squat. Code that's already out there under BSD I can use, modify and sell, and potentially make a few bucks that way... and that's obviously a benefit to ME

      As you said after you said "squat" you do get something out of BSD code.

      However, how many of those companies that TAKE from that code pool put anything into it? They don't HAVE to, and they don't necessarily get anything back if they do... and thus very few of them do.

      And why should they HAVE TO return any code back?

      just sticking it in the public domain would be pretty nearly as good for that sort of code.

      Not if you want to eat.

      Copyrights are alright but not patents.

      Which is partly why the GPLv3 is so hostile to patents. Patents can be used to effectively deny users the very rights the GPL purports to give. So its only common sense that the GPL contain provisions to ensure patents cannot be used in this way.

      I don't have a problem with patent protection, which shoudn't be needed!!!

      Falcon
    5. Re:copyright and license by vux984 · · Score: 1

      As you said after you said "squat" you do get something out of BSD code.

      No. I get SQUAT from releasing any BSD code.
      I get something from other peoples BSD code -- but then THEY get SQUAT.
      In other words a party releasing BSD code gets SQUAT.

      just sticking it in the public domain would be pretty nearly as good for that sort of code.
      Not if you want to eat.

      How do you figure. If I release something into the public domain I can still charge for copies of it. I can't prevent someone else from giving copies away for free... but then that's true of the BSD too. (And the GPL for that matter.)

      I don't have a problem with patent protection, which shoudn't be needed!!!

      I don't have a problem with patents either, but I agree with the FSF that releasing something under the GPL and then threatening to sue anyone who uses that code, which under the GPL they have express permission to use and modify is utterly ridiculous. And I agree that the GPL should be hostile to attempts to restrict the rights granted by that code via patents or any other technique.

  35. Key word: *community* by Tony · · Score: 1

    I believe that is what Microsoft will try to do. But, they aren't going to spend a lot of time or money on it, because open-source and free software isn't important to Microsoft. I don't believe they even really care.

    It's all about marketing. Microsoft is successful only to the extent they can control the market. Market dominance and market control are one and the same to Microsoft.

    Controlling the market is two parts controlling the distribution chain, and one part controlling public opinion. Microsoft's Linux deals are about controlling Linux vendors (Linspire, Novell), and also controlling public opinion ("GPLv3 is illegal, because of the 'No Lawsuit' provisions. No, this isn't like the 'no lawsuit' provisions in our EULA at all.").

    Microsoft has no interest in building a free software community, and even if they did, I don't think they have the resources. Most of their third-party developers don't care about community; they only care about selling products. There's nothing wrong with that, but not the stuff for building a community.

    --
    Microsoft is to software what Budweiser is to beer.
    1. Re:Key word: *community* by thethibs · · Score: 1

      You forgot the "Nya Ha Ha Ha Ha!"

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
    2. Re:Key word: *community* by petrus4 · · Score: 1

      Can I ask...
      What is your own definition of the word community?

  36. GPL v3 by falconwolf · · Score: 1

    both Sun and IBM appear to have learned the lessons of fractured markets and IP warfare.

    True, but I see GPL v3 as a treat to more fracturing.

    It creates many more losers than winners, and it damages the market as a whole

    Yeap, GPL v3 certainly does that. Remember the GPL is meant for the freedom of the user not the freedom of the developer. And with Linux having literally thousands of contributors each one of them would have to approve the move to v3. I seriously doubt that will happen, so either Linux stays v2 or it forks with people needing to write code to replace the code the programmers who refuses to move to v3 wrote. I am afraid v3 will damage the GNU movement specifically and the FOSS movement generally.

    Falcon
    1. Re:GPL v3 by twistedcubic · · Score: 1


      Remember the GPL is meant for the freedom of the user not the freedom of the developer.

      This is not true. Users are free to use GPL code in any way they want (except distribute). The GPL is ALL ABOUT the developers! It prevents authors of code from being ripped off. Anyway, the "freedom" you talk about really refers to the code; i.e., the code cannot be "enslaved" (excuse the extreme choice of word).

  37. 3 problems: Samba, GNU Coreutils and Tar. by strredwolf · · Score: 5, Insightful

    Don't they know that coreutils and tar form a good chunk of any Linux distribution? And Samba's used to talk to MS Windows?

    Don't they know that those packages are GPL v3?

    In other words, Microsoft ether has to rewrite those packages themselves, break the distro into an unusuable state, or drop any Linux deals.

    Or give up on the patent saber rattling.

    --

    --
    # Canmephians for a better Linux Kernel
    $Stalag99{"URL"}="http://stalag99.net";
    1. Re:3 problems: Samba, GNU Coreutils and Tar. by Shados · · Score: 1

      Or use outdated or forked versions of the last version of the software under GPL2, which in these cases, as of today, is probably 99.9% alike to the GPL3 version, hmm? Of course, that won't last though...

    2. Re:3 problems: Samba, GNU Coreutils and Tar. by sensei+moreh · · Score: 1

      I ask this out of ignorance - how difficult would it be for Novell (or even Microsoft) to maintain (by which I mean security updates only), say, for a couple of years, forks of the last GPLv2 versions of Samba, the GNU coreutils, and tar?

      --
      Geology - it's not rocket science; it's rock science
    3. Re:3 problems: Samba, GNU Coreutils and Tar. by domatic · · Score: 1

      If it is just security updates then I don't see Novell having any harder a time of it than say the maintainers of Debian Stable. They essentially do this with their Enterprise releases anyway. Novell can indeed maintain a GPLv2 status quo for a couple of years if they desire. The problem for them is that significant development will occur on desirable GPLv3 codebases like the packages you mention. Customers will want those features and at that point we aren't talking "maintaining" anymore. We are talking "forking". A feature parity fork of Samba alone would Novell big bucks two years down the line.

  38. Great! by Wooky_linuxer · · Score: 1

    Concise explanation. Why do some people find it so difficult to see that no one is forced to use whichever GPL version they are talking about? Don't agree with GPLv3, fine,stick with v2, use BSD or another license. Heck, write your own. The GPL exists to provide the user these freedoms. Not everyone will agree with that. But as we begin to see more and more GPL software encased inside hardware where it can't be effectively modified by the end user, more and more shady patent agreements like Novell's, perhaps more FOSS developers will understand why GPLv3 came into being and adopt it.

    --
    Where is that guy who'd die defending what I had to say when I need him?
  39. We win by nexxu · · Score: 1

    I don`t think all this is over but it looks like we`ve won... -- $ /usr/bin/fortune

  40. Microsoft does not have enough money for that. by Shirotae · · Score: 2, Interesting

    won't that just mean that MS will fork every open source project

    Microsoft may be very rich but they do not have enough income to hire enough developers to fork every open source project.

    Customers and stockholders would be very angry if MSFT diverted a large part of their current staff to forking open source projects. They can't just pull the open source work into their existing teams because of the possibility of contamination of their precious source code assets with some Open Source or - horror! GPLv2 - licensed code.

    MSFT forking the code would mean them hiring a whole lot more developers of the required skill level and as far as I know there is not currently a large pool of sufficiently skilled unemployed developers. Hiring enough to even make a start is going to be significant expenditure for no extra income and that means taking a substantial hit in profits. Financial analysts and stockholders are not going to be happy with that and if they start to sell the share price goes down and we see just how much of MSFT's money is real and how much is just a high P/E ratio that could collapse frighteningly fast if investors lose confidence.

    MSFT's best bet is to try to cause divisions between different groups of open source developers but I think that the problem there is that whatever license they prefer, open source developers tend to have respect for technical contribution and contempt for the marketing bullshit and 'business' dirty tricks that are MSFT's stock in trade. Heated public arguments over the merits of different licenses are not a sign of the community fragmenting, they are a sign that the open source community does its thing in the open and collectively comes up with a set of variants that can satisfy everyone and an understanding of how to work together.

    What we all need to do is to keep shining a light into the corners where MSFT is trying to play its dirty tricks - like the ballot stuffing in the standards committees - so that they are seen for what they are. The advantages of open source speak for themselves, even to businessmen, if we make sure that the real facts are available.

    1. Re:Microsoft does not have enough money for that. by davek · · Score: 1

      You're right, the scope of open source is simply too large for MS to create their own. However, I do fear that they will hijack open source this way. In other words, create hip and cool hacker communities with no obvious connection to MS, install project managers on the MS payroll, and use them as puppet governments to control masses of honest developers who believe they are working on a free (as in freedom) project. I believe we've already seen this with some commercial semi-open software (Skype comes to mind...).

      Taking it a step further, many people might say, "Great! If the source code is open, and I can copy it to my heart's content, then its a win no matter who controls the copyright!" Here lies the dragon: inevitably, some of the more functional code will get copied into some true F/OSS projects, leaving the door open for MS to make good on their patent enforcement promises.

      itsatrap?

      --
      6th Street Radio @ddombrowsky
  41. Re:I say by XoloX · · Score: 1

    I think originally it implied forced penetration: rape (irrespective of gender). That should explain its offensiveness.

  42. shenanigans by oliphaunt · · Score: 1

    Or, when you put conflicting statements in front of anyone but a bunch of lawyers, everyone else will call shenanigans and point out you were full of crap from the get go?

    That's kind of the point that I was going for. This tactic might work on paper in a courtroom, but not in the real world- the correct response in the realm of PR should be to attack Microsoft for failing to take a consistent position.

    Imagine if Giuliani was asked for his position on abortion, and he said "1. I believe abortion should be legal and provided on-demand to anyone who requests it, and 2. Roe v. Wade must be overturned because abortion is murder." Sure, Tim Russert would just continue with his blowjob, but everyone else would flip out, becuase half of that statement MUST be a lie, but it's impossible to know which half.

    I know of two main reasons to do things this way- the first one is efficiency. This style of pleading encourages both parties to put everything they have on the table right at the start, so that both sides know what the fight is really about. Imagine if MS does land in court over some infringement- they get sued for GPL3 violation, and they use only one of these excuses as a defense. The trial goes on for 5 years, and at the end of it, MS loses, and then they trot out the OTHER defense... new trial, 5 more years of bullshit in the courts... So it's more efficient for the courts to force the parties to do it all at once.

    The other argument is discovery. US federal courts have liberal discovery rules, but you can only ask for stuff that's related to your case. So if you have multiple theories, you can potentially discover more evidence than you would if you only had the one theory. When "evidence" is defined as "corporate email discussing how to discriminate against employees, destroy competitors, and violate license agreements," more is generally better.

    I think the reason it works in law is that it has become accepted legal shorthand to leave out the "if... elseif" part of the argument, and before the case gets to the point where you're going in front of a jury, you usually collapsed the arguments and settled down to one internally consistent theory. It would be disaster if you were on trial for murder, and your defense was "1. I wasn't actually there: here's a witness who saw me somewhere else, but if you don't believe that then 2. I shot him in self defense." Just becuase it's an acceptable formal logical contstruct doesn't mean that you wouldn't suffer because the jury evaluates your statement on a moral basis, and punish you for what they can't help but percieve as a lie.

    Obviously this creates problems when the legalese so permeates a company's business that it starts leaking out around the edges. People are naturally repelled when you lie to them, and this kind of statement is the worst sort of PR because its necessary partial falsehood taints the entire message.

    --




    Humpty Dumpty was pushed.
  43. Code is free as long as people may use it by skandalfo · · Score: 2, Insightful

    What's "free code" (I reckon you prefer "open code", but GPL is about "free") if people does not have the freedom to use it?

    The two things that made most noise about GPL 3 were its stance agaist patents, and its requirements against effective tivoization.

    I feel lucky that software patents seem unenforceable still here in the EU. The intent of the GPL 3 in this respect is clearly to avoid a (re)distributor from applying a layer of selective patent licenses on the receiving users. Many of us would like to ban software patents globally, as they actually can strangle independent innovation and be the means that incumbents may use in order to squash any competition, in this case in the software field. A third party (a non-user and non-distributor) could try to enforce software patents against GPL 3'd software users; GPL 3 cannot project its software-freeing agenda here, since the license does not bind a third party that does not use or (re)distribute the software. So, in the end, the behave-well-with-patents enforcement is done on the only ones the license applies to (users and redistributors), which is as far as the license may take this part of the FSF political agenda. This is, BTW, part with which I happen to agree fully.

    I recognize the aspect about anti-tivoization to be a more difficult point because, unlike the former one, transcends out of the software world into the hardware one. In the TiVo case you get the code... and you would be able to use it if you were able to replicate the hardware that it's intended to run on minus the selective restrictions on the software it can run.

    The case of TiVo may seem a petty one, as in this case the restriction on the software isn't placed on individuals on an arbitrary basis. "It's their hardware; let them do what they want with it." That's what people that doesn't like this aspect of the GPL 3 say. Ok; maybe you cannot replicate their hardware, and you lose some little bit of code thats GPL'd but actually unusable because there's no free hardware to use it on.

    But if Microsoft is able to take along its agenda about "Trusted Computing", in which each computer available to customers would be required to enable hardware-based DRM on software (no TPM, no Windows, that's what the computer vendors would hear), then they would in fact be able to control ANY code that could be used in the hardware that's readily available to customers. And that would be very similar to a new layer of selective licensing that could be used against any user of any software, free or not.

    So, even if you may be in the "free software is ok; free hardware is not really needed" camp, you may recognize that free software may be successfully reduced to insignificance if no free hardware (or "open hardware", at least) is available in order to run it. Although I don't really mind proprietary hardware to enforce restrictions on the software it may run (I simply don't buy the hardware), the possibility of ending up with no unrestricted hardware if we do nothing about it, actually makes me fully support the anti-tivoisation clause.

    So, paraphrasing the famous poem:

    • First, they came to secure their game consoles, so that no one would run unlicensed software on them.
    • I did not worry, because I didn't use game consoles, nor wrote software for them.
    • Then, they came over the TiVo, so that the broadcasters could have their contents controlled.
    • I didn't say anything, since I had my MythTV.
    • Then, they came to oversee home optical media, so that no one could copy those contents, or even skip the commercials at the beginning.
    • I did not mind about it, since I used free players on my computer systems.
    • Then, they came with Trusted Computing, saying they would patch in hardware the gaping holes in their software.
    • Then, as time passed, my computers died one after another of natural death, and I was no longer able to find any new computer to run my software.
  44. Free Software != Open Source by goldspider · · Score: 1

    But as we all know, Free Software is not the same as Open Source.

    --
    "Ask not what your country can do for you." --John F. Kennedy
  45. Zune by alexgieg · · Score: 1

    Microsoft isn't a party to the GPLv3 license and none of its actions are to be misinterpreted as accepting status as a contracting party of GPLv3 or assuming any legal obligations under such license
    Then I urge Microsoft to change the Zune firmware so that no GPLv3-licensed MP3 file is edited by the device when sending it over WiFi, or at least a provision explicitly prohibiting users from sending those. A Zune-modified MP3 is, AFAIK, a derivative work, and as such any change made by Microsoft to it "carries over" into the receiving Zune the requirement for fully licensing the DRM technology used to lock it down, as well as any and all related patents.

    It would be a good idea to also block or forbid transmission of GPLv2 MP3. Although GPLv2 doesn't have the anti-DRM clause, it does indeed have the patent-licensing one. If Microsoft doesn't agree with such licensing, it must cease and desist, effective always, from distributing said GPLv2 music.
    --
    Conservatism: (n.) love of the existing evils. Liberalism: (n.) desire to substitute new evils for the existing ones.
    1. Re:Zune by Anonymous Coward · · Score: 0

      You're an idiot. If someone uses a window's box to violate a license, the user is the violator not Microsoft. Same thing with zune. What a bunch of zealot fools... I used to equate FOSS users with intelligence, but like any great philosophy, the morons have signed up and are turning it into something less.

    2. Re:Zune by Farmer+Tim · · Score: 1

      A Zune-modified MP3 is, AFAIK, a derivative work

      Wrong. It's the same work in a different wrapper. If your theory was correct, iTMS (or in fact anyone) could avoid the need to license music from recording companies just by adding DRM. Obviously this isn't how it works.

      In order to be a "derivative work" as defined by copyright legislation, the nature of the original work must be changed substantially (more than MC Hammer changed Rick James' "Superfreak" for "Can't Touch This", if you want a real world example). Adding DRM does not remix, change lyrics, tempo or melody, all it does is limit what exactly the same song can be played on.

      In order to avoid future confusion, just remember: "The song is the work, the format is irrelevant".

      If Microsoft doesn't agree with such licensing, it must cease and desist, effective always, from distributing said GPLv2 music.

      The user transferring music via a Zune is technically the distributor, not Microsoft. When you consider that (DRM excepted) the Zune is essentially a hardware file-sharing device, what you're asking is exactly the same as insisting that BitTorrent's developers take responsibility for making sure that no licenses are violated...you do see the problem with that, I hope.

      --
      Blank until /. makes another boneheaded UI decision.
    3. Re:Zune by alexgieg · · Score: 1

      Wrong. It's the same work in a different wrapper. If your theory was correct, iTMS (or in fact anyone) could avoid the need to license music from recording companies just by adding DRM. Obviously this isn't how it works.

      In order to be a "derivative work" as defined by copyright legislation, the nature of the original work must be changed substantially (more than MC Hammer changed Rick James' "Superfreak" for "Can't Touch This", if you want a real world example). Adding DRM does not remix, change lyrics, tempo or melody, all it does is limit what exactly the same song can be played on.
      IANAL, but if what you're saying is correct, then the whole section 6 of GPLv3 (a.k.a. "the anti-tivoization clause") is for all practical purposes void and null, because I would be able to workaround it by, say, asking a 3rd party to add DRM "features" to it, build it in a non-DRMed machine, distribute the new version for all the world to download, then take this pre-built version myself, CRC and SHA-1 it, put it into a machine who will only run a Samba with such a CRC and SHA-1, and sell said machine. This, I'm glad to say, isn't the way it works. If you read section 6 you'll notice that no, DRM-wrapping a GPLv3 component in this way isn't allowed and voids your right to distribute it.

      By the way, causing a GPLv3 work which is explicitly intended (by the fact of it being a GPLv3 music!) to be used (played) in any place, way or form to not be usable (played) in any place, way or form is, IMHO, an extreme change in the nature of said work. iTMS can change the musics it carries because the copyright owner explicitly allowed iTMS to do so. If a GPLv3 music's author don't allow its copyrighted work to be DRM'ed (by the fact of having GPLv3'ed it!), then no one can do so without breaking his copyright. What he does allow (by the fact of having GPLv3'ed it!) is for the music to be changed so long as it's not DRM'ed. What he does not allow (per section 6) is for it to be DRM'ed without the DRM'er providing his recipient with the tools or with the complete information needed for him, the recipient, to un-DRM'ing it.

      The user transferring music via a Zune is technically the distributor, not Microsoft. When you consider that (DRM excepted) the Zune is essentially a hardware file-sharing device, what you're asking is exactly the same as insisting that BitTorrent's developers take responsibility for making sure that no licenses are violated...you do see the problem with that, I hope.
      The user asked for the file 'haha.mp3' to be sent. Microsoft itself, by automated means, decided to not send the file 'haha.mp3' as is, but to edit it, "compiling" a new into 'haha.drm', and sending this 'haha.drm' itself instead of the file the user asked it to send. Thus, Microsoft is already acting as censor, and must comply with everything the law says about it. Where the Zune to work as a dumb passive means of data transfer, which is what a BitTorrent softwares (and sites!) do, and you might argue it weren't responsible for what the user (the active party) is doing. If the user sent copyrighted work, it would be his wrong, not Zune's. But the moment the Zune steps inside to force copyright-compliance on users, by not letting them freely share as they do with any normal WiFi device out there, then it must do this right, or it will be responsible for any copyright violation, not the user. And what is the DRM'ing of a non-DRM'able GPLv3 music other than copyright violation by the party responsible, namely Microsoft?

      I might be completely wrong on this, I admit. But to be completely sure I think we (and Microsoft) should check this with a lawyer specialized on both GPLv3 as well as copyright law applied to music. Anyone reading this who can solve the matter?
      --
      Conservatism: (n.) love of the existing evils. Liberalism: (n.) desire to substitute new evils for the existing ones.
    4. Re:Zune by alexgieg · · Score: 1

      You're an idiot.
      And you're an AC, thus you lose and I win! :D

      If someone uses a window's box to violate a license, the user is the violator not Microsoft.
      Yes, but the Zune is the opposite. It's designed to both forbid and protect the users (both the sender and the receiver) from violating a license. It's blessed by the main content producers as a tool that, no matter how a user uses it, won't make neither the sender nor the receiver a copyright violator. Thus, it's the active party in the non-violating behavior, and as such, is also the responsible for when the violation happens. IMHO, of course.
      --
      Conservatism: (n.) love of the existing evils. Liberalism: (n.) desire to substitute new evils for the existing ones.
    5. Re:Zune by VGPowerlord · · Score: 1
      IANAL

      Then I urge Microsoft to change the Zune firmware so that no GPLv3-licensed MP3 file is edited by the device when sending it over WiFi, or at least a provision explicitly prohibiting users from sending those.

      I wasn't aware that data files could be protected under the GPLv3, due to the restriction of having to distribute the original source. Given the GPL definition of source code ("the preferred form of the work for making modifications to it."), I'm fairly sure that would be uncompressed audio ripped from the CD.

      It's a moot point, though. If you are not the copyright owner or someone authorized by the copyright owner to make copies, you don't have the right to distribute it, making any license you attempt to apply to it invalid.
      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    6. Re:Zune by Farmer+Tim · · Score: 1

      if what you're saying is correct, then the whole section 6 of GPLv3 (a.k.a. "the anti-tivoization clause") is for all practical purposes void and null...

      You're still failing to make the distinction between the "work" and the "format". It's similar to the difference between "source" and "binary". The compiled binaries on different platforms are completely different, but the rights are still owned by the person who owns the source code; that is because the source is the "work", the binary is the "format" that embodies the work (that's not entirely accurate, but it'll do).

      If you take GPLv3 code (the work) and modify it's functionality to include DRM you have created a derivative work because you have substantially changed the nature of the work, and this is indeed a violation of the terms of the GPLv3.

      However, as I pointed out, adding DRM to an MP3 does not change the nature of the work embodied in the MP3. The song itself (the source) remains the same, only the format (the binary) has changed, so unlike your modified GPLv3 code example it doesn't meet the established legal definition of "derivative work". The sequence of notes and lyrics that reaches your ears has not been changed by DRM (regardless of audio quality or other technical concerns), and that is what copyright covers (copyright also applies to sheet music, BTW; it's the same information, notes and words, in another format).

      Another analogy: I write you a letter, which you then OCR and encrypt without changing. I still own the rights precisely because you haven't changed the content; it is not a derivative work, because the information contained in the letter is the same as the original. Encryption (=DRM) and OCR (=format shifting) does not change the content, only who can access it and how. See how content=content and format=format, but content!=format?

      The user asked for the file 'haha.mp3' to be sent. Microsoft itself, by automated means, decided to not send the file 'haha.mp3' as is, but to edit it, "compiling" a new into 'haha.drm', and sending this 'haha.drm' itself instead of the file the user asked it to send.

      Which is irrelevant: the "work" in this case is "haha" by $artist, the .mp3 or .drm is merely the wrapper that contains the work, and that's the critical difference. Unless you substantially change the nature of "haha", regardless of whether it's encoded as mp3, .drm, PCM or a groove on a disc, it isn't derivative, it's the same work; it is not "edited" in any way, only the wrapper has been changed.

      That's the point you're not grasping here: it doesn't matter what format you shift a work to, unless you're significantly changing the nature of the work (ie: lyrics, tempo, melody for music, function for software) it is still the same work; for example, the GPL applies to source (content), even though the final binaries are completely different on Linux and Windows (format). That is how copyright works, and there's a wealth of jurisprudence behind this interpretation (I even provided an actual example, but if a real court finding isn't enough to convince you you're wrong I don't see any way I can succeed).

      But the moment the Zune steps inside to force copyright-compliance on users, by not letting them freely share as they do with any normal WiFi device out there, then it must do this right, or it will be responsible for any copyright violation, not the user.

      This is merely your opinion of how things should work, not an example of your understanding of how they do work.

      Video DVDs attempt to force copyright compliance on users, but are DVD manufacturers liable for end users defeating the DRM? No, the DMCA clearly and unambiguously states otherwise, and copyright still applies regardless of DRM considerations; so what you're saying is entirely contrary to the relevant laws.

      But please, google for any court finding stating that adding DRM shifts the liability for copyr

      --
      Blank until /. makes another boneheaded UI decision.
  46. The GPL is ALL ABOUT the developers! by falconwolf · · Score: 1

    No it isn't. If I write a killer app and release it under GPL I can't prevent someone else from taking it and selling it without me making a dime. Sure I could sell it but so could anyone else and I couldn't stop them from giving it away either. I'm hoping to break into phototgraphy and want to create a photography suite so the business will run smoother than otherwise. If I'm going to spend much tyme and effort into programming it I'd like to be able to sell it to other photographers and not be concerned others could sell or give it away too. Some have said what I could do is sale service and support, but remember I said I wanted to be a photographer, I don't want to be a service and support person.

    Falcon
    1. Re:The GPL is ALL ABOUT the developers! by twistedcubic · · Score: 1


      No it isn't. If I write a killer app and release it under GPL I can't prevent someone else from taking it and selling it without me making a dime. Sure I could sell it but so could anyone else and I couldn't stop them from giving it away either.

      Your argument is strange. Why release something under the GPL if you don't want others to sell it? This requires a non-free license, doesn't it?

      But anyway, if someone else sells your GPL code for a profit, you can sell it too, and include their enhancements. And if someone gives your GPL code away for free, you can do that too, but well, you already did. And if someone is selling it for a profit, and another is giving it away for free, the person selling it for a profit won't be making much profit unless they add value, like support, because otherwise customers could just get it for free. What do you lose, as a developer, in these scenarios which you bring up?

    2. Re:The GPL is ALL ABOUT the developers! by I!heartU · · Score: 2, Insightful

      It sounds like you don't want to use the GPL for that project then.

    3. Re:The GPL is ALL ABOUT the developers! by falconwolf · · Score: 1

      What do you lose, as a developer, in these scenarios which you bring up?

      Whatever I want such as prevent others from making copies and selling the copies themself without paying me royalities.

      Falcon
    4. Re:The GPL is ALL ABOUT the developers! by falconwolf · · Score: 1

      It sounds like you don't want to use the GPL for that project then.

      And I wouldn't. I'd use a BSD type license or maybe the Apache license, I'd have to read it first though as I don't really know about it.

      Falcon
  47. Yes! by Anonymous Coward · · Score: 0

    YES!!

  48. clout by falconwolf · · Score: 1

    Microsoft will never sue - they know that the only thing they can do is amke noises. Actually suing would be the equivalent of a first strike in a MAD - Mutually Assured Destruction - scenario, which they would ultimately lose.

    Well, does Red Hat have the clout to bring the big boys to their side? You see, MAD only works when both sides have an arsenal.

    It's not just Redhat, there's IBM and a number of others as well. And IBM has a big patent portfolio.

    Falcon
  49. Sure they are by g2devi · · Score: 1

    Of course they're an open source company. They just don't advertise that they ship GLPv2 software:
    http://en.wikipedia.org/wiki/Interix

    1. Re:Sure they are by Vintermann · · Score: 1

      Correct me if I am wrong on any points:
      * GCC is a full GNU project,
      * which means that all contributors sign over copyright to the FSF.
      * In any case, GCC has the "or any later version" clause.
      * It's a fair bet that GCC will switch to GPL v3 pretty quickly, if they haven't already (at the very worst, they'll lose some developers).
      * So, no new versions of GCC for Microsoft, if they want to have newer versions, they'll have to write them themselves from now...

      --
      xkcd is not in the sudoers file. This incident will be reported.
  50. My thoughts by PhotoGuy · · Score: 1

    I'm against GPLV3 as well (sure plug the Tivo hole, but leave my web services alone! A good hearted open source geek needs to make a living.)

    Anyhow, at first I thought Microsoft move's a good thing. But then again, microsoft is evil, so if they oppose GVLV3, then *it* must be a good thing. But I'm against it. But I don't like Microsoft.... Ahhrhhrhrhrrhghh... *HEAD EXPLODES*...

    --
    Love many, trust a few, do harm to none.
    1. Re:My thoughts by Anonymous Coward · · Score: 0

      There is no web services clause in the FSF published GPLv3, the web services stuff is going into the next version of the Affero GPL - a completely separate license.

      We're all for share and share alike ourselves, the problems we saw with the web services stuff were security related. I'm not talking about our code, I'm talking about every kid with a PHP hosting account and a copy of notepad. **shudder**

    2. Re:My thoughts by Chandon+Seldon · · Score: 1

      I'm against GPLV3 as well (sure plug the Tivo hole, but leave my web services alone! A good hearted open source geek needs to make a living.)

      Have you actually read GPLv3? It doesn't have a web services clause in it. They split that out into a completely separate license.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
  51. Re:15 years ago: by FreakinSyco · · Score: 3, Funny

    All of this gardening lingo has me lost. Can I get this in terms of cars?

  52. Re:15 years ago: by h4ck7h3p14n37 · · Score: 4, Insightful

    I agree with you that a BSD license is superior to a GPL license if you're looking to build a business around the software. So why are so many companies using GPL licensed code? Why are Microsoft and Novell trying to make money from a Linux distribution when they could have selected a BSD distribution instead?

  53. Re:M$ sucks!!!11! by Evangelion · · Score: 1

    You are my new best friend. Thank you.

  54. Hey Microsoft, let's get something right... by Anonymous Coward · · Score: 0

    Microsoft Excludes GPLv3 From Linspire Deal

    In capitalist America, GPLv3 excludes you!

  55. Re:15 years ago: by Anonymous Coward · · Score: 0

    "Yep thats pretty much explains why BSD is the product of choice over Linux in many of the above cases. 15 years later BSD made it into mainstream products from large manufacturers (F5, OS/X and iPhone, etc)"

    So where can I download Mac OS X source code?

    Oh, they made it non-free

    so how is that an advantage for the free software community?

  56. Re:15 years ago: by SpaceLifeForm · · Score: 1

    Because Microsoft is not really trying to make money
    off of a Linux distribution, they are trying to kill
    GNU/Linux. Novell got suckered via quick cash.

    --
    You are being MICROattacked, from various angles, in a SOFT manner.
  57. Re:15 years ago: by ksd1337 · · Score: 1

    Other licenses allow you to take code improve it, and then redistribute it in proprietary walled gardens that may restrict who can use it. Nah... It isn't a garden, its more like a castle with copyright lawyers guarding it.
  58. I'm not sure ... by Anonymous Coward · · Score: 0

    ... Microsoft is able to successfully manage a large software development project. Look at Vista. MS is really more of a marketing company.

  59. Does GPLv2 attempt to control software design? by Anonymous Coward · · Score: 1, Insightful

    GPL 3 reaches past this (some would say overreaches), and controls attempts to control the hardware designs of the user. The GPL 3 is much more focused on the rights of certain users, shifting those rights away from other users and developers.


    The GPL was a radical invention to begin with. From the BSD point of view, even GPLv2 is overreaching. So calling GPLv3 overreaching isn't very convincing.

    Calling it an attempt to control hardware design is fallacious too. If you want to run GPLv3 software in your hardware product, you can design it any way you want so long as you don't take away the user's ability to modify that software and run it on the same hardware.

    That's the same kind of restriction that GPLv2 puts on software, and you don't run around saying that "GPLv2 attempts to control software design".
  60. Killers by Bloater · · Score: 1

    Microsoft has sounded the death knell for Novell/SuSE and Linspire. As the software moves on, they will have to maintain their own clean-room tree's under GPLv2 in order to both continue doing business and to satisfy their contracts with Microsoft. The problem is Novell and SuSE have been extremely good for the Linux using/developing community and I think Microsoft did it deliberately. With a few simple contract deals, Microsoft has significantly dented the appeal of Linux. While that hasn't really been popularly accepted yet due to the euphoria of the GPLv3 attack against Microsoft the economic after-effects will start to trickle through in the next couple of years.

    1. Re:Killers by MichaelSmith · · Score: 1

      Microsoft has sounded the death knell for Novell/SuSE and Linspire. As the software moves on, they will have to maintain their own clean-room tree's under GPLv2 in order to both continue doing business and to satisfy their contracts with Microsoft.

      Maybe the next step will be for Microsoft to maintain their own GPLv2 Linux distribution, which they will proceed to market to Tivo and other builders of DRM equipped embedded systems.

      With an upgrade path to WinCE, or course.

  61. Re:15 years ago: by geschild · · Score: 4, Insightful

    "Yep thats pretty much explains why BSD is the product of choice over Linux in many of the above cases. 15 years later BSD made it into mainstream products from large manufacturers (F5, OS/X and iPhone, etc) And the companies that try to abuse Linux (Tivo, Cisco) are treated as the enemy by GPLv3. Has GPL been like GPLv3 from the get go, would Tivo or Linksys ever consider using Linux or would those be BSD products?" There, fixed that for ya.
    --
    Karma? What's that again?
  62. Re:15 years ago: by Anonymous Coward · · Score: 0

    Yep thats pretty much explains why BSD is the product of choice over Linux in many of the above cases. While there is some truth in that, the GPL is also the reason why so many companies contribute to Linux and not to BSD.

    And the companies that try Linux (Tivo, Cisco) are treated as the enemy by GPLv3. They are not, in fact, they are welcome to use Linux. They just have to stick to the rules. For Tivo, it means they cannot lock users out of their own hardware.

    Has GPL been like GPLv3 from the get go, would Tivo or Linksys ever consider using Linux or would those be BSD products? Tivo: perhaps not, if they think locking users out is so important to them. But I respect Linus opinion that they should be allowed to do so. But I certainly do not want to support them with my code.

    Linksys: sure, they were a good member of the free software community with their home routers. Nothing they did would be in conflict with the GPLv3. So why not?

  63. Re:15 years ago: by Em+Ellel · · Score: 1

    So where can I download Mac OS X source code?

    Oh, they made it non-free

    so how is that an advantage for the free software community? How about here?

    As for advantage for the free software community a.k.a. developers, I thought this was about USERS and not about DEVELOPERS (free software or otherwise) and And users seem to prefer OS/X to Linux 8 to 1. You want to explain to an average os/x user why it not to their advantage to use it? I think having OS/X is a bigger advantage to users than limiting their choice.

    -Em
    --
    RelevantElephants: A Somatic WebComic...
  64. "coupon expiration date" "works" as counterFUD by anwyn · · Score: 1
    The Microsoft patent claims are FUD. Both sides know that Microsoft will never bring these claims into a court where they could be carefully checked. This allows both sides to say virtually anything and get away with it.

    Microsoft can say its patent claims are valid, without telling anyone precisely what they are.

    On the other hand, Eben Moglen, and Pamala Jones of Groklaw, are free to expound this ridiculous "coupon expiration date + gplv3" counterFUD theory. Any stick is good enough to beat a mad dog with.

    Apparently, the tactic has worked. Because the tactic is aimed at suits, who might be worried about Microsoft's FUD, the counterFUD theory does not have to be sound to work.

    No one has ever come up with some on point case law showing that distributing coupons is the same thing as "distributing software" within the meaning of Title 17 section 106.

    Pure software licenses, like both version of the gpl, lack the power to prohibit anything that is allowed by copyright law with out the permission of the copyright holder. The GPLv3 does not even try. Let us look at the definitions section:

    To propagate a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

    To convey a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

    As you can see, if something is allowed by the applicable copyright law, without permission of the copyright holder, it is not propagating or conveying. Since the gplv3 is basicly a bunch of complicated restrictions on propagating and conveying, the gplv3 does not even try to prohibit such activity. Not that it would do any good if it did try to prohibit such activity.

    The other way to go, is to say, that Microsoft's activity with the coupons is indirect infringement. Indirect infringement is not in the statute, it is judge made law. A recent court decision on a totally unrelated matter seems to block this path.

    In a totally different case, with a totally different fact picture, Capitol Records, Inc., et al., vs Debbie Foster and Amanda Foster, Lee R. West United States District Judge says:

    The Copyright Act does not expressly render anyone liable for infringement committed by another. Metro_Goldwyn-Mayer Studios, Inc. v. Grokster, Ltd.. 545 U.S. 913, (2005). Rather, the doctrine of secondary liability emerged from common law principles. Id. Under those common law principles, one infringes a copyright contributorily by intentionally inducing or encouraging a direct infringement. The elements of a claim for contributory copyright infringement are: (1) direct infringement by third party; (2) knowledge by the defendant that third parties were directly infringing; and (3) substaintial participation by the defendant in infringing activities. See Newborn v. Yahoo!, 391 F. Supp.2d 181, (D.D.C. 2005); see also Newborn v. Yahoo! Inc., 437 F.Supp.2d 1 (D.D.C 2006) (finding defendant was entitled to an award of attorneys' fees after prevailing upon plaintiff's frivolous and objectively unreasonable contributory copyright claim). Merely supplying means to accomplish infringing activity cannot give rise to imposition of liability for contributory copyright infringement. Id.;see also A & M Records, Inc. v. Napster, Inc. 239. F.3d 1004, 1013 (9th Cir. 2001). One infringes a copyright vicariously by profiting from direct infringement while declining to exercise a right to stop or limit it. Grokster, 545 U.S. 913.

    1. Re:"coupon expiration date" "works" as counterFUD by Verte · · Score: 1

      The coupons thing will probably bow to common sense in the end. As much as I'd like MS to be bitten by that, I'm quite sure it will get thrown out in any reasonable court of law. On the other hand, the premise of the deal will probably be enough to bite them hard in court, because any way you look at it they seem to be modifying and distributing GPL code without allowing users to redistribute it, or making subsequent users pay.

      Then again, it's not like common sense prevails often when M$ are involved, so who knows what could happen? :)

      [IANAL]

      --
      We at slashdot are scientists, specialists and kernel hackers. Your FUD will be found out.
  65. Re:15 years ago: by mrchaotica · · Score: 1

    And the companies that try Linux (Tivo, Cisco) are treated as the enemy by GPLv3.

    First of all, what's Cisco's problem with the GPLv3? Second of all, what TiVo did was always wrong. The GPLv3 only gives legal weight to the ethos that existed all along.

    --

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

  66. Re:15 years ago: by mrchaotica · · Score: 2, Insightful

    Well, Microsoft is pathological. But the question remains: if BSD is really so superior, why are so many companies (not just the "big guns" like Novell, Red Hat, and IBM, but also ones like Trolltech, MySQL, etc.) betting the farm on the GPL instead?

    --

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

  67. Re:15 years ago: by Em+Ellel · · Score: 1

    Yep thats pretty much explains why BSD is the product of choice over Linux in many of the above cases. While there is some truth in that, the GPL is also the reason why so many companies contribute to Linux and not to BSD. I think you are 100% right. I have never been against GPL - think it is a powerful tool. I just think v3 has gone a bit too far and I hate being lied to and having my freedoms eroded under the promise of "greater freedom". We get enough of that from the government.

    Tivo: perhaps not, if they think locking users out is so important to them. But I respect Linus opinion that they should be allowed to do so. But I certainly do not want to support them with my code. Tivo has always walked the line on this one. Early on while they officially said they frown on hacking, tivo employees were frequently on forums discussing hacking of tivos. There was little encryption.

    As time went on and they found themselves needing support from the content creation and distribution industry and to survive in the business they have to promise that they are not enabling copyright infringement via their device and while anyone can run anything on their hardware they simply cannot do that. This came to a head in DirectTV deal where they were forced to add encryption to the boot process. Mind you this was a feeble attempt at quashing fears in the industry but without it and DTV deal, tivo would have been out of business long ago. Even today, on the latest and greatest of tivo devices you still have ability to run whatever you want. They don't make it easy, but it is not impossible either.

    Personally, with all this talk about this being good for the users, as a user I would rather have non-hackable tivo than no tivo at all.

    Linksys: sure, they were a good member of the free software community with their home routers. Nothing they did would be in conflict with the GPLv3. So why not?

    Last I checked (and this could be wrong like my F5 info) You still had to do some exploit to get a linksys router to load and run custom code, they do not ship easy instructions or root passwords or anything to get into it, which is against the GPLv3 just like Tivo.

    -Em
    --
    RelevantElephants: A Somatic WebComic...
  68. Re:15 years ago: by Anonymous Coward · · Score: 2, Informative

    Linksys: sure, they were a good member of the free software community with their home routers. Nothing they did would be in conflict with the GPLv3. So why not? Last I checked (and this could be wrong like my F5 info) You still had to do some exploit to get a linksys router to load and run custom code, they do not ship easy instructions or root passwords or anything to get into it, which is against the GPLv3 just like Tivo. I have a Linksys router. They give me complete instructions how to log in and set my own root password. Then, I can upload any firmware I want (like OpenWRT) using their standard firmware update mechanism. Anyway, the GPLv3 does not demand efforts to make it easy, but only disallowes efforts to make it hard or impossible. If flashing the firmware were impossible because they chose to use a ROM instead of flash memory because it is cheaper, that would be ok with GPLv3.
  69. 396-word response to a 1-line Darth Vader quote by Anonymous Coward · · Score: 0

    This must be slashdot.

  70. Hey! by crhylove · · Score: 1

    You forgot chair-throwing!

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
  71. Re:15 years ago: by Em+Ellel · · Score: 1

    And the companies that try Linux (Tivo, Cisco) are treated as the enemy by GPLv3.

    First of all, what's Cisco's problem with the GPLv3? Second of all, what TiVo did was always wrong. The GPLv3 only gives legal weight to the ethos that existed all along.

    I was under impression linksys products required a hack via insecure web form to get into the os to replace it, but apparently thats no longer the case.

    So, what did Tivo do that was ALWAYS wrong?

    -Em

    --
    RelevantElephants: A Somatic WebComic...
  72. proof? by themusicgod1 · · Score: 1

    "But I am :)"

    ...proof? your website seems to be a linkfarm and although you seem to know what you're talking about, I don't see any evidence of this...I'm trying to take you seriously, that's all.

    --
    GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    1. Re:proof? by hawk · · Score: 1

      I'd forgotten that link was still there. I think it's gone now.

      Eventually I'll find time to write the columns again. I made the mistake of using godaddy for hosting. They kept double-billing my credit card, which resulted in the credit card company not processing the second charge. Then they stopped hosting without telling me . . . they're unwilling to restore my data and code unless I commit to a year's hosting with them, which isn't very likely under the circumstances (though an inquiry from the Attorney general is :)

      Godaddy's web farm is quite permissionless . . .

      You can find most (all?) of the old content with the wayback machine. You can probably find my old penn state site there, too (I don't know; haven't tried). Or you could look me up with the Nevada bar's website . . . hmm, you might even find my old iowa state website with the wayback machine . . .

      hawk, jd, phd, esq, etc

  73. Re:Well of course... by Hucko · · Score: 1
    http://www.ubuntu.com/ http://www.debian.org/ http://fedoraproject.org/ http://www.openbsd.org/ But you want one compatible with Windows, but more stable didn't you? Ah! Here it is! http://www.reactos.org/

    Vista is far more secure than Lunix.
    It's only less of a target because it has a smaller userbase...
    --
    Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
  74. GPLv3 excluded to protect Linspire, not Microsoft by anwyn · · Score: 1

    The expiration date on the grandfather clause has expired. If Linspire agreed to this deal without excluding GPLv3 software, Linspire would be in violation of GPLv3. Thus, the exclusion of GPLv3, from the deal is to protect Linspire, not Microsoft. Microsoft does not give a *%$#, it has not and does not agree to any version of GPL, so GPLv3 terms are not relevant to Microsoft.

  75. Re:15 years ago: by mrchaotica · · Score: 1

    I was under impression linksys products required a hack via insecure web form to get into the os to replace it, but apparently thats no longer the case.

    As far as I can tell from looking at the installation page for one of the replacement firmwares, there's no hack involved.

    So, what did Tivo do that was ALWAYS wrong?

    Disabling the hardware from running user-modified (and therefore, unsigned) software.

    --

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

  76. No one ever claimed that! by Anonymous Coward · · Score: 0

    > No one has ever come up with some on point case law showing that distributing coupons is the same thing as "distributing software" within the meaning of Title 17 section 106.

    That might be because no one ever claimed that. But distribution is NOT the only thing copyright covers. Look under the exclusive rights section sometimes. You can become a party to some infringement without actually distributing the work. Just look at your own three reasons!

    (1) direct infringement by third party;

    Yup, when you redeem a SLES voucher for GPLv3 code, you do so without permission. That's direct infringement because of that "nothing else permits you" clause you may or may not have read.

    Others have pointed out that this may not be the case for audio CDs (and video games, I think), but that doesn't apply here.

    (2) knowledge by the defendant that third parties were directly infringing; and

    After all the news stories about this, they had to know that the GPLv3 forbids the voucher deal. They even published a press release about it. This one is well-covered.

    (3) substaintial participation by the defendant in infringing activities.

    They SOLD the voucher, effectively selling the infringing copy (even if they didn't personally copy it). Now, IANAL, but that seems reasonably substantial to me.

    Just how shaky do you think this is when you're quoting the very reasons that forbid this?

  77. probably not by kardar · · Score: 1

    It just has to be believable - believable enough. Such and such person took someone's lunch money, and uh... it was lost, or there was a 95-year-old widow who needed groceries or whatever.

    The desired end goal is this: You give Microsoft money. That's all there is to it. Whether it covers anything or not is besides the point. The point is that Microsoft gets your money. And, as long as they get your money, everything is peachy keen, so it doesn't matter what anything covers because nothing will happen as long as you pay up.

    Basically, more or less.

    The nice thing about this situation is that you can basically (more or less) tell them to go bother someone else. Everyone knows these patent cross-licensing deals are silly, and Linux just happens to be physically incapable of entering into them. That's the way Linux is, and the sooner people realize that, the sooner they'll realize it. Whether they realize it or not isn't going to change the fact that Linux is not "cross-licensable".

  78. Because GPLv3 is a change by adah · · Score: 1

    The real story is how Microsoft changed its patent covenant, after the deal with Linspire was already finalized. Is Microsoft free under that deal to alter the patent covenant however they want - making it useless?

    Why is this surprising? Linspire is not a static object. If it can change and adopt new licences—GPLv3 in this case—why can't Microsoft change its convenant?

    Although I dislike DRM and patents, the way in which many GPLv3 advocates treat Microsoft makes me uncomfortable. They have their rights too. Whether their rights are legal/moral or not should not be judged by just advocates of FOSS.

  79. Re:15 years ago: by wirelessbuzzers · · Score: 1

    It's more like a series of tubes...

    --
    I hereby place the above post in the public domain.
  80. I don't have a problem with patents by falconwolf · · Score: 1

    I DO have problems with software patents. Software should not be patented, neither should business methods.

    Falcon
  81. Re:Well of course... by nnm.one · · Score: 1

    It's only less of a target because it has a smaller userbase... SELinux

  82. it encourages me by r00t · · Score: 1

    I'm sort of cool on the whole GPLv3 thing, because of the preamble that unjustly tries to rename Linux against the wishes of the core developers.

    But...

    If the license really bothers Microsoft, then it must be good.

    Hmmm. Tough decision...

  83. purpose served, project ended by r00t · · Score: 4, Informative

    Samba had been encoding/decoding network packets in a very manual way, with a collection of ugly macros to do the job. Samba-TNG was forked largly to switch over to doing RPC via IDL (an Interface Devinition Language, which gets processed at build time to produce *.c stub/wrapper functions to do the marshalling and unmarshalling).

    The main Samba team learned their lesson. They switched to an IDL for Samba 4. Samba-TNG has been a very close clone of the Microsoft implementation, warts included. Samba 4 is far better.

    Thus Samba-TNG has served it's purpose: teach the Samba developers that IDL is a good idea. Done. Mission accomplished.

    1. Re:purpose served, project ended by mrchaotica · · Score: 1

      Perhaps you should update the Wikipedia entry to mention all that then, so people (like me) don't get the wrong idea.

      --

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

    2. Re:purpose served, project ended by Jeremy+Allison+-+Sam · · Score: 2, Informative

      Wow, what interesting revisionist history you have there :-).

      Yes, we know IDL was a better idea, we've always known that :-). It's taken a while to get to the point where we can start to remove the hand-marshalled IDL infrastructure originally added by the main author of the TNG fork :-). But we're there now. The Samba-tng fork happened over a disagreement about separate deamons, not over auto-generated IDL.

      Jeremy.

  84. Stupid you by I'm+Don+Giovanni · · Score: 1

    "GPL2 or later versions of GPL" doesn't mean "GPL2 AND later versions of GPL".
    Oh, and you don't know what "implicit" means either, genious.

    --
    -- "I never gave these stories much credence." - HAL 9000
  85. Re:15 years ago: by jimicus · · Score: 2, Insightful

    GPL does something BSD doesn't. It levels the technology playing field, forcing companies to compete on services rather than products.

    Let's say I produce a brilliant product which once installed doesn't require a great deal of service. There's no sense in me basing it off a GPL project because then I'd have to make the source code available to everyone, and Fred down the road could undercut me because he isn't doing any development.

    Now, change that business model slightly. Let's say I contribute to a product, but my main business model is based around selling services and consultancy to go with that product. Now it doesn't matter so much if I use a GPL product because I'm going to make most of my money from charging consultancy fees to adapt it to specific businesses. In fact, there's something to be said for the GPL because it means that the product will wind up with my name all over it - so anyone who wants consultancy may well think of me first.

  86. Odder than that by Anonymous Coward · · Score: 0

    If MS aren't involved in the distribution (else they are bound by GPL2 rules on patent included by patent owners in GPL code) then how can they say that they are not accepting GPL3 terms? It doesn't mnatter! It's if *Linspire* accept GPL3 terms. MS aren't involved (according to them) so they get no say.

    It's like me saying "I do not agree to abide by the publishing limit of the new Harry Potter before the official release date". It doen't matter: I don't have a right to release the book at all.

    By stating they aren't bound by the GPL3 provisions means that they are admitting the possibility they are a part to the copyright distribution and are therefore bound by the GPL2 provision that code included under patent is licensed for GPL use.

  87. Why? by Anonymous Coward · · Score: 0

    Why will hardware developers not go for GPL3 if they are willing to go for GPL2? Under GPL2 the patent owner (the driver developer) already gives license to GPL use of their patent. So no change there. Driver writers can't sign and enforce signature use because they aren't writing the entire hardware box, just a component of it.

    So, really, why would device drivers refuse GPL3 when they are happy with GPL2?

    "Slashdot requires you to wait between each successful posting of a comment to allow everyone a fair chance at posting a comment.

    It's been 19 minutes since you last successfully posted a comment"

  88. Supporting Samba by Anonymous Coward · · Score: 0

    will mean that MS's interoperability patents get released under the GPL.

    I don't think "wild" even covers that idea...

  89. ...or later by toolz · · Score: 1

    I wonder which part of "GPLv2 or later" Microsoft's lawyers are unable to comprehend.

    Do they even realize of most free software today is licensed this way? Would someone do an analysis of everything in Linspire and publish a report of how much of it falls under the "...or later" clause?

    --
    You aren't remembered for doing what is expected of you
    1. Re:...or later by toolz · · Score: 1

      argh! s/of most/how much of/

      --
      You aren't remembered for doing what is expected of you
  90. and more! by hawk · · Score: 1

    After I submitted that, it also occurred to me that you can find my dissertation in downloadable form (I forget where I found that), various versions of my paper on the economics of open source (which was ultimately published in netnomics), and listings of my presentations at past international society for computational economics (or whatever it's calling itself this year; it seems to change almost every year, sometimes including "finance").

    I'd show you the little plastic card in my wallet identifying me as a member of the NV bar, but . . .

    hawk of the many suffixes

  91. New Abbreviation!! by Anonymous Coward · · Score: 0

    "I'm not a lawyer, yet."

    INALY!!

    1. Re:New Abbreviation!! by oliphaunt · · Score: 1

      I-ANALY.

      --




      Humpty Dumpty was pushed.
  92. Re:15 years ago: by Anonymous Coward · · Score: 0

    Companies bet the farm on GPL'd code for several reasons:

    1. The GPL is better for businesses that intend to write or alter software. The GPL limits the use of the code in other products and forces changes out into the open. If IBM modifies the Linux kernel, those changes are public and Novell could pick them up. Similarly, if they release code they get the changes back.

    2. Linux is a buzzword and thanks to companies like IBM has been used in advertising. Executives and marketing types can market "Linux" with their products. BSD doesn't have the same buzz either as a license or in the OS sense. That is starting to change, but it's not huge yet.

    3. Hardware vendors are just starting to support some BSD derived operating systems. FreeBSD gets binary blobs from Intel and NVIDIA now. They like binary blobs so much that they added a binary blob loading mechnism to make intel happy. This puts FreeBSD on par with Linux. However, many people don't realize there are binary blobs to suppor their latest NVIDIA card and they are limited to i386 last I checked. Intel has done a lot of nice things with open source, but their wireless policy sucks. Point is, Linux has the advantage of open and close sourced drivers plus the newer BSD code can be downgraded to GPLv2 for linux drivers.

    4. Trolltech and MySQL couldn't make money with the BSD license.

  93. Re:15 years ago: by petermgreen · · Score: 1

    different licenses benifit different companies.

    The BSD licenses primerally benifit those who don't want to give much back.
    The GPL primerally benifits library developers as (at least if you follow the FSFs interpretation) its restrictions are effectively far nastier for library users than for users of other types of software.

    Afaict companies like redhat and IBM make the bulk of thier money out of support and the GPL ranges from inconsequential to an annoyance (think of the large number of distros that freeload off RHEL) for them.

    I suspect the GPLs dominance over BSD has a lot to do with it's viral nature, if you are agnostic about license issues but see an interesting GPL library your app will have to be GPL even if that doesn't represent what you belive in.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  94. Re:Well of course... by Hucko · · Score: 1

    Not sure what you are saying...? Linux > Vista > SELinux? Or Linux > SELinux > Vista? Either way, SELinux is a subset of linux, so Vista would still only be more secure because of its obscurity.

    But agreed, if you can get SELinux to be useful (I don't think it is yet intuitive, and not everyone running linux is going to go the SELinux way as there are other solutions that are 'good enough').

    __________

    Okay, before this becomes a flame, I don't know if Vista actually is less secure or has less users. Just answering a troll/flamebait cos i thought at the time it was funny. Retrospect hasn't vindicated my initial intent. Just be grateful I am not basing a career on my "talents"

    --
    Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
  95. Re:15 years ago: by BLKMGK · · Score: 1

    The S3 can still be hacked mind you however you must unsolder an EPROM, flash another, solder a socket, and then proceed with hacks - same with soem of th elater S2 boxes - yuck! However since they have apparently removed some of the code in the S3 rather than just turning it off like they did with the DTIVO there's not too much going on last I checked the DealDatabase forums. Actually, some of the coders seem to be lying a bit low on this too since no one wants the CableCard twits to go nutz and pull the S3 certificate

    Frankly right now TIVO is a mess! I enjoy my DTIVO and all but the HD stuff is ugly so I'm sitting tight watching Sd on an HD set...

    --
    Build it, Drive it, Improve it! Hybridz.org
  96. Re:Well of course... by nnm.one · · Score: 1

    I was refering to SELinux being the solution for optimal security in with Linux (in response to the comment about Linux isn't attacked that much because it has a small market share). You got lots of tools that just does everything automatically for you with SELinux like audit2allow, audit2why (that really dumbs down the AVC messages), and semanage etc., you just do something like "cat /var/log/messages | egrep "(xxx|sshd)" | audit2allow -m newModule" and there you have it, a new module for your needs, just for giving a quick example. If you thinkn that SELinux is just too hard then you probably don't need a really really secure Linux based system. IMO Vista's closed-sourceness will always make so that the best zerodays will remain in the dark and all you have is Microsoft's word for it, of how secure it is etc.

  97. Re:Well of course... by Hucko · · Score: 1

    Ha ha! I was refering to Vista had the smaller user base...

    --
    Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
  98. You stop being an user ..... by jotaeleemeese · · Score: 1

    .... when you distribute code.

    It is not as complicated as some make want us to believe.

    --
    IANAL but write like a drunk one.
  99. Then we move to Solaris. by jotaeleemeese · · Score: 1

    The only thing missing in the equation for the x386 architecture would be drivers, but the considerable muscle of Sun may persuade manufacturers to be more amenable to providing drivers for Solaris, even if it is GPLed v3, thant they have been so far for Linux. Most userland tools have been ported already, are easy to port, or may even run under binary compatibility mode without alterations.

    --
    IANAL but write like a drunk one.
  100. Are Sun and IBM big enough for you? by jotaeleemeese · · Score: 1

    And lest not forget a worldwide community of developers and users that would dig out any prior art in order to invalidate any MS alleged patents?

    Honestly, this is a battle MS should not want ot fight. If they do, they will really do so at their own peril (I don't see much public goodwill towards MS as the monopolist suing the competition, most patents would be invalidated, and the ones with any legal basis would see a US only version of Linux been released with any "infringing" stuff removed, while Europe and other places with sane patent law just ignore the whole issue).

    --
    IANAL but write like a drunk one.
  101. Don't be stupid. by jotaeleemeese · · Score: 1

    The GPL applies to software.

    MP3 files are not software.

    --
    IANAL but write like a drunk one.
  102. Not quite. by jotaeleemeese · · Score: 1

    The only thing Novell needs to do is flush the agreement with MS down the toilet, where it belongs, and behave in the future. After all many people there (SuSe and Mono former people) have contributed to the free software effort and should not be punished if at all possible just because the PHBs had a moment of monumental stupidity.

    As for Linspire, they can go to the moon as far as I am concerned.

    --
    IANAL but write like a drunk one.