Date: Wed, 06 Oct 2010 20:11:43 -0700 From: merlyn@stonehenge.com (Randal L. Schwartz) To: Michael Powell <nightrecon@hotmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core Message-ID: <864ocywvbk.fsf@red.stonehenge.com> In-Reply-To: <i8jd3u$9v1$1@dough.gmane.org> (Michael Powell's message of "Wed, 06 Oct 2010 23:04:48 -0400") References: <86fwwjyurd.fsf@red.stonehenge.com> <20101006215345.1a57c45c@gumby.homeunix.com> <86pqvnxbre.fsf@red.stonehenge.com> <20101006174309.407e4216@scorpio> <86d3rnxadh.fsf@red.stonehenge.com> <AANLkTikMoCn_JY9u%2B2QTFqcWY9N1s4zNwPw_owtEV%2BSD@mail.gmail.com> <i8jd3u$9v1$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Michael" == Michael Powell <nightrecon@hotmail.com> writes: Michael> I was under the impression that the most onerous of these Michael> export rules and restrictions applied to crypto technology. If Michael> this is so, what I don't quite grasp is what do crypto export Michael> restrictions have to do with acpi? Is acpi a copyrighted, Michael> patented, or trademark otherwise owned by some entity? Quite Michael> possibly so as it is in contrib. I just have no idea who might Michael> "own" it. Or how it would fall afoul of crypto export Michael> restrictions. Exactly my point. Either it's crypto, and the whole distro is tainted and should be marked as such UP FRONT, or it's not, and the paragraph should be removed, if possible. Or a third alternative... use the ACPI implementation from OpenBSD, which doesn't have such a restriction. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>; Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?864ocywvbk.fsf>