Slashdot Mirror


The Real Reason For Microsoft's TomTom Lawsuit

Glyn Moody writes "We now know that Microsoft's lawsuit isn't just against TomTom, but against Linux too: but what exactly is Microsoft hoping to achieve? Samba's Jeremy Allison has a fascinating theory: 'What people are missing about this is the either/or choice that Microsoft is giving Tom Tom. It isn't a case of cross-license and everything is ok. If Tom Tom or any other company cross licenses patents then by section 7 of GPLv2 (for the Linux kernel) they lose the rights to redistribute the kernel *at all*. Make no mistake, this is intended to force Tom Tom to violate the GPL, or change to Microsoft embedded software.' Maybe embedded Linux is starting to get too popular."

408 comments

  1. Say It Ain't So by alain94040 · · Score: 5, Interesting

    Ok, I'll play devil's advocate for a second. Here are the relevant parts of section 7 of the GPLv2:

    If, for any reason, conditions are imposed on you that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all.

    Here's an example. The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

    You got to be careful with literal interpretation of legalese... sometimes you can push the arguments too far.

    I hope the same applies to this theory that Microsoft is forcing people to violate the GPL and therefore lose their rights to the code.

    1. Re:Say It Ain't So by FrYGuY101 · · Score: 5, Informative

      So really you lose all rights to using that code?

      You lose all rights to DISTRIBUTE that code. You can still use that code in perpetuity, though.

      --
      "If we let things terrify us, life will not be worth living."

      - Seneca
    2. Re:Say It Ain't So by Hognoxious · · Score: 5, Insightful

      So really you lose all rights to using that code?

      Only in so much as using means the same as distributing, or more specifically distributing to those countries.

      So in other words, no.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    3. Re:Say It Ain't So by Anonymous Coward · · Score: 1

      Why doesn't TomTom just stop using FAT on their memory cards and switch to one of many better formats anyway?

    4. Re:Say It Ain't So by Anonymous Coward · · Score: 5, Interesting

      Since they have to distribute the code so people can use their devices they could just switch to a free FS. As I understand (IANAL) this lawsuit mostly concerns their use of FAT for their memory cards. If they used EXT2 and bundled EXT2IFS with their windows app they might well be able to avoid a lot of the hassles from Microsoft regarding this.

    5. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      "You lose all rights to DISTRIBUTE that code."

      I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.

    6. Re:Say It Ain't So by Thuktun · · Score: 1

      The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      Let's look at that again:

      If, for any reason, conditions are imposed on you that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all.

      Though IANAL, the second "distribute" seems to be in the same context as the first. That is, if you can't distribute in some context without violating the license, you can't distribute in that context at all. I don't think the "at all" is intended to mean "in any context".

      Perhaps a lawyer could clarify this.

    7. Re:Say It Ain't So by Chaos+Incarnate · · Score: 2, Informative

      Because then users would need to install a special app on their desktop just to copy data to/from the memory card.

      --
      Benford's Corollary to Clarke's Law: "Any technology distinguishable from magic is insufficiently advanced."
    8. Re:Say It Ain't So by Predius · · Score: 1

      Using FAT means they can present the file system directly to the host machine for updates/etc. Much easier than having to run an internal file system, and establish a custom communication protocol to handle pushing and pulling files.

    9. Re:Say It Ain't So by Anonymous Coward · · Score: 2, Informative

      Here's an example. The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      No, because the GPL doesn't oblige you to sell or otherwise distribute software to Cuba or Iran, so a law prohibiting you from doing so does not conflict with your obligations under the GPL. This isn't difficult.

      Now if the law did permit you to distribute the binary code to Cuba but not the source then effectively the section would prohibit you from distributing just the binary to Cuba, but wouldn't stop you distributing it elsewhere.

      Next question?

    10. Re:Say It Ain't So by dgatwood · · Score: 5, Insightful

      And would make updating the thing nearly impossible. They do firmware updates by mounting it as a USB mass storage device. Without a hardware redesign to emulate FAT (which would probably also violate M$'s patents), they're pretty much stuck here.

      This is why I've been arguing for nearly a decade that file and volume formats should not be patentable, nor the means used to read and write those formats. Free and open access to data formats is fundamentally crucial to the interoperability of all hardware and software, and as such, statutes should very clearly define those as part of a class explicitly excluded from patent protection. As soon as the courts allow even one patent like this to stand, they are pretty much saying "f**k you" to the entire computing industry and depriving consumers of their fundamental right to have access to data of their own creation. That data isn't Microsoft's. It belongs to the users, and it is a violation of the most fundamental rights of the users to deny them access to content that they create merely because they choose to not use a particular software product, regardless of whether that product is made by Microsoft, AutoCAD, or anybody else.

      Locking down user content is fundamentally wrong and unjust, and any laws that allow a company to do so are also fundamentally wrong and unjust. Therefore, it is our right, nay, our duty to users everywhere to violate those bits of intellectual property at every possible opportunity until it becomes such a legal nightmare for these companies that they are forced to back down. Anything less would be uncivilized. I know this is no Rosa Parks moment, but it still very much necessary for the long-term viability of computing as we know it. Just say no to data format patents.

      --

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

    11. Re:Say It Ain't So by morgan_greywolf · · Score: 5, Interesting

      Forget ext2, they can use UDF, which is already supported on Windows, Linux and Mac OS X and is not patent encumbered.

    12. Re:Say It Ain't So by Rob+Riggs · · Score: 5, Insightful

      I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.

      Because the primary reason for the success of Linux is that it forces everyone to share their improvements. You get an exponential return on investment. The best you can ever hope for with BSD is an incremental return.

      --
      the growth in cynicism and rebellion has not been without cause
    13. Re:Say It Ain't So by rbanffy · · Score: 5, Insightful

      You don't need to emulate the FAT long file names in order to do that. Only the long file name hack is covered by their patents. I see no good reason to even use long file names in applications like GPS or cameras, since you don't see the files most of the time.

    14. Re:Say It Ain't So by Slumdog · · Score: 0

      Since they have to distribute the code so people can use their devices they could just switch to a free FS

      Ok, slow down. They don't HAVE to distribute the code. They can distribute the binaries, and code on demand.

    15. Re:Say It Ain't So by dgatwood · · Score: 2, Interesting

      Actually, there are plenty of patents on UDF, or at least patents on ways of implementing UDF whose performance is even slightly usable.... In other words, just making sure the UDF implementation in Linux is clear of patent issues would be a major headache. There's really no good solution for storing user data that can't potentially run afoul of patents short of convincing the courts to ban data format patents and void all existing patents in this area. It's yet another clear example of how patents are stifling innovation in the field of computing for anyone without a multi-billion-dollar patent portfolio.

      --

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

    16. Re:Say It Ain't So by MikeBabcock · · Score: 1

      UDF never did catch on for removable memory but I wish it would have. It has some obvious advantages, and its universally supported as well.

      --
      - Michael T. Babcock (Yes, I blog)
    17. Re:Say It Ain't So by mrsteveman1 · · Score: 2, Insightful

      Does UDF work well on storage like flash?

    18. Re:Say It Ain't So by DragonWriter · · Score: 1

      The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      No, because the only way you lose rights given by the GPL (which are not necessary to use code, anyway) is if the conditions "contradict the conditions of this License". Since the GPL does not require you to sell (or even give) software to anyone, rules which prohibit you from selling software to Cuba or Iran don't contradict the license. All it requires is, in essence, that you provide a specified license and make source code available to anyone to whom you do provide the software, whether you are selling it or not.

    19. Re:Say It Ain't So by morgan_greywolf · · Score: 1

      It's already being used for large flash disks.

    20. Re:Say It Ain't So by Ant+P. · · Score: 1

      Without a hardware redesign to emulate FAT (which would probably also violate M$'s patents), they're pretty much stuck here.

      Or they could use UDF.

    21. Re:Say It Ain't So by Jimmy_B · · Score: 3, Insightful

      Here's an example. The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      You have misread this section. Having a condition imposed on you which prevents you from to distributing to a specific party does not prevent you from fulfilling the conditions of the license, because the license does not obligate you to distribute the program to anyone; rather, the GPL gives the conditions you must follow when you do distribute the program. Since US export restrictions do not prevent you from fulfilling the terms of the GPL when you export to a non-restricted country, the fact that there are parties which you can't distribute the program to is irrelevant.

      Note, however, that only a government can enforce export restrictions; the GPL forbids you from taking on that responsibility yourself. So if you send a GPL'ed program to someone in Europe, they could legally send that program to someone in Cuba, and the GPL would forbid you from interfering. If the US were to pass a law which said that you couldn't export something that could possibly be re-exported to a sanctioned country, then that would be a problem for the GPL, but to my knowledge no such law exists.

      Disclaimer: I am not a lawyer and this is not legal advice.

    22. Re:Say It Ain't So by morgan_greywolf · · Score: 3, Interesting

      UDF is an ISO/IEC standard, so the format itself is not patent encumbered. Yes, ways of implementing it are, but the important thing is that Microsoft only has 3 patents that even mention UDF, and only one of those is specific to UDF. Also, IBM seems to be one of the largest patent holders on UDF implementations. I'm guessing they'd willing to launch a patent salvo against Microsoft should Microsoft try to sue someone over Linux' UDF implementation.

    23. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      >Note, however, that only a government can enforce export restrictions; the GPL forbids you from taking on that responsibility yourself. So if you send a GPL'ed program to someone in Europe, they could legally send that program to someone in Cuba, and the GPL would forbid you >from interfering. If the US were to pass a law which said that you couldn't export something that could possibly be re-exported to a sanctioned country, then that would be a problem for the GPL, but to my knowledge no such law exists.

      Just so you know, there ARE laws preventing this if you do it willfully (in an attempt to evade export restrictions) or negligently (you should have known someone ELSE was attempting to do so).

    24. Re:Say It Ain't So by morgan_greywolf · · Score: 1

      Not so. Read the linked-to article.

    25. Re:Say It Ain't So by dgatwood · · Score: 3, Interesting

      The problem is that these extensions aren't just used for long file names. IIRC, extra directory records in the FAT filesystem are also overloaded for other purposes like permissions, without which Linux et al would be unbootable off of FAT. I'd imagine that many of those uses would run afoul of the patent, but I could be wrong.

      More to the point, if it only applies to its use for naming purposes and not to the concept of storing additional data about a file in additional directory entries with reserved type codes that older OSes ignore, then the invention should have been unpatentable anyway, as there's nothing particularly original about taking the Rock Ridge extension set from ISO-9660 and applying the exact same concept to FAT except insofar as it uses additional directory entries. That's literally all they did here. Instead of an additional entry in the system use area of the variable-length directory record, they use additional directory entries with a different type code, but that's basically caused by differences in how the filesystem describes a file....

      --

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

    26. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Only in so much as using means the same as distributing, or more specifically distributing to those countries.

      You don't even lose the right to distribute the code (generally speaking). The GPL, after all, does not require you to provide the source code to *everyone*: only to those who received binaries from you. There is nothing in the GPL that would preclude anyone from making the code available to third parties, obviously, but YOU are NOT required to do so yourself.

      So in the case of an open source embargo against another country, there'd be absolutely no problem at all - you'd only be obliged to send them the source code if you already sent them binaries, but as long as you didn't do so, everything would be fine. (In fact, given the embargo, chances are you'd want to take all reasonable steps to ensure they would NOT get binaries from you.)

    27. Re:Say It Ain't So by Anonymous Coward · · Score: 5, Informative

      I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.

      Maybe because companies like Microsoft have a history of stealing BSD code, making minor changes, and then patenting their implementation. This is why Ted Tso' said he would use the GPL for Kerberos instead of the BSD license if he had it to do over again.

    28. Re:Say It Ain't So by malkavian · · Score: 1

      In the case of TomTom, you mean the TomTom software application that starts up every time the device is connected?
      I see no problem with that.
      Also, there are windows drivers that let you mount EXT2 partitions as well.. So that could be included in the package for anything wanting to use EXT2..
      I fail to see why everyone uses FAT, apart from that it's very simple to implement (giving a very small memory footprint requirement for embedded devices). If it gets to be an issue (patent threats, for example), then simple. Change your format to EXT2.
      Most, if not all embedded devices, such as cameras, GPS systems etc. have more than enough memory and processing power to handle EXT2.

    29. Re:Say It Ain't So by ultranova · · Score: 1

      Here's an example. The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      No. After all, you have no duty under the GPL to distribute to Cuba or Iran in the first place. The GPL only states under what conditions such distribution must occur if it occurs: you must give them the source code, which stays under the GPL, so they have all the same rights you did.

      Now, if the US government forbade you from giving the source to Cuba, then you couldn't distribute to Cuba at all. However, you could still distribute to anyone else, who could then distribute to Cuba.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    30. Re:Say It Ain't So by lazy_playboy · · Score: 1

      They HAVE to distribute the code on demand.

    31. Re:Say It Ain't So by Tanktalus · · Score: 0

      Other than USB memory sticks, most USB devices seem to require a special app anyway. Even when it's just a VFAT device that can be accessed by simply mounting it on Linux. So, I don't see the problem, other than, perhaps, actually producing said "driver" (which probably also is mostly GPLd already).

    32. Re:Say It Ain't So by Forge · · Score: 1

      not that simple. Right to distribute Code == Bineries OR source. Loosing that right means they cannot distribute the binaries or the source.

      --
      --= Isn't it surprising how badly I spell ?
    33. Re:Say It Ain't So by remmelt · · Score: 1

      Wait, is that like one of those pyramid schemes? I've heard about those.

    34. Re:Say It Ain't So by Chaos+Incarnate · · Score: 1

      My understanding was that while you can hook the device up via USB, you can also just drop the updates directly on a memory card via a standalone reader without ever hooking the TomTom up to your computer (and thus without installing or using the application).

      --
      Benford's Corollary to Clarke's Law: "Any technology distinguishable from magic is insufficiently advanced."
    35. Re:Say It Ain't So by JerkBoB · · Score: 5, Insightful

      Right, but then everybody gets your improvements. Where's the competition in that?

      With BSD you get a solid base for your product and it's not infected with the GPL.

      This old clinker again... Closed-source competition is so 1980s.

      Software is a commodity. Any intelligent company now is not trying to make money on their proprietary code. They're making money on hardware to run their code, or services to support their code, or data to feed their code.

      Sure, for certain niche markets, closed source can give a company a competitive advantage for a while... But if the market is "hot" enough, Open Source will eventually be there to eat its lunch. This has been happening over and over again for the past two decades. Were you asleep?

      Let me ask you this: Have you ever written code and released it to the public? Was it used? I have. As a developer making contributions to public projects, I am much more inclined to contribute under the GPL than other licenses. Most of the world feels the same, hence the popularity of the GPL (and similar "viral" licenses) over the BSD-style licenses.

      --
      A host is a host from coast to coast...
      Unless it's down, or slow, or fails to POST!
    36. Re:Say It Ain't So by theillien · · Score: 2, Insightful

      I'm wondering if a patent can become so diluted that it is unenforceable. FAT is ubiquitous. It is used just about everywhere in every industry in innumerable devices. If Microsoft were to fight to enforce their patent they'd essentially be taking on the entire IT space. I doubt the courts would allow that to happen.

    37. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      You get an exponential return on investment

      That's what the bankers promoted and look at the American economy now.

    38. Re:Say It Ain't So by Anonymous Coward · · Score: 1

      Most GPS devices act as media players too. This is why they're using FAT, whether it be an internal drive that is mounted on a computer and shows up like a USB stick, or access to external devices themselves, where one may have a firmware update waiting. FAT, although shit, is the unfortunate de-facto standard for external drives not needing to exceed 4GB files. Just because us linux/bsd uses wipe devices and use left-field filesystems for fun, the general consumer does not, and certainly not something any consumer electronic device manufacter will do.

      What is needed is for all the manufacturers to agree to use the same unencumbered opensource file system, and start rolling it into devices. A filesystem that can happily run in userland, not one tied to a kernel, allowing doze users to use the device. Nah, use a GPL and piss off doze users. They're nothing but problems generally.

    39. Re:Say It Ain't So by Anachragnome · · Score: 5, Interesting

      "Therefore, it is our right, nay, our duty to users everywhere to violate those bits of intellectual property at every possible opportunity until it becomes such a legal nightmare for these companies that they are forced to back down. Anything less would be uncivilized. I know this is no Rosa Parks moment, but it still very much necessary for the long-term viability of computing as we know it. Just say no to data format patents."

      This is precisely the tactic I encourage everyone I know to use.

      These people are no longer playing fair, WHY SHOULD WE?

      In this day and age, corporations are, quite simply put, walking right over common sense. There is no more "customer service", but rather corporations simply see us all as resources to be mined.

      When these people no longer see reason, no longer work to provide a product without stifling the competition, then "Intellectual Disobedience" is the ONLY route left to address the situation.

      Speak with your mind, voice and dollar, in that order.

    40. Re:Say It Ain't So by Anonymous Coward · · Score: 5, Informative

      I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.

      Because the primary reason for the success of Linux is that it forces everyone to share their improvements. You get an exponential return on investment. The best you can ever hope for with BSD is an incremental return.

      The primary reason for success of Linux is a combination of timing and luck. When the BSD project's viability was in serious question due to the AT&T lawsuit, Linux hit its stride.

      Moreover, your response demonstrates a common fallacy: the idea that, if not forced to share improvements, companies will not do so.

      The reality -- as usual -- is much more complex:

      • The cost-benefit of analysis of failing to share re-usable improvements to BSD licensed code is fairly simple -- it costs quite a lot to maintain sizable private changes. Merging your code into the primary code base decreases maintenance costs and pushes the effort to the larger development community
      • Many corporations will not invest in GPL'd software if it can be avoided, as they often won't be able to use it. How many contributions does GPL software *lose*?

      I would argue that Linux has succeeded *in spite of* the GPL. Speaking with those in the embedded hardware industry, it's clear that Linux has a foothold because of its brand name, not because of significant technical differentiation. Many embedded hardware vendors -- even the major ones -- don't even understand the implications of the GPL! (see the Linksys GPL violations)

      If you observe the BSD projects, you'll note that features, bug fixes, and developer time is often provided by corporations that leverage the BSD licensed code in otherwise closed source products.

      To quote Juniper's VP of Foundation Technologies, Naren Prabhu:

      Juniper benefits from the powerful collaboration between leading universities, individuals, and commercial organizations developing FreeBSD to advance the operating system functionality. The FreeBSD release system provides Juniper with a roadmap for features and a stable base for our code, while its practical licensing enables Juniper to develop intellectual property for advancing high-performance networking. Juniper employs many active FreeBSD developers that continually contribute to the FreeBSD project to further its development as a leading operating system.

      I wouldn't be so quick to point to the GPL as a recipe for success. When you force individuals to choose between your way or the highway, many of them will choose the highway. The BSD project's more pragmatic stance has allowed corporations to contribute as they are able to do so, and has resulted in an extremely productive, ongoing relationship with commercial software vendors.

    41. Re:Say It Ain't So by Anonymous Coward · · Score: 0, Troll

      What are you having for lunch?

      It isn't web browsers, since IE continues to dominate. It isn't office software, since MS Office continues to dominate. It isn't photo editing, video editing, sound editing, graphics software, file formats, file systems.

      Not on the web, where Flash and Java reign. Not email either on the client or server side. CAD software, no. Automation, no. Enterprise databases, no. Music, no. Cell phones, no. You might be doing well in embedded devices but judging from this move by MS, combined with Stallman's poison pill against Tivo, that probably won't be true for long.

      You have a good hold on web servers, I'll give you that, but I'd think you'd tire of the same dish for every meal.

    42. Re:Say It Ain't So by RiotingPacifist · · Score: 2, Interesting

      If they used EXT2 and bundled EXT2IFS with their windows app
      Lets see if you read it this time

      --
      IranAir Flight 655 never forget!
    43. Re:Say It Ain't So by Ded+Bob · · Score: 1

      According to this piece, Microsoft avoided the MIT license for unknown reason(s) and wrote their own code anyway. GPL would not have stopped them at all.

    44. Re:Say It Ain't So by Anonymous Coward · · Score: 2, Insightful

      Good rant, but I think the above post was trying to say EXT2IFS are windows drivers that allow you to access ext formatted drives. All TomTom has to do is supply those drivers on their install CD and presto problem solved. I've got a lot of usb devices formated ext2, because NTFS support wasn't too cool in linux for a while and I needed large file support.

    45. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      IIRC, extra directory records in the FAT filesystem are also overloaded for other purposes like permissions, without which Linux et al would be unbootable off of FAT.

      Since umsdos filesystem was shipped in 1994, Microsoft's Patient might well be invalid if this reasoning is correct.

    46. Re:Say It Ain't So by Davorama · · Score: 1

      Why wait? IBM is probably already at risk from the current FAT suit. They should send a UDF shot across MS's bow now.

      --

      Davo -- Free speech, free software, AND free beer.

    47. Re:Say It Ain't So by Nimey · · Score: 5, Insightful

      Wrong. FAT does not support permissions of any kind. VFAT adds long file names, which is done by using half of a given directory's entries for long filenames and the remainder as the standard 8.3 short names.

      If you were talking about FAT attributes (archive, read-only, hidden, system, volume label), those are done with flag bits.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    48. Re:Say It Ain't So by Man+On+Pink+Corner · · Score: 4, Informative

      UDF is an ISO/IEC standard, so the format itself is not patent encumbered.

      Um, that doesn't mean it's not patent encumbered. MP3 is patent-encumbered all to hell, and it's an ISO/IEC standard.

    49. Re:Say It Ain't So by russotto · · Score: 1

      You're right. A settlement with Microsoft where TomTom licensed the patents in question wouldn't trigger any GPL violations, provided TomTom remained free to distribute source to anyone who bought a TomTom, and grant a license (a _copyright_ license) to redistribute source and binary to anyone who bought a TomTom. Microsoft could continue to go after the redistributors, but as long as they didn't require TomTom to do so, TomTom would not have violated the GPL.

      If the code was GPL V3, then licensing with Microsoft would trigger a violation, but not GPL V2.

    50. Re:Say It Ain't So by ollywompus · · Score: 0

      "The best you can ever hope for with BSD is an incremental return." Unfortunately though, that incremental return may start to look a lot more attractive when factored against the monumental loss that patent wars with a company like Microsoft may cost you. Even if long term GPL-style licensing has a higher return, you have to survive as a company long enough term for that to apply. If Microsoft sues the bejesus out of anyone using that code, then companies will sacrifice that long term gain for short term stability, aka a BSD-style license. That being said, I'm not convinced that a BSD-style license would be the answer here anyway, but patent litigation is not cheap, so even if it's a partial deterrent to closed source patents, companies may jump on it. Now, my question to you licensing gurus: what does this mean for the overall Linux ecosystem? If Microsoft gets this patent enforced, are we looking at an MPEG style situation? Where distros start removing FAT support out of the box? THAT would truly be a disaster, as it's just one more hurdle for the average person to install and use Linux on a regular basis.

      --
      -- "We're only gonna die from our own arrogance, that's why we might as well take our time..." -Bad Religion
    51. Re:Say It Ain't So by OeLeWaPpErKe · · Score: 1

      UDF is for non-eraseable media "only". That's not to say it can't be used at all for things like usb sticks, but it would be unwieldy in the extreme.

    52. Re:Say It Ain't So by arkhan_jg · · Score: 4, Insightful

      Why not got one further, and simply ban software patents of all kinds, like most other countries in the world?

      Software is covered by copyright; there's no need to grant patents on it too. Filesystems, like many other software concepts are relatively easy to come up with, on a broad basis - and the same general patent covers many, many approaches and denies them to competitive forces for way too long. The clever, hard work is in actually implementing the idea and making it work.

      Patents were originally intended so that someone could come along, read the patent, and easily replicate the entire product, once the monopoly period was over, and the inventor compensated for putting his work into the public domain. The equivalent for software, direct instructions on how it works - is the code and documentation itself, not some vague patent intentionally designed to cover as many possible variations upon the idea as possible.

      Software patents are solely about preventing competition and raising the bar to entry for smaller, innovative firms. When engineers are specifically instructed to never, ever read patents in case they get sued for subsequently implementing anything that vaguely touches on a similar area; when this happens, patents are actively harmful to innovation and endeavour. Get rid of them, as pretty much every other country in the world has done.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    53. Re:Say It Ain't So by gbjbaanb · · Score: 1

      Wait, is that like one of those pyramid schemes?

      Its the GPLv4:

      by accepting this licence you agree to:
      * remove the name of the person you received this code from, and send him a cheque or alternative valued at $0.
      * add your own name to the licence
      * send this to 5 other people not on the list

      something like that :)

    54. Re:Say It Ain't So by Teun · · Score: 2

      So what if they are used as madia players?

      There are many USB gadgets that require you to first install a driver before plugging them in and be usable.
      Even right now you need to install drivers to update and organise a TomTom Navigator.
      Once ext2ifs is installed any ext2 USB device will by Windows be recognised and treated as native.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    55. Re:Say It Ain't So by morgan_greywolf · · Score: 1

      Okay, well, I did a Google patent search for Universal Disk Format, and AFAICT, no one has a patent on the format. I invite you to try for yourself.

    56. Re:Say It Ain't So by adiposity · · Score: 1

      Any intelligent company now is not trying to make money on their proprietary code.

      Maybe that's so, but I don't know how you can be sure. Granted, Microsoft has made some bad decisions, but I'm pretty sure they are "trying to make money on their proprietary code" and it's working. In fact tons of software companies make money on closed source. Or you do you mean selling the actual code and not the finished product?

      -Dan

    57. Re:Say It Ain't So by nabsltd · · Score: 1

      Other than USB memory sticks, most USB devices seem to require a special app anyway.

      Although most USB devices seem to come with a special app that you can install, very few of them absolutely require it.

      Most generic music players and cameras work just fine acting as mass storage devices. I even have a GPS that supports DRM-encumbered music and audio books, and the special app was only required once--to read the serial number off the GPS and send to the server so that future downloads will have the correct encryption applied.

    58. Re:Say It Ain't So by Bradley · · Score: 2, Insightful

      What if I'm in the Canada, and buy (from a US company) a GPL program which comes with a written offer to provide the source. Then a month I move to Cuba, and send a letter to the US company asking them to please send me the source (including proof of purchase, and cash to cover costs of copying and sending the source code back to me)

      What does the US company do now?

      I'm not a lawyer, and for all I know US law deals with this sort of situation. But assume that it doesn't (and assume that I can't, for some other reason, distribute the source and binary together)

      Since any of my customers could move to Cuba/etc, I cannot make the promise for written source, so I cannot be sure that I can "satisfy simultaneously [my] obligations under this License and any other pertinent obligations". which means I can't distribute the software at all.

    59. Re:Say It Ain't So by SanityInAnarchy · · Score: 1

      The closest thing to Linux file permissions, of the kind you might be able to boot Linux off of, was umsdos, which is probably what you're thinking of. I think that's actually incompatible with vfat, and runs directly on fat itself.

      --
      Don't thank God, thank a doctor!
    60. Re:Say It Ain't So by Khyber · · Score: 1

      "Because then users would need to install a special app on their desktop just to copy data to/from the memory card."

      As if other companies don't sneak shit past you without your fucking permission anyways - e.g. EA/SecuROM. They could just make it 'part of the installation' and be done with it.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    61. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Since they have to distribute the code so people can use their devices they could just switch to a free FS.

      ehhh careful there selling a product that implements code isn't the same as 'distributing' code.

      tomtom isn't distributing code by selling their gizmo's anymore than steam is distributing code when you buy TF2, there is a differnce between giving source code, and using a complied binary.

    62. Re:Say It Ain't So by SanityInAnarchy · · Score: 1

      I don't see UDF mentioned on any of the three linked-to articles. Which are you talking about?

      --
      Don't thank God, thank a doctor!
    63. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      They do firmware updates by mounting it as a USB mass storage device.

      So? That does not prevent their firmware-upgrader application from mounting it as an ext2 fs. To the user this wouldn't make any difference, even shielding him/her from accidentally writing to the filesystem, because FAT is visibly mounted on a X: drive letter. They should take this patent BS as a chance to boot MS and it's crappy technology from their devices IMHO.

      This is why I've been arguing for nearly a decade that file and volume formats should not be patentable ...

      Not arguing with any of that, but software/algorithms (=math) should not be patentable, period.

    64. Re:Say It Ain't So by Dan+Ost · · Score: 1

      What patent protections do you receive if you use BSD over GPL?

      I'm pretty sure you don't get any.

      Please explain how I missed your point.

      --

      *sigh* back to work...
    65. Re:Say It Ain't So by morgan_greywolf · · Score: 1

      The Wikipedia article linked to in my post.

    66. Re:Say It Ain't So by Man+On+Pink+Corner · · Score: 2, Insightful

      I'm not saying UDF is encumbered; I have no idea if it is. I'm saying the fact that it's got an ISO/IEC number does not mean it's not encumbered. Just didn't want anyone to get the wrong impression from your earlier comment.

    67. Re:Say It Ain't So by Lord+Bitman · · Score: 1

      being able to express something in high-level branches of math-like things does not make it "math". There is nothing fundamental to the structure of the universe which defines SHA-1. The idea of "math can't be patented" is because /discoveries/ can't be patented, only inventions. (recent abuses are a separate issue).

      --
      -- 'The' Lord and Master Bitman On High, Master Of All
    68. Re:Say It Ain't So by History's+Coming+To · · Score: 0

      Precisely. Couldn't agree more. We don't need to fight these gruppets in the same way that we don't need to fight the creationists. They're irrelevant. We've got something better and free...let them carry on all they want, I'm quite happy with my superior and patent free OS thank you very much. If people want to pay for it let them, but I'm not going to waste my time and effort protecting the stupid from the greedy.

      --
      Please consider this account deleted, I just can't be bothered with the spam anymore.
    69. Re:Say It Ain't So by mcgrew · · Score: 1

      IINM the GPL says you have to provide the source with the product.

    70. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      That's easy. They tell you that you're the one who changed your situation, and that so soon as you move to a country with which they can do business they'll send you the source. They'll also probably tell you that you're free to get the source from mirror X that's already in Cuba via some third party, because someone got the source from the US in a country that doesn't bar business with Cuba.

    71. Re:Say It Ain't So by Patch86 · · Score: 4, Insightful

      The GPL and BSD licenses fulfil completely different purposes, and attract different contributors because of it.

      You can't declare either license the "winner" without first deciding what it is they're competing in. If you want the biggest, most widely used cross-platform free software, GPL wins- Linux's desktop share beats any of the *BSDs, and it has massive penetration in embedded devices, webservers and cross-platform applications. If you want the biggest, most widely used platform full stop, BSD wins- MacOSX has a colossally larger desktop share than Linux (but is of course mostly non-free), and BSD code can be found in almost any project you care to mention.

      For people and big companies who want their free contributions to remain free, the GPL is far more attractive (just ask all those Linux vendors). For people who just want to see technology get out there and be used, BSD is the drawer.

      The 2 camps can't both be pleased at the same time, and that's why the 2 licenses can exist side-by-side. Acting like the GPL is detrimental to Linux (or the same with BSD) is just plain ignoring the reality of the situation.

    72. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      File and volume formats are simply a matter of where the data is stored. Imagine a patent on notebook paper storage format. There are lines and you write between them. I'll patent that and nobody will be able to write between the lines on notebook paper.

    73. Re:Say It Ain't So by SanityInAnarchy · · Score: 2, Informative

      Wrong. Linux is successful because it was there, at the right place, at the right time. HURD was decades from usability, though it still looked like it might be just around the corner. BSD was, according to another poster, involved in some sort of lawsuit with AT&T. Minix was simply copyrighted, with no right to redistribute.

      So your choice was, pretty much: Buy an 8086 and a copy of Minix, and then download a bunch of patches, install the Minix source code, apply the patches, recompile, and reinstall, and still not have quite the feature set Linux did, but don't you dare distribute your changes as anything other than a patch...

      Or save your money and buy a much faster 386, get a copy of Linux for free, and go play.

      Or go use DOS.

      As for the GPL vs BSD, I can tell you from experience that even the smallest of companies isn't going to be "caught" by the GPL and "forced" into anything. In fact, just the opposite -- we were using extjs, which was under a more liberal license. It was then switched to GPL -- and worse, the author tried to claim that the GPL also applied to the server it was connecting to.

      So our choice was to either at least GPL all our JavaScript, or buy a license. Or the third option: Say "fuck extjs" and switch to jQuery. It was painful, but in the end, we have something where we know the rug won't be pulled out from under us.

      And while I haven't contributed a lot back to jQuery, I have sent patches back to projects like Capistrano, Ruby on Rails, Castronaut, and other little libraries and tools. What you'll notice is, none of these are GPL -- they're almost universally MIT-licensed. In fact, given a GPL version and an MIT version, I'll usually try the MIT version first.

      Which means GPL is actually a disadvantage, if you're looking for commercial support. Yes, I could keep all my improvements to myself. But if I avoid your software altogether because it's GPL'd, I may as well have -- you get exactly zero code back either way. If your software is MIT'd, maybe I keep some of my improvements to myself -- but it makes much more sense for me to send some back -- after all, it's really not cost-effective for me to be maintaining Capistrano at this point.

      And keep in mind -- this is mostly stuff that I'm being paid to do. If I'm just playing around in my spare time, or if it's a completely, physically separate project (Capistrano might be a good example) that never links against code we really care about, I have no problem using and contributing to GPL'd code.

      But when I'm writing a brand-new program, I like to have the option to license it however I want, from public domain to a corporate EULA. The LGPL mostly allows that, the GPL doesn't allow it at all.

      --
      Don't thank God, thank a doctor!
    74. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Microsoft have a history of stealing BSD code

      How exactly do you steal BSD code? As long as you provide attribution (and then, only if you are distributing the code), you're free to do with the code as you wish.

    75. Re:Say It Ain't So by Lennie · · Score: 2, Informative

      Euh... Nokia is/has released Symbian as open source. I think we can say Cell Phones is something which has been concurred. LCD-TV's is also a field where Linux is doing well: Sony, Mitsubishi, LG, etc. are selling TV's based on Linux. Most ISPs run their e-mail servers on Linux or BSD with open source POP- or IMAP- and SMTP-software. I could go on, but I do want a life. ;-)

      --
      New things are always on the horizon
    76. Re:Say It Ain't So by FrankieBaby1986 · · Score: 1

      ...establish a custom communication protocol to handle pushing and pulling files.

      FTP?

      --
      ERROR: SIG NOT FOUND (A)bort, (R)etry, (F)ail?:
    77. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      because /discoveries/ can't be patented, only inventions

      And that's exactly why software cannot be patented, it's just a way of finding, discovering if you will, an efficient and/or elegant way of implementing a solution for a problem. I do not disagree that intricate algorythms like SHA are not an invention, but don't those inventions come mainly from state-sponsored institutions like universities anyway. And who's going to arbitrate fairly what is really an invention anyway, the Texas PO right? Therefore I'm just for the simple rule, *software is not patentable*, period. Could you tell me what you think are arguments in defense for sw patents? Until then my opinion is pending, like their crappy patents ;-)

    78. Re:Say It Ain't So by Predius · · Score: 1

      Ok, so now you've got to speak IP at some level over your USB link, AND make sure you don't conflict with the existing IP setup on the client machine, ever. Plus, because you're emulating a network link, you've got software firewalls to worry about as well.

    79. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      So you are suggesting they should violate the GPL?

    80. Re:Say It Ain't So by Hucko · · Score: 1

      Is it actually impossible to do firmware updates of ext? Not being trollish I hope; I do understand that currently *everyone* uses fat... but can we change?

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    81. Re:Say It Ain't So by JerkBoB · · Score: 1

      Maybe that's so, but I don't know how you can be sure. Granted, Microsoft has made some bad decisions, but I'm pretty sure they are "trying to make money on their proprietary code" and it's working. In fact tons of software companies make money on closed source. Or you do you mean selling the actual code and not the finished product?

      Listen, I'm not saying that OSS will completely kill proprietary software. What I am saying is that it has and will continue to destabilize existing markets, while it creates and enables new ones.

      For some specific niches, closed-source software can provide a competitive advantage, at least in the short term. But in many cases, software is just a loss-leader for other stuff like hardware, services or proprietary data sets. It just doesn't make sense to pay a whole staff of developers to reinvent an Open Source wheel.

      In the case of Microsoft, I think that times are going to be tough over the next few years. They've got a huge pile of cash to ease the pain, though. I think a lot of that has more to do with the shift toward lightweight computing and cloud services, though.

      --
      A host is a host from coast to coast...
      Unless it's down, or slow, or fails to POST!
    82. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      When TomTom just wants to pay Microsoft to be able to use their patents they are violating the GPL. They don't violate BSD License though. That is why BSD was mentioned here.

    83. Re:Say It Ain't So by Dogtanian · · Score: 2, Funny

      Ironically, this article is about an 'Open' software license from a movement that is all about 'Freedom', and how TomTom doesn't have the right to exercise that 'Freedom'.

      You know... I do believe that you must be the *very first person* to have realised that the GPL's perpetuation of certain freedoms is done by curtailing certain others at source, and to have contrasted this with BSD's approach.

      Let's use this as the start of an original and stimulating discussion on the subject. Or then again, heed the words of an exceptionally wise man and let's not.

      Also, an interesting thought that just occurred to me is that GPL has its own RIAA/MPAA/MediaSentry thing going, of course the EFF and FSF have not been evil, yet ...

      Your ideas are intriguing to me and I wish to subscribe to your newsletter.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    84. Re:Say It Ain't So by Anonymous Coward · · Score: 1, Insightful

      So if Microsoft stole the code for Kerberos, why can download it here?

      The double standard here is really funny. When it comes to RIAA and Pirate Bay then using the term "stealing" is bad. But when it comes to using code in a way that it was allowed to be used, then you get modded informative for using that term.

      So one question to you: Is Google stealing GPL code? They surely have lots of modifications to GPL code they will never publish, but as with Microsoft noone requires them to.

    85. Re:Say It Ain't So by Hucko · · Score: 1

      IIRC Microsoft didn't comply with the restrictions you stated.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    86. Re:Say It Ain't So by metamatic · · Score: 1

      So our choice was to either at least GPL all our JavaScript, or buy a license. Or the third option: Say "fuck extjs" and switch to jQuery.

      Or presumably the fourth option, fork it.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    87. Re:Say It Ain't So by justthinkit · · Score: 1
      VFAT adds long file names, which is done by using half of a given directory's entries for long filenames and the remainder as the standard 8.3 short names.

      There is no simple ratio between short and long filenames on a FAT volume. Three-quarters of the way down a pretty hefty page, Wiki says:

      Long File Names (LFN) are stored on a FAT file system using a trickadding (possibly multiple) additional entries into the directory before the normal file entry.

      and later clarifies that up to 20 additional directory entries can be used to express a single LFN.

      Also, as wiki states later on:

      If a filename contains only lowercase letters, or is a combination of a lowercase basename with an uppercase extension, or vice-versa; and has no special characters, and fits within the 8.3 limits, a VFAT entry is not created on Windows NT and later versions such as XP.

      --
      I come here for the love
    88. Re:Say It Ain't So by Hucko · · Score: 1

      So you are clever enough to know how to use it as a mass storage device...

      Now, all the users I know only do things the 'official' way. The amount of times I have surprised people by 'just plugging it in' gets very wearying. They are always accompanied by comments like "...are you some kind of computer guru? (I am *their* computer technician damn it!) So you're good with computers then?"

      The point is people don't even grasp the basic potential of computers. So we lead them. If you need it everywhere, I'm sure you can come up with a suitable solution.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    89. Re:Say It Ain't So by Belial6 · · Score: 1

      That's what I've been thinking. They can use Fat 12/16 to store the file system install if they want, so they don't even need to distribute a disk.

    90. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      IIRC Microsoft didn't comply with the restrictions you stated.

      Well then they didn't steal any code. They violated a licensing agreement.

      After all, this is /., where "theft != infringement".

    91. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      And how do they offer this driver to the user? Via a FAT partition?

    92. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.

      Maybe because companies like Microsoft have a history of stealing BSD code, making minor changes, and then patenting their implementation. This is why Ted Tso' said he would use the GPL for Kerberos instead of the BSD license if he had it to do over again.

      Plenty of other companies are more reasonable:

      Juniper - FreeBSD
      Isilon - FreeBSD
      NetApp - FreeBSD
      Apple - FreeBSD
      Force10 Network - NetBSD

      Perhaps the reason why Kerberos (and BSD's TCP/IP stack and X11 as well) were incorporated in so many places is because of the liberal license? If commercial companies had more restrictions on the use of the code, do you think would have spread as much as they did?

    93. Re:Say It Ain't So by jakykong · · Score: 2, Interesting

      Nobody is standing in our way right now -- but of course, "intellectual disobedience" (that is, refusing to accept bad patents or trampling of our rights by "rights holders") is one way to keep a future away where someone is in our way. If that future came, I don't want to say "I just stood around while it happened".

      They don't need to give up everything. They can exist. They may turn a profit (whether the can is another story...). They can make all the software they want. But here's the real issue:

      I would be very willing to pay $50 for a good operating system, with source code, that did not have activation, didn't phone home behind my back, didn't require 80% of my system resources to run, and wasn't made by a company that tries to strong-arm me at every turn.

      I am not willing to pay $200+ for a shoddy operating system, without source code, that requires activation (and worse: may be deactivated), phones home behind my back, eats system resources like popcorn, and is made by a company that tries to strongarm me at every turn.

      I'm not opposed to microsoft because they cost money. No. I'm opposed to microsoft because they're against me. And I will gladly trample on their "intellectual property" if it shows them that their customers matter.

    94. Re:Say It Ain't So by shutdown+-p+now · · Score: 1

      No, it doesn't. You are given an option of either doing that, or, as GP noted, supplying an offer to provide the source upon request.

    95. Re:Say It Ain't So by ignavus · · Score: 1

      The nice thing about the world is: people who want to use BSD - for whatever reason - can. And people who want to use Linux - for whatever reason - can.

      Just like KDE vs Gnome vs XFCE vs ... and just like emacs vs vi.

      Use what you want.

      (PS: did you not know that Linux and BSD are part of a big social experiment? Set up two different projects, run them for several decades, and see which one(s) actually work. Maybe both of them will succeed.)

      --
      I am anarch of all I survey.
    96. Re:Say It Ain't So by sortius_nod · · Score: 1

      Not all of us live in the backwards land you call the USA. So really, this only effects a country that's more of dead weight to the world than a leading entity.

      I know I'll get modded flamebait, but I'm so sick of this US-centric view that's perpetuated on open discussions. Maybe think outside your indoctrinated narrow view for just a second to realise the word doesn't reflect US opinion or sentiment.

      If Americans can't do this, be prepared for a nice big slap in the face in the near future. The whole anti-communism, anti-arab, pro-protectionism crap that gets spun by US citizens merely reinforces the stereotype that Americans are gun-toting, small-minded, religious nuts.

      Wake up or you'll be woken up by the international community.

    97. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Its obvious. F/OSS cheerleaders know they cant win in the market so they resort to creating animosity towards Microsoft.

      In the 80's whenever someone started to convince you to turn against a company for being against your "freedom" or how the "evil" company was stifling the little guy or doing it for the "greater good" and similar happy sounding phrases you would think they were on drugs. Now we call them the F/OSS - Internet Attack Squad. You will find them mentioning DRM in almost every MS related story or mentioning how they just installed linux on their neighbours brothers dog's PC. (This is not really true. dogs cant use computers, yet) You will find them routinely exaggerating capabilities of GPL based software and at the same time downplaying/badmouthing non-free software for no other reason that its not free. These are the same guys that will do whatever it takes to bury the truly interesting and insightful comments and mod up "Windows Sucks" comments or your usual fake and contrived this-one-time-windows-crashed stories.

      Obviously MS is no no way in danger of any of these morons actually harming them, its actually going to end up destroying slashdot and the sane people jumping ship to Ars technica - A much better website with more technical contributors and original content.

    98. Re:Say It Ain't So by Hucko · · Score: 1

      yeah fair enough. It is so easy to degenerate int RIAA type thinking.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    99. Re:Say It Ain't So by Drgnkght · · Score: 1

      What part of "install CD" was too difficult to read?

    100. Re:Say It Ain't So by SanityInAnarchy · · Score: 1

      That is true.

      However, forking is quite a lot more work than migrating our own code to something else, and still letting the rest of the world maintain it.

      Not that we never forked anything, these were just usually tiny Github projects, always with the intention that they'd be merged eventually.

      --
      Don't thank God, thank a doctor!
    101. Re:Say It Ain't So by clampolo · · Score: 2, Insightful

      There is a theorem in computability theory that anything that can be computed in software can be implemented as a digital circuit. Also anything that can be computed in a digital circuit can be computed in software.

      So by arguing against software patents, you are also stating that there should be no hardware patents.

      I just wanted to make this point since I don't understand why people are against software patents but not hardware patents. Mathematically speaking the two are identical.

    102. Re:Say It Ain't So by idlemachine · · Score: 3, Insightful

      These people are no longer playing fair, WHY SHOULD WE?

      "He who fights with monsters should look to it that he himself does not become a monster."

      Or how about: "Two wrongs don't make a right."

      Because how you win is as important, if not more so, than winning itself. I agree that there are times that we need to fight but we also need to be sure we don't lose ourselves in the battle.

    103. Re:Say It Ain't So by pwizard2 · · Score: 1

      Here's an example. The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      However, if you put your code up for free public download and someone from Cuba or Iran happens to come along and get a copy, then that is hardly your fault. You didn't personally give it to them; they simply acquired a copy that was meant for anyone who happens to want it, regardless of point of origin.

      What about the opposite situation? Can an American citizen be forbidden from using open source code that was downloaded from a neutral third party yet originated from a country like Cuba or Iran? If you're an American and use code from that project in your open source project and redistribute it, does the whole thing become "Americanized?" Just curious.

      --
      "It is a denial of justice not to stretch out a helping hand to the fallen; that is the common right of humanity."
    104. Re:Say It Ain't So by Bradley · · Score: 1

      and which part of the GPL allows you to do that? Yes, in practice I'm sure that that would happen, but that's not the point.

    105. Re:Say It Ain't So by Kalriath · · Score: 1

      and BSD code can be found in almost any project you care to mention.

      Including Windows, and I think there's BSD in parts of most Linux distros too.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    106. Re:Say It Ain't So by Kalriath · · Score: 1

      Wrong. The only rule in BSD is attribution, and if you run strings on the Windows binaries, the copyrights of the regents of UC Berkeley is all over bits of it (TCP/IP, FTP, pretty much the rest of the network stack, etc). BSD doesn't require distribution of the code, AT ALL.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    107. Re:Say It Ain't So by jhol13 · · Score: 1

      There are many crappy USB gadgets that require you to first install a driver and several adware/crapware add-ons before plugging them in and be usable.

      Now it is closer to truth.

      There should be absolutely no reason to install anything to get mp3 player working.

    108. Re:Say It Ain't So by jeremypv · · Score: 1

      There should be absolutely no reason to install anything to get mp3 player working.

      Tell that to Steve Jobs and his "mp3" players

      --
      ~jeremypv
    109. Re:Say It Ain't So by Logic+Worshiper · · Score: 1

      Protecting the helpless from the greedy is one of the most noble callings in this life.

    110. Re:Say It Ain't So by williamhb · · Score: 2, Insightful

      "Therefore, it is our right, nay, our duty to users everywhere to violate those bits of intellectual property at every possible opportunity until it becomes such a legal nightmare for these companies that they are forced to back down. Anything less would be uncivilized. I know this is no Rosa Parks moment, but it still very much necessary for the long-term viability of computing as we know it. Just say no to data format patents."

      This is precisely the tactic I encourage everyone I know to use.

      These people are no longer playing fair, WHY SHOULD WE?

      In this day and age, corporations are, quite simply put, walking right over common sense. There is no more "customer service", but rather corporations simply see us all as resources to be mined.

      When these people no longer see reason, no longer work to provide a product without stifling the competition, then "Intellectual Disobedience" is the ONLY route left to address the situation.

      If by "Intellectual Disobediance", you mean "allegedly violating their patent by distributing Linux access to FAT in major products", then your theory doesn't appear to work. Far from disrupting Microsoft, in the manner of civil disobedience, it just lets their lawyers think "woot, more revenue streams after we've won the first patent lawsuit!" If your complaint is that they see us as resources to be mined, then the solution is unlikely to be just to give them more resources to mine... you actually need to work out how to prevent the mining.

    111. Re:Say It Ain't So by williamhb · · Score: 1

      Precisely. Couldn't agree more. We don't need to fight these gruppets in the same way that we don't need to fight the creationists.

      Is Slashdot running a competition for who can get a religious argument started in the least relevant topic? If so, I think we have a nominee!

    112. Re:Say It Ain't So by williamhb · · Score: 1

      Sure, for certain niche markets, closed source can give a company a competitive advantage for a while... But if the market is "hot" enough, Open Source will eventually be there to eat its lunch. This has been happening over and over again for the past two decades. Were you asleep?

      Ah, that lovely weasel-word: "eventually". OpenOffice.org still hasn't managed to eat Microsoft Office's lunch (and looks nowhere near getting a nibble at Excel) -- never mind, it's just not "eventually" yet. Firefox, celebrated champion of lunch eating, still lags at half or less of the market share compared to IE -- "don't complain, it's just not eventually yet." iTunes -- that's really popular, surely it's lunch should have been eaten now ... "hold your horses, I said eventually" SAP? Salesforce.com? Google (indexing and search algorithms)? "You can't call me up on it because I said 'eventually'."

    113. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      I think this is a good distillation of BSD vs. GPL: the GPL license takes freedoms from software distributors (not the programmers themselves, unless they are the same person) using GPL code and obligates them to provide source code along with any distributed binaries made from that GPL code. all of this grants all freedoms to anyone who receives such a program and wishes to modify it and further develop it. it's meant to preserve the full freedoms of anyone using the code and they are obligated to preserve the full freedoms of the next person who uses the additions that they wrote based upon the original GPL code.

      the BSD license puts no such obligation onto distributors of code and as such gives them the freedom to prevent further developments from being made by the recipients of such code.

      so it's really a shifting of freedoms and conversely a shifting of restrictions. one favors user/developer freedoms, the other favors developer/distributor freedoms. it's really a question of who's freedoms are more important in your eyes.

      personally i hold the freedoms of an individual in much higher regard than a company, so i favor the GPL, even though i realize it puts a greater obligation on an individual developer who wants to distribute code. such a developer, however, would have much bigger things to worry about than the license of the code they are modifying (like software patents should they gain any fame).

      the main advantage i see with the BSD license is that it only holds the potential to restrict the developer/user, it's not a guarantee, but it allows for greater abuses, but these are pretty much the same statement. developers are mostly (well not really, but for programs that most people use) companies of varying size, mostly larger. a large company is more likely to abuse their customers unless their product intrinsically prohibits that. see the comment near this one about MS stealing BSD code and patenting minor changes.

      i think most of us know all this already but i've never seen it all put together in one place. many people say that the BSD license is truly free but i think the real issue is that the freedoms of two people can oppose one another and when that happens you have to decide who's freedoms get trumped, that is the difference between GPL and BSD.

    114. Re:Say It Ain't So by robinvanleeuwen · · Score: 1

      Fine with me, but only if you implement Windows as a digital hardware circuit you can patent it. As long as it's just text in an editor you get copyright...

      --
      If you don't like my sig then don't read it.
    115. Re:Say It Ain't So by ozphx · · Score: 1

      They don't even need to do that. There was nothing stopping them from using ext2 on the device completely and bundling an ext2 driver with their firmware update utility.

      Quite simply there was many technical ways they could have achieved their goals. These ways may have cost more to implement. They chose to use the patented* file system without paying the license - and they got caught.

      * Not that I agree that something as straightforward as LFN support for FAT should be patentable (its just an obviously fucking long->short map after all) - but this is a seperate matter for discussion.

      --
      3laws: No freebies, no backsies, GTFO.
    116. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Except that in real life, many didn't choose the highway. The most popular license is the GPL. BSD doesn't even come close. I think your theory is therefore flawed.

    117. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Hrmmm sounds like it would just be cheaper to pay MS to use its bloody filesystem then.

    118. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      "MacOSX has a colossally larger desktop share than Linux"

      Not according to Steve Ballmer.

    119. Re:Say It Ain't So by Yfrwlf · · Score: 1

      I hope your not some corporate turfer, you never know these days, but I'll argue your point. The main point of argument here, aside from arguing against patents in general and their effects on technological progress and the sharing of information, is that the major difference between software patents and "normal" patents is that software can implement an idea, any idea, whatsoever. If it is something that the computer can physically interface with, it can be done. In other words:

      If you can dream it, you can implement it.

      This is very, very different from patenting physical things, which requires physics to actually, you know, function in favour of your idea for it to actually work. This is why someone cannot patent, say, a teleportation device that transports big objects, because even though this has been dreamed up, it requires getting the physics right to implement it. Software does not require this. In software, you can implement anything. With software patents, I could come up with something so-called "unique" that hasn't been patented yet and lacks "prior art", throw together some stupid program (or do they even require some actual software before patenting??) that does it, and I'm golden. For instance, I'll patent the interface between a computer and, lets see, a device that calculates the number of molecules in Leonard Nimoy's butt. Sure, it's just a stupid program that uses some stupid protocol or whatnot to interface with the device, like all devices, but because it's so-called "unique", even though in reality it's really fucking not unique at all, it'll be awarded a patent I assure you.

      Let me summarize:
      Regular patents: pretty fucking stupid in most cases, and in general slow the progress of technology.
      Software patents: really god damn fucking stupid in every case, like patenting math or dreams.

      --
      Promote true freedom - support standards and interoperability.
    120. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Losing with dignity and honor is: losing

      Now when it comes to things like losing a game or sporting event, then we should lose with dignity and honor. When it comes to losing liberties (including the right to make a living in any industry of your choice, because the industry of your choice is locked up by ridiculous laws which implement unjust monopolies) there is a long standing tradition (at least in the US) of "Live Free or Die", "Give Me Liberty or Give Me Death", and civil disobedience.

      Even if you are not trying to make a living, you still have a fundamental right to freedom, including the fundamental freedom to write software. If a law is unjust, you have a moral right to break that law - however, you must be prepared to face the consequences. When you break that unjust law, you must be prepared to go to jail, or have your property or assets confiscated.

      You've got to be willing to 'face the firehoses and dogs' (metaphorically speaking, here) if you hope for change. It might not be fair, but that's how it is. If you try to somehow avoid the consequences, people will then (at least, quite possibly) view your cause as not being just.

    121. Re:Say It Ain't So by bmcage · · Score: 1

      Dude, go watch/read The Watchmen, and then think some more about this.

    122. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      The primary reason for success of Linux is a combination of timing and luck. When the BSD project's viability was in serious question due to the AT&T lawsuit, Linux hit its stride.

      I don't think that can be the reason. If I recall
      it correctly the BSD lawsuit was resolved in 1994,
      by then Linux was still a toy operating system, unusable for any serious purpose (with the possible exception as a case study in a college course).

    123. Re:Say It Ain't So by jaseuk · · Score: 1

      If Ted had released his Kerberos implementation under the GPL, one of two things would have happend.

      1. Microsoft would have implemented their own Kerberos implementation.
      2. Microsoft would have developed an alternative to Kerberos.

      If Microsoft had not utilised Kerberos at all then Open Source would not be in a position to integrate with Windows at all.
      Despite making some extensions, Microsoft's Kerberos and Active Directory interoperate well with Unix systems.

      So the irony is, that had Ted GPLed Kerberos, then Windows interoperability with Linux could have been severely impacted and the GPLed Samba implementation would be struggling right now.

      Jason.

    124. Re:Say It Ain't So by kasperd · · Score: 1

      What if I'm in the Canada, and buy (from a US company) a GPL program which comes with a written offer to provide the source. Then a month I move to Cuba, and send a letter to the US company asking them to please send me the source (including proof of purchase, and cash to cover costs of copying and sending the source code back to me)

      What does the US company do now?

      They are screwed. They either have to violate the USA law, or violate the license and thereby losing the rights to distribute the software. They could have prevented this exact scenario by giving the sources to begin with instead of the offer to give them at a later time. I'm still not certain if they are violating the law by giving the software to somebody who then later take it to Cuba.

      But that is not the only risk a company runs by placing their headquarter in USA. If they end up having departments in different countries, USA law requires their departments abroad to discriminate against people from certain countries. That may very well be illegal in the country where that department is actually based. That way a company could end up in a situation where the company would be violating the law of one of the countries no matter what they do. In short, it is risky to do business in a country that try to make laws about what happens outside its own borders.

      --

      Do you care about the security of your wireless mouse?
    125. Re:Say It Ain't So by Anachragnome · · Score: 1

      "... you actually need to work out how to prevent the mining."

      As I said....."Speak with your mind, voice and dollar, in that order."

      The one thing these corporations understand CLEARLY is not giving them your money. I don't just TELL friends and family about the crap that Microsoft pulls, I SHOW them, usually with their own Windows machines. That is usually enough to stop the flow of money from them to Microsoft.

    126. Re:Say It Ain't So by idlemachine · · Score: 1

      Dude, go read some Nietzsche. If you had, you'd have been more inclined to call me out for my use of that quote, as Nietzsche's idea of the Ubermensch has more in common with the "win at all costs" philosophy that I was responding against.

      As it is, 'The Watchmen' promotes the complete and utter opposite of that idea. So maybe you might want to rewatch/reread it, and actually think.

    127. Re:Say It Ain't So by Drinking+Bleach · · Score: 1

      Uh... no. UDF works fine in full read-write mode as any other regular filesystem does.

    128. Re:Say It Ain't So by hkBst · · Score: 1

      I don't just TELL friends and family about the crap that Microsoft pulls, I SHOW them, usually with their own Windows machines. That is usually enough to stop the flow of money from them to Microsoft.

      What exactly do you show them that convinces them?

    129. Re:Say It Ain't So by Schraegstrichpunkt · · Score: 1

      Here's an example. The US government probably prevents you from selling your open source software to Cuba or Iran. If I read section 7 correctly, that counts as a "condition imposed on you". So really you lose all rights to using that code?

      What section in the GPL prohibits you from refusing to distribute anything to Cuba? At worst, this might cause some trouble for people who take the "written offer" approach instead of distributing sources alongside binaries.

    130. Re:Say It Ain't So by nabsltd · · Score: 1

      So you are clever enough to know how to use it as a mass storage device...

      If "just plugging it in" == "clever", then, OK, I'm clever.

      Every USB device I have that acts as mass storage was configured as that by default...I would have to have changed a setting to put it in to a mode that made not appear as a drive. Even my camcorders that use Firewire haven't needed any special software, although they appear as a camera, not a drive.

      Again, most of these devices still have a special program that can be installed and will pop up when that specific device is plugged in, but with a default Windows install, just plugging in the device gets the standard autorun dialog. I guess everyone else is as sick as I am of seeing that useless dialog with the "always do this" checkbox that never seems to be remembered, so they always install the software for their devices.

    131. Re:Say It Ain't So by BlortHorc · · Score: 1

      That is one of the most succinctly stated reasons for opposing the mind control of the weak I have ever seen.

    132. Re:Say It Ain't So by BlortHorc · · Score: 1

      C'mon, clearly creationists are not about religion. Haven't you heard, they're scientists.

      No, really

      *guffaw*

    133. Re:Say It Ain't So by bmcage · · Score: 1
      I was not replying against the ansatz of this thread (fighting patent litigation) but against the general claim

      Because how you win is as important, if not more so, than winning itself

      It implies a certain morality which we ourselves define first. It can lead to stupidity if the moral values are (in someone else's eyes) stupid.

      It also depends on the price attached to failing, and the publicity of the fight.

      I really dislike generalities.

    134. Re:Say It Ain't So by idontgno · · Score: 1

      Tell that to Steve Jobs and his "mp3" players

      Well, I know I've tried. But the damn RDF surrounding him is changing what he hears. Every time I tell him I just want to treat the music storage on my iPod as a filesystem, and just skip that annoying iTunes, he smiles and thanks me, so I assume that he hears me complimenting his turtleneck or praising Apple's most recent polishing of its product line.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    135. Re:Say It Ain't So by idlemachine · · Score: 1

      I really dislike generalities.

      Point taken. You should have expressed it that way initially :)

    136. Re:Say It Ain't So by MHDK · · Score: 1

      "Steal" would be a bad choice of word, that's all. However, as the links describe, Microsoft had engaged in the objectionable practice of taking the Kerberos code, making some changes that were deliberately difficult to implement by other people (by making them secret and encumbered with various legal requirements that were not present in the original BSD code). The point is that they benefitted from the work of other people - as the BSD licence allows them to - and then took advantage of this work to lock in people to the Microsoft version of Kerberos. So perhaps you'd like to address that point rather than focus on a poor word choice?

    137. Re:Say It Ain't So by bhtooefr · · Score: 1

      The other reply mentions an install CD, but you could actually do an ISO9660 partition on a USB Mass Storage device, IIRC.

      I believe that's how U3 works.

    138. Re:Say It Ain't So by Anonymous Coward · · Score: 0

      Liar, liar, pants on fire.

      Or in a more conventional tone:

      You should provide an argument before you come with mathematical assertions. Why would "Force" (which makes a fraction of the changes available) give exponential while "When it benefits" (which makes another fraction of the changes available) move from incremental to exponential?

      It IS clear that not everybody release changes even with the GPL, and it is also clear that there are proprietary developers release some of their changes with the BSD license, given than both many small changes and large subsystems in FreeBSD comes from embedded developers.[1]

      Please provide a coherent argument, or accept that you've been wrong and thereby misinforming people, and post an apology.

      [1] I'll also note that many of these developers say they would have used a proprietary base or not done their development at all if they couldn't have made some of their changes proprietary, so there has been extra development going on due to the non-GPL-ness of the codebase. However, it is hard to verify the amount of this, or the correctness of the motivational claim - heck, it is even hard to verify when I've been part of one of those development teams making that choice.

    139. Re:Say It Ain't So by palegray.net · · Score: 1

      Soap box, ballot box, jury box, ammo box - to be used in that order.

    140. Re:Say It Ain't So by spitzak · · Score: 1

      The TomTom (I have one) does have a special app. However it is on the TomTom and it is installed because the installer is an auto-run program. There is no way to make this work on Windows (as Microsoft will absolutly refuse to support by default any FS that they did not write themselves). People saying that TomTom should include an install CD are completely missing the point, no matter how cheap the CD is, it must be more expensive than not having one, and it can get lost/broken.

    141. Re:Say It Ain't So by rbanffy · · Score: 1

      "There should be absolutely no reason to install anything to get mp3 player working."

      Except maybe because MS patented every workaround required to make their crappy old technology work as expected by any modern (as in "post-1990") operating system.

    142. Re:Say It Ain't So by rbanffy · · Score: 1

      That is probably why iTunes mangles filenames when storing them in a Windows-formatted iPod.

    143. Re:Say It Ain't So by Anachragnome · · Score: 1

      My latest trick, if they have been using Netflix, and thus have Silverlight installed, is a good example of Microsoft being no better then any purveyor of Spyware.

      Simply save a Youtube video and view it with Windows Media player.

      As soon as you close the player, their firewall will ask them if they want WMP to be able to connect to the Microsoft server. Deny it once, then try it again with another video. Same result, every time. Just make sure they haven't already added WMP to their exclusion list.

      WMP is being used to track their video usage. Not just Netflix, but ALL videos.

      9 out of 10 people I show this to, who are then introduced to VLC, never use WMP again, other then to view Netflix.

      I could go on and on with little demonstrations like this, but I prefer to just plant the seed of distrust and let it ripen on its own. Those that actually care start noticing this stuff by themselves. And more importantly, some of those that didn't care, begin to.

      The other thing I do is provide them with Process Explorer. Yeah, I know it is owned by Microsoft, but if you know where to look, version 10.20 is still out there (I carry it, and Revo Uninstaller on my keychain thumbdrive), and Microsoft doesn't have their fingers in that version, as it was the last version put out before Microsoft acquired sysinternals.

    144. Re:Say It Ain't So by handydan918 · · Score: 1

      quothe the idlemachine: " 'He who fights with monsters should look to it that he himself does not become a monster.' Or how about: 'Two wrongs don't make a right.' Because how you win is as important, if not more so, than winning itself. I agree that there are times that we need to fight but we also need to be sure we don't lose ourselves in the battle" Spoken like a person who has never engaged in a REAL battle. Fighting "fair" is for Boy Scouts, (who can no longer use the name) and the Marquis de Queensbury, (who is dead). If the battle is worth fighting, I would submit that it is not only permissible, but all too often necessary to "lose ourselves in the battle". The 'moral high ground" is for losers and preachers. The warriors will accept mere victory.

    145. Re:Say It Ain't So by idlemachine · · Score: 1

      The warriors will accept mere victory.

      You need to spend some time doing something other than playing 'Halo'.

    146. Re:Say It Ain't So by Hucko · · Score: 1

      If "just plugging it in" == "clever", then, OK, I'm clever.

      You obviously weren't concentrating when you read my comment. To the average users, that apparently is clever. You have to look at files directly! Nothing to guide but what is displayed on the screen in front of you!

      I'm afraid you sort of reversed the direction of my rant. I apologise for getting your hopes up under false pretences and not articulating myself in a manner that communicated my meaning accurately.

      I meant users are dumb.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    147. Re:Say It Ain't So by ion.simon.c · · Score: 1

      Not on Windows XP or earlier, it doesn't!

      http://en.wikipedia.org/w/index.php?title=Universal_Disk_Format&oldid=269059905#Native_OS_support

      WinXP (or Server 2k3) has *no* idea WTF to do with a UDF formatted USB flash drive, either.

    148. Re:Say It Ain't So by ion.simon.c · · Score: 1

      Do you have any packet dumps from this WMP experiment?

    149. Re:Say It Ain't So by ion.simon.c · · Score: 1

      FFS. Are those *all* twitter sockpuppets?

      Also, thanks for the U3->ISO9660 info!

    150. Re:Say It Ain't So by ion.simon.c · · Score: 1

      Mathematically speaking the two are identical.

      Pragmatically speaking the two are worlds apart.
      When's the last time that your simulated quartz RTC generated erroneous results 'cause a simulated incoming phone call wobbled the simulated voltage on the simulated trace two layers down in the PCB that the RTC was simulated to be sitting on top of?

      It's details like this -and their explanation in the patent application- that make hardware worthy of patenting.

    151. Re:Say It Ain't So by Eunuchswear · · Score: 1

      Got a link to the source code?

      Thought not.

      --
      Watch this Heartland Institute video
    152. Re:Say It Ain't So by Lennie · · Score: 1

      I have to agree, Symbian is not yet open source.

      --
      New things are always on the horizon
    153. Re:Say It Ain't So by bhtooefr · · Score: 1

      Actually, that's nowhere near a complete list.

    154. Re:Say It Ain't So by Boaz17 · · Score: 0

      And would make updating the thing nearly impossible. They do firmware updates by mounting it as a USB mass storage device. Without a hardware redesign to emulate FAT (which would probably also violate M$'s patents), they're pretty much stuck here.

      There is a 3rd and much more elegant way, I think, NAS.
      All these gadgets should just export a network filesystem via cifs for example, they can stay in master-mode of their local disks and serve files over usb-network device. This also eliminates lots of the HW and SW hacks done on these devices for emulating local-attached USB-slave storage. The NET cost and user experience is much better. And the actual applications do not change much. A file is a file is a file.

      Free Life Boaz

    155. Re:Say It Ain't So by badkarmadayaccount · · Score: 1

      How about a bubble saying "Please install Ext2IFS drivers from this website." ?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    156. Re:Say It Ain't So by LordVader717 · · Score: 1

      Moron. That's cause a patent covers the patented method, not the name. The patents were probably filed long before anybody used the term "UDF"

    157. Re:Say It Ain't So by spitzak · · Score: 1

      It can't even run the program to pop up that bubble!

      There has to be FAT (or NTFS) on that internal disk or Windows will not run any program off of it.

    158. Re:Say It Ain't So by badkarmadayaccount · · Score: 1

      iso9660 good enough?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    159. Re:Say It Ain't So by spitzak · · Score: 1

      iso9960?

      Maybe. Some other posters mentioned UDF.

      I'm not sure if Windows will recognize and read those systems when they are what it thinks is a USB flash disk, though.

    160. Re:Say It Ain't So by badkarmadayaccount · · Score: 1

      Each partition on USB Mass Storage Device instance is a separate device function, IIRC. If it isn't, it's pretty damn easy to fix that. Also, More Windows installs support iso9660 than UDF.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  2. Misleading title. by DaveV1.0 · · Score: 1, Insightful

    Samba's Jeremy Allison has a fascinating theory

    So, in other words, it is not "The Real Reason For Microsoft's TomTom Lawsuit", but rather the theory of someone who is not connected to Microsoft, has no actual knowledge of Microsoft's reasons and strategies, and who could be considered hostile to Microsoft.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    1. Re:Misleading title. by ichthus · · Score: 5, Insightful

      As a Samba developer, I would think he's especially familiar with Microsoft's strategies.

      --
      sig: sauer
    2. Re:Misleading title. by Gordonjcp · · Score: 1

      as someone who has used samba, he is responsible for one of the worst configuration file formats ever

      Let's see your alternative to it, then. Show us all a better way.

    3. Re:Misleading title. by Anonymous Coward · · Score: 0

      So, in other other words, perfect Slashdot material. Now, if only they could have found a funny picture for the article and posted it under Idle...

    4. Re:Misleading title. by morgan_greywolf · · Score: 1

      as someone who has used samba, he is responsible for one of the worst configuration file formats ever.

      What's wrong with Samba's configuration file format? It's a Windows .INI-style format. Human readable, easy to parse, easy to write. What's not to like?

    5. Re:Misleading title. by nine-times · · Score: 1

      Well it seems like it's a theory about what the "real reason" might be. I'm not sure what your problem with that is. Would you prefer to only get the side of the story that Microsoft's PR people want to put out?

    6. Re:Misleading title. by Hognoxious · · Score: 2, Funny

      GP is the guy who invented the registry, you insensitive clod!

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    7. Re:Misleading title. by rbanffy · · Score: 1

      Not exactly. The Samba folks worked with the EC judges on the Microsoft antitrust case. I say they are as familiar to Microsoft's ways as Interpol cops are with organized crime and, mind you, there is not much difference between Microsoft and organized crime when it comes to bullying companies.

    8. Re:Misleading title. by Anonymous Coward · · Score: 0

      maybe it s not the real reason, but there is something of the most strategic importance for ms here, or they wouldn t take the (quite high, because of the obvious prior art) risk to lose

    9. Re:Misleading title. by geekboy642 · · Score: 4, Informative

      one of the worst configuration file formats ever

      Wrong.
      I hold up for example: XML, the Windows Registry, and sendmail.cf

      --
      Just another "DOJ fascist authoritarian totalitarian bootlicker" -- Zeio
    10. Re:Misleading title. by Anonymous Coward · · Score: 0

      And we all know how friendly Microsoft is to the "cancer of linux and open sores". Riiight.

      TomTom can always port it to bsd and tell Microsoft to fuck themselves.

    11. Re:Misleading title. by Jeremy+Allison+-+Sam · · Score: 5, Interesting

      Thanks dude. I guess I should take my complements where I can :-).

      We are moving to a registry based config in later versions, but I'm not sure you would think that an improvement :-).

      You have to remember Samba is 17 years old, and you can still parse original smb.conf files from the first version. These things do tend to acrete over time, and it's hard to break existing configs. Not an excuse, but...... :-).

      Jeremy.

    12. Re:Misleading title. by FictionPimp · · Score: 4, Funny

      Just get me release quality AD support via 2003 server and we will call it even.

    13. Re:Misleading title. by Sponge+Bath · · Score: 5, Informative

      sendmail.cf

      Gah! Noooooo!
      You have invoked the name of ultimate evil, dooming us all!

      You should edit sendmail.mc (evil light) instead and process it with m4.
      Nothing could be more intuitive.

    14. Re:Misleading title. by Anonymous Coward · · Score: 0

      As a lifelong bully I resemble that statement.

    15. Re:Misleading title. by Anonymous Coward · · Score: 0

      ...We are moving to a registry based config in later versions, but I'm not sure you would think that an improvement :-).

      Jeremy.

      No I wouldn't. I've dealt with the problems a registry can pose for Windows and I've had to flat-out concede defeat on a mucked-up registry for Gnome.

      A Registry sounds like a good idea. And when it was first invented, it had a major selling point - it used disk space more efficiently than the native DOS (FAT) filesystem did.

      However, a Windows registry is an all-or-nothing thing. If you're transporting apps or attempting to recover a broken system, there's no way to restore just PART of a registry the way you can when you copy a directory subtree in /etc.

      Furthermore, the fact that the Windows registry is in secretbinaryformat is a serious liability. /etc has its faults, but you can do just about any sysadmin task you want on it, because it's totally accessible as a file system tree and because all the stock *n*x text manipuation tools can be used on it.

      So I DEFINITELY wouldn't think it an improvement. Sometimes the simple solutions just work better.

    16. Re:Misleading title. by Anonymous Coward · · Score: 0

      It looks to me like someone has been busy trying to hide Microsoft's patent escapades. I have recently noticed that the Kerberos FAQ and the Wikipedia entry for Kerberos no longer reference the patents Microsoft added to Kerberos, as still found here:

      17. Not content with Microsoft's corruption of the Kerberos standard, Microsoft has filed for a patent on its proprietary version. Consequently, not only will Microsoft products fail to interoperate with non-Microsoft products (because of the modification), but Microsoft will not allow anyone else to use its version unless they purchase a license from Microsoft.

    17. Re:Misleading title. by fava · · Score: 2, Insightful

      From a half remembered source:

      It takes a brave man to edit sendmail.cf by hand, it takes a stupid man to do it twice.

    18. Re:Misleading title. by Hordeking · · Score: 1

      It looks to me like someone has been busy trying to hide Microsoft's patent escapades. I have recently noticed that the Kerberos FAQ and the Wikipedia entry for Kerberos no longer reference the patents Microsoft added to Kerberos, as still found here

      So go into the history and roll it back. And report the IP/username of whoever edited it out.

      Problem solved

      --
      Disclaimer: The opinions and actions of the US Gov't are in no way representative of those held by this author or its ci
    19. Re:Misleading title. by Anonymous Coward · · Score: 1, Insightful

      It's not exactly all-or-nothing; if you know what keys you need you can back up and restore just those ones. However, knowing which keys you need is not a trivial task (depending on the application, of course). On the other hand, most of the valuable stuff is stored in (HKLM | HKCU)\Software\[Vendor]\[Application] (or similar). For instance, if all you need is a registration key or something you'll likely find it there; of course, it's not always that simple. Another problem is that registry values often point to files or folders; obviously these paths can be different on different machines.

      The registry is not *officially* documented, but there is plenty of documentation out there.

      That being said, I tend to agree with you. Simpler is better and you probably want to maintain compatibility with previous versions.

    20. Re:Misleading title. by cptnapalm · · Score: 2, Interesting

      Once upon a time I decided to change over to sendmail, after all that was what the big boys used.

      So, I apt-geted sendmail.

      Then I looked at the configuration file.

      30 seconds later, I was installing postfix.

    21. Re:Misleading title. by Anonymous Coward · · Score: 0

      ... huh? That doesn't follow at all.

    22. Re:Misleading title. by Anonymous Coward · · Score: 0

      If you hear unfortunately the meaning of my thoughts not present in translation, sorry forgive that lack of English ability in me.
       
      Contributing factors, many famous companies in the hands of the Association, and president. The company has more foreign variety of technologies to improve the quality of a need to consider it. Therefore exist many reasons to which the leadership of the organization beginning with the CEO require change. The decisions of the present leader are made in a manner not glorious to the continued excellence of the company. Such is the need to bring a manager more experienced in the art of magnificent decision process to improve the outer virtuosity of the company with no need for prosecution of challengers such like Tom Tom. For improvement is more efficient when technological products are best, opposed to legal prosecution to substitute it.

    23. Re:Misleading title. by Anonymous Coward · · Score: 0

      *mumble* *mumble* defocus *mumble*

    24. Re:Misleading title. by Rufty · · Score: 1

      You are not a *real* sysadmin until you have hand edited sendmail.cf. Corollary: you are not sane if you have done this more than once.

      --
      Red to red, black to black. Switch it on, but stand well back.
    25. Re:Misleading title. by Kalriath · · Score: 1

      I just checked - it was never in the Wikipedia article.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    26. Re:Misleading title. by MichaelSmith · · Score: 2, Funny

      I bought a book on configuring sendmail. It did a pretty good job of selling me on qmail.

    27. Re:Misleading title. by MadMidnightBomber · · Score: 1

      Heh. I picked up a copy of sendmail for $3 NZD in Palmerston North. The reason being that the university used postfix and the local ISP used postfix leaving no-one who wanted or needed to know about sendmail.

      --
      "It doesn't cost enough, and it makes too much sense."
    28. Re:Misleading title. by ion.simon.c · · Score: 1

      You are aware of the Samba Plugfests?

  3. Really an attack on using Microsoft tech in Linux by guruevi · · Score: 5, Interesting

    What TomTom (and others) need to do is start using EXT2/3 on their external cards and then distribute Fuse with their software. This will force FAT and with that Microsoft tech slowly but surely out of the market.

    What do you think will happen when all external media starts using alternative formatting?

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
  4. It's embedded by jythie · · Score: 0, Troll

    Non-Industrial embedded developers are probably going to move away from linux (or at least the gnu bits) after GPLv3 anyway.

    1. Re:It's embedded by Microlith · · Score: 1

      Well, considering that the core of embedded Linux these days seems to be busybox and the kernel, they aren't going anywhere (locked to GPLv2.)

      The rest of the GNU environment will probably be shed as they force it all to GPLv3. I wonder if it wouldn't be possible to port the BSD userspace to Linux (BSD/Linux) to compensate?

    2. Re:It's embedded by Mysticalfruit · · Score: 1

      That's a pretty broad statement, what do you propose people move too instead?

      If this Microsoft lawsuit is because TomTom included code in their software that allows them to read CF cards formatted with the FAT filesystem, why hasn't MS gone after Redhat/Suse/etc?

      I can't remember a linux box I've sat down at that can't read FAT...

      --
      Yes Francis, the world has gone crazy.
    3. Re:It's embedded by Hognoxious · · Score: 1

      Every cameras, PDA and the like I've ever owned has used FAT on removable storage. I don't if the manufacturers of those were licensed to use it - but if not, then wouldn't laches apply?

      IANAL, BPSWI could explain whether "sleeping on your rights" with regard to one person's supposed infringment may be used as a defence by someone else?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    4. Re:It's embedded by IntlHarvester · · Score: 1

      Every camera I've owned only writes short filenames. And the patent is being broadly licensed.

      --
      Business. Numbers. Money. People. Computer World.
    5. Re:It's embedded by mea37 · · Score: 1

      Laches applies to a specific infraction, not a type of infraction. If MS could have brought action against TomTom much earlier, but MS delayed in bringing that specific action, and TomTom is now in a worse position as a defendant than they would've been were the action brought in a timely manner, then laches might apply.

      In short, if I notice you're letting other people get by with stealing your donuts, that doesn't mean I can steal your donuts with impunity. (Trademark, but not patent, is a notable exception.)

  5. Re:Really an attack on using Microsoft tech in Lin by Anonymous Coward · · Score: 0

    Not easy considering they distribute upgrades and maps as downloadable files that people put on a usb key to load them in the device.

  6. Patents, not code by Anonymous Coward · · Score: 1, Insightful

    Last time I checked, MS sued TomTom over patents. If TomTom would use its patent pool to cross license patents with MS to resolve the situation, where does this violate GPL2 (which is a copyright license)?

    Mod article down as "FUD".

    1. Re:Patents, not code by shentino · · Score: 5, Informative

      Actually, the GPL forbids restricting other people's freedom.

      It is, and should be, a GPL violation to secretly get a patent license. If TomTom were to cave to MS without getting slapped with a GPL violation, then anyone who uses tomtom's work would be opening themselves up to patent infringement suits.

      Please RTFM and actually read the GPL. A good grep would be "they do not excuse you". Search the GPL for that text and you'll zero in on what I think is a very critical "failsafe" in the GPL.

    2. Re:Patents, not code by MikeBabcock · · Score: 1

      Licensing a patent so that you can use and/or distribute GPL'd software in no way restricts others' use of that same software, and therefore has nothing in my opinion to do with the GPLv2. The GPLv3 was written with this in mind, and explicit entries were added to deal with patents and other such nonsense.

      The kernel is not GPLv3, but GPLv2 and unless Tomtom tries to in some way restrict access to the source for the software it distributes, they are in no way violating the GPLv2 in spirit or in fact.

      --
      - Michael T. Babcock (Yes, I blog)
    3. Re:Patents, not code by AtomicJake · · Score: 1

      So, either TomTom has patents and can cross-license them (patents, not code) or not. Where is Linux involved?

      TomTom can use Linux and run licensed code and patented code on top of Linux. Where did you read "patents on Linux"?

      [I see that MS might want to blow Linux with this patent suit -- but I can't see the "fascinating theory", which just results into "FUD".]

    4. Re:Patents, not code by Dare+nMc · · Score: 2, Interesting

      it's still not black and white. At least with GPLv2 you don't have to have all open hardware, IE the entire device doesn't have to be patent/license free, just the software that was compiled with GPL'd code. IE they are free to negotiate license's for attached devices sold in the same package. Also since the FAT resides on a separate chip, then how does a license negotiation over that affect the GPL'd code, as long as the interface used in the kernel doesn't require a license?
      Otherwise every computer/TIVO, etc shipped with any DRM, or propitiatory video card, or Sony memory stick reader could be sold with GPLv2 code. Since that was changed in GPLv3, that would be different analysis.

    5. Re:Patents, not code by Anonymous Coward · · Score: 0

      The GPL v3 has done more to get companies to move to Windows CE than any threats of patent litigation can ever do.

      Say a company has a manufacturing process that is considered a trade secret, where they put in man-years figuring out the right timing for dumping in chemicals into a vat, combined with heating and cooling for some type of material.

      Said company wants to sell machines that do some process for customers, perhaps an EZ bake oven that has some special timing to get cakes coming out just right even when using a LED lamp. If they use GPL v3 code, they have to give the customers the special timing, and every trade secret related with getting the embedded device to work.

      With Windows CE, the company pays their $3 per widget licensing fee, writes their embedded code, and ships. No worries that a customer can demand every single trade secret from a company because one line of GPL v3 code was on the Linux distro. A trade secret means a lot to a company, and it can be their identity. The formula of Coke for example.

      The GPL v3 is great in theory, and may be fine for universities and K-12 schools, but in the "real" business world, there is no place for the license in production use, compared to more business friendly licenses like BSD, or even commercial EULAs.

    6. Re:Patents, not code by BitZtream · · Score: 1

      Ahh, define irony ...

      Actually, the GPL forbids restricting other people's freedom.

      Isn't that restricting the freedom of the person who wants to restrict other peoples freedoms?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    7. Re:Patents, not code by BitZtream · · Score: 1

      And doesn't that make GPL invalidate itself? There by making it effectively nullified and non-binding?

      Since I'm not a lawyer, I'm sure there are a bunch of retarded clauses/reasons why its still considered valid, but its certainly funny as hell.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    8. Re:Patents, not code by blueskies · · Score: 1

      With Windows CE, the company pays their $3 per widget licensing fee, writes their embedded code, and ships. No worries that a customer can demand every single trade secret from a company because one line of GPL v3 code was on the Linux distro. A trade secret means a lot to a company, and it can be their identity. The formula of Coke for example.

      You are a genius! OMFG! You figured it out!!! But what if there is one line of GPL v3 code in your windows code? What happens then? They'll have to give up EVERY SINGLE TRADE SECRET THE COMPANY OWNS!!! Oh, noes!!!

    9. Re:Patents, not code by Dan+Ost · · Score: 1

      Actually, the GPL forbids restricting other people's freedom.

      It does no such thing. It conditionally grants freedoms that are otherwise forbidden by copyright law.

      Isn't that restricting the freedom of the person who wants to restrict other peoples freedoms?

      This isn't hard.

      The GPL guarantees that the recipient of the software has specific rights. In order for the recipient to be guaranteed those rights, the GPL places an obligation on the distributor. The distributor accepts this obligation because without the GPL, the distributor can't distribute the software without violating copyright.

      --

      *sigh* back to work...
    10. Re:Patents, not code by xant · · Score: 1

      It isn't, and shouldn't be a GPL violation to secretly get a patent license. GPL v2 only requires you to make your source code available for any use with no restrictions (other than the continuation of the GPL itself). As long as TomTom is doing that, they are legal. The day they stop doing that, they are in violation. TomTom's patent license for VFAT or *anything else* does not invalidate GPL v2, it simply *permits* TomTom to keep using the "patented" process. For example, it does not require TomTom to force anyone else downstream to recognize the validity of the patent, or to purchase a license. If this occurs as part of a settlement, it doesn't even establish a precedent, as no ruling has taken place on whether VFAT is actually violating any patent.

      (Microsoft may ask TomTom to do those things in a contract as part of a settlement, but that's a completely different discussion. It is not inherent in the patent license.)

      They would be in violation if they:
      * stopped making their modifications available
      * started putting restrictions on others' use of their code

      FTR, I doubt a patent swap is going to happen in this case. More likely TomTom will switch filesystems.

      --
      It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    11. Re:Patents, not code by Anonymous Coward · · Score: 0

      i am the bearer of prima facie PROOF that there is one single line of GPL v3 code in the software. therefore every single company and person who ever wrote code to run on that software, used code that runs on that software, or heard that the software exists, must give up all their code, patents, copyrights, trademarks, trade secrets, secret formulas, bank account, credit cards, all their assets, and their soul.

    12. Re:Patents, not code by js_sebastian · · Score: 1

      it's still not black and white. At least with GPLv2 you don't have to have all open hardware, IE the entire device doesn't have to be patent/license free,

      Nor does the GPLv3 require this. It simply requires that I must be able to modify the GPLed code, re-compile it, and run it on the hardware you sold me.

      Also since the FAT resides on a separate chip, then how does a license negotiation over that affect the GPL'd code, as long as the interface used in the kernel doesn't require a license?

      FAT is implemented inside the linux kernel. How else would TomTom software read/write to a FAT file system?

    13. Re:Patents, not code by Dare+nMc · · Score: 1

      FAT is implemented inside the linux kernel.

      the FAT filesystem table is not contained in the kernel, only a method for accessing the FAT filesystem. So far MS went after (and got a settlement) with Lexar for shipping FAT formatted media, they didn't care if Lexar formatted that media with windows. Because neither the methods or implementations of accessing FAT media, is currently under challenge from MS, only the resulting media.

      How else would TomTom software read/write to a FAT file system?

      simple, add a chip that's not GPL'd that talks to both the kernel, and flash memory. if pushed, one could call it a "external memory controller" (you know like what all usb drives use)

    14. Re:Patents, not code by badkarmadayaccount · · Score: 1

      Mod grandparent down "-infinity Idiot"

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  7. Slashdot's Super Accurate Information Bandwagon by Jamie's+Nightmare · · Score: 1, Insightful

    I love how the title uses the words "Real Reason", then goes on to cite a blog author who says "I have heard rumors...", then points to another blog that promotes a "fascinating theory".

    And yet we wonder why Kdawson hasn't been reprimanded.

    --
    "When you see a unixer brainwashed beyond saving, kick him out of the door." - Xah Lee
    1. Re:Slashdot's Super Accurate Information Bandwagon by thermian · · Score: 2, Funny

      And yet we wonder why Kdawson hasn't been reprimanded.

      He was reprimanded most severely. That is I mean I think he was. Actually I heard they denied him cake once. Well, someone I know said they read it.

      I think.....

      --
      A learning experience is one of those things that say, 'You know that thing you just did? Don't do that.' - D. Adams
    2. Re:Slashdot's Super Accurate Information Bandwagon by Anonymous Coward · · Score: 1

      I don't know why you got modded insightful, but CmdrTaco posted this article, not kdawson...

    3. Re:Slashdot's Super Accurate Information Bandwagon by Pope · · Score: 1

      It meant nothing, as the cake was a lie.

      --
      It doesn't mean much now, it's built for the future.
    4. Re:Slashdot's Super Accurate Information Bandwagon by JCSoRocks · · Score: 1

      Oh, I think I know what you're talking about. I think I saw a discussion of that here. I'm pretty sure that's it. Yeah, that's obvious evidence that he was.

      --
      You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.
    5. Re:Slashdot's Super Accurate Information Bandwagon by ianare · · Score: 2, Informative

      And yet we wonder why Kdawson hasn't been reprimanded.

      Uh, because he didn't post the article ?

    6. Re:Slashdot's Super Accurate Information Bandwagon by genner · · Score: 1

      It meant nothing, as the cake was a lie.

      Yeah they had pie instead and we all know pie is superior to cake.

    7. Re:Slashdot's Super Accurate Information Bandwagon by Anonymous Coward · · Score: 0

      I think GP is referring to the fact that CmdrTaco is likely the one to reprimand Kdawson, and CmdrTaco did post this.

  8. Why does tomtom need long filenames anyways? by Anonymous Coward · · Score: 0

    What harm would it do their software if they stripped out the portion that gets around the 8.3 filename limitation? Do they really need long filenames that bad?

    1. Re:Why does tomtom need long filenames anyways? by jedidiah · · Score: 1

      Files that contain their own long names by way of internal metadata, get around the craptitude of classic FAT quite well.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  9. Re:Or Maybe... by mlwmohawk · · Score: 5, Insightful

    maybe they are just trying to protect their intellectual property

    I'm not saying that "intellectual property" is a pointless concept, but what is currently implemented is frighteningly Philip K. Dick.

    Software is particularly problematic. An invention does not always come from the intellect and work of the inventor. More often than not it is merely an observation and augmentation of the work and intellect of others.

    Software is nothing more than building on that which was built by others, which was built on the work of people before that, and before that, ad infinitem. Even the implementor of a statistical analysis system owes credit to the creators of the programming language used to write it, the creators of the math system, etc.

    Intellectual property my ass, it is a land-grab of an environment created by two generations of engineers that worked and published without patent protection. Now college drop-out Bill Gates, sues for trivial implementations of theoretical models created by men far better than him.

  10. Re:Really an attack on using Microsoft tech in Lin by Chaos+Incarnate · · Score: 1

    Absolutely nothing will happen, because either consumers won't buy devices that don't use FAT, or they'll have the proprietary apps needed already installed so there's no reason for Microsoft to add support for more filesystems.

    --
    Benford's Corollary to Clarke's Law: "Any technology distinguishable from magic is insufficiently advanced."
  11. Re:Really an attack on using Microsoft tech in Lin by DoofusOfDeath · · Score: 1

    What do you think will happen when all external media starts using alternative formatting?

    Microsoft to start filing patent lawsuits against users of the EXT 2/3/4 file systems.

  12. I'm Hooked on Linux!! by Anonymous Coward · · Score: 0

    I would never use anything else! Hi Joanne!

  13. Re:Classic GPL by pembo13 · · Score: 2, Interesting

    So Microsoft sues someone and the GPL is what you blame?

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  14. Re:Classic GPL by iplayfast · · Score: 4, Informative

    You seem to have a misunderstanding of what the GPL is. It is a method of payment. TomTom using GPL'd software must abide by the payment method. That is, by providing the source for use or change by the people who they are selling to. Instead of dealing with dollars they deal with IP.

    The problem at hand is that MS feels that TomTom should be paying for their patents, which would violate the GPL payment method.

    You should be marked troll as you are obviously trolling for this response.

  15. Legalese might as well be program code by macraig · · Score: 2, Insightful

    Legal documents aren't inherently perfect just because it's intended that they be perfect. Legalese is "code" intended to solve a problem just as surely as anything written in COBOL; legalese can have bugs in it, too.

  16. Linux Action Show says no by pembo13 · · Score: 3, Insightful

    The guys over at the Linux Action show (in their last episode) seem to adamantly think that this lawsuit has nothing to do with Linux. Jeremy Allison is probably a pretty jaded individual at this point (and rightly so), so having the view of someone else more familiar with these legal quagmires may be helpful.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    1. Re:Linux Action Show says no by AlXtreme · · Score: 1

      Linux Action show (in their last episode) seem to adamantly think that this lawsuit has nothing to do with Linux.

      Then they haven't read the documents MS filed. At least the long filename patent was in it, and TomTom uses Linux's vfat module for reading files. I don't see how you could have TomTom "violate" this patent without discussing Linux.

      IANAL and neither are the guys from the show, but I wouldn't be so quick to consider this case as merely a battle between two companies.

      --
      This sig is intentionally left blank
  17. Re:Classic GPL by mhall119 · · Score: 2

    It's not a problem if you agree with the principles of the GPL. Otherwise someone could modify the Linux kernel, and while being forced to release the code, they could make it illegal for anybody else to modify and distribute the code by entangling it with a patent license.

    BSD has the same problem, they don't don't see it as a problem. If someone wants to close off BSD code to you and I, they can.

    --
    http://www.mhall119.com
  18. UDF by tzot · · Score: 2, Interesting

    So, is UDF an acceptable replacement for FAT (FAT32) filesystems on CF, SD etc devices?

    I think it's not patented (but ICBW) and I believe (but ICBW again) Windows has the ability to read/write UDF filesystems.

    --
    I speak England very best
    1. Re:UDF by ericrost · · Score: 1

      Wish I had mod points, that's an excellent idea! Its an ISO standard (not that that means anything anymore) but should be unencumbered.

    2. Re:UDF by Hordeking · · Score: 1

      So, is UDF an acceptable replacement for FAT (FAT32) filesystems on CF, SD etc devices?

      I think it's not patented (but ICBW) and I believe (but ICBW again) Windows has the ability to read/write UDF filesystems.

      Patented? I can't tell. Possibly, but then again, possibly not.

      Can MS do it? Yes. Windows can handle UDF. Some versions of Windows require an IFS, though. I think XP can do it natively.

      --
      Disclaimer: The opinions and actions of the US Gov't are in no way representative of those held by this author or its ci
    3. Re:UDF by Mad+Leper · · Score: 2, Interesting

      So why do so many devices that use GPL software still use FAT (FAT32) instead of UDF?

      If it's a standard and unencumbered by patents (unclear but likely) why the resistance to using it?

  19. Re:Classic GPL by The+River · · Score: 1

    Yeah, causes unnecessary "problems" in the same way that all licenses do: you can't use the software in a way the license forbids. "Unnecessary problems" are common to all non-public-domain software, and most have more of these "problems" than software licensed under the GPL.

  20. Good work Stallman... by cyphercell · · Score: 3, Interesting

    "There is no avoiding war; it can only be postponed to the advantage of others." Niccolo Machiavelli The escalation is not all Microsoft's. GPLv2 is proof that the FSF was looking forward to this scenario.

    --
    Under the influence of Post-Cyberpunk Gonzo Journalism
    1. Re:Good work Stallman... by Anonymous Coward · · Score: 0

      The escalation is not all Microsoft's. GPLv2 is proof that the FSF was looking forward to this scenario.

      Kinda like the Jews were looking forward to the Holocaust?

      God, I pity any woman foolish enough to go out on a date with you...

    2. Re:Good work Stallman... by cyphercell · · Score: 1

      No, of course the Jews weren't looking forward to the holocaust. They may have been well served if the Nazi's had been aggressively confronted early on. That's funny, I'm a huge misanthrope so I guess that's "kind of" accurate. Generally, I guess if a woman says something that conflicts too much with my world view I just want to walk away from the date a little depressed, but I've got the common courtesy to finish the thing with a smile on my face. Example: I believe in Zero Population Growth, when a woman says she wants eight kids someday, I know first dates and such generally mean she is not talking about having that many kids with me, but I just can't stand it. I feel like she is irresponsible to live that way. No I wouldn't start arguing about how I thought she was an idiot, but it's not likely that I would go on a second date. Anyways, this is slashdot man, what are you talking about?

      --
      Under the influence of Post-Cyberpunk Gonzo Journalism
  21. Again... by Anonymous Coward · · Score: 0

    Please folks, stop making a big FUD out of this. Always people tend to blow any lawsuit from Microsoft regarding Linux, FOSS, GPL or GNU. If we'd like to see more users start to use Linux or FOSS products, just ignore these cases.

    With this people start to doubt if they even should consider using any of these products because of these cases we all as a community blow out of its proportions. I once nearly convinced a big customer (a bank) to switch to Linux, but they did not pursue because of the pattent infringements Linux would have done, which it didn't.

    The point is with us blowing these things up, we are creating far more PR for Microsoft then they ever could have dreamt of.

    1. Re:Again... by ericrost · · Score: 1

      BS, you ripped that anecdote from the Linux Action Show: Season 10 Episode 1.

  22. Re:Classic GPL by stonecypher · · Score: 1

    Absolutely. If Tivo weren't using a GPL product, Microsoft wouldn't be able to hang Tivo on disconnected third party patent purchase. You like that Netflix show download? 'Cause Tivo pays Frauenhoffer for their MPEG2 MP3 decoder.

    You've never in your entire life seen BSD, ZLib or MIT license cause a problem like this.

    --
    StoneCypher is Full of BS
  23. fascinating explanation by viralMeme · · Score: 3, Insightful

    'then points to another blog that promotes a "fascinating theory"'

    Actually that's .. points to a fascinating explanation by Jeremy Allison of the Samba project...

  24. Excuse Me? by ratboy666 · · Score: 4, Informative

    Gates (and Allen) developed MBASIC, and DISK BASIC. DISK BASIC used the "FAT" system to control free space.

    CP/M did NOT use the same scheme. Instead, CP/M built up free space maps by scanning the directory. It also did not use a linked list. Personally, I thought FAT was weak then, and still is....

    But the "industry" adopted it. It was allowed; we had a (at least) minimal common system for file systems. Enhanced to support directories and sub-directories.

    Then, Microsoft designed a long filename system on top of it, that was back-compatible with the old method. THAT was patented. And, no, it wasn't even the "obvious" solution -- that would have been a mapping file.

    What does this mean? It means that the long filename code SHOULD be ripped out. 8.3, baby! You want longname mapping? Linux has UMSDOS on top of FAT -- same result, no patent violation. Or, just use short names. Or, build a program that reindexes MS FAT longnames into UMSDOS (for read compatibility). Just don't write that format. It can be argued (I would try) that ANY longnames in MS FAT format that were found on a FAT filesystem then MUST have come from an MS patent licensee (because our proposed system wouldn't generate the MS FAT longname format). So, there are solutions. Maybe UMSDOS is too "crufty" to be resurrected, but it strikes me that something like posixovl.fuse could be used (with modifications).

    Microsoft was creative with the MS FAT longname solution. Either deal with it, or get the patent overturned.

    --
    Just another "Cubible(sic) Joe" 2 17 3061
    1. Re:Excuse Me? by mlwmohawk · · Score: 3, Interesting

      Gates (and Allen) developed MBASIC, and DISK BASIC. DISK BASIC used the "FAT" system to control free space.

      Gates and company copied basic from other sources.

      The FAT system is nothing more than a fixed size array allocation system, in use in many systems of the time.

      CP/M did NOT use the same scheme. Instead, CP/M built up free space maps by scanning the directory. It also did not use a linked list. Personally, I thought FAT was weak then, and still is....

      CP/M was better, yes.

      But the "industry" adopted it.

      One has to wonder about the anti-trust issues of patent usage. Yes the industry adopted it, but could it have, in any practical sense, adopted anything else?

      Then, Microsoft designed a long filename system on top of it, that was back-compatible with the old method. THAT was patented. And, no, it wasn't even the "obvious" solution -- that would have been a mapping file.

      The word "obvious" is subjective. LFN in FAT is implemented simply using the existing directory mechanisms. Is the only way to do something "non obvious?"

      Microsoft was creative with the MS FAT longname solution. Either deal with it, or get the patent overturned.

      "Creative" is not what makes something worth a patent. Was it obvious? The only answer to that is yes, as someone skilled in the art (someone with file system experience, particularly FAT) their method was the only way to do it.

    2. Re:Excuse Me? by Anonymous Coward · · Score: 0

      I'm not sure that this is correct. The OS/2 HPFS used extended attributes to hold long file names as early as 1993 or 1994. From the standpoint of the patent, the approach seems the same, though the precise implementation differs. The patent's description certainly seems broad enough that the HPFS / Extended Attributes would describe the same thing - or perhaps more to the point, this patent seems to describe the same thing as HPFS short / long file name mappings using EAs... I relise that MS was involved in the development of the HPFS, but I don't think that matters. So far as I am aware, theis feature of HPFS was not patented...

    3. Re:Excuse Me? by Anonymous Coward · · Score: 0

      GO take an intro course to file systems before you open your mouth on a technical forum and make a fool of yourself.

      Or better yet, peddle your FUD somewhere else. We aint buyin what you sellin.

    4. Re:Excuse Me? by shutdown+-p+now · · Score: 2, Interesting

      "Creative" is not what makes something worth a patent. Was it obvious? The only answer to that is yes, as someone skilled in the art (someone with file system experience, particularly FAT) their method was the only way to do it.

      Is the patent on "using directory entries for LFN" in general? or is it on a specific encoding for LFN in directory entries?

      If it's the latter, then, arguably, it's not all that obvious, and, in fact, reasonable on its own (since you can always use a different way to encode LFN).

      The problem is that, in practice, you have to encode LFNs the way Windows does it, because that's what the majority of your users will be using. But it's not the fault with the patent itself in this case.

    5. Re:Excuse Me? by ustolemyname · · Score: 1
      Allow me to paraphrase your argument for you:

      You're wrong, shut up.

      Mmm, powerful logic you have there.

  25. Re:Really an attack on using Microsoft tech in Lin by Anonymous Coward · · Score: 4, Insightful

    What TomTom (and others) need to do is start using EXT2/3 on their external cards and then distribute Fuse with their software.

    No, the easy way out here is to not use long filenames. The patents is not about FAT, but about long filenames on FAT. If they need long filenames, distribute it as an tar file or loop back-file system file with a short name.

  26. Re:Classic GPL by stonecypher · · Score: 2, Informative

    At no point did I try to evaluate what GPL is; as such by definition I could not be misunderstanding the nature of GPL, as I made no observations in that direction.

    Trolling is when people make ugly jokes to start a fight, not when people have an opinion you don't agree with. GPL zealots seem uniquely unable to tell the difference.

    The problem at hand is that MS feels that TomTom should be paying for their patents

    Wrong. The trouble is that TomTom is paying for their patents. Which means they can't use their GPLed products at all. Wait'll you realize how many other GPL vendors also break this GPL rule; it ruins almost every GPL basis device on the market.

    Like that TiVo internet download? Not for long: it licenses Frauenhoffer and Dolby technologies.

    Please stop lashing out with attacks every time someone disagrees with you. Slashdot's GPL community didn't used to be this rabid or ugly.

    --
    StoneCypher is Full of BS
  27. Which bank is that AC? by jotaeleemeese · · Score: 1, Insightful

    All banks are using Linux, so I really look forward to know about the only one that is not doing so.

    --
    IANAL but write like a drunk one.
    1. Re:Which bank is that AC? by BitZtream · · Score: 1

      Yes, Its likely they use some device somewhere in their organization that is running Linux.

      However, I personally know of at least 2 banks which do not use Linux. They are both small town banks with only a couple of branches, and of course there is an exception to every rule, but to pretend that Linux rules the banking industry like you are attempting to do is just silly.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  28. Re:Or Maybe... by internerdj · · Score: 1

    So it is perfectly reasonable to deny a patent on any physical engineering product as well as long as it "does not come from the intellect and work of the inventor?" In most cases, it is impossible to describe a patent as something other than being built on the hard work and ideas of others. Does the hobbyist inventor owe his wire supplier a piece of the pie for making available the exact wire he needs for his product?
    The problem with the patent system is that it isn't being used to stimulate new properties; it is being used to stifle new properties.

  29. Re:Classic GPL by stonecypher · · Score: 1

    It's not a problem if you agree with the principles of the GPL.

    It is if you remember that the context is the device vendors who are going down in a tailspin because the principles of the GPL extend to cutting off everything they need to do business, such as access to purchase licensed technologies.

    BSD has the same problem, they don't don't see it as a problem.

    You've completely missed what's going on, here. The problem is specifically that GPL says if you license a technology you cannot have ours. BSD explicitly does not have this problem. At all.

    It's unfortunate that you feel the need to replace the problem with something of your own device, then say it isn't a problem, then say BSD has the problem too. It keeps you from understanding what's wrong with GPL, these jumping through of the standard answer hoops.

    If someone wants to close off BSD code to you and I, they can.

    Yes. And when they do, it's almost always by moving to GPL; note what happened to the Antigrain Graphics crowd. More important here is that GPL IS ALWAYS CLOSED OFF, which is what's causing this lawsuit in the first place; it's just that the way in which it's closed off is in a fashion that people who drink the koolaid insist isn't a problem.

    All the while screaming about how BSD code can be closed.

    Which one do you see happening in the real world?

    --
    StoneCypher is Full of BS
  30. obligatory... by JCSoRocks · · Score: 1

    No one will ever need more than 8 characters for a file name...

    --
    You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.
    1. Re:obligatory... by genner · · Score: 1

      No one will ever need more than 8 characters for a file name...

      Not when their system only has 640k of memory.

  31. a patent agreement would violate the GPL by viralMeme · · Score: 1

    "If TomTom would use its patent pool to cross license patents with MS to resolve the situation, where does this violate GPL2 (which is a copyright license)?"

    '7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License'

    'If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program'

  32. Re:Classic GPL by stonecypher · · Score: 1

    Uh, no.

    1) BSD doesn't cause these problems, because it doesn't forbid things asininely. Same goes for the other counterexamples I gave.
    2) Unnecessary legal problems have never happened with any of my libraries, or any MIT/BSD/ZLib library I can name, other than the GPL goons insisting on detail oriented license compatability.
    3) You're confusing problems with unnecessary problems. The problems other licenses have do not uniformly regard restrictions which serve no purpose. This restriction serves no purpose.

    I'd say it was a nice try, but it wasn't. Please give concrete examples instead of vague handwaving if you choose to reply. Making universal statements which aren't actually universal is boring GPL canon.

    --
    StoneCypher is Full of BS
  33. Re:Classic GPL by listen · · Score: 1

    Make sure you read the mere aggregation clause.
    Dunce.

  34. This will happen by betterunixthanunix · · Score: 1

    What will happen? Massive incompatibilities between device makers on either side of this war. The only solution is for consumers to install the EXT2 driver on their Windows PC, which is asking a lot for most people (really, I am not kidding, it is asking a lot).

    --
    Palm trees and 8
    1. Re:This will happen by Anonymous Coward · · Score: 0

      Is there some reason why noone has ever written a GOOD ext2 or ext3 driver for Windows? I've tried some of the more popular ones out there, but they all seem to be unstable and buggy.

    2. Re:This will happen by ion.simon.c · · Score: 2, Insightful

      The only solution is ... to install [software] ... which is asking a lot for most people (really, I am not kidding, it is asking a lot).

      My father has a Zune (one of the flash-memory models). To use the device on a particular machine, one must insert the Zune software disc and install the Zune software on an internet-connected machine. The software *must* call home before use; this installation *can not* happen on an offline machine. Also, one cannot drag and drop media to the Zune, one *must* install the Zune software.

      The iPod similarly requires one to install iTunes before using it with a PC. (Granted, this can be an offline install, so yey! for that.)

      I would think that most consumers are very familiar with the "Insert the CD and run setup before using this device." step. :)

    3. Re:This will happen by ion.simon.c · · Score: 1

      Lack of desire, probably. Why the fuck should we waste our time improving MSFT's operating system? :)

    4. Re:This will happen by Teun · · Score: 1

      You must have given up long ago.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    5. Re:This will happen by Anonymous Coward · · Score: 0

      Yeah, why use an OS which is the best PC gaming platform, has awesome driver support has a lot of commercial applications when you can compile the kernel all day long. Sounds like fun...

      When is linux going to catch up with Win95? Yawn.. Cant wait...

    6. Re:This will happen by spitzak · · Score: 1

      The TomTom I have has no removable media, and it has an installable program, but it is *on the TomTom itself*. Plugging the TomTom into a Windows machine triggers autorun and runs the installer (I have not tried this as I don't have a Windows machine). I see no way they could replicated this without FAT support (though VFAT may be avoidable). Microsoft will refuse forever to install by default support for any filesystem that competes with one they control, so EXT2 or whatever is not going to happen no matter what.

    7. Re:This will happen by ion.simon.c · · Score: 1

      I see no way they could replicated this without FAT support

      Agreed. Sounds like the TomTom folks would have to include installation media if they stopped using FAT inside their devices.

    8. Re:This will happen by ion.simon.c · · Score: 1

      When is linux going to catch up with Win95?

      Last I heard, it had caught up in 1995. :)

    9. Re:This will happen by badkarmadayaccount · · Score: 1

      Or, add bootstrap code in a iso9660 partition on the USB Mass Storage Device...

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  35. Re:Classic GPL by IntlHarvester · · Score: 1

    Otherwise someone could modify the Linux kernel, and while being forced to release the code, they could make it illegal for anybody else to modify and distribute the code by entangling it with a patent license.

    Which is more-or-less exactly what happened when they shipped a kernel with FAT LFN support. It's not like the kernel devs were ignorant of this patent.

    --
    Business. Numbers. Money. People. Computer World.
  36. GPL doesn't forfit your right to n by Bazar · · Score: 1

    A few thoughts here.

    The GPL doesn't force you to distribute your source code unless you've distributed a derived work (ie: binary executable).

    In other words when you distribute anything based on the GPL, you distribute ALL of your work, holding nothing back.

    Its still your right to not distribute anything

    To give a further example.
    If I've built some killer utility application, and I decide I want to licence it under the GPL I can.

    A friend comes to be, lets call him Adam, and he asks for the software, since he's a friend I give it to him. I can even SELL the distribution to him.

    Its now his copy to use and redistribute as he likes, under the restrictions of the GPL. (He can even redistribute it for free or for more if he likes)

    Later tosspot Bob comes along from a competitor's company and decides he needs it, and asks for it. I can refuse to distribute to him.
    He can ask my friend Adam, and Adam can choose to distribute or not.

    In this case, since no one has distributed to Bob, he has no recourse for acquiring the source code or even derived works. He can't demand it from either of us since we never distributed to him in the first place.

    If he steals the code/binaries from Bob its copyright infringement, as he was never given a licence to use the software from anyone.

    Now if you understand that you only need to supply source code to those you've distributed to, the fact that you can be restricted from distributing to places and people has little effect on the integrity of the GPL.

    If you can't release source code to Cuba, you can't release anything to Cuba, the GPL forbids it. But that does not invalidate or contradict the licence in any form or way.

    Probably the biggest misconception with the GPL is that people think once its licensed under the GPL you have no control over who you distribute it to. That's just not the case, you can distribute nothing, or everything. There is no in-between however.

    --
    To avoid criticism; Say nothing, Do nothing, Be nothing.
  37. Re:Classic GPL by stonecypher · · Score: 1

    Make sure you read the lawsuit. The mere aggregation clause isn't strong enough, as evidenced by what's happening right now.

    It is, however, classic GPL zealot behavior to question the intelligence of people who disagree with them. So thanks for letting me know you're a dutiful herd member.

    --
    StoneCypher is Full of BS
  38. The real reason KDawson spouts FUD by Anonymous Coward · · Score: 0

    We know KDawson spouts a lot of FUD: but what exactly is KDawson hoping to achieve? Slashdot's Anonymous Coward has a fascinating theory: 'What people are missing about this is the either/or choice that CmdrTaco is giving Slashdot editors. It isn't a case of turning up at work, playing with a red stapler, posting a few stories and pissing off home. If KDawson or any other editor fails to generate a certain number of visitors-per-day for Slashdot, then under Section 7 of their employment contracts, they lose the right to not be anally violated by CmdrTaco. Make no mistake, this is intended to force KDawson to be anally violated, or get more visitors to Slashdot.'

  39. CUBA and the GPL by viralMeme · · Score: 1

    "Here's an example. The US government probably prevents you from selling your open source software to Cuba"

    Where does it say that, there is no mention of the GPL on the U.S. Treasury Cuba Sanctions site.

    "I hope the same applies to this theory that Microsoft is forcing people to violate the GPL and therefore lose their rights to the code"

    Microsoft claims that the Linux kernel used in Tom Tom devices violates Microsoft own patents. If Tom Tom were to start paying Microsoft royalties for such, that would be in violation of section 7.

    'Yes, well, three of the eight patents in this dispute read on the Linux kernel as implemented by TomTom .. What I mean is the patents cover the implementation of the Linux kernel done by TomTom in their products'

    1. Re:CUBA and the GPL by Nick+Ives · · Score: 1

      You didn't even try did you? From the overview of sanctions:

      o EXPORTING TO CUBA - Except for publications, other informational materials
      (such as CDs and works of art), certain donated food, and certain goods licensed
      for export or re-export by the U.S. Department of Commerce (such as medicine and
      medical supplies, food, and agricultural commodities), no products, technology,
      or services may be exported from the United States to Cuba
      , either directly or
      through third countries, such as Canada or Mexico. This prohibition includes
      dealing in or assisting the sale of goods or commodities to or from Cuba, even
      if done entirely offshore
      . Such brokering is considered to be dealing in
      property in which Cuba has an interest. Provision of consulting services is
      also prohibited. Thus, no U.S. citizen or permanent resident alien, wherever
      located, and no foreign subsidiary or branch of a U.S. organization may export
      products, technology, or services to Cuba or to any Cuban national, wherever
      they may be located, or broker the sale of goods or commodities to or from Cuba
      or any Cuban national.

      But in any case I think restrictions placed on you due to sanctions are probably exempt, I mean, how can a court award damages for GPL violation because you refused to do something criminal?

      --
      Nick
    2. Re:CUBA and the GPL by Logic+Worshiper · · Score: 1

      The court wouldn't have to be in the US.

    3. Re:CUBA and the GPL by Nick+Ives · · Score: 1

      After a bit of head-scratching, I think I see your point. American companies and individuals aren't allowed to transfer technology to Cuba via a third party or country meaning they could be sued for violation in some other country. That would mean nobody in the USA could safely use or distribute GPL software outside of the USA.

      Of course neither of us is a lawyer, right?

      --
      Nick
  40. Re:Or Maybe... by Anonymous Coward · · Score: 0

    Interesting, but all inventions are an improvement upon the work of others. This doesn't just apply to software.

    The difficulty lies in determining if the new invention was "nonobvious to one skilled in the art." This determination is even more difficult in that you can not use hindsight. It is easy after something is invented to say that it was obvious, but it is much more difficult to articulate why it was obvious.

  41. Re:Really an attack on using Microsoft tech in Lin by Savage-Rabbit · · Score: 1

    What do you think will happen when all external media starts using alternative formatting?

    That won't happen because Microsoft controls most of the PC market and they won't support anything that threatens any part of their monopoly. Try mounting a HFS volume on an out-of-the-box Windows system.

    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow
  42. The real real reason microsoft is attacking tomtom by Anonymous Coward · · Score: 0

    Their GPS are really really good.

  43. Collateral Estoppel / Issue Preclusion and YOU! by MarkvW · · Score: 5, Interesting

    If Microsoft wins, it sucks for Tom Tom and it creates FUD. That's bad, but not too bad. Microsoft still has to sue everybody violating its software patent.

    But if Microsoft loses because the Court rejects the concept of software patents a'la Bilski, then Microsoft is royally screwed because if it sues anybody else over a software patent, that defendant can argue that Microsoft can't argue software patents anymore because they already fully fairly and finally litigated the issue against Tom Tom and they lost. They don't get to relitigate the same issue all over again.

    You can see why this is HUGE for Microsoft. If they win, they get some money from Tom Tom and they put a scare into the Linux community. If they lose because their software patents are no good, then Microsoft's whole software patent edifice is gravely jeopardized. Microsoft will really fight this hard.

    Tom Tom is really vulnerable because the GPS market is slammed in this economy. I suspect that Microsoft is betting that they'll give up. The Linux community ought to prop up Tom Tom with legal and technical support--at least on the software patent theory.

    Microsoft's invasion should be defended at the beaches. They should be thrown back into the sea before they create more FUD!

     

    1. Re:Collateral Estoppel / Issue Preclusion and YOU! by snspdaarf · · Score: 1

      ... The Linux community ought to prop up Tom Tom with legal and technical support--at least on the software patent theory.

      As as long long as as they they don't don't bring bring back back those those stupid stupid ads ads.

      --
      Why, without your clothes, you're naked, Miss Dudley!
    2. Re:Collateral Estoppel / Issue Preclusion and YOU! by Dan+Ost · · Score: 1

      I bet that was hard to type.

      --

      *sigh* back to work...
    3. Re:Collateral Estoppel / Issue Preclusion and YOU! by Anonymous Coward · · Score: 0

      We shall go on to the end, we shall fight in court,
      we shall fight on the seas and oceans,
      we shall fight with growing confidence and growing strength in the courts, we shall defend our Licence, whatever the cost may be,
      we shall fight on the beaches,
      we shall fight on the landing grounds,
      we shall fight in the fields and in the streets,
      we shall fight in the hills;
      we shall never surrender

  44. Re:Classic GPL by mhall119 · · Score: 1

    It is if you remember that the context is the device vendors who are going down in a tailspin because the principles of the GPL extend to cutting off everything they need to do business, such as access to purchase licensed technologies.

    Not exactly. The GPL doesn't prevent you from purchasing licensed technology to use with GPL code, it just requires that you grant the license to anyone you distribute the code to, and let them do the same. That is a gist of the MS-Novell deal.

    You've completely missed what's going on, here.

    No, but maybe I worded it poorly.

    It's unfortunate that you feel the need to replace the problem with something of your own device, then say it isn't a problem, then say BSD has the problem too.

    I was actually referring to two different problems. The first, TomTom's problem, is what I said was "not a problem" in the GPL, but rather one of it's principles. The second, the problem of people closing off open code, is a problem to GPL developers, but not to BSD developers, who see it as just another right of open software.

    --
    http://www.mhall119.com
  45. Drivers for TomTomFS? by pentalive · · Score: 1

    Could TomTom have a non fat file system and retain the "see it from the OS" if there were a windows driver for the file system they used? Can one install foreign file systems in windows?

    Could one for instance install a drive for ext3 in windows? Or ReiserFS (to Kill the suit.)

    1. Re:Drivers for TomTomFS? by Lusixhan · · Score: 1

      Yes. However, it mounts an ext3 drive as ext2, so you don't have journaling. Incredibly useful for fetching data off ext2/3 partitions when you don't feel like burning a livecd.

  46. But why use Windows CE? by 91degrees · · Score: 1

    They cross licence the patents and then switch to a different OS. Perhaps BSD would be unsuitable for some inexplicable reason. This is far from their only option. QNX is desiigned for devices like Tomtom, and it's likely to be a lot easier to get Linux software to work on that than Windows. Tomtom have the level of sales that would allow them to get a pretty sweet licensing deal from them.

    Even if Tomtom do switch to Windows. Is there really a major gain for Microsoft here? It's useful for every PC in the world to be running their software, but that's because you need cross-compatibility. Tomtom just needs to be compatible with the software tomtom produce.

    1. Re:But why use Windows CE? by Anonymous Coward · · Score: 1, Informative

      TomTom do have a Windows Mobile port of TomTom Navigator. It is buggy as sin and semi-discontinued but it does exist. (TTN6 was dropped after mass-piracy... they did eventually make TTN7, but it bundles with devices and can't be purchased standalone)

      Having said that, IMHO a court case is just begging them to finally drop the Windows Mobile version once and for all.

  47. Re:Classic GPL by stonecypher · · Score: 1

    Not exactly. The GPL doesn't prevent you from purchasing licensed technology to use with GPL code, it just requires that you grant the license to anyone you distribute the code to, and let them do the same.

    Which is something that's essentially never possible with licensed technologies: you would have to pay the holder enough money for them to forego any other licensor ever. That's effectively saying "you just have to be willing to give anyone who asks for a house a house for one dollar." The sentence makes sense, but the underlying sentiment does not.

    Fee seeking patent holders do not grant such licenses, basically ever, because it ruins their ability to continue their existing business practice.

    You've completely missed what's going on, here.

    No, but maybe I worded it poorly.

    No, you really have. The problem here is that the GPL sets up restrictions which no intermediate vendor can realistically comply with. What this should have done was drive intermediate vendors like TomTom and TiVo to BSD, but they were naive; this is exactly why Steve Jobs avoided the GPL, and as much as I hate him, he made the right choice. Going down the GPL path means constantly looking over your shoulder for unexpected threats and costs, shelling out enormously higher patent costs to third parties for special kinds of licenses they're rarely willing to sell at all, and a variety of other business driver poison pills.

    Sometimes I wonder just how long it's going to take for the patent vampires to start sinking their teeth in. There is a glorious violation minefield out there, and so many penalties and fines just waiting to be had by the people who will soon be called abusers, but who you're currently positing as the defenders of righteous GPL belief.

    Let me ask you a question. What if this kind of lawsuit becomes common? Is the GPL still holding an enviable set of principles then? Is it then all those intermediate vendors' faults? Is this TomTom's fault, for not sticking to GPL principles? Wouldn't you expect the average TomTom user to be happier if they'd used OpenBSD, which would have essentially no impact on the device, but would prevent this lawsuit, the incoming penalties, the service charge increases that the company will have to make to cover it, the bugs that will be introduced when they hastily hack other solutions into place, et cetera?

    Don't you see how this is all wasted work, wasted effort? Why are there lawyers involved?

    It's because of the GPL. If they'd used BSD license properties, none of this would be happening. Yes, it's the vendor's fault for breaking the spirit of the GPL. The problem is, the spirit of the GPL is very carefully structured so that it appears to cause no problems for business. However, if it really didn't, then TomTom wouldn't be stuck in this spot right now.

    Doing normal consumer business may not violate the spirit of the GPL, but the way in which GPL restrictions are written makes it asininely difficult and expensive.

    And when this house of cards starts collapsing? Will you be saying "it protects linux from being run away with"? Nobody's run away with Linux. For that matter, nobody's run away with or closed NetBSD, either. That's a giant red herring. It doesn't happen in the real world. People don't just show up one day with the workforce to completely out-do the generating body. It's not realistic.

    So tell me. What good did the GPL do here? In what way is the set of GPL's restrictions causing more benefit than harm, here?

    And I really don't want to hear a lot of theoretical handwaving about how people might sneak in through an open window one night and steal my source code's good silver. That kind of nonsense doesn't interest me.

    Explain to me how this isn't a clear, obvious example of GPL's catastrophic failure to interact with normal business, or if you prefer, instead how this extremely healthy, large money viable business is being shaken to the ground by a few sentences for a good reason.

    Tell me why GPL is good for TomTom.

    --
    StoneCypher is Full of BS
  48. Re:OPEN SORES software by Sinning · · Score: 0

    Don't you mean CLOSED SORES SOFTWARE?

    /sigh Filter error: Don't use so many caps. It's like YELLING.

  49. Re:Classic GPL by comm2k · · Score: 1

    The GPL DOES NOT cover usage - get it? It covers distribution.

  50. Re:Classic GPL by stonecypher · · Score: 2, Interesting

    Things like this make me wish I could request metamoderation. There was no trolling here, and yet it was done in under ten minutes. If someone's ability to request metamoderation was tuned down if they abused the request, then the metamoderation system would waste less work on articles nobody wants challenged, people would get more involved in metamoderation because they'd be presented with more examples of where it's productive, and problems where metamoderation was required would be less likely to slip under the radar simply because the dice didn't come up.

    Also, a +0, Disagree flag would go a long, long way to solving the constant abuse of troll and flamebait. Sometimes people are just looking for a way to register disagreement, and having a 0 attached to it visibly would help them remember that disagreement isn't meant to alter a score.

    --
    StoneCypher is Full of BS
  51. Re:Classic GPL by Jeremy+Allison+-+Sam · · Score: 4, Insightful

    This :

    "The problem here is that the GPL sets up restrictions which no intermediate vendor can realistically comply with" should get you marked down immediately as -1 Troll".

    Or at least as -1 clueless. Do you know how many intermediate vendors ship GPL code, both v2 and v3 ? It's a *lot*. You can even get patent cross licenses for all your other code so long as the patents you are licensing don't cover the GPLed code. Please post your ignorant long diatribes elsewhere.

    Jeremy.

  52. Those that cannot compete, litigate. by QuietLagoon · · Score: 3, Interesting

    Wasn't that what Microsoft said about the Windows anti-trust lawsuits?

  53. What's the problem ? by Anonymous Coward · · Score: 1, Informative

    All they need to do in order to comply with both the patent and GPL : Get a Microsoft license for the patent, write a new VFAT driver with long file names support from scratch, release it as a binary module (like nvidia drivers for example).

  54. You assume that you have the right to data created by Anonymous Coward · · Score: 2, Funny

    You assume that you have the right to data created by apps you were using,
    by pretending/believing/maintaining it is YOUR data,
    when in fact it is the data of the proprietary apps.

    From the legal perspective, you're making a long shot gamble, not an assertion of fact.

    The data *before you put it into the app* was your data.

    The data *the app created* belongs to the owner of the app.

    Claiming e.g. YOU own the images in your camera's raw format is false: you don't.

    You legally have copyright on the *visual pattern* of their display, not on the data in the file.

    Poor you.

    The OWNERS have rights, and individuals don't own the patent-world: corporates do.

    hahahahaha.

  55. Remember GIF by fritsd · · Score: 4, Interesting

    I'm wondering if a patent can become so diluted that it is unenforceable. FAT is ubiquitous. It is used just about everywhere in every industry in innumerable devices. If Microsoft were to fight to enforce their patent they'd essentially be taking on the entire IT space. I doubt the courts would allow that to happen.

    IIRC, that's exactly what happened to GIF: After it was well established and used, Unisys decided to see dollar signs.

    --
    To be, or not to be: isn't that quite logical, Slashdot Beta?
    1. Re:Remember GIF by aweraw · · Score: 1

      ... and then all of a sudden, the PNG format experienced a massive surge in popularity and usage. Let's hope that something analogous happens in this situation.

      --
      5468652047616D65
    2. Re:Remember GIF by Thinboy00 · · Score: 2, Interesting

      IANAL, but the patent seems to be VERY broad. It basically covers "everything that's not FAT12/16 and is within the same class of stuff as FAT32" (of course such patents are invalid IIRC, but that doesn't mean it isn't expensive and difficult to defend against a lawsuit). In other words, if you make a FAT-lookalike (or even an incompatible filesystem that has similar functionality, even with a completely different underlying structure), Microsoft might still decide it wants to sue you. IANAL, this isn't legal advice, use of the word "you" instead of "one" does not make it legal advice.

      --
      $ make available
  56. Re:Or Maybe... by Anonymous Coward · · Score: 0

    with daddy's money

  57. Re:Classic GPL by stonecypher · · Score: 1

    should get you marked down immediately as -1 Troll

    I agree, if I had said that (cutting half a sentence out of context changes its meaning) that that would be stupid. However, as someone with a four digit UID should know by now, the appropriate moderation is -1, Overrated. I would think you've been here long enough to know what the moderation stamps mean; there's a faq on it. Troll doesn't mean "wrong" and it doesn't mean "disagree with". It means "trying to pick a fight". Troll applies to people who make ugly jokes in order to pick a fight. That isn't one of them, even though it makes you uncomfortable to see someone taking a position you disagree with on solid grounds.

    This is the sort of behavior one expects from religious people in secular discussions. Just because you disagree with someone doesn't mean they're wrong, and it doesn't mean they're causing problems. I would remind you of John Stuart Mill should I believe you'd ever read him: "The worst offense that can be committed by a polemic is to stigmatize those who hold a contrary opinion as bad and immoral men."

    Also, don't use words you don't understand. It's pretty pathetic to see someone use the phrase "ignorant diatribe", when diatribe means "highly educated monologue". The word you were looking for was "speech", though if you wanted to drop big words to seem smart (it doesn't work), you probably should have said "eristic" or "vitriolic". You know, if you knew those words, which given your cumbersome dopery in what is charitably called monologue one tends to doubt.

    Honestly. Ignorant diatribe? It amazes me that you're willing to speak in public, the way people must catch you on details. Were you a speech writer for Bush?

    Do you know how many intermediate vendors ship GPL code, both v2 and v3 ? It's a *lot*.

    Yes, the cutting the sentence out of context game is cute, and all. If you return to context, which was "and who license patents", then that number drops precipitously. Indeed, I would be willing to bet that you cannot name even one, except those who have been sued for it (eg Tivo and TomTom) or perhaps someone you work for.

    Go on, prove me wrong.

    --
    StoneCypher is Full of BS
  58. I have a solution! by Hordeking · · Score: 0

    This is so simple I think I'd have to be stupid to come up with it.

    • Given: We've got an economy that's tanking.
    • Given: Exactly one president who will (he claims) save the economy by hook or by crook.
    • Given: Aforementioned president has indicated that he supports open-source software as the way of the future.
    • Given: Aforementioned president has declared that the American people must SPEND their way out of recession (isn't this a bit lie fighting for peace?)

    Now, given those, we can approach this intelligently. Since Obama wants people to SPEND SPEND SPEND, it makes sense that they need something to spend it on. Now, if Microsoft puts Tom Tom out of business, or the resulting settlement somehow makes Tom Toms get more expensive, people won't be able to spend money on Tom Toms. Therefore, this would be one of those ideal situations to A) promote patent reform, to the benefit of the economy, B) Somehow turn the president against Microsoft, due to their obviously anti-competitive and monopolistic practices that are contrary to HOPE(tm) and CHANGE(tm) and the little people, and C) Convince people to switch to either Linux or Mac. Microsoft has such piss poor FS support. Linux can handle everything under the sun, and some things that aren't. Mac can probably handle more than MS. Windows? It just deals with FATx, ISO9660 (but only on a real CD, no facilities to mount an image), and UDF. If Linux/Mac support their hardware better, I bet people would use those operating systems more. I know I would have in the past.

    --
    Disclaimer: The opinions and actions of the US Gov't are in no way representative of those held by this author or its ci
  59. Re:Should have used Ninnle! by Anonymous Coward · · Score: 0

    I tried Ninnie Linux, but had some issues:

    • Hardware support - I don't know which is worse, other distributions simply not supporting hardware, or Ninnie discovering all hardware perfectly, then insulting your choices: 'Why did you buy from Dell? Their cases are flimsy and their components cheap.' or when I plugged-in a Microsoft mouse, Ninnie said, 'You know all this shit is made by Logitech right?'
    • Porn. Seriously, I like big butts and I cannot lie, but Ninnie won't let me watch any porn that isn't of some supermodel-thin, barely legal girl. Not my cup-of-tea at all.
    • The wireless support is terrible. I hooked Ninnie up to my wireless access point with no trouble, but did Ninnie then really need to crack all my neighbours wireless access points, and DoS the RIAA?

    I tried it, but Ninnie isn't ready for prime-time.

  60. Re:Classic GPL by The+River · · Score: 1

    Limiting "distribution" is clearly a limitation on the use of the software: when you cannot distribute your software, limits have been placed on where it can be used, and by who it can be used by.

  61. Re:Classic GPL by Anonymous Coward · · Score: 0
    Your entire post is based on the premise that software patents have a right of existence.

    Abolish software patents, and the whole problem goes poof.

  62. Re:Really an attack on using Microsoft tech in Lin by drinkypoo · · Score: 2, Interesting

    What TomTom (and others) need to do is start using EXT2/3 on their external cards and then distribute Fuse with their software.

    FUSE for Windows doesn't exist. Someone claims to have one but isn't releasing it. Don't know or much care, since there's not a lot I can do about it. There is an Ext2 "IFS" (installable filesystem?) driver package for Windows; it makes Windows XP far crashier than it already is. There is also an Ext2 access program which I found to not be able to access filesystems I was trying to read at all.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  63. JFFS2 by Khopesh · · Score: 1

    If you're going to start pushing a different filesystem for use on flash-based storage devices, you might as well look at the formats that optimize for such storage mechanism. JFFS2 (which is included even in 2.4 kernels) does this quite well, and there are others, too.

    --
    Use my userscript to add story images to Slashdot. There's no going back.
  64. Re:Classic GPL by The+River · · Score: 1

    Unnecessary legal problems have never happened with any of my libraries, or any MIT/BSD/ZLib library I can name, other than the GPL goons insisting on detail oriented license compatability.

    Neither have they happened with most GPL software projects. This proves no point.

    You're confusing problems with unnecessary problems.

    No, I'm conflating them both with restrictions, since that's what licenses are for.

    The problems other licenses have do not uniformly regard restrictions which serve no purpose.

    I assume you're speaking of the GPL here. I think the "purpose" the GPL restrictions serve have been clearly stated in the "boring" GPL canon. The GPL restrictions serve as much purpose to those developing GPL software as the BSD restrictions do to those using BSD style licenses.

  65. Re:Classic GPL by mhall119 · · Score: 1

    Heh, right, what would Jeremy Allison know about the GPL and patent licenses anyway?

    --
    http://www.mhall119.com
  66. I don't think so by speedtux · · Score: 1

    It is far from clear that Section 7 of the GPL implies that. A cross license just says "whatever patents we have, you can use, and vice versa". A cross license agreement wouldn't impose any conditions on anybody that didn't exist before.

  67. Re:Really an attack on using Microsoft tech in Lin by Muros · · Score: 1

    You might find that those external media are not bought by the vast majority of people. Sorry if I'm getting it wrong, not familiar with Fuse, but I know windows doesn't mount EXT*, and most people want something that works with windows.

    On a different note, and again I know nothing about law, if TomTom are doing nothing unusual in how they implement FAT in linux, is there any possible way of forcing this lawsuit into MS vs. Linux instead of MS vs. TomTom? I would assume that if TomTom are using a product in good faith, and Microsoft has not brought any kind of litigation to successful conclusion to protect any patents that are violated by that product, then Microsoft should have to first settle the fact that that product (Linux) is violating their patents in court, BEFORE being able to initiate any proceedings against users of said product. They are instead going about effectively blackmailing small companies who cannot afford litigation. I'm glad TomTom have stood up to them, but it's unfortunate that a single company has to take the brunt of an indirect legal assault by Microsoft when they seem to be either unable or unwilling to make that legal assault in a direct manner.

  68. Re:Classic GPL by Wolfbone · · Score: 1

    "Also, don't use words you don't understand. It's pretty pathetic to see someone use the phrase "ignorant diatribe", when diatribe means "highly educated monologue"."

    Hahaha... *irony meter implodes*

  69. BSD or GPL by falconwolf · · Score: 1

    Because the primary reason for the success of Linux is that it forces everyone to share their improvements.

    The GPL only requires you to share if you distribute what you added or changed.

    The best you can ever hope for with BSD is an incremental return.

    Nope. The GPL offers freedom for users whereas BSD style licenses offer programmers freedom.

    Falcon

    1. Re:BSD or GPL by Anonymous Coward · · Score: 0

      Because the primary reason for the success of Linux is that it forces everyone to share their improvements.

      The GPL only requires you to share if you distribute what you added or changed.

      The best you can ever hope for with BSD is an incremental return.

      Nope. The GPL offers freedom for users whereas BSD style licenses offer programmers freedom.

      You could provide users with non-GPL freeware and they'd be just happy with the same apparent freedoms that they have with GPL software.

      Give them shareware and they'll probably even be happier, because the author of a paid product often must work harder to meet their needs and requirements to justify the cost.

      Given that the majority of users don't -- and won't ever -- care about distribution rights and code licenses, why optimize your licensing to support them?

  70. Re:Really an attack on using Microsoft tech in Lin by Touvan · · Score: 1

    It would be easy for manufacturers (such as TomTom) to include some modified version of this on their install CDs: http://www.fs-driver.org/ to allow Windows users to access their ext2/3 formatted discs.

    I don't see why that would be a problem. This is the right solution here.

  71. Re:Really an attack on using Microsoft tech in Lin by Teun · · Score: 1

    The last 2 years I bought 3 TomTom Navigators and they don't have any removable media.
    I know they used to but now it's all integrated.

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  72. Re:I disagree! by Lord+Bitman · · Score: 4, Interesting

    Software is covered by patents, there is no need for it to be covered by copyright, too.

    Software is often distributed in binary form: a form which cannot be derived from. The protection, for a limited time, of original works, is meant to allow them to be developed so that people in the future can create derivative works based on them.

      - NO protection without source code.
      - NO copyright on compiled software (makes as much sense as copyrighting a hammer)
      - Patent protections on binaries, contingent on the full source being provided.
      - NO obvious patents.

    Software patents aren't bad, they just have a bad name because stupid ones have been granted.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  73. Re:Really an attack on using Microsoft tech in Lin by Teun · · Score: 1

    Pfff, there are at least two drivers available that allow use of ext2/3 from Windows, once they are installed a Windows computer treats the ext2/3 devices as native. To hook up a TomTom you need to install a driver anyway so including the file system driver is no problem what so ever.

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  74. open source replacements by falconwolf · · Score: 1

    But if the market is "hot" enough, Open Source will eventually be there to eat its lunch. This has been happening over and over again for the past two decades.

    So where's the drop-in replacement for Photoshop? Sure some may be able to get by using GIMP but if you're a pro photographer who does print media then GIMP does not cut it.

    Have you ever written code and released it to the public? Was it used? I have. As a developer making contributions to public projects, I am much more inclined to contribute under the GPL than other licenses. Most of the world feels the same, hence the popularity of the GPL (and similar "viral" licenses) over the BSD-style licenses.

    I hope to RSN. I've been talking about starting my own business combining computers and photography for a while. What I want to do is create a system for pro photographers to use computers and the net to sell photos, I started out wanting to do it for my own photography business. However after hearing a number of other photographers, pros and students, say they wanted to use the net to sell their photos I decided if I'm going to put the tyme and effort into programming my own software it may be worthwhile to sell what I come up with to others. If so I don't want them to just give the source code away to others. With the GPL I can't prevent that but with a BSD license I can.

    Falcon

    1. Re:open source replacements by JerkBoB · · Score: 1

      So where's the drop-in replacement for Photoshop? Sure some may be able to get by using GIMP but if you're a pro photographer who does print media then GIMP does not cut it.

      This is kind of missing the point... There have been other replies that echoed what you just stated. Sure, there are some things that the GIMP doesn't do that Photoshop does. Just as there are some things that Oracle does that MySQL/PostgreSQL don't, etc. etc.

      The fact is, though, that the Open Source options in these markets are undoubtedly hurting the proprietary vendors. More so in some cases than others. Do I think that MySQL is going to kill Oracle? No, but I do think that MySQL has cut into Larry Ellison's jetfighter budget more than a little.

      When I started my career back in the 90s, the first startup I worked at had Oracle running on Solaris. This was for some random web crap running Perl. We paid for those -- they weren't pirated. We even paid for Oracle support a few times. These days, wasting capital on that stuff would be crazy.

      When I say that Open Source is eating the proprietary vendors' lunch, I mean that the OSS alternatives are pushing them into tighter verticals and demolishing the low-middle sections of those markets. One could argue that the people in those sections would have pirated anyway, and that's true to some extent.

      One doesn't have to look much further than Sun to see how OSS has demolished a once-mighty giant. (Open)Solaris is technically superior to Linux, but it's been continually marginalized to specific market verticals (financials and data warehousing with Oracle, mostly).

      ... decided if I'm going to put the tyme and effort into programming my own software it may be worthwhile to sell what I come up with to others.

      As a service or as binaries? Just worth pointing out that you don't have to give away your source code if you're not distributing anything. A common misconception about the GPL is that it somehow compels developers who incorporate any GPL-licensed code into always giving away their code. The only time that comes into play is when you distribute the code. The primary goal of the GPL is to enable the end-users, if they choose to be enabled (e.g. modifying behavior, fixing bugs, security audits, etc.)

      --
      A host is a host from coast to coast...
      Unless it's down, or slow, or fails to POST!
    2. Re:open source replacements by TropicalCoder · · Score: 1

      So where's the drop-in replacement for Photoshop?
      What I want to do is create a system for pro photographers to use computers and the net to sell photos...

      Have you seen this?

    3. Re:open source replacements by Anonymous Coward · · Score: 0

      So first it was FOSS eating someone's lunch, now it is 'undoubtably hurting'.

      Make up your fucking mind.

      And I question your qualifications to proclaim that GIMP is hurting Adobe. Are you an insider at Adobe?

    4. Re:open source replacements by falconwolf · · Score: 1

      So where's the drop-in replacement for Photoshop? Sure some may be able to get by using GIMP but if you're a pro photographer who does print media then GIMP does not cut it.

      This is kind of missing the point... There have been other replies that echoed what you just stated. Sure, there are some things that the GIMP doesn't do that Photoshop does. Just as there are some things that Oracle does that MySQL/PostgreSQL don't, etc. etc.

      And your reply kind of misses my point, which is there's places and uses for both open source and closed source proprietary software. While there are areas where open source fills a need quite well, closed source does as well. Photoshop is one of those closed source programs. I'd love an open source program that could replace PS but GIMP isn't there. Now before I buy PS it, I've been thinking about installing Ubuntu on my Mac to try out CinePaint and see if it can do what I'll want to do. There is a version of CinePaint for OS X but it is not a native Mac app, instead it requires X11 and though I installed both I wasn't able to get CinePaint to run. Unfortunately I wasn't able to find a tutorial or book on it either.

      One doesn't have to look much further than Sun to see how OSS has demolished a once-mighty giant.

      I don't doubt FOOS can and does eat into proprietary closed source software venders. But that's good for a free market. Competition pushes businesses to innovate or make a better product. Microsoft is a prime example. Besides Apple and Linux pushing MS to improving Windows, look at Internet Explorer. Once IE overtook Netscape in browsers used MS basically stopped improving and making IE standards compliant. It was only after Netscape was open sourced and Firefox, which I've been using for years, started growing did MS start improving IE. IE 5 came out on March 18, 1999 and IE 6 on August 27, 2001, about 2 1/2 years later. IE 7 though took 5 years for MS to release it after IE 6, it was released on October 18, 2006. In "August 2007 at the latest. On March 5, 2008, the first public beta (Beta 1) was released to the general public". I doubt if IE 8 have happened so fast if not for the competition from Google's Chrome, Firefox, and Apple's Safari.

      ... decided if I'm going to put the tyme and effort into programming my own software it may be worthwhile to sell what I come up with to others.

      As a service or as binaries? Just worth pointing out that you don't have to give away your source code if you're not distributing anything.

      As I don't want to start a software business I'd sale it as a binary. Selling a service would mean I'd have to provide a service which would take away tyme I could be taking photographs instead.

      A common misconception about the GPL is that it somehow compels developers who incorporate any GPL-licensed code into always giving away their code. The only time that comes into play is when you distribute the code.

      And if I try to sell it I will be distributing it. Sure I wouldn't have to sell it but if I'm going to put the effort into programming I'd like to be able to make more money off of it. There's just no way I could compeat with the commercial venders who sell to pro photographers using the GPL. Thinking of it this way may help, being able to sell software I program could make it worthwhile to take the tyme to program.

      Falcon

  75. Re:Classic GPL by Anonymous Coward · · Score: 0

    If you two could muster enough self control to not add your second paragraphs, you would actually be performing a reasonable discussion, from which you could both learn something.

    Instead, you both feel the need to add personal insults.

    Why? Do you think the insults add anything of value to your discussion? Do you think they will somehow convince your counterpart that you are right?

    Hint: They don't.
    Hint2: Stick to the facts (you both obviously know some of them) and you'll both be better off.

    Or don't, and continue to look like two arrogant twits.

  76. Re:Classic GPL by Teun · · Score: 1

    Tell me why GPL is good for TomTom.

    Sure, without GPL there would be no Linux to run on TomTom hardware.

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  77. It's all about market saturation by SteelAvian · · Score: 1

    They didn't care when TomToms cost $600 and hardly anybody had them, I guess now that everybody got one for the holidays for under $100 they finally noticed

  78. GPL, patents, Irony? by MobyDisk · · Score: 1

    It's ironic that there is a GPL'd FAT implementation, when the GPL forbids licensing patents.

    1. Re:GPL, patents, Irony? by Pinky's+Brain · · Score: 1

      Patent validity and applicability is proven in Texas courts, not by the patent office.

      The mere existence of a patent says just about jack shit nowadays.

    2. Re:GPL, patents, Irony? by ozphx · · Score: 1

      True, however the reason they are proven in Texas courts is because the only patent to ever be rejected was P8978634: "Method of calling the judge a fag".

      --
      3laws: No freebies, no backsies, GTFO.
  79. oh noes, GPL violation by kyliaar · · Score: 2, Insightful

    Make no mistake, this is intended to force Tom Tom to violate the GPL, or change to Microsoft embedded software

    There are other embedded kernel choices besides Linux or Microsoft. The FreeBSD license is much less restrictive than the GPL and wouldn't be broken by most, if not all, cross licensing.

    Why must slashdot polarize things so incorrectly and ignorantly?

  80. Re:Classic GPL by Dan+Ost · · Score: 1

    Use and distribution are distinct concepts.

    "Distribution" is not a subset of "Use".

    --

    *sigh* back to work...
  81. Re:Or Maybe... by Anonymous Coward · · Score: 0

    Not really, as IP is limited in time, so our civilisation can build upon public domain in the long run. In the very short run your rights are protected and you can earn some cash.

  82. With all that's at stake here... by roc97007 · · Score: 1

    Why aren't some other big companies coming to TomTom's defense? "We must hang together or we will hang separately".

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  83. Re:Classic GPL by msuarezalvarez · · Score: 1

    Limiting "distribution" is clearly a limitation on the use of the software

    No it isn't. 'Distribution' and 'use', in this context, have very specific meanings, and they are disjoint.

  84. FUSE for Windows does exist by Anonymous Coward · · Score: 0

    hg clone http://hg.sharesource.org/fuse4win

  85. Proper tactics? by colinrichardday · · Score: 1

    Microsoft's invasion should be defended at the beaches. They should be thrown back into the sea before they create more FUD!

    But as the Germans discovered at Normandy, that allows the enemy to use his heavy naval guns. In this case, Microsoft's lawyers. Tom Tom might win, but this does not fit in with the guerilla warfare model of open source.

    1. Re:Proper tactics? by MarkvW · · Score: 1

      Normandy was a close-run thing. Had the panzers been released, the outcome might have been very different.

      Your point (and your continuation of the metaphor) is interesting!

      I can't agree with it though. If Microsoft wins, then it gets money (that's the only reason to file a commercial lawsuit) and then it gets bolder and stronger. If Microsoft loses, then its argument dies.

  86. Re:Classic GPL by Jeremy+Allison+-+Sam · · Score: 1

    Hmmm. That's not what the dictionary says. Let me check....

    http://dictionary.reference.com/browse/diatribe

    "a bitter, sharply abusive denunciation, attack, or criticism:"

    Yep, that shoe fits. Wear it. Ignorant diatribe indeed :-).

    Jeremy.

  87. Re:You assume that you have the right to data crea by Anonymous Coward · · Score: 0

    So if I have an idea for a novel, which I write on a new type of patented paper using a newfangled patented pen, then the resulting sheet of writing does not belong to me because the tools I used were proprietary and I only own the idea as it exists in my head and the stationery manufacturers own the actual physical document I created?

    Wrong from a moral standpoint, wrong from a legal standpoint, and wrong from a "you're a fucking idiot" standpoint.

  88. Re:Classic GPL by stonecypher · · Score: 1

    Anyone willing to accept a Random House Dictionary citation deserves what they get. RHD doesn't even require degrees from their authors. They accept definitions from any random jagoff who writes pleasantly and convincingly. Neither reference nor citation is required of their definitions. They're no better than Wikipedia.

    From AmHet, a real etymological dictionary: 1581, from L. diatriba "learned discussion," from Gk. diatribe "discourse, study," lit. "a wearing away (of time)," from dia- "away" + tribein "to wear, rub."

    --
    StoneCypher is Full of BS
  89. Re:Classic GPL by stonecypher · · Score: 1

    Linux is neither the only nor even the first free Unix. TomTom could (should?) have been built on other operating systems which are free without restriction. Without GPL, there would have been no barrier to TomTom's being created. With GPL, there is a barrier once they're underway (and indeed a serious one).

    TomTom had other options.

    --
    StoneCypher is Full of BS
  90. Why use FAT anyway? by flyingfsck · · Score: 1

    It is probaly apt pubishment for Tom Tom' stupidity. There is no reason to use FAT anyway. It is not like there is a shortage of better file systems in Linux.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  91. Re:Classic GPL by stonecypher · · Score: 1

    That's an interesting and viable position. It's somewhat telling that the only actual meritocratic statement here was made by an AC.

    Let me ask you a question, in case you're still reading (and watch the three douchebags arguing with me try to pretend to be you): cannot the exact same thing be said of GPL? I'm certainly no fan of software patents, but the parallel I find telling.

    --
    StoneCypher is Full of BS
  92. Re:I disagree! by Zeinfeld · · Score: 1
    Copyright and patents serve entirely different purposes. Patents are much less useful in practice as they expire and they are only available to the first inventor.

    I doubt that the amateur lawyering that began this thread bears any resemblance to reality. In the first place there is a question of who has the right to bring an infringement case and what the scope would be. Linus is highly unlikely to want to get into a patent pissing contest with Microsoft. He is even less likely to try to sue TomTom for signing a cross licensing deal.

    There is also the issue of public policy which in US terms is roughly speaking that the rich be allowed to get richer.

    Microsoft is not a monolith. There are many views on software patents in the company. To date they have spent billions to license other company patents. They seem to be net payers on all their cross licenses. My guess would be that Microsoft's objective is not to get stung by another multi-hundred million dollar patent troll suit.

    If their objective was to use patents to exclude competition from the market they would be idiots. All signs point to the Obama administration returning to the line that existed up till Reagan that severely punished companies with dominant market positions that abuse patent rights.

    --
    Looking for an Information Security student project suggestion?
    Try http://dotcrimeManifesto.com/
  93. Re:Really an attack on using Microsoft tech in Lin by Anonymous Coward · · Score: 0

    prediction of the future

    1 M$ forcing fat on devices by not supporting other fs by default. EU will call it unfair market competition monopolization blabla

    2 m$ is forced to include ext3/4 support

    3 end of m$ fs portable monopoly

  94. Re:Classic GPL by Jeremy+Allison+-+Sam · · Score: 1

    I take great care with my language, which is why I'm bothering to respond, troll though you are (as I correctly categorized you :-).

    From Mirriam-webster online:

    http://www.merriam-webster.com/dictionary/diatribe

    1 archaic : a prolonged discourse
    2: a bitter and abusive speech or writing
    3: ironic or satirical criticism

    Note, your usage is flagged "archaic", much like your anti-GPL tirades :-)

    More information (if such were needed).

    http://www.thefreedictionary.com/diatribe

      A bitter, abusive denunciation.
    [Latin diatriba, learned discourse, from Greek diatrib, pastime, lecture, from diatrbein, to consume, wear away : dia-, intensive pref.; see dia- + trbein, to rub; see ter-1 in Indo-European roots.]
    Word History: Listening to a lengthy diatribe may seem like a waste of time, an attitude for which there is some etymological justification. The Greek word diatrib, the ultimate source of our word, is derived from the verb diatrbein, made up of the prefix dia-, "completely," and trbein, "to rub," "to wear away, spend, or waste time," "to be busy." The verb diatrbein meant "to rub hard," "to spend or waste time," and the noun diatrib meant "wearing away of time, amusement, serious occupation, study," as well as "discourse, short ethical treatise or lecture, debate, argument." It is the serious occupation of time in discourse, lecture, and debate that gave us the first use of diatribe recorded in English (1581), in the now archaic sense "discourse, critical dissertation." The critical element of this kind of diatribe must often have been uppermost, explaining the origin of the current sense of diatribe, "a bitter criticism."

    Again, your usage of the word is "now archaic".

    Please learn the current use of the language before engaging in discourse with your betters, else learn to tug your forelock appropriately :-).

    Jeremy.

  95. Embedded OS/2 ... by cyberspittle · · Score: 1

    Hmmm. Before Microsoft feared Linux, IBM's OS/2 operating system was the biggest threat. Look how that turned out.

  96. Re:Really an attack on using Microsoft tech in Lin by Kalriath · · Score: 1

    HPFS or HFS+? This is very important, HPFS is the OS/2 file system and HFS+ is the Mac OS file system. I'm sure you can guess why the Mac OS file system isn't supported, but an HPFS volume could theoretically mount fine - after all, HPFS by any other name is... you guessed it, NTFS.

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  97. WTF? Hardware and Software patents are different by Logic+Worshiper · · Score: 1

    That's like saying because Ford owns the patent on your car, therefore Ford can tell you where and how you can drive it. A car, like a computer, is a piece of technology, capable of doing many things.

    Someone makes a piece of technology that processes 1s and 0s (hardware). Someone else tells the technology what set of 1s and 0s to process; the hardware is not predisposed to use one set of 1s & 0s over the another, although one set may give a desired result the other set does not. The hardware is a physical object, while the software is information.

  98. You assume that you have the right to GCC. by Anonymous Coward · · Score: 0

    "You assume that you have the right to data created by apps you were using,
    by pretending/believing/maintaining it is YOUR data,
    when in fact it is the data of the proprietary apps."

    You do realize just how nonsensical your statement is? No one would ever be able to use say programming tools, or audio/video equipment. Also your statements have no support in case law.

  99. Re:I disagree! by Anonymous Coward · · Score: 0

    No, software patents are bad. They are like patenting math.

  100. Re:Classic GPL by Anonymous Coward · · Score: 0

    You can even get patent cross licenses for all your other code so long as the patents you are licensing don't cover the GPLed code.

    Jeremy.

    But the GPL applies to a "work as a whole" so by design it cannot be combined with any part that has any restrictions other than exactly the GPL - in anything that qualifies as a 'work'. I've always been amazed that MS has not yet made a patent claim regarding samba that would make it impossible to distribute even to those willing to license the covered code.

  101. Doesn't civilization invalidate it's self? by Logic+Worshiper · · Score: 1

    Civilization is based on the principle of limiting one person's freedom to protect another persons freedom. You don't have the freedom to murder, so you have the freedom not to be murdered. You don't have the freedom to steal, so you have the freedom to keep your property. You don't have the freedom to rape, so you have the freedom to chose to have sex with another consenting adult (if people had the freedom to rape, you couldn't chose when to have sex, it would be forced on you). This concept is called civilization; the alternative is might = right.

  102. Re:I disagree! by Raenex · · Score: 1

    Software is often distributed in binary form: a form which cannot be derived from.

    And you call yourself "Lord Bitman"?

    The protection, for a limited time, of original works, is meant to allow them to be developed so that people in the future can create derivative works based on them.

    Even just having a copy without changes is to the public benefit.

    Software patents aren't bad

    Yes they are, because they are completely unneeded. They bring far too much harm for any proposed benefit. All you have to do is look at the industry before software patents were available.

    they just have a bad name because stupid ones have been granted.

    It's hard to say what is stupid. Lots of things sounds obvious after somebody has spent the time researching and coming up with a clever solution. Then again, research into software has such a low threshold that invariably somebody will come up with a good solution and make it popular. It's a damn shame to lock up all this technology for twenty years, because in the end it retards the growth and competitiveness of the industry.

  103. Re:I disagree! by Anonymous Coward · · Score: 0

    A friend of mine used to say, and I have to agree - I find it insulting that anyone would insinuate that I cannot read a binary. The idea that it cannot be processed by a human is an artificial restriction, and only demonstrates a lack on knowledge of how to read it. A binary is source code.

  104. BSD license worse than broken: controlled by MS by jonaskoelker · · Score: 1

    The FreeBSD license is much less restrictive than the GPL and wouldn't be broken by most, if not all, cross licensing.

    Well, that depends on the licensing deal.

    Let's say Tom Tom only uses BSD-licensed code, and gets a license from MS to redistribute the code as much as they want, royalty-free.

    Well, that must mean MS has a patent on something in (say) FreeBSD. They then go around and sue FreeBSD for patent violation, and demand royalty from any distribution of the code.

    Now Microsoft "owns" FreeBSD and can decide who it will be "sold" to, and how much Microsoft earns for "selling" it.

    I think that's broken. You apparently disagree. Is that appearance real?

    1. Re:BSD license worse than broken: controlled by MS by Anonymous Coward · · Score: 0

      I believe the redistribution factor was in regards to software built on top of GPLed code, which has a lot of qualifications on being able to redistribute code, particularly in commerical uses.

      For Microsoft, it is pretty much 'Pay us a license fee and you can use our embedded systems and libraries to build software that you can then resell'. Microsoft is suing for patent infringement and is asserting that, in order for TomTom to use that functionality, must pay a license fee.

      I believe then they would be paying microsoft a license fee for code that can not be re-distributed under the openness of the GPL. Microsoft would own that functionality due to the patent. Thus, forcing them away from a licensed use of the linux kernel.

      With a FreeBSD license, they would be able to redistribute the code that is licensed without any requirements to also redistribute other code that was built on top of that code.

      Microsoft could go after FreeBSD specifically for code that they've released but that is an entirely different legal proceeding than what is going on.

      That is my understanding of the issue.

  105. Re:I disagree! by PCM2 · · Score: 1

    Software is often distributed in binary form: a form which cannot be derived from.

    That's just not true. Back in junior high, I figured out the binary format that Origin Systems used to store the maps for the game Ultima III. Using a floppy disk sector editor, I went in and changed the maps and then distributed copies of my modified version of the game to my friends who were certifiable Ultima III junkies. I bet it wouldn't take much to convince a jury that I had created a derivative work.

    --
    Breakfast served all day!
  106. You lose by js_sebastian · · Score: 1

    one of the worst configuration file formats ever

    Wrong. I hold up for example: XML, the Windows Registry, and sendmail.cf

    The argument is over, and you lose... or does mentioning sendmail.cf not trigger Godwin's law?

    1. Re:You lose by badkarmadayaccount · · Score: 1

      Did you just meta-Godwin this thread?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  107. Re:Classic GPL by Teun · · Score: 1
    While you keep repeating the BSD style licenses have advantages over the GLP you should also take time to think about why Linux more than BSD has over the years gained far more support from companies and individuals. Surely not (only) because the code base is better.

    In this particular case a BSD OS would still have the same problem when implementing a FAT LFN extention.

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  108. Re:Really an attack on using Microsoft tech in Lin by houghi · · Score: 1

    What they should do is make their software usable under Linux. I can not buy a map and activate it, unless I have Windows (or use somebody elses machine)

    --
    Don't fight for your country, if your country does not fight for you.
  109. but when you approach the linux lords by Anonymous Coward · · Score: 0

    and offer your services, you'r asked to f**k off too. Then what do you do? Use Linux and shut up. That's what I'm doing for over a year now.

  110. And an imminent problem.... by Anonymous Coward · · Score: 0

    The same scenario looks to be set for SDXC cards - they are likely to use exFAT which is an M$ proprietary format. Hopefully enough word will get round as a result of the TomTom issue that manufacturers will consider switching to UDF. Might be too late for that though, I'm not sure if the SDXC standard includes the card format.

  111. Re:I disagree! by Lord+Bitman · · Score: 1

    Patents, in the U.S., expire. Copyright, in the U.S., does not expire. By the time either expires, there is no benefit at all to having a binary. I challenge you to benefit from a 20-year-old binary anything. You're generally screwed unless you have the source for either it, or for what it was meant to operate on.

    Yes, it is hard to say which ones are stupid. That's a reason to not grant them easily, not a reason to abolish them. The same could be said of pretty much any invention, ever. More harm is done to competitiveness through lack of implementation details (which patents require, and the current broken copyright system does not) than could ever be done by a waiting period.

    And you call yourself Raenex?!

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  112. Re:I disagree! by Lord+Bitman · · Score: 1

    I think that if you tried to submit something as heavily-obfuscated as the binary form of something which was originally written in a high-level language to a patent examiner, they'd throw it out.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  113. Re:I disagree! by Lord+Bitman · · Score: 1

    Comparing binary "data" to an executable seems extremely flawed to me, due to the huge difference in the level of complexity usually seen. As is saying "I can reverse-engineer it, therefor it doesn't need patent protection", since that argument, if valid, could be applied to anything which has ever been patented.

    Try doing that usefully when the copyright has expired / would have expired, then we'll talk. By then, the hardware used to run the software used to read the modified data will be such ancient history it will be hard to even determine what it was named. Had you the source code, you have to admit it would likely be easier to derive from.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  114. Re:Should have used Ninnle! by Anonymous Coward · · Score: 0

    That's cos you got a cheap ripoff. Now try Ninnle, with an L, not Ninnie. Ninnle HAS been prime time for some time now.

  115. Re:I disagree! by Raenex · · Score: 1

    I challenge you to benefit from a 20-year-old binary anything.

    I have. I've played old games under simulators. People have even hacked around some of these games to make them playable online with multiple players. I've run old mainframe software under simulators. Where there's a will, there's a way.

    Yes, it is hard to say which ones are stupid. That's a reason to not grant them easily, not a reason to abolish them.

    Many ideas are generally patent worthy, but I'd rather have the chance to re-invent it myself than have it monopolized for twenty years.

    More harm is done to competitiveness through lack of implementation details (which patents require, and the current broken copyright system does not) than could ever be done by a waiting period.

    No way. Open source can reverse engineer and re-implement around proprietary programs. Patents put up a significantly higher barrier.

  116. Re:Classic GPL by iplayfast · · Score: 1

    Or maybe you could look to see who the authors of the post are before calling people names yourself.

  117. New Rights by clbyjack81 · · Score: 1

    ... and depriving consumers of their fundamental right to have access to data of their own creation.

    Why do we need to keep creating new rights? I thought we had a right to life, liberty, and the pursuit of happiness. I don't recall the founding documents mentioning healthcare, housing, or the interoperability of manufactured goods as fundamental rights.

    ... our duty to users everywhere to violate those bits of intellectual property at every possible opportunity until it becomes such a legal nightmare for these companies that they are forced to back down. Anything less would be uncivilized.

    Another alternative is to petition your congressman/woman to change the laws to the same effect. I would imagine this to be a more civilized answer.

    I know, I'm an idealist.

    --
    Cole's Axiom: The sum of the intelligence on the planet is a constant. The population is growing.
  118. Re:Classic GPL by MHDK · · Score: 1

    BSD licences cause problems too, of a different nature of course, so it is difficult to discern any substance to your comment. Has the GPL caused the problem, or did Microsoft cause the problem with their patent? I suppose it depends on what problem is being referred to here. Is the problem that a lawsuit has arisen? Or is the problem that people cannot do sensible and ethical things with their computer equipment? The GPL seems to cause difficulties using computers via legal troubles, whereas the BSD licence seems to cause difficulties using computers via the extortion that results from people using more popular versions of modified BSD code.

  119. No-one can comply with the GPL. by Fzz · · Score: 1

    It is, and should be, a GPL violation to secretly get a patent license. If TomTom were to cave to MS without getting slapped with a GPL violation, then anyone who uses tomtom's work would be opening themselves up to patent infringement suits.

    Actually, at this point, anyone distributing the Linux kernel (whether they are TomTom, RedHat or Linus) has already opened themselves up to patent infringement suits if they are located in the US. Whether or not TomTom license the patents does not change this. The only thing that changes this is if TomTom fight it and the patents are found invalid.

    Whether TomTom licenses the patents or not, right now no-one in the US can legally distribute the Linux kernel. There really isn't any doubt that it violates the FAT patents. As we all know about these patents now, none of you located in the US can really agree to the terms of the GPL when you redistribute Linux.

  120. Re:Classic GPL by MHDK · · Score: 1

    Your comment about GPL causing problems was nothing more than vague invective so there does not seem any grounds for complaint.

  121. Moody and Allison need to re-read history on GPLv3 by morganew · · Score: 1

    I'm bothered that FSF has pulled down the discussion and dialog that led to the GPLv3, but if anyone can find it, you will see that under v2 you could structure a patent licensing deal in a way that did not cover downstream users of the code. The clear and obvious example was the Novell deal. v3 was altered to prevent patent deals like the Novell deal (and you'll note that Linux still seems to stick with v2).

    So for Jeremy to argue that deals can't be done under v2 flies in the face of Eben Moglen's reading of the law. And while Jeremy's a better coder, Moglen's a better lawyer.

    This is pure bunk. Ignore and move on.

    --
    A sig?!? I don't think so.....
  122. Re:I disagree! by PCM2 · · Score: 1

    Comparing binary "data" to an executable seems extremely flawed to me, due to the huge difference in the level of complexity usually seen.

    There's no difference in complexity. Bytes is bytes.

    Yes, I am being dead serious. In my younger days I used to input machine language -- yes, you heard that right, I did not say assembly language -- programs directly into the system monitor as hexadecimal numbers. One needed to decode the same numbers in order to crack the copyright protection on computer games. All of this was commonplace, once.

    I'm not saying that it just as easy to decipher machine code as it is source code, but so far as I know there's no "harder to do" provision in intellectual property law. It's harder to make a bit-for-bit copy of a CD than to copy an LP record to cassette tape, but both are equally against the law.

    As is saying "I can reverse-engineer it, therefor it doesn't need patent protection"

    I don't think anyone has ever made that argument. What they're saying is that computer software is already adequately covered by copyright law and therefore does not need the additional (and problematic) protection of patents.

    Try doing that usefully when the copyright has expired / would have expired, then we'll talk. By then, the hardware used to run the software used to read the modified data will be such ancient history it will be hard to even determine what it was named. Had you the source code, you have to admit it would likely be easier to derive from.

    I don't understand this paragraph at all.

    --
    Breakfast served all day!
  123. Re:I disagree! by PCM2 · · Score: 1

    I think that if you tried to submit something as heavily-obfuscated as the binary form of something which was originally written in a high-level language to a patent examiner, they'd throw it out.

    Likewise, a patent application for a new type of drill that consisted of a prototype of the drill and nothing else would be thrown out. A patent application consists of a description of the invention, plus any relevant articles (such as a prototype). No description, no patent.

    But the parent's point stands -- humans have interpreted all sorts of binary codes since the dawn of computing, and continue to do so. Just because you can't understand a given code doesn't mean somebody else can't. If I'm applying for protection under intellectual property law, why should I only be protected from you but not from someone more technically sophisticated than you?

    --
    Breakfast served all day!
  124. Re:I disagree! by ion.simon.c · · Score: 1

    I challenge you to benefit from a 20-year-old binary anything.

    I take it that you've heard of neither IDA nor OllyDbg? :)

  125. Re:I disagree! by ion.simon.c · · Score: 1

    Try doing that usefully when the copyright has expired / would have expired, then we'll talk. By then, the hardware used to run the software used to read the modified data will be such ancient history it will be hard to even determine what it was named. Had you the source code, you have to admit it would likely be easier to derive from.

    This makes no sense. US copyright terms can be longer than 90 years. I very much doubt that a binary would be any hard to run or reverse engineer than a source file. (Hell, if you have the binary, and have knowledge about the processor that it was designed to work on, you may be *closer* to a working program than if you just have the source code. You no longer have to write a compiler for whatever crazy language the source code was written it. "All" that's left in the task is to write a CPU and OS emulator.)

  126. What about IBM/HP/Intel/Novell/Sun? by Anonymous Coward · · Score: 0

    Is Jeremy Allison saying that by licensing a patent TomTom wouldn't be able to distribute GPL2 software any more? Huge companies like IBM, HP, Intel, Novell, Sun, etc. have licensed tons of patents AND they're all distributing Linux and other GPL2 Software. What do they know that Jeremy doesn't?

    1. Re:What about IBM/HP/Intel/Novell/Sun? by Jeremy+Allison+-+Sam · · Score: 1

      Remember I used to work for HP. The patent cross licensing deals done by companies like HP and IBM (don't know about Sun) explicitly exclude free software/open source use. They have very sophisticated legal departments that know the GPL *very* well. Their patent cross licensing doesn't include GPL code.

      Jeremy.

  127. Have you seen by falconwolf · · Score: 1

    this

    I hadn't seen it before. I looked at the site and notice it needs a net connection. I want to be able to work with photos offline. I also searched Photo.net but didn't see anything about it.

    Falcon

  128. Re:Really an attack on using Microsoft tech in Lin by badkarmadayaccount · · Score: 1

    "Hello, operator? Could you set up a conference call with IBM, Sun Microsystems and Google legal departments? Thank you. "

    If I have to use this one more time, I might as well add it to my .sig...

    --
    I know tobacco is bad for you, so I smoke weed with crack.
  129. Re:Classic GPL by listen · · Score: 1

    Your claim is that paying for a patent licence in "merely aggregated" software results in being unable to distribute any software under the GPL. In the cases you state - Fraunhofer & Dolby, the patent licenced software is in userspace, which is a clear "mere aggregation" boundary set out by major copyright holders. Seperate processes, or running your code in a chip, are also pretty much watertight boundaries. And almost certainly other "not quite" process things like running a bit of firmware in kernel space is very very unlikely to be found to be a derived work of the kernel and thus have any effect on this ... so, unless tivo are idiotic enough to do codecs in a kernel module rather than in hardware or in userspace, it doesn't matter.

    This case is different, it is about patent violations *in* a particular bit of GPL'ed software, ie FAT in the kernel. And no, I'm not a GPL zealot, I find it incredibly irritating in a huge number of situations - basically the point at which a project grows up and realises it wants to be a platform or library, and then has to go through a relicencing nightmare. I would never make new code GPL'd, unless its on a project that can't possibly relicence.

    However I do get tired of people claiming to have found fatal flaws in the GPL : the aim I think is wrong, but take some time to understand that the implementation is solid.

    The legal coward solution to this is to use a fuse implementation of vfat, and pay the ridiculous MS tithe. This way you don't impact on the GPL licence you were granted for the kernel.

  130. Re:Really an attack on using Microsoft tech in Lin by badkarmadayaccount · · Score: 1

    HPFS is based on FAT32, only it sorta fixes it, and adds up to 2TB file system support, and NTFS was made from scratch by the OpenVMS team from DEC. HPFS was included in the Windows NT series up to 4.0 to aid the transition from existing OS/2 installs, with a OS/2 compatibility layer remaining in Windows XP © as reminder of times gone by. Also, a separate HPFS driver is available for later NT versions.

    --
    I know tobacco is bad for you, so I smoke weed with crack.
  131. Re:Really an attack on using Microsoft tech in Lin by badkarmadayaccount · · Score: 1

    No ext3, the journaling is gonna burn the flash faster than XP with an overloaded Firefox swapping. Just ext2.

    --
    I know tobacco is bad for you, so I smoke weed with crack.
  132. Re:Really an attack on using Microsoft tech in Lin by Kalriath · · Score: 1

    Interesting, are you 100% sure that HPFS and FAT32 are the related ones? I mean, if you open FDISK (the old DOS partitioning tool) it recognises all HPFS partitions as NTFS ones.

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  133. Re:Really an attack on using Microsoft tech in Lin by badkarmadayaccount · · Score: 1

    Maybe DOS understands file systems in terms of "native" and "non-native". Though I've been through some docs, (Google is your friend) and it seems just that - an improved FAT. Even M$ agrees. ;)

    --
    I know tobacco is bad for you, so I smoke weed with crack.
  134. Re:Really an attack on using Microsoft tech in Lin by Touvan · · Score: 1

    fs-driver only supports ext2 anyway, so I guess that's bonus. :-)

  135. Re:Really an attack on using Microsoft tech in Lin by ion.simon.c · · Score: 1

    I mean, if you open FDISK (the old DOS partitioning tool) it recognises all HPFS partitions as NTFS ones.

    I would imagine that FDISK is just looking at the "partition type" (0x07 for "HPFS/NTFS" ones, 0x82 for Linux swap and 0x83 for Linux partitions), rather than figuring out what the disk has actually been formatted with.

    I haven't used FDISK in YEARS... pardon any inaccuracies.

  136. Re:Really an attack on using Microsoft tech in Lin by ion.simon.c · · Score: 1

    Also, sorry if the point of your comment *WHOOSHED* over my head. (I've been kinda thick-headed today.)

  137. Re:Really an attack on using Microsoft tech in Lin by Kalriath · · Score: 1

    Ah, that would explain it. I assumed it was considerably more intelligent than it actually is.

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  138. Tom Tom is Dutch by Dollyknot · · Score: 1

    Ok so Microsoft takes Tom Tom to court in the US, I should imagine the Dutch people would have something to say about that, sort of like get lost.

    I have a Tom Tom. and the fact that it runs Linux gives me pleasure.

    So MS wins in the American court, to achieve anything it must also win in the Dutch court this is laughable.

    SCO all over again.

    Also what is to stop Tom Tom changing their file system?

    --
    It's called an elephant's trunk whereas it is in fact, an elephant's nose, a nose by any other name would smell as sweet