From owner-freebsd-hackers Fri Feb 13 05:49:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26889 for freebsd-hackers-outgoing; Fri, 13 Feb 1998 05:49:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26872; Fri, 13 Feb 1998 05:48:50 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id FAA06846; Fri, 13 Feb 1998 05:48:50 -0800 (PST) To: sos@FreeBSD.ORG cc: mike@smith.net.au (Mike Smith), koshy@india.hp.com, freebsd-hackers@FreeBSD.ORG Subject: Re: General policy on trademark violations In-reply-to: Your message of "Fri, 13 Feb 1998 08:37:53 +0100." <199802130737.IAA01675@sos.freebsd.dk> Date: Fri, 13 Feb 1998 05:48:50 -0800 Message-ID: <6842.887377730@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that one of our biggest problems here is the "affiliation" > with Walnut Creek, the legalese people see a company that they can > sue for real money. Remember the requests to remove parts of our Actually, we've never even come close to being sued for money (or even threatened with such) during any of these instances. In each and every case, it's been some bored, by-the-book lawyer saying he's representing client blah-blah's trademark interests and would we please cease and desist from saying blah-diddy-blah on our FTP site. They don't want money, they're just playing whack-a-mole here with "trademark violations" and ftp.cdrom.com is a rather large and obvious mole to go after on the net, it doesn't exactly take an Einstein to find us! Our biggest problem... Heh.. You want to know our "biggest problem?" It's the "affiliation" with ftp.cdrom.com and the bazillion search engines out there empowering lawyers like Hasbro's daily in finding "boggle violations" with a few trivial keystrokes. So now what? Would you then propose that we vacate our own flagship machine in order to prevent such problems in the future? Sure, why not, I'll bet the Linux folks would be more than happy to occupy the space we currently take up - heck, that'd free an entire 8GB archive slice for all kinds of new kernels and things! :-) :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message