From owner-freebsd-questions Wed Feb 7 12:41:08 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA25457 for questions-outgoing; Wed, 7 Feb 1996 12:41:08 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA25452 for ; Wed, 7 Feb 1996 12:41:06 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA06282; Wed, 7 Feb 1996 13:38:07 -0700 From: Terry Lambert Message-Id: <199602072038.NAA06282@phaeton.artisoft.com> Subject: Re: Can FreeBSD be used in a commercial way? To: marino.ladavac@aut.alcatel.at Date: Wed, 7 Feb 1996 13:38:06 -0700 (MST) Cc: terry@lambert.org, questions@freebsd.org In-Reply-To: <9602071337.AA06093@atuhc16.atusks01.aut.alcatel.at> from "marino.ladavac@aut.alcatel.at" at Feb 7, 96 02:37:43 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk > > 3) You have to include the credit clauses for everyone in the > > sources for the components you use. This should take one > > or two pages of fine print (like the trademark acknowledgement > > page) in your distributed docuemntation. > > Shouldn't a file listing copyright lines be enough? I.e, he doesn't > really have to print it? Yes. I felt that if he were doing manuals, printing it would be easiest. Easier than a "README" in "/". He could take the existing distribution tree, dike out the GPL parts, replace tar, build his own distribution, and not have to deal with any changes to the OS itself, only his printed docs. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.