Slashdot Mirror


How Nokia and Linux Can Live Together

Bruce Perens writes "Ari Jaaski of Nokia is concerned that the Linux developers need to learn to live with DRM, SIM-locking, and 'IPR'. But they won't. Fortunately, Nokia can do all that it wants with Linux, while being GPL2 and even GPL3-compatible. The key is knowing how to draw bright lines between different parts of the system. That's a legal term, and in this case it means a line between the Free Software and the rest of the system, that is 'bright' in that the two pieces are very well separated, and there is no dispute that one could be a derivative work of the other, or infringes on the other in any way. All of the Free Software goes on one side of that line, and all of the lock-down stuff on the other side." A very interesting read, and a good how-to for any company that is looking to use GPLed code as part of their products, or even just make their products to be hacker-friendly.

3 of 155 comments (clear)

  1. The Bright Line by camperdave · · Score: 5, Interesting

    Looks like the Bright Line for me may be the Nokia label, if they are going to maintain their attitude.

    --
    When our name is on the back of your car, we're behind you all the way!
    1. Re:The Bright Line by mrsteveman1 · · Score: 5, Interesting

      I don't think Nokia is taking the wrong position here, they have to satisfy a number of different interests, and as long as they comply with the license terms of the software they use I don't see a problem.

      The alternative is to choose a different OS to build on, and with some exceptions most open source advocates don't want to see that happen, because it would be bad for the platform if companies stop using it.

  2. What's IMHO the problem here... by Enleth · · Score: 5, Interesting

    When I learned electronics, engineers built products by soldering together resistors and transistors. But today, the job of engineers is to build derivative works by combining units of intellectual property owned by third parties. That's not what they're trained for, and it's a mine-field of potential litigation for every company that puts software in its products This is exactly why, while being fascinated with electronics and embedded systems, I don't want to work in the consumer product industry when I graduate. Even if the pure research work in the field pays less than product development. I feel that the "engineering" constrained by sales requirements and legal gibblerish is not really engineering anymore and, being able to see its outcomes - dozens of devices that show unspeakable amounts of absolute blockheadedness and lack of ANY thought in their design - I don't want to have anything to do with it.
    --
    This is Slashdot. Common sense is futile. You will be modded down.