Open Source at TiVo 226
CowboyRobot writes "ACM Queue has an article by TiVo co-founder Jim Barton, in which he explains how the company relies on open source technologies to create a closed-source product. A good lesson in how other companies can do the same. From the article: Careful management of our sources to abide by the terms of the GNU General Public License while protecting our proprietary developments is a small price to pay for this benefit."
Readable version (Score:3, Informative)
The "printable version" [acmqueue.org] is far easier to read.
Re:Nice one Jim ... (Score:5, Informative)
Ummm.. yea, everyone basically does this. (Score:5, Informative)
The old point was, pay for a product, you pay for support; however, this is not true anymore (just try and call MS technical support without having a license you pay $1000 for).. But something like MySQL or PHP you can easily and quickly get help in any forum..
But I digress.. the point is, most "smart" companies do this to keep costs down.
always (Score:5, Informative)
TiVo runs a modified version of Linux, which is protected by the GPL. Therefore, legally they have always been required to release their source.
TiVo has distributed source code for the version of the Linux kernel included in the devices [tivo.com] for as long as I can remember.
Re:finally (Score:4, Informative)
What are you talking about? [tivo.com]
Re:Interesting quote (Score:4, Informative)
It is the GPL v2 with the following preamble:
NOTE! This copyright does *not* cover user programs that use kernel
services by normal system calls - this is merely considered normal use
of the kernel, and does *not* fall under the heading of "derived work".
Also note that the GPL below is copyrighted by the Free Software
Foundation, but the instance of code that it refers to (the linux
kernel) is copyrighted by me and others who actually wrote it.
Linus Torvalds
Doesn't seem to be anything other than user level code mentioned here, I guess we must assume that TiVo's modifications are user level.
John.
Re:Good for Open Source? (Score:4, Informative)
Re:Nits (Score:2, Informative)
Having signed for more than my fair share of VA Linux hardware deliveries, I can confirm that they did, indeeed, have their own distribution (in the loosest sense).
The distro was based off of RedHat, carried the same revision numbers as RedHat, but came on VA-labeled media with VA-specific software for server administration.
% cat
VA Linux Release 6.2.4 02/21/01
Tools vs. Applications (Score:4, Informative)
"Keep the tools open and free: Make your money from developing applications."
Mr. Butler and company have done well following this philosophy.
Great article too.
How 'bout Wine? (Score:3, Informative)
I just had blazing success with Paltalk. The harder it is for you to use Linux in your niche, the more significant an accompolishment it will be when you are finally able to go 100% Windows free.
Best of luck!
Don't be mislead by the language of the article. (Score:3, Informative)
The article gets some concepts profoundly wrong when it comes to discussing licensing (which is at the heart of the article). These items may confuse readers not already familiar with copyright law and the Free Software community.
Toward the bottom of the article "Public domain soft-ware [sic]" is mentioned and the "X Window System and BSD operating system" are cited as "notable" examples. Then the article mentions a "license limitation" that is only true for the old BSD license. This clearly illustrates the author is confused about what the public domain is and that works cannot be both licensed (as these examples are, under different but largely similar licenses) and in the public domain. Placing a work in the public domain is not a license, no matter how liberal the license's terms may be. Putting a work into the public domain is the irrevocable abdication of all copyright power over the work.
The terms "Linux" and "GNU/Linux" are used interchangeably, as if they both refer to the same thing (early in the article "Linux" is meant to refer to an operating system, later on "GNU/Linux" refers to an operating system). The GNU Project asks (and simple fairness requires) that we give GNU a fair share of the credit for their work in the GNU/Linux operating system. Technical precision requires us to distinguish between the Linux kernel and a GNU/Linux operating system. To these ends, the GNU Project publishes a FAQ [gnu.org] on the issue of naming GNU/Linux, and an older essay [gnu.org].
Finally, just to be clear, the Open Source and Free Software movements are not the same. They have different philosophies, they began at different times, they were started by different people, and they speak to different audiences. The GNU Project's essay on the two movements and their social implications [gnu.org] is helpful.
Re:Interesting quote (Score:4, Informative)
binary modules are allowed; and by using a boot PROM which verifies the kernel has a valid signature they can be sure the kernel is approved by them. (Series 2 units with the latest kernels are extreemly difficult to hack in the same way as the first units.).
Linus at some point specificly mentioned that doing a signature check was outside of the scope of the Linux kernel copyright and GPL license. So Tivo is on the up-and-up. Even if it upsets some people.
Re:Good for Open Source? (Score:4, Informative)
Go to this site [bclary.com] and install the Mozilla evangelism sidebar. Set your user agent string to something IE5ish. I'll bet that a recent Mozilla will work just fine. After all, the sign says ``IE5 or better''!
I've done this on several IE-only sites, and had great results.
Re:hmmm (Score:4, Informative)