Mail Archives: cygwin/2004/04/15/09:17:29
> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Dave Korn
> Sent: 15 April 2004 14:03
> To: cygwin AT cygwin DOT com
> Subject: RE: Quick hack to implement gethostbyname_r() through
> gethostbyname()+mutex lock
>
>
> > -----Original Message-----
> > From: cygwin-owner On Behalf Of Enzo Michelangeli
> > Sent: 15 April 2004 13:49
>
> > Another self-followup :-)
> >
> > ----- Original Message -----
> > From: "Enzo Michelangeli" <em AT em DOT no-ip DOT com>
> > To: <cygwin AT cygwin DOT com>
> > Cc: ""Brian Ford"" <ford AT vss DOT fsi DOT com>
> > Sent: Thursday, April 15, 2004 12:03 PM
> > Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe
> >
> > > P.S. By the way, Corinna: couldn't I just put my
> > gethostbyname_r() in
> > > the public domain, rather than going through the
> > bureaucratic chore of
> > > the copyright assignment? Also because I feel that implementing it
> > > through mutex-protection of gethostbyname(), as I did, is
> > just a quick
> > > hack, as it unnecessarily blocks other threads that could access the
> > > name server in parallel (with separate network I/O and properly
> > > re-entrant code). It may help other implementors to solve an urgent
> > > problem, but I don't think it should be released as part of
> > the Cygwin
> > > code.
> >
> > Well, OK, here is the code, hereby placed in the public
> > domain. Everybody
> > can do with it whatever s/he likes; attribution will be
> > appreciated. Of
> > course, no guarantees etc.
>
>
> Ah, but it's not a matter of it having no copyright, but of the copyright
> existing and belonging to the FSF so that the GPL can be enforced on the
> file. If you submit a completely PD bit of source to a GPL project, other
> people can take that code, modify it and release it as binaries without
> being obliged by the GPL to provide sources, because they can
> claim they're
> working on your PD version rather than any version distributed under GPL.
> IOW, making code PD makes it impossible to apply and enforce the
> GPL to it.
> IIUIC.
The inclusion of PD code in a GPL project makes a derivative work that is
also licensed under the GPL. Someone can independently take the PD code and
do whatever they want with it, but they must abide by the terms of the GPL
if they wish to modify the derivative work.
Chris
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -