From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 11 17:38:31 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 28012361 for ; Mon, 11 Nov 2013 17:38:31 +0000 (UTC) (envelope-from Kamil.Choudhury@anserinae.net) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id DE147295E for ; Mon, 11 Nov 2013 17:38:30 +0000 (UTC) Received: from [74.73.121.187] ([74.73.121.187:64520] helo=janus.anserinae.net) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 6E/B5-19454-51611825; Mon, 11 Nov 2013 17:38:30 +0000 Received: from JANUS.anserinae.net ([fe80::192c:4b89:9fe9:dc6d]) by janus.anserinae.net ([fe80::192c:4b89:9fe9:dc6d%11]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 12:38:29 -0500 From: Kamil Choudhury To: Atte Peltomaki , "hackers@freebsd.org" Subject: RE: pkgng for configuration management? Thread-Topic: pkgng for configuration management? Thread-Index: AQHO2yOq/7mvNW7G5EudJegpEdwvh5ogcM8A//+s2KU= Date: Mon, 11 Nov 2013 17:38:29 +0000 Message-ID: References: <20131106164807.GW11443@kiwi.coupleofllamas.com>, <20131111142348.GB2584@ass.pp.htv.fi> In-Reply-To: <20131111142348.GB2584@ass.pp.htv.fi> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [204.4.182.16] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 17:38:31 -0000 > I've done this on Linux in the past. It's a handy trick to distribute=0A= > small configuration pieces for clients which are not under same=0A= > administration (eg. users workstations). I used it to create meta-=0A= > packages like 'company-dev-environment' which includes all basic=0A= > packages for dev workstation, and packages like 'company-krb5-conf'=0A= > which installs and configures a proper /etc/krb5.conf for accessing=0A= > intranet services.=0A= =0A= This pretty much sums up my experience. =0A= =0A= The initial distribution of configurations goes well, generally speaking, a= nd is=0A= okay for getting hosts up and running upon creation -- but woe betide you = =0A= if two packages alter the same file (necessary for things like rc.conf...).= =0A= =0A= I'm using cfengine instead -- much less finicky. =