On Sun, Jun 17, 2007 at 05:17:57AM -0300, Alexandre Oliva wrote: > Just make the tivoization machinery require two keys: one that the > vendor keeps, one that the vendor gives to the user (maybe without > ever knowing it). Neither one can install modifications alone, but > the user can approve modifications by the vendor, and the vendor can > approve modifications by the user. This is still not ideal, but it at > least doesn't permit the vendor to remove features from under the > user.
So what features has Tivo removed (or threatened to remove) from the GPL licensed parts? I think at some point they disabled the _undocumented_ skip feature in their own proprietary software, and ended up reenabling it when a lot of customers complained. Even if those customers had the ability to replace any GPL licensed parts, it would not have reenabled the feature. And it was an undocumented easter egg type thing at that, it isn't like they widely announced it in their advertising or as a selling point. So Google is using Linux right. What if they remove some feature? (let's pick a randomg one, i.e. phone number lookup) Should I get a keycard for their machine room to fix the problem, or maybe we should use some secret sharing mechanism to prevent them from removing the feature. > RMS does not want TiVo (or anyone else) to disrespect users' freedoms, > and installing technical measures to prevent users from adapting the > software to suit their needs and running their modifications is > disrespecting users freedoms. So if Tivo would allow you to boot your own kernel, but keeps the harddisk encrypted if the booted kernel does not have the right signature? In such a case you can run your own kernel and if you replace the harddrive you can install all the applications you might want. You cannot however use their software, any of the recorded content or obtain any further guide data/service updates. And how is that any different from taking an off-the-shelf PC and booting your own kernel with Tivo's modifications? Or really different from the current situation. Tivo complied in as far as they made GPL licensed code available, you can examine it, modify it, compile it. You just can't use it _in combination with TiVo's own software and service_. I didn't think the GPLv2 covered anything related to use and you have retained all the freedoms the GPL promises. > That he is not opposed to the idea of TiVo using a GPLv3 kernel is > easy to see, if you take the time to read the draft instead of > spreading false assumptions about it: > > this requirement does not apply if neither you nor any third party > retains the ability to install modified object code on the User > Product So they keep the system locked down, but include perl/python/emacs and distribute updates in the form of scripts/source code which are either interpreted or compiled to a ramfs filesystem at boot. Time to add another exception? Jan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
