From owner-freebsd-hackers Tue Mar 14 16:43:51 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA02753 for hackers-outgoing; Tue, 14 Mar 1995 16:43:51 -0800 Received: from vector.enet (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA02441 for ; Tue, 14 Mar 1995 16:35:16 -0800 Received: (from jhs@localhost) by vector.enet (8.6.10/8.6.9) id BAA05948; Fri, 10 Mar 1995 01:30:36 +0100 Date: Fri, 10 Mar 1995 01:30:36 +0100 From: Julian Howard Stacey Message-Id: <199503100030.BAA05948@vector.enet> To: branson@dvals1.larc.nasa.gov, dufault@hda.com Subject: Re: BSD Consortium? Cc: freebsd-hackers@freefall.cdrom.com, hsu@cs.hut.fi, terry@cs.weber.edu, witr@rwwa.com Sender: hackers-owner@FreeBSD.org Precedence: bulk > Having a consortium may also give potential comercial software > creators more reason to write/port software to the os's. And may also give other software vendors (OS vendors) reason to go for round two with us :-( Don't forget the business adage: If you'r a big company, & your market place is being threatened by a small company, Sue them, doesnt matter what for, just Sue them, it wastes the directors time, they slip schedules, & may even give up .... Well FreeBSD doesnt have directors, but it does have activists who would'nt want to see more lawyers letters. I can see some benefirt from a consortium, but I can see some danger too, I also forsee a request to create a seperate mailing list to dump such discusions into, to keep 'em out of hackers@f.. Julian S