From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263527AbTEIWhL (ORCPT ); Fri, 9 May 2003 18:37:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263548AbTEIWhL (ORCPT ); Fri, 9 May 2003 18:37:11 -0400 Received: from smtp-out2.iol.cz ([194.228.2.87]:56252 "EHLO smtp-out2.iol.cz") by vger.kernel.org with ESMTP id S263527AbTEIWhH (ORCPT ); Fri, 9 May 2003 18:37:07 -0400 Date: Fri, 9 May 2003 12:59:06 +0200 From: Pavel Machek To: "David S. Miller" Cc: Dax Kelson , Larry McVoy , "Downing, Thomas" , Linux Kernel Mailing List Subject: Re: Why DRM exists [was Re: Flame Linus to a crisp!] Message-ID: <20030509105906.GA2895@zaurus.ucw.cz> References: <1051789446.8772.13.camel@rth.ninka.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1051789446.8772.13.camel@rth.ninka.net> User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > Current --in production-- DRM. Clearly no. Current DRM is mostly all > > targeted to audio / video content protection. > > > > So, nothing that we have *today* is a response to Open Source. > > I can't believe nobody talks about TiVO and what they're doing (only > allowing signed Linux kernels to boot on their machines). > > That is DRM, and directly in response to open source. When they make their bootloader only boot one particular kernel, they are essentially making bootloader&kernel same product, right? That does not seem "mere aggregation" to me... Pavel -- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...