Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <384575FA.2CF87814@us.oracle.com> Date: Wed, 01 Dec 1999 11:24:43 -0800 From: "David M. J. Saslav" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com CC: David Subject: Re: Question on Cygwin User Tool licensing References: <3AC9A1611DF4D211AA8E00105AA56D8A04946F AT iis000 DOT microdata DOT fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Thanks to all for the rapid responses. The question #2 I am trying to get an answer for does not involve DISTRIBUTING THE CYGWIN CD TO ANYONE -- rather providing them with the use of the tool long enough to emulate the product's Unix shell script tools in a classroom environment -- say, a one to three day experience -- after which all traces of the Cygwin user tools would be deleted from the NT boxes the students had been using. They walk away with nothing but knowledge/awareness of Cygwin tools! Am I allowed to download the I'd like to specify my question further: the product's command line tools only use "sh" to work properly. Does the GPL allow me to download once to the classroom (on a per-class-experience-basis), install locally to the student NT machines, run the course, then delete everything as soon as the course is done? -- Regards, ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| David Saslav, Bldg 400, Room 580 dsaslav AT us DOT oracle DOT com Senior Product Manager Tel: (650) 506-6969 Oracle Internet Directory Fax: (650) 506-7221 http://oid.us.oracle.com/ Directory Infrastructure Group http://www.oracle.com/database/oid/ Server Technologies Division ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Bernard Dautrevaux wrote: > > -----Original Message----- > > From: Chris Faylor [mailto:cgf AT cygnus DOT com] > > Sent: Wednesday, December 01, 1999 6:43 PM > > To: David M. J. Saslav; cygwin AT sourceware DOT cygnus DOT com > > Subject: Re: Question on Cygwin User Tool licensing > > > > > > On Wed, Dec 01, 1999 at 08:25:12AM -0800, Earnie Boyd wrote: > > >--- "David M. J. Saslav" wrote: > > >> I have two questions: > > >> > > >> Scenario: > > >> > > >> Company builds and ships a set of Unix command line tools > > as Unix shell > > >> scripts alongside a proprietary server product. > > > > > >No problem. > > > > > >> Company ports server product to Windows NT and ships that too, but > > >> chooses not to convert the Unix shell scripts into .BAT file > > >> equivalents. > > > > > >No problem. > > > > > >> Customers with Win32 shell emulation environments (MKS > > toolkit or Cygwin > > >> user tools) have no problem invoking and using the Unix > > shell scripts > > >> "as is" from NT workstations. > > >> > > > > > >Good! ;) > > > > Most of the tools like 'ls', 'awk', 'sed', etc. are > > distributed under the > > terms of the GPL. That means that you must be able to supply > > your users > > with the exact sources that were used to create these tools. > > You can't > > just post a cygnus URL and say "go there for the sources". > > > > Some of the utilities, like sh, are distributed under the BSD license > > which probably won't present an obstacle. > > > > >> Questions: > > >> > > >> 1) In the case of Cygwin User tools, does this sort of use require > > >> purchase or licensing of the Cygwin User tools on the part of the > > >> Customers? > > > > > >Free net downloads. Or a purchase of the Version 1 CD > > allows for multiple > > >installs to as many machines as you wish. > > > > NO! You do *not* have the right to distribute copies of the Cygwin CD > > to your customers! > > > > The answer is that if you adhere to the GPL you won't have to worry > > about anything. There is no alternative to this. You have to comply > > with the GPL. > > > > Since you apparently aren't using the cygwin DLL in your proprietary > > server, the only thing that you need to worry about is the > > GPL. If you > > are using the Cygwin DLL in your server, then, your server becomes > > DLL'ed too. > > > > If this is unclear, send email to cygwin-info AT cygnus DOT com. > > > > >CAVEAT EMPTOR: I'm not a lawyer and this is not legal advice. > > > > cgf > > > > -- > > Want to unsubscribe from this list? > > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > > > > So, if I understand correctly, if I put on a CD togetehre with my software > (which is proprietary, do not use cygwin.dll, but needs sh, ls, etc.) both > user.exe for cygwin-B20.1 and the corresponding user.src.tar.gz (or whatever > the tarball is exactly named) I have no problem, Isn't it? > > Regards, > > Bernard > > -------------------------------------------- > Bernard Dautrevaux > Microprocess Inginiirie > 97 bis, rue de Colombes > 92400 COURBEVOIE > FRANCE > Tel: +33 (0) 1 47 68 80 80 > Fax: +33 (0) 1 47 88 97 85 > e-mail: dautrevaux AT microprocess DOT com > b DOT dautrevaux AT usa DOT net > -------------------------------------------- -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com