Date: Mon, 11 Nov 2013 17:38:29 +0000 From: Kamil Choudhury <Kamil.Choudhury@anserinae.net> To: Atte Peltomaki <atte.peltomaki@iki.fi>, "hackers@freebsd.org" <hackers@freebsd.org> Subject: RE: pkgng for configuration management? Message-ID: <F9A7386EC2A26E4293AF13FABCCB32B30126C1BCAA@janus.anserinae.net> In-Reply-To: <20131111142348.GB2584@ass.pp.htv.fi> References: <F9A7386EC2A26E4293AF13FABCCB32B3011DC398B5@janus.anserinae.net> <20131106164807.GW11443@kiwi.coupleofllamas.com>, <20131111142348.GB2584@ass.pp.htv.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F9A7386EC2A26E4293AF13FABCCB32B30126C1BCAA>