From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21834 invoked by alias); 16 Dec 2005 02:57:59 -0000 Received: (qmail 3865 invoked by uid 22791); 16 Dec 2005 02:35:33 -0000 X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,BAYES_40,RCVD_IN_SBL,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <43A227EC.DBB68282@dessent.net> Date: Fri, 16 Dec 2005 02:57:00 -0000 From: Brian Dessent Organization: My own little world... X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,en-US MIME-Version: 1.0 To: cygwin-licensing@cygwin.com Subject: Re: 1NIWGYC.DLL ?? References: <005301c601cb$8cc46d70$2602a8c0@itefixb> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-licensing-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-licensing-owner@cygwin.com X-SW-Source: 2005-q4/txt/msg00007.txt.bz2 Tevfik Karag=FClle wrote: > on the target machine. However, It is tempting to find an ultimate soluti= on to this problem: > renaming dlls and registry references. I have tested and verified that it= is technically possible. Just renaming the DLL and registry keys is not enough to avoid conflicts with an existing cygwin1.dll. You will also have to modifiy the name of the shared memory region and all other shared objects. =46rom a licensing point of view you can do anything you want as long as you provide the source packages to build the binaries. AFAIK. IANAL.=20 etc. Brian