From owner-freebsd-questions@FreeBSD.ORG Thu Nov 22 20:55:31 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99BEF86C; Thu, 22 Nov 2012 20:55:31 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 590598FC17; Thu, 22 Nov 2012 20:55:30 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id qAMKtT2s011178 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 22 Nov 2012 14:55:29 -0600 Received: from [10.0.0.100] (10.14.152.61) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.2.309.2; Thu, 22 Nov 2012 14:55:28 -0600 Subject: Re: Build a Distro using FreeBSD? MIME-Version: 1.0 (Apple Message framework v1283) From: Devin Teske In-Reply-To: <50AE7C1A.4080504@FreeBSD.org> Date: Thu, 22 Nov 2012 12:55:27 -0800 Message-ID: <3B05C51E-80BE-4A02-A8EE-BFF46B517C7F@fisglobal.com> References: <20121122182014.228740@gmx.com> <50AE7C1A.4080504@FreeBSD.org> To: Matthew Seaman X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185, 1.0.431, 0.0.0000 definitions=2012-11-22_07:2012-11-22,2012-11-22,1970-01-01 signatures=0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 20:55:31 -0000 On Nov 22, 2012, at 11:25 AM, Matthew Seaman wrote: > On 22/11/2012 18:20, Ron Blake wrote: >> I wanna make a distro but linux is too buggy for me so i thought >> about FreeBSD how do i go about building my own distro? Also are we >> allowed to make custom distros using FreeBSD please get back to me >> with info on building a custom distro using FreeBSD thanks. >=20 > Sure, you can make your own 'distro' based on FreeBSD if you want, and > distribute it under whatever terms you like. The BSD license is very > liberal in this regard: more so than the GPL even. >=20 > However, a 'distro' is a Linux concept that doesn't really apply very > well to FreeBSD. We have a base system incorporating kernel, system > libraries and all essential applications already: there's no need to > gather all those things together to distribute to end users. >=20 > There are disto-like things in BSD-land: PC-BSD and pfsense are a couple > of interesting examples. These are essentially FreeBSD plus various > additional software packages tuned for specific purposes (desktop usage > in the case of PC-BSD, firewalls for pfsense) and it's this sort of > value-added system built on top of the basic FreeBSD OS that is most > likely to be successful as a distribution. >=20 > If you still want to create your own distro, start by learning how to > make your own customized install media. See the release(7) man page for > starters, but you'll have to put some work in to come up anything > significantly above and beyond the standard base system. It's not > something you can just sling together in an afternoon=85 >=20 Matthew is right on all accounts. Once you feel that you've got a mental grasp of the release(7) process (lin= k below): http://www.freebsd.org/cgi/man.cgi?query=3Drelease&sektion=3D7 If you find the need to make modifications to the source of the base operat= ing system, try and digest my own recipe for creating DruidBSD from FreeBSD: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/free= bsd/patches/README?revision=3D1.2&view=3Dmarkup My recipe relies on the release(7) process and my howto shows how one might= go about maintaining things. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.