From owner-freebsd-stable Tue Dec 14 4:20:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 57B8D14F77 for ; Tue, 14 Dec 1999 04:20:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xqgA-000Ak2-00; Tue, 14 Dec 1999 14:03:42 +0200 From: Sheldon Hearn To: Pekka Savola Cc: Spidey , freebsd-stable@FreeBSD.ORG Subject: Re: Selecting which programs to have in the base system In-reply-to: Your message of "Mon, 13 Dec 1999 14:41:27 EST." <14421.19431.833872.458577@anarcat.dyndns.org> Date: Tue, 14 Dec 1999 14:03:42 +0200 Message-ID: <41293.945173022@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Dec 1999 14:41:27 EST, Spidey wrote: > > How can I manipulate -easily- which base system files (in e.g. /bin, > > /sbin, /usr/bin, /usr/sbin) will be installed/compiled when I cvsup the > > sources and make world ? > > I don't think that's a really good idea. It's not really 'made' that > way. Hi Pekka, "Spidey" is right. FreeBSD is an integral operating system, not a collection of bits and pieces. The advantage of having a single, known base system is that support is simplified and migrating administrators find it fairly easy to merge solutions across from one FreeBSD host to the next. There are two cases where it's understandable that you'd want to remove certain components from the base system: * For embedded systems, where space is a serious issue. * For secure/specialty systems where only that which is needed for a specific taks should be made available to users. FreeBSD caters for these two scenarios by providing a mechanism through which you can engineer your own release with the ``release'' target. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message