From owner-freebsd-hackers Mon Aug 7 14:44:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA02821 for hackers-outgoing; Mon, 7 Aug 1995 14:44:34 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id OAA02813 for ; Mon, 7 Aug 1995 14:44:32 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id OAA18977; Mon, 7 Aug 1995 14:44:07 -0700 From: Julian Elischer Message-Id: <199508072144.OAA18977@ref.tfs.com> Subject: Re: software rights To: john@starfire.mn.org Date: Mon, 7 Aug 1995 14:44:06 -0700 (PDT) Cc: hackers@FreeBSD.org In-Reply-To: <199508072017.PAA12295@starfire.mn.org> from "john@starfire.mn.org" at Aug 7, 95 03:17:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 644 Sender: hackers-owner@FreeBSD.org Precedence: bulk If it's in the FreeBSD distribution then It's permissable to use it in any way you like as long as you follow the instruction in each file.. > > Where do I go to begin the quest for the One True Answer to what is owned > by whom, what use is permitted, and whose permission you need to use > TCP/IP and NFS implementations such as those in FreeBSD in a commercial > bundled, turnkey product? p.s. what are you doing with the TCP and not the rest of the kernel? it suggests you're doing a lot of low lever hacking :) > > John Lind, Starfire Consulting Services > E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417 >