Slashdot Mirror


RTLinux Patents: Issue Closed?

Anonymous Coward writes "LinuxDevices.com reports that the Free Software Foundation has reached an agreement with Victor Yodaiken which resolves what FSF considered to be a violation of GPL by the Open RTLinux Patent License. Details are not yet available, but it sounds like the clause in the license which required users of RTLinux to keep records and provide them to FSMLabs on demand was the principal source of the violation, and that the requirement is being dropped from an updated version of the RTLinux license that will be published in the next day or two. All in all, it seems like the FSF has successfuly enforced the GPL even though it was neither an owner nor co-owner of the software (i.e. the linux kernel) whose license terms were being violated. It's interesting to see this practical example of FSF in action, and bodes well for the future of GPL -- at least in a small way."

crimoid points to ZDNet coverage of the FSF's criticism of RTLinux's licensing terms, written before such a resolution was clear. Sourceforge on Thursday quoted RTLinux CEO Victor Yodaiken, CEO as saying that his company is happy to change "minor problems" with the RTLinux license, and that discussions are still going on with the FSF about those changes.

121 comments

  1. "even though it was neither an owner nor co-owner" by bigpat · · Score: 1

    Couldn't anyone be considered a "co-owner"?

  2. I don't see it that way by _Mustang · · Score: 4, Insightful

    It's interesting to see this practical example of FSF in action, and bodes well for the future of GPL -- at least in a small way."

    How do you figure? The supposed breach involved someone who is a part of the community. Presumably he shares at least some of the same views as those espoused within the GPL. That means it was a fairly good bet that he would deal with this (in an amicable manner) once it became apparent that he had violated the GPL terms.

    Surely a much better test would involve people/companies who don't share the linux view of the world but who wish to leverage the codebase for their own gain..

    1. Re:I don't see it that way by Whyte+Wolf · · Score: 2
      Surely a much better test would involve people/companies who don't share the linux view of the world but who wish to leverage the codebase for their own gain..

      Yes, but the more the FSF and GPL are seen as enforceable in a business content (even if the 'business' who agrees to abide by the GPL is one of 'us') the more bigger business who isn't one of 'us' will see it as not worth taking on the FSF and GPL.

      Especially if there are a legion of rabid slashdotters ready to take on the eveil bad-guys.

      Go my unholy army of the night...

      --

      Beware the Whyte Wolf.

      With a gun barrel between your teeth, you speak only in vowels...

    2. Re:I don't see it that way by Anonymous Coward · · Score: 0

      It's amazing how noble you guys get about GPL... yet when it comes to the license on other people's stuff eg the MPEG4 algorithm.... licensing becomes a bad restrictive thing...

  3. No legal precedent by Anonymous Coward · · Score: 1, Interesting

    It's interesting that the GPL and Stallman's way of dealing with violations does not establish legal precedents, since it's all solved out of the courts.

    I wonder how much tech lawyers must hate this kind of behavior. It means less money in their pockets if everyone starts using the GPL. We may after all be headed to a better world.

    1. Re:No legal precedent by Anonymous Coward · · Score: 0

      > We may after all be headed to a better world.

      Sure, we are already in it. Many Linux related companies are collapsing thanks to the GPL.

  4. Re:"even though it was neither an owner nor co-own by almightyjustin · · Score: 4, Interesting

    "Owner" as in owner of the copyright. Contrary to popular opinion, Linux and other GPL software is actually copyrighted. The GPL is essentially a EULA, and has no legal force unless the program it is included with is copyrighted. Since the FSF did not write the Linux kernel, they have no copyright on it and therefore no legal rights to it, so their power is limited in this matter. Presumaby Linus Torvalds holds the Linux copyright, but I really don't know. Probably it's co-owned by several people, but it does *not* include everyone who's ever submitted a patch.

    --

    Omnes arx vestrum sunt adiuncta nobis.

  5. So.. by Anonymous Coward · · Score: 1, Insightful

    FSF succeeded to turn on legions of mindless GNUtroids to jihad against RTLinux with the use of 'patent'-curseword in a case that was just a disagreement over details in the patent license. Do note, that the RTLinux policy of licensing the patent freely only to GPL software and collecting cash from proprietary code makers continues unaffected and FSF has no problems with it.

  6. Actually... by mrcparker · · Score: 3, Interesting

    .. it really has nothing to do with the future of the GPL. It would be different if RTLinux decided that they did not want to work with the GPL while using GPL'ed software.

    This is a company who made an honest mistake and did what they could to fix it. Really, a non-issue. They probably has no clue that they were violating the GPL.

    1. Re:Actually... by Anonymous Coward · · Score: 0

      Unfortunately this story doesn't give enough background on FSMLabs, but they've done a lot of harm to Linux. It's definitely not a case of "honest mistake" ... It's more a case of "oh fuck, we're dead" which prompted them to comply with the FSF.

  7. The text in question by sphix42 · · Score: 1

    6. You will keep complete and accurate records of all commercial uses of the Patented Process and all commercial distributions of the Patented Process whether that distribution occurs directly or as part of your products or services. You will also provide copies of all such records upon request from Licensor.

  8. Re:Katy! by lavaforge · · Score: 1, Offtopic

    Yeah, but "Can I ride her?"

  9. Re:FSF by Anonymous Coward · · Score: 0

    Get Used to it.

    You are about to be policed by a moderator.

  10. But the big question about this "Stallman"... by Anonymous Coward · · Score: 0

    is "Does he run Linux?"

    1. Re:But the big question about this "Stallman"... by Anonymous Coward · · Score: 0

      Actually, he does.

    2. Re:But the big question about this "Stallman"... by Anonymous Coward · · Score: 0

      Assmunch, that's GNU/ Linux to you!

  11. Re:Katy! by lavaforge · · Score: 1, Offtopic

    Karma got maxed out. Had to lower it...

  12. I still don't understand... by Zwack · · Score: 3, Insightful

    Why this is called RTLinux. It's a real-time OS that is very lightweight that can run Linux or NetBSD as a pre-emptible process.

    Isn't this an infringement of the Linux trademark?

    Won't Linus lose the rights to the trademark if he doesn't follow this one up?

    --
    -- Under/Overrated is meta-moderation, and therefore is Redundant.
    1. Re:I still don't understand... by Anonymous Coward · · Score: 1, Funny

      Isn't this an infringement of the Linux trademark?

      No, because this project is called "RTLinux" and not "Linux". You can't easily get confused between the two.

    2. Re:I still don't understand... by LordNimon · · Score: 2, Insightful
      Two guesses:

      • Linus may already be allowing them to use the term "RTLinux". Some companies allow others to use their trademarked terms in certain circumstances. This does not dilute the trademark.

      • I don't think Linus has to worry about the term "Linux" being diluted. RTLinux is based on Linux and is under the GPL, so it's not like Linux is being used as a term to describe any operating system.
      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    3. Re:I still don't understand... by Anonymous Coward · · Score: 0

      I guess Microsoft won't have any problems then when they ship a version of Windows XP called "MSLinux".

    4. Re:I still don't understand... by Graymalkin · · Score: 2

      Though they should probably call it "MSVMS".

      --
      I'm a loner Dottie, a Rebel.
  13. Re:"even though it was neither an owner nor co-own by redhog · · Score: 3, Interesting

    Unless they have signed over their copyrights (to Linus), any submitter of a patch of significant size (a patch having a work status) is a co-owner. But, IANAL. I don't know if any employee of FSF have submitted any patches of significant size, but it's not impossible.

    --
    --The knowledge that you are an idiot, is what distinguishes you from one.
  14. 2345678 by l00ny_bstrd · · Score: 0

    ...is coming. ARE YOU READY???

    --
    buy, now...
  15. The FSF are a bunch of real smart people by Rosco+P.+Coltrane · · Score: 4, Informative
    The bottom of the problem is that Victor should never ever have been granted a patent for RTlinux : there is plenty of prior art (DR-Multiuser-DOS, Concurrent DOS and even the current DR-DOS multitasker have been around for 15+ years and use the exact same technique). Moreover, Victor didn't "invent" all of RTlinux, his students did.

    Considering that the patent is easily breakable in court, the FSF settled with Victor very easily. Why ? because RTlinux is irrelevant : RTAI is the way to go now. It provides all that RTlinux provides and much more, and it isn't encumbered by silly patents.

    All in all, a much better move than it first appears by the FSF : they win on the PR front by making Victor change his license and they save money by not contesting a patent that isn't important anymore. Way to go guys !

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:The FSF are a bunch of real smart people by iplayfast · · Score: 1
      Having a public debate isn't the same as enforement. The RTLinux guys messed up, in a minor way, and then they corrected it.

      End of story.

    2. Re:The FSF are a bunch of real smart people by Anonymous Coward · · Score: 0

      The license was't changed. The FSF didn't read the active one, and basically admitted that they were reading an old license. RTAI is known for overengineering and is really not moving anywhere.

  16. A Win-Win Result by Bruce+Perens · · Score: 5, Informative
    The GPL requires patents embedded in GPL code to be available for everyone's free use. This can be implemented by making the patents available for use in GPL programs. Victor thought he was already doing this, what happened here is simply the resolution of a small issue of GPL compatibility. So, Victor gets to use the patent to enforce his revenue stream and pay for more Free software, Free Software users get to use the patent for free, and as far as I can tell everyone wins.

    This is not really about enforcing the GPL, it didn't get close to that point. All we had was a short public dialogue. Enforcement is something that happens in court. I wouldn't even count an out-of-court settlement as enforcement, that's just avoiding the issue because the defandant thinks that a successful enforcement would be likely or doesn't think it's worthwhile to mess around in court. This was way far from anything like that.

    Thanks

    Bruce

    1. Re:A Win-Win Result by SamBeckett · · Score: 1

      pay for free software?

    2. Re:A Win-Win Result by mattdm · · Score: 2

      pay for [the creation of] free software.

    3. Re:A Win-Win Result by Arandir · · Score: 1

      The problem is that the GPL lets me use the software without hindrance. A patent does not.

      I can use ANY other Linux to run my programs on. But if RTLinux only lets me run a particular class of software (those covered by the GPL), then I could not run any X11 based software, no Python software, and no Apache. I could run KDE, but I coudln't run KWin or Kicker.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:A Win-Win Result by Webmonger · · Score: 2

      Does this mean that you can use the patent for any GPLed work? Because you can take RTLinux and mutate it, until your "derivative work" bears no resemblance to the original-- except for performing operations that fall within the scope of the patent.

    5. Re:A Win-Win Result by Bruce+Perens · · Score: 2
      Yes. I should have pointed out that this doesn't mean I like patents. And there probably is a prior-art issue here related to the DOS multitaskers.

      Thanks

      Bruce

    6. Re:A Win-Win Result by Steeltoe · · Score: 1

      What many feel is that combining patents with free software breaks the spirit of free software. Suddenly, use is restricted. What if I want to create a real-time kernel for FreeBSD for instance?

      Besides, if this patent is about masking interrupts and prioritizing them, it's a laughable patent anyways. There should be fines for such patents. In fact, that would be a HUGE income source for the patent office.

      - Steeltoe

    7. Re:A Win-Win Result by Bruce+Perens · · Score: 2
      Yes.

      The license is here.

      Bruce

      P.S. This useless text added to pass the slashcode "postercomment compression filter", which seems to penalize brief replies.

    8. Re:A Win-Win Result by Anonymous Coward · · Score: 0

      You misunderstand the reach of this. Here is a reply by Victor to a question on a public mailing list (the first part is the question, the second part starting with "No. But ..." is Victor's reply):

      > >Will I have obligations (financial) to anyone, should we decide to use a
      > > modified version of RTLinux for a commercial product, even though we have made
      > > said modifications available to the world in source format?
      >
      > No. But: the exception allowing you to run non-GPL RT applications under the
      > RTLinux OS applies only to unmodified RTLinux. This is a restriction of
      > our patent license. The license says: modifications to RTLinux code
      > terminate the option to run non GPL RT applications under the resulting
      > code.

      This is akin Linus charging for non-GPL applications that run on top of Linux. This is a very serious blow to the GPL which specifically mentions that its intention is not to impose any kind of condition on the object of its intended use. The intended use of GCC is to compile programs and, as such, it does not require that the programs being compiled to be licensed under the GPL. Applying a license similar to the RTLinux patent license to GCC would mean that all applications compilled with GCC must be licensed under the GPL themselves. This is certainly not what the GPL is about.

      The original message from which the quote is taken can be found here. And, please, don't argue about the specifics of this message. I can provide tons of other message like this which show that Victor has the firm intention to charge for any non-GPL real-time application.

      Bottom line is that although RTLinux is distributed under the GPL, it cannot be put to its intented use without violating the patent license. This is a clear breach of the GPL by a prominent figure of the OSS.

      The worst part here is that key figures such as kernel developers have been fooled by Victor's depiction of his license while he has been giving a complete different version of things to people actually using real-time derivatives such as RTLinux and RTAI (which, by the way, is far better than RTLinux).

  17. Your right by Ghoser777 · · Score: 2

    but this helps set a precedent. Too bad it's not in the legal sense. What we really need is a test case, to find some business that violated the GPL and take them to court over a big, intentional GPL violation where they'll attack the integrity of the GPL. If it survives the court case, we're in good shape and makes it likely that companies will think twice before they violate the GPL.

    For some strange reason I have an urge to dig through code from a certain company.

    F-bacher

    --
    James Tiberius Kirk: "Spock, the women on your planet are logical. No other planet in the galaxy can make that claim."
    1. Re:Your right by Anonymous Coward · · Score: 0

      There's actually a very good reason for GPL software to be bloated and buggy. The GPL licence permits people to take the source code, change all the credits so it looks like they made it, and distribute it without giving the original authors any credit at all. But if software is bloated and buggy, nobody wants to take credit for it.

    2. Re:Your right by Anonymous Coward · · Score: 0

      Amen to that! As somebody pointed out a few days ago, when you release code under the GPL, that code belongs to the "General Public" and there is no way to take it back! You cannot re-release the code under some other licence since this is strictly prohibited by the GPL (this is the so called "copy-left").

    3. Re:Your right by Anonymous Coward · · Score: 0

      Um, no it doesn't. Read it some time.

      http://www.gnu.org/copyleft/gpl.html

      Here's a relevant section:
      "You may copy ...the Program's source code ... provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice ..."

      Since the work copyright notice includes the original author's name, what you suggested cannot happen.

  18. Re:And if anyone wants proof positive that ZDNet/C by RazorJ_2000 · · Score: 1

    says "page not found"

    --
    pi=sigma{n:0-infinity}[(1/16)^n][(4/(8n+1))-(2/(8n +4))-(1/ (8n+5))-(1/(8n+6))]
  19. Re:Katy! by Anonymous Coward · · Score: 0

    :) perhaps one day you will be back with Katy.

  20. Does this improve the outlook for the GPL? by hillct · · Score: 2

    The asertion was made that this outcome bodes well for the future of the GPL. I'm not sure if I see that. No legal prescident was set here; only more evidence of the FSF's ability to bully people into bending to their will. Don't get me wrong, I believe the FSF was right in this case, in insisting on the changes that were mand, but as a matter of law, a third party still has no standing in a license negotiation, and that's probably a good thing - as a matter of law

    --CTH

    --

    --Got Lists? | Top 95 Star Wars Line
  21. The real power is in the community. by BierGuzzl · · Score: 3, Insightful
    The FSF issued a press release because on it's own, it doesn't really have any clout to get Company x,y, or z to change. It needed the press coverage and the discussion that it generated to have any amount of sway. It has everything to do with Politics and PR rather than power and substance.

    All the same, I'm glad things seem to have worked out for the best, albeit at the unfortunate cost of airing dirty laundry in public.

  22. Pre emptive patent? by Sheldon_Brown · · Score: 0, Troll

    In what is quite possibly the worst pun ever, is it possible that Victor has received a pre-emptive patent on pre-empting? That is, he has prevented others from nefariously patenting the process, by patenting it himself. It's not as if he is trying to exploit it financially, and the patent process is quite costly.

    --
    "A coward is incapable of causing destruction; it is the prerogative of the brave" - Mahatma Ghandi
    1. Re:Pre emptive patent? by Anonymous Coward · · Score: 0

      If you do not change your website URL so it doesn't screw up the page, you will leave me no choice but to pull down your pants and rape you.

    2. Re:Pre emptive patent? by Anonymous Coward · · Score: 0

      let me do it!!! let me do it!!!

  23. Corrected link by matty · · Score: 2

    Well, I tried to post a corrected link, but there must be a problem with Slashcode. Here's my attempt below:

    http://www.zdnet.com/zdnn/stories/news/0,4586,28 12 834,00.html?chkpt=zdnnp1tp02

    When I type it in above, there's no space, but when it shows up as a comment, there's a space between 2812 and 834. Just copy and paste, then remove that space.

    I'll save you some time: it's anti-OSS FUD saying that Open Source is "Rocked" by this awful transgression. Yeah, right. It was a minor dispute, nothing more.

    P.S. I don't think ZDNet is anti-Linux "at it's core", they simply have some writers that are anti-Linux, just as they have some writers that are pro-Linux (like Evan Liebovitch [sp?]).

    1. Re:Corrected link by hebertrich · · Score: 0

      correct is still incorrect says page not found...lol
      in all cases ZDNet is commercial to the bone.
      im quite sure they have nightmares seeing free
      as free beer and free as free software like
      the Linux distros when crappy software is being sold for top dollars and there is actually
      people buying it ./..

      ric

    2. Re:Corrected link by matty · · Score: 2

      correct is still incorrect says page not found

      ...there's a space between 2812 and 834. Just copy and paste, then remove that space.

      Did you follow those directions? I just did and it worked fine for me.

    3. Re:Corrected link by etymxris · · Score: 1

      You shouldn't do it that way. Slashdot will randomly insert spaces into really long words to keep the tables lined up correctly. Otherwise, everytime someone put in a really long word like thisssssssssssssssssssssssssssssssssssssssssssssss ssssssssssssssssssssssssssssssssssssssssssssssssss ssssssssssssssssssssssssssssssssssssssssssssssssss ssssssssssssssssssssssssssssssssssssssssssssssssss sssssssssssssssssssssssssssssssssss it would cause the page to be much wider than it should be. As it is, since spaces are inserted, the rendering of your page is not screwed up.

      Anyway, since Slashdot allows href tags you should use them, and links will work fine, like this.

    4. Re:Corrected link by matty · · Score: 2

      Oh, all right, I didn't know that, thanks.

      I sure wish they would do that for personal URL's, tho.......

  24. Re:FSF by Anonymous Coward · · Score: 0

    Get Used to it.

    You are about to take it up the ass from a moderator.

  25. Still need a real test by rkent · · Score: 3, Insightful

    All in all, it seems like the FSF has successfuly enforced the GPL even though it was neither an owner nor co-owner of the software...

    But in this "enforcement," as in others by the EFF, the change required was minor and the party was cooperative when the problem was pointed out -- the blurb even said that RTLinux was "happy to change" license provisions to comply with the GPL.

    We still need a test against a genuinely aggressive GPL violator. One who either denies the violation, or tells the EFF to go fsck themselves. The "enforcement" so far seem like a football team scrimmaging against itself: conceptually useful, but not necessarily predictive of real victory.

    1. Re:Still need a real test by Todd+Knarr · · Score: 3, Insightful

      True, but every time some company changes the licensing terms on software they derived from GPL'd code it's one more point on the FSF's side when they finally do meet up with a hostile infringer. Firstly it establishes a track record of the industry considering the GPL valid. Secondly, if the infringer tries to claim it's not valid because it's unreasonable, the FSF can trot out examples of the actual, reasonable changes needed to comply to rebut the infringer. It's a variation on the same principle the big boys have used: start with the small fry and the ones who don't lose much by accomodating you and build up precedent before going after larger targets.

    2. Re:Still need a real test by Anonymous Coward · · Score: 0

      Even nicer would be for everyone who comes into contact with free software (GPL or other license) to behave in a reasonable manner and it to never have to be challenged.

      Would that kind of persistant, prolonged and reasonable behaviour be a world first?
      ( I won't hold my breath )

  26. Linux Kernel Bloat Chart by Anonymous Coward · · Score: 0

    This is a chart of how bloated the Linux kernel is. (each b represents 1 megabyte of the .tar.gz file)


    1.0: b
    1.2: bb
    2.0: bbbbb
    2.2: bbbbbbbbbb
    2.4: bbbbbbbbbbbbbbbbbbbbbbb

    1. Re:Linux Kernel Bloat Chart by Anonymous Coward · · Score: 0

      that means it has more drivers and supports more architectures dumbfuck.

    2. Re:Linux Kernel Bloat Chart by Anonymous Coward · · Score: 0

      that means you have more cocks up your ass dumbfuck.

    3. Re:Linux Kernel Bloat Chart by bug1 · · Score: 1

      If you compared the size fo binaries built with the same features then you may have had a point.

      Also it has many archs now.

    4. Re:Linux Kernel Bloat Chart by Anonymous Coward · · Score: 0

      that means less brains in your head dumbfuck.

    5. Re:Linux Kernel Bloat Chart by Anonymous Coward · · Score: 1

      would someone kindly ram their cock up the ass of this little boy ? he needs the fucking of his life, preferably on the tip of a 14 inch penis. if youll notice he's quite a soft little twink and would probably squeal like a little piggie at first but would be easily subdued by a good whipping about his pudgy white ass and soft effeminite feet. i suggest kidnapping him and tying him hand and foot then giving him the fucking and torturing he deserves. mmmm...

      i've heard he has a raging foot fetish and will kneel and lick the feet of any fat little gay boy and gladly let you tie him up and fuck the shit out of him once you torture him enough.

  27. This can happen more! by Anonymous Coward · · Score: 0

    Remember to email the FSF at licensing@gnu.org if you see a GPL, LGPL, or GFDL violation.

    Document the situation as fully as time allows, and the FSF will do everything it can to get the problem fixed.

  28. Owner? by Cardinal+Biggles · · Score: 3, Interesting
    All in all, it seems like the FSF has successfuly enforced the GPL even though it was neither an owner nor co-owner of the software

    I suppose you mean to say that the FSF is not the copyright holder of (part of) the software?

    Copyright does not make you an owner, it makes you the beneficiary of a temporary exclusive right to copy the work. You can't own software.

    You may think I'm nit-picking, but I think that that's a very important distinction to make. The general public's (and politician's) failure to see this point is a (the?) basic problem in the thinking behind all those bad IP laws.

    1. Re:Owner? by DHam · · Score: 1

      Actually in some sense copyright does make you the "owner" of a work. Let me explain. Common law (physical) property is based on the doctrine of estates. An estate is a bundle of rights attached to a thing (a car, an apple, a house etc.). Such rights include the right to posession, the right to modify or destroy, and depending on the nature of the thing, many others. Property rights may be perpetual or they may be limited in time. Different people may own estates in different things. For example, if I lease your house for a year then I own the right to posess (live in) that house for one year and some auxiliary rights, you own a whole load of other rights, including the right to my rent payments and the right to possession after that year. Some property rights arise at common law and some are created by statute.

      In the case of "Intellectual Property" rights, they are similarly rights attached (by statute) for a limited time to a thing - in this case, though, the thing is information (for example with patents) or the expression of information (for example copyright). Once again different people can hold rights in the same piece of intellectual property and, due to the nature of property, it is common for very large numbers of people to have rights (even buying a book gets you some rights in it).

      Now, intellectual property is always created by statute and hitherto usually for finite time (although successive extensions of copyrigbt have begun to change this). Also, the rights generated are quite a bit different from those involved in physical property. For this reason, they are usually regarded as separate legal fields with similar terminology because of the analogies mentioned above. The problem arrises because these are technical terms often misunderstood by lay people who then leap to the unfortunate conclusions that property and IP are the same thing.

      Stupid "copying is theft" messages result.

  29. RTAI is covered by the same patent by Anonymous Coward · · Score: 0

    AFAIK, RTAI is an offshoot of RTLinux. The RTLinux philosophy is that the RT side should be highly simplistic and have a tiny set of primitives. RTAI seeks to evolve the RT services to encompass everything you'd ever expect from a RT operating system.

    In the RTLinux approach you want to place the minimum amount of stuff on the RT side for reliability reasons. The RTAI people feel that approach handicaps the RT application programmer.

    However, Yodaiken's license applies to RTAI all the same.

    Marko

  30. Re:Katy! by Anonymous Coward · · Score: 0

    HOW DARE YOU USE THAT WORD!?!?! Call him a sand nigger :)

  31. excellent! by Lumpy · · Score: 3, Insightful

    This looks like the first real win for the FSF. Hopefully there are many many more, Now if we could get geeks and techno-prople to donate 1/25th of what they donated to the WTC disaster they'd get some real teeth to go after larger targets.

    BTW, before you click on the (TROLL) button because I didnt mention the WTC while crying and wailing.. It's an example that the geeks donated and helped overwhelmingly to the aid of those poor people and the red-cross. and the fact that many are willing to donate time to go and help that is way above and beyond the call.

    --
    Do not look at laser with remaining good eye.
  32. GPL is dying by Eil · · Score: 2


    Hmm, looks like I'm going to have to retune my "GPL is Dying..." troll.

  33. Here's the license by ben_tarval · · Score: 1
    You can read the current license at ftp://ftp.rtlinux.com/pub/rtlinux/v3/PATENT_LICENS E .

    Note that the last mod time, as I write this, is Jan 22, 2001 - so it hasn't been changed yet. It looks like section 2.6 is going to be removed.

    One has to wonder why rtlinux screwed up here. This seems like a ton of bad publicity for such a minor change. To say nothing about the negative publicity over a patent (and a patent that wouldn't hold up in court, no less).

  34. Yes, Stallman runs Linux by yerricde · · Score: 1

    But the big question about this "Stallman" is "Does he run Linux?"

    Of course. Linux makes up a part of the primary operating system used at the FSF; it's the kernel of the GNU/Linux system: GNU's Not UNIX®, and Linux® Is Not UNIX®. I still wonder why FSF didn't register the "GNU" mark.

    Get a GNU/Linux system today!
    --
    Will I retire or break 10K?
  35. I don't even use the word "IP" by yerricde · · Score: 1

    Copyright does not make you an owner, it makes you the beneficiary of a temporary exclusive right to copy the work. You can't own software.

    Right. In that vein, many people have dropped the term "IP" entirely and taken up calling such rights "government-granted monopolies," or GGMs. ( Read More... | )

    --
    Will I retire or break 10K?
  36. Quickwy by Anonymous Coward · · Score: 0

    turn to twoll!

  37. The role of "public shaming" ... by LL · · Score: 1

    Oddly enough, the talk of press releases and social-karma (or corporate equivalent of avoiding brand tainting) seems to work in imposing social norms on recalcite companies. This is not to claim that the GPL is good or bad, but to point out that they are doing the modern equivalent of the church punishing obnoxious behaviour in the middle ages by parading perpetuators around in public with ugly masks and placards. The effectiveness might be questionable but there's no doubt that people's desire to conform (peer pressure) is a powerful psychological force (sometimes excessively so in teenagers) and it does have the advantage of being cheaper than lawsuits.

    The problem is so far the main groups that can take advantage of open source are the relatively prosperous western countries. Enforcement of the GPL license is going to be harder in places which don't respect intellectual endeavours (Eastern pirates), much less international laws (Taliban, etc). Ultimately laws are self-imposed constraints ... we don't murder people because we understand the consequences of arbitrary violence. The GPL, whether mindless ideology or social conviction, is no less powerful in that at least people in the hacker community recognise the benefits and are willing to follow the principles.

    The interesting fact about a global software economy is that reputation becomes so much more important. When details are kept track of contributors in freshmeat, sourceforge, etc. Old fashioned social ties are reused to subtlely enforce trust. Would you start up a company or work with someone you know that doesn't recognise the legimacy of software licenses? Public naming and threats to lose "face" in front of peers may ultimately unveil all sins (programming or otherwise).

    LL

  38. fuck jeremy olsen by Anonymous Coward · · Score: 0

    would someone kindly ram their cock up the ass of this little boy ? he needs the fucking of his life, preferably on the tip of a 14 inch penis. if youll notice he's quite a soft little twink and would probably squeal like a little piggie at first but would be easily subdued by a good whipping about his pudgy white ass and soft effeminite feet. i suggest kidnapping him and tying him hand and foot then giving him the fucking and torturing he deserves. mmmm...

    i've heard he has a raging foot fetish and will kneel and lick the feet of any fat little gay boy and gladly let you tie him up and fuck the shit out of him once you torture him enough.

  39. Re:"even though it was neither an owner nor co-own by ewhac · · Score: 3, Informative

    Contrary to popular opinion, Linux and other GPL software is actually copyrighted. The GPL is essentially a EULA, [ ... ]

    Actually, that's not precisely correct, either. The GPL is definitely not a EULA. Whereas most software "licenses" purport to place conditions on how you may use the software, the GPL places conditions on how you may copy and redistribute the software. This is a subtle but important difference.

    Schwab

  40. Good, or bad? by man_ls · · Score: 1

    I don't agree with the GPL. While it certainly does standardize open-source licensing, for any free software organization to become legalistic about another free software organizaion not following their terms to the letter is like biting the hand that feeds.

    The FSF doesn't own any of the things covered by the GPL. They do, however, feel compelled to dictate terms of useage to the people who are making their software publically available. This shows, to me, little more then slightly masked greed.

    I've released a few software programs that were very, very specialized, under a license I wrote myself...a 1-liner. "You can do whatever you want to this program, provided that you give me credit for making it in the first place and you don't blame me for anything wrong in it, known or not." No complaints...

    The FSF seems to have gotten too big of an ego for its own good. Someone needs to cut them back down to size, in my opinion.

    J.W. Koebel

    1. Re:Good, or bad? by fsmunoz · · Score: 1

      I don't agree with the GPL. While it certainly does standardize open-source licensing, for any free software organization to become legalistic about another free software organizaion not following their terms to the letter is like biting the hand that feeds.


      The GPL was made with a goal in mind; the exact terms are like they are (and keep changing slightly) because the FSF actually has lawyers and actually needs a decent license that hold ups in court or similar situations, and not just a general "Do what you want and don't bug me" thing that not only defeats the meaning and purpose of the GPL but also is virtually void legally.

      I can however understand your disliking of the GPL (i.e. I admit that ppl have reasons for not liking it), but we have to view the GPL in face of the FSF's goals (the world 'goals' and 'agenda' and constantly being said to scare people about the FSF.. so the FSF has goals? So what? It's because they have goals and they take actions to pursue them that we have the software in the first place!).


      The FSF doesn't own any of the things covered by the GPL.


      You are wrong here (probably this was not exactly what you meant). The FSF is owner of *lots* of software under the GPL; in fact all the major software that is part of the GNU system is "owned" (i.e. has copyright asigned to) by the FSF. The examples are so many and of so well known and fundamental programs that I will not need to enumerate them. And this ownership isn't surpising either... people sometimes talk about "the FSF" like the FSF is some kind of rigid corporation with a fixed set of people... tha's just not the case. Many ppl assign the copyright to the FSF because they want to, and in that sense the FSF is just about everyone that believes in the FSF goals and contributes code/documentation/testing/etc to the GNU project. The FSF is, grosso modo, a community of people joined around Free Software (and a specific view on how it should be, granted), and is thus much more fluid that people like to believe.


      They do, however, feel compelled to dictate terms of useage to the people who are making their software publically available. This shows, to me, little more then slightly masked greed.


      They do not feel compeled to dictate, thay have legitimate concerns about breachs on the GPL, even though in this situation they are not copyright owners. Making software 'publically available' counts very little per se in a free software perspective. Is interesting to note that many people are very eaguer to see the GPL tested on court (and many ppl would love to see it lose) but do not like to see the FSF settling things outside them. If the FSF doesn't produce a statement about what they are doing then they are 'following their agenda' and 'locking out the community'; if they do they are 'enforcing their views' and 'trying to get support from the community because they can't make it themselves'. Honestly, I fail to see what 'community' is this one, since we all know that that the concept of what is free software (among lots of other things) are totally distinct for ppl inside the 'community'; the FSF as a community, on the other hand, has a much more solid point of view and defined ideas (like most of the BSD ppl).

      Greed? If the FSF refused to say anything just because they aren't the copyright owners ppl would cry havoc with 'they are abandoning other ppl just because they didn't assign the copyright to them, serves you to see their hidden agenda, etc,etc'. The FSF has a pragmatic view on things, once again because of it's well defined goals and ideas (which are of course questionable and ppl are free to like them or not).


      I've released a few software programs that were very, very specialized, under a license I wrote myself...a 1-liner. "You can do whatever you want to this program, provided that you give me credit for making it in the first place and you don't blame me for anything wrong in it, known or not." No complaints...


      Why should there be? In what way does that prove anything about the GPL or the FSF?


      The FSF seems to have gotten too big of an ego for its own good. Someone needs to cut them back down to size, in my opinion.


      LOL. The ppl who delight in using software that they obtain freely and then question the very essence of what makes the software available to them are the ones with an oversized ego. To think that someone should change the FSF just because a present hype and coolness of being and anti-GNU badass is laughable.

      Cut them to their size? Hardly. The size of the FSF is mainly symbolic and because of that, and as long as they continue with their course of action, virtually impossible to 'cut down'.

      yours,

      fsm

      fsmunoz@sdf.lonestar.org

  41. Something better to do? by codeforprofit2 · · Score: 0, Troll

    Doesn't that RMS fanatic have anything better to do?

  42. Re:FSF by codeforprofit2 · · Score: 1

    Couldn't agree more. Socialists running around and dictating how software shall be used and produced.

  43. Not as good as you might think... by GreyPoopon · · Score: 2
    I'm suprised at the number of "this is good" posts. Actually, I'm glad that they've resolved this dispute, but all of this "hubub" should have never happened in the first place. When I read the some of the background articles on this, I noticed that Yodaiken was initially very surprised at the community reaction to his license. Although the article was worded mildly, it sounded to me like he was insulted not only by the FSF accusation but also by many of the comments posted on our own loving Slashdot. It was an obvious case of "oops, we goofed" that should have been handled by FSF sending a nice letter saying something like "Please notice that you have altered the GPL language to impose conditions on this license that are contrary to the goals of the GPL and FSF. Assuming that your work does not contain the efforts of others which are already licensed under the GPL, please considering removing this restriction or use a different license." Instead, a rather inflammatory press relese about violations of the GPL was sent out, and lots of comments about "Who are these people?" were posted.


    Yodaiken's company is a big contributor to Linux and OSS. I believe that, as such, they are due at least a modicum of respect and consideration. If polite attempts at correcting them are ineffective, you can always turn to the more heavy-handed approach later. People need to remember that if we want to be a community, we have to act like one. There will, as a matter of course, always be disagreements. Most of them can truly be solved without too much sword rattling by merely going to lunch together or something.


    No, I believe this whole thing was just rotten. It's enough of an issue to make me very cautious about using GPL on any software I may contribute. I would hate to see what would happen if I accidentally did something contrary to the goals of the FSF.

    --

    GreyPoopon
    --
    Why is it I can write insightful comments but can't come up with a clever signature?

  44. What happened to Kerberos? by Anonymous Coward · · Score: 0

    I haven't heard that they've enforced the GPL on Kerberos against Microsoft. What happened there? Isn't that a little more important?

    1. Re:What happened to Kerberos? by Second_Derivative · · Score: 0

      Kerberos is licensed under the BSD license; there's plenty of commercial implementations and the loophole is an intentional one.

  45. Re:"even though it was neither an owner nor co-own by Anonymous Coward · · Score: 0

    lay off the pipe dude. the gpl certainly is an eula. and there eula that says "you can't use this software to write anti communism treatises" doesn't exist.

  46. None of their business by darthtuttle · · Score: 1

    I'm curious why the FSF got involved in this at all. They have nothing to do with the Linux kernel. That's someone elses IP. I think this is another example of the FSF sticking it's nose in to other peoples business and making it theirs. I just don't like that.

    If the owners of the IP had issues with what was going on they could have handled this.

    --
    Darthtuttle
    Thought Architect
  47. Patent woes by Bruce+Perens · · Score: 2
    Agreed, I still don't like patents. But rather than fine people who apply when there's prior art, it should simply be easier to invalidate the patent. Their filing and legal fees would be fine enough.

    Bruce

  48. Don't need to be owner by geekoid · · Score: 2

    Lawyers defend copyrights everyday, even though they don't own them.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  49. Re:FSF by kz45 · · Score: 0

    I should be used to it.

    The socialists/communists running slashdot censoring my every word is not a suprise to me.

    'nuff said

  50. Re:FSF by Anonymous Coward · · Score: 0

    You know, if you ever bothered to post something that wasn't moronic, illiterate, lying, unsupported flamebait, you might have better luck.

  51. Re:FSF by kz45 · · Score: 0

    here is my original post:I don't know what's going to be worse, the US government or the GNU police......

    What part of this DON'T you understand. The gnu license is as free as the copyright. IF it were a truly "free" license, it would be in the public domain, with NO restrictions. Instead of going to a copyright holder to see if it is in violation, we are going to Richard Stallman and the FSF. You can also still get sued in court for violating the license.

    I realize that noone is forcing this license upon anyone, but judging from the dribble that I have read at the FSF/stallman's website, he believes it should be. (as well as the hundreds of posts relating to napster in the OSS community with something to the effect of: "information needs to be free" including music,programs,etc,etc,anything that can be turned into 1's and 0's. Sharing someone's music,program,etc. without their permission is FORCING your beliefs on to them).

    and how about some of the latest news? There's no problems in the slashdot community when a prop. protocol is broken and forced into the open source community (hence violating copyright) (http://slashdot.org/article.pl?sid=01/09/19/00132 35&mode=flat). But when the GNU is violated, you NEVER hear the END of it:

    Examples:

    1) RTLinux
    2)NVIDIA GPL VIOLATION
    (http://www.slashdot.org/features/00/05/01/00472 19 .shtml)
    3)Corel Linux GPL violation
    (http://www.slashdot.org/articles/99/09/20/10512 26 .shtml)

    im just trying to set the facts STRAIGHT

  52. Re:FSF by Anonymous Coward · · Score: 0

    IF it were a truly "free" license, it would be in the public domain, with NO restrictions.

    IF the US were a truly "free" country, I would be able to murder and enslave people, with NO restrictions. Just because it isn't public domain doesn't make it unfree. What exactly gives you the right to claim that thousands of people are offensively wrong in claiming the GPL is free? Why is YOUR definition of "free" the only right one? They believe all software should be free, and they are active in CONVINCING other people to free their software. THIS IS NOT WRONG. Until they try to force someone, you have nothing to bitch about.

    Instead of going to a copyright holder to see if it is in violation, we are going to Richard Stallman and the FSF.

    but judging from the dribble that I have read at the FSF/stallman's website, he believes it should be.

    No one went to the FSF, and the FSF explicitly said they weren't going to take any action as they didn't have the legal right. How about you actually let the FSF start acting authoritarian before you accuse them of it, for Bob's sake.

    Can you come up with ONE FUCKING INSTANCE where the FSF has tried to force someone to free code they didn't want to, except in the case of people distributing derivatives based on GPL'd code, in which case the other party HAD ALREADY AGREED to do so? Once case where they've acted like the fascists you want so hard to believe them to be? Just one? Until you have, just shaddup and stop spouting FUD.

    as well as the hundreds of posts relating to napster in the OSS community with something to the effect of: "information needs to be free" including music,programs,etc,etc,anything that can be turned into 1's and 0's.

    And what about the hundreds of posts saying the exact opposite? Or the thousands of posts somewhere in between? Contrary to your small-minded prejudices, THERE IS NO FUCKING SLASHDOT CONSENSUS! The Slashdot community is made up of a whole lot of different people with a whole lot of different beliefs. Your constant attempts to fit the beliefs of every single person who posts to Slashdot into your fantasy of a bunch of hypocritcal socialistic anarchists is offensive in its sheer stupidity, just like any other type of bigotry.

    In addition, you refuse to comprehend the concept that opposition to the media companies' constantly extending copyright law to infringe on our fair use rights, or to the absurdity of "contributory infringement," does not constitute opposition to copyright in general. In addition, you seem unable to understand that it isn't necessarily the same people posting in music discussions versus license discussions.

    There's no problems in the slashdot community when a prop. protocol is broken and forced into the open source community

    Ummm... How exactly is that a copyright violation? You can't copyright a protocol. Unless you have evidence that actual Fasttrack copyrighted code was included in giFT's code, I'd suggest you refrain from libelous remarks. Reverse engineering for interoperability isn't a copyright violation even under the DMCA. And it sure as hell isn't wrong.

    But when the GNU is violated, you NEVER hear the END of it:

    Didn't pay attention to the NVidia case. In the Corel case, they failed to understand the GPL. A bunch of people flamed them, a bunch more took the time to write them and explain that what they were doing was a copyright violation. They fixed the problem, and except for a few idiots, that WAS the end of it. Same thing is happening here. They fucked up, they fixed it. End of story.

    im just trying to set the facts STRAIGHT

    Then why do you keep posting blatant untruths?