From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 73CEABC6B for ; Thu, 20 Sep 2007 20:14:56 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALZV8kbAXQImn2dsb2JhbACOFQEBAQEHBAYHCBg X-IronPort-AV: E=Sophos;i="4.20,279,1186351200"; d="scan'208";a="16493557" Received: from discorde.inria.fr ([192.93.2.38]) by mail4-smtp-sop.national.inria.fr with ESMTP; 20 Sep 2007 20:16:21 +0200 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l8KIFS4l001331 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Thu, 20 Sep 2007 20:15:33 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALZV8kZK0ATEnmdsb2JhbACOFQEBAQEGBQYPARc X-IronPort-AV: E=Sophos;i="4.20,279,1186351200"; d="scan'208";a="1479358" Received: from mout.perfora.net ([74.208.4.196]) by mail2-smtp-roc.national.inria.fr with ESMTP; 20 Sep 2007 20:16:15 +0200 Received: from 72-173-38-22.cust.wildblue.net [72.173.38.22] (helo=[192.168.1.4]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis), id 0MKpCa-1IYQZ72P6z-0007PW; Thu, 20 Sep 2007 14:16:05 -0400 Message-ID: <46F2B89A.6030009@nc-sys.com> Date: Thu, 20 Sep 2007 11:14:50 -0700 From: Ken Rose Reply-To: rose@acm.org User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.6) Gecko/20070813 SeaMonkey/1.1.4 MIME-Version: 1.0 To: caml-list@inria.fr Cc: skaller Subject: Re: [Caml-list] Re: [ANN] coThreads 0.10 References: <87lkb5fe3f.fsf@pps.jussieu.fr> <87sl5d8cgd.fsf@pps.jussieu.fr> <46F174D9.5060900@ujf-grenoble.fr> <877imm2z7h.fsf@pps.jussieu.fr> <1190249430.6642.1.camel@rosella.wigram> <20070920142938.d48552f2.mle+ocaml@mega-nerd.com> <1190272316.23116.34.camel@rosella.wigram> <20070920175233.a510630b.mle+ocaml@mega-nerd.com> <87abrhka16.fsf@pps.jussieu.fr> <1190284989.6770.28.camel@rosella.wigram> <87abrhwopc.fsf@mid.deneb.enyo.de> <1190303208.6036.33.camel@rosella.wigram> In-Reply-To: <1190303208.6036.33.camel@rosella.wigram> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19hIXWFLxLIzRSk8bjRcXCImMTtpW9eRQKh1Fw j0BtwjcInNmQbWM2P3FfKBcMWgQvTQn9/bjv+8PjReGj6OW0lD //IYiXW6DvsNSAO0gDSKNBvXs3z7dGv X-Miltered: at discorde with ID 46F2B8C0.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; linkable:01 hacker's:01 0.10:98 producers:98 ffau:98 wrote:01 caml-list:01 partially:02 masked:02 binary:02 library:03 library:03 depends:04 perhaps:05 modify:05 skaller wrote: > Whether or not the conditions are straightforward to fulfil > depends on the producers goals. If you were making an embedded > application it would almost certainly not be, and it would > be a legal impediment. Do you know any vendors of console > games, for example, that tell you how to modify a part of the > game? The software build processes used are almost certainly > trade secrets. > > Even in my own FFAU product, whilst the whole of the sources > is available for inspection and modification, I certainly > don't document all of it -- if you want to modify a library > you'll have to go read all the source and find out yourself. > > It isn't clear that satisfies the "make it possible for the > client to replace the library" requirement. There was a discussion ten years ago or so, perhaps on the cross-gcc list, that Stallman joined. He said something to the effect that if you provided object code in a linkable format (even partially linked) so that a user could link in the library in question, you'd satisfied the license. You didn't have to provide instructions, guidance, or help. If the binary then had to be embedded in a masked ROM in the middle of your giant ASIC, that was the hacker's problem, not yours. - ken