From owner-freebsd-hackers Tue Mar 14 15:43:06 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA01062 for hackers-outgoing; Tue, 14 Mar 1995 15:43:06 -0800 Received: from kithrup.com (kithrup.com [140.174.23.40]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA01055 for ; Tue, 14 Mar 1995 15:43:05 -0800 Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id PAA29332; Tue, 14 Mar 1995 15:40:28 -0800 Date: Tue, 14 Mar 1995 15:40:28 -0800 From: Sean Eric Fagan Message-Id: <199503142340.PAA29332@kithrup.com> To: faulkner@mpd.tandem.com, terry@cs.weber.edu Subject: Re: BSD Consortium Cc: faulkner@devnull.mpd.tandem.com, hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >what goals would you personally put forth? Such a consortium should be willing and able to promote BSD. It should be willing to sponsor distributions, scholarships, grants, whatever. More realistically, if such a consortium is seriously being considered, someone (Jordan?) should talk with Kirk McKusick. Things that would be really good for the Consortium to offer would be CD-ROMs of the next 4.4-lite distribution, as well as printed manuals. More hopefully, it would be good if such a consortium were able to take over half of CSRG's job -- that of being "clearing house" for the code. I doubt "the BSD Consortium" could afford to hire on one, let alone all, of the CSRG members, but it might not be too difficult to have releases made through it. The real problem is that there are only three camps, really, that would benefit from such a beast: NetBSD, FreeBSD, and BSDi. Two of those can't really talk to each other, and the third has an interest in making as much of their code as possible proprietary. This is different from the X Consortium, which has several Big Name members. Frankly, I don't think it would ever happen. But it would be nice, I suppose. Sean.