From owner-freebsd-chat Mon Mar 13 10:26:49 2000 Delivered-To: freebsd-chat@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id DDD9137B5F5 for ; Mon, 13 Mar 2000 10:26:43 -0800 (PST) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id LAA04258; Mon, 13 Mar 2000 11:26:20 -0700 (MST) Message-Id: <4.2.2.20000313111904.041e0c00@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 13 Mar 2000 11:26:15 -0700 To: Brad Knowles , Doug Barton From: Brett Glass Subject: Re: The Merger, and what will its effects be on committers? Cc: Paul Richards , freebsd-chat@FreeBSD.ORG In-Reply-To: References: <4.2.2.20000313103859.0410fe30@localhost> <4.2.2.20000312160425.00b16e80@localhost> <4.2.2.20000312122651.00b1e880@localhost> <4.2.2.20000312144558.04190e80@localhost> <4.2.2.20000312160425.00b16e80@localhost> <4.2.2.20000313103859.0410fe30@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:02 AM 3/13/2000 , Brad Knowles wrote: > But FreeBSD is not just a kernel (like Linux is). It's a kernel plus all the userland stuff and a whole lot more. Therefore, you can't have another "distribution" of FreeBSD, unless it includes all the exact same stuff that FreeBSD does. Non sequitur. Red Hat, and other Linux distributors, do their own builds of the Linux kernel with unique features and drivers. For example, Red Hat ships with Winmodem support while other distributions do not, and their product is still called Linux! There's no reason why this should not be true for FreeBSD. Since FreeBSD includes a "userland," creators of distributions should be able to provide enhancements there too. Anyone who omitted something or broke existing software would, of course, be subjected to the wrath of users, so the market would quickly take care of any omissions. > If you want to take FreeBSD and make your own modifications, you're welcome to do so and call it "WhateverYouWantBSD", but you can't call it FreeBSD In that case, Walnut Creek should not be able to do that either. So, again, the FreeBSD Foundation should require it to change the names of all of its "enhanced" FreeBSD packages. Otherwise, it is not being evenhanded. >-- because the FreeBSD core team and the FreeBSD Foundation would have no control over your product, you can't use their copyrighted name. Do you understand intellectual property law? It's a trademark, not a "copyrighted name." --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message