Date: Fri, 8 Oct 2010 20:33:24 -0700 From: Rob Farmer <rfarmer@predatorlabs.net> To: Ian Smith <smithi@nimnet.asn.au> Cc: freebsd-questions@freebsd.org Subject: Re: Like it or not, Theo is having a good laugh .. Message-ID: <AANLkTi=n5NUaG4EF%2BFAj4eZPqf=FzcyEsxZNuOk8o8GZ@mail.gmail.com> In-Reply-To: <20101009014310.O2036@sola.nimnet.asn.au> References: <20101009014310.O2036@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 8, 2010 at 10:31, Ian Smith <smithi@nimnet.asn.au> wrote: > We've had a clear explanation of why it's still there - an historical > oversight at worst, pre present levels of paranoia and litigiousness - > by Jung-uk Kim, who's been importing Intel ACPICA code into FreeBSD for > five or so years, among large works on other core aspects of FreeBSD. > > He stated that it will be dealt with in the next import of the code. > End of story? =A0Let facts get in the way of such a splendid beat-up?] What do you mean by "dealt with"? Just drop clauses from the license? Has someone who legally represents the copyright holder approved that in writing? > If anyone finds any State Secrets or vaguely crypto code in Intel's free > (in both senses) ACPICA code implementation of open ACPI specifications, > I'm sure we'll get to hear about it. =A0Meanwhile, please shut the FUD up= . Export restrictions apply to more than crypto, and removing the license terms saying this doesn't actually remove the restrictions - they are a law. The only people spreading FUD here are those who are have an anti-American attitude and are unwilling to accept that since key parts of FreeBSD are contributions by people in the US and are then exported, it just might actually be affected by what US lawmakers say about exports. --=20 Rob Farmer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=n5NUaG4EF%2BFAj4eZPqf=FzcyEsxZNuOk8o8GZ>