From owner-freebsd-ports@FreeBSD.ORG Wed Jan 14 17:31:48 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5C8DD7C for ; Wed, 14 Jan 2015 17:31:48 +0000 (UTC) Received: from udns.ultimatedns.net (ultimatedns.net [209.180.214.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9739CF29 for ; Wed, 14 Jan 2015 17:31:47 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t0EHUYQF070097 for ; Wed, 14 Jan 2015 09:30:34 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <54B660BE.1020404@yahoo.com> References: <54B3C28C.10605@sorbs.net> <20150112130804.GD44537@home.opsec.eu> <9132c8812ccd3906dd487830a912d00c@ultimatedns.net> <9f016d9eec43a047bcfbae526367a2c1@ultimatedns.net> <54B5389D.2020708@astart.com> <54B53DC8.6000701@infracaninophile.co.uk> <20150113155553.GJ44537@home.opsec.eu>, <54B660BE.1020404@yahoo.com> From: "Chris H" Subject: Re: BIND REPLACE_BASE option Date: Wed, 14 Jan 2015 09:30:34 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <34c67e5e59cd70457872c05ced69c776@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 17:31:49 -0000 On Wed, 14 Jan 2015 04:27:42 -0800 Jeffrey Bouquet via freebsd-ports wrote > On 01/13/15 07:55, Kurt Jaeger wrote: > > Hi! > > > >> customizations you need available. If the default options don't cut it > >> for you, in order to use only binary packages that means you need to run > >> your own poudriere setup -- which is well worth it if you're managing > >> several machines / jails etc. > > poudriere allows you to manage several seperate pkg trees with different > > options, so you can: > > > > - build a default tree (and pkg repo), provide it to all generic hosts > > - build a seperate tree (and pkg repo) with modified options, and > > provide it to the special hosts > > > > It helps to keep the poudriere build tree on fast flash/SSD drives 8-} > > > > This all works and is very, very good! Thanks for the work! > > > As I probably won't ever know enough from experience, if one wants a > local lan > build tool is there any flowchart with use cases > > 1... foo foo bar use case >> tinderbox > 2... foo foo bar use case >> build jail > 3... foo foo bar use case >> bhyve > 4... foo foo bar use case >> poudriere > 5... foo foo bar use case >> csbd OR qjail OR ezjail OR man jail OR > bastille script > 6... foo foo bar use case >> server on lan serving packages > > And where they may overlap, which takes the least setup time, which > takes the > least maintenance time, which can be most easily migrated version > > version ... Excellent observation. These look like prime "install candidates". A sort of meta-install, much like a Server, or Desktop install is already. Maybe someone with good install-foo could easily cobble up appropriate scripts to accommodate such a thing. Thanks for bringing it up, Jeffrey! --Chris > > > > Not to mention the wiki, but if that information was "[some term ] use > cases" like > virtualization or multi-machine or... on the freebsd.org page > prominently, it may > result in a larger userbase... more coders onboard. > > Recognizing that a lot of this is emerging technology. Apologies. I've > a slight > interest in reading any such document, having read an hour or so > yesterday not > a few htm explaining jails, (10 pages of threads linked from > a search 'ezjail' in the forums, for example) to know that acquiring the > expertise of > a quickstart group of terms to focus on in any particular scenario is > something I don't > easily expect to acquire. > > On the other hand, to include the wiki... vs links from it. > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"