From owner-freebsd-jail@FreeBSD.ORG Sat Apr 28 22:52:43 2012 Return-Path: Delivered-To: freebsd-jail@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7980106566B for ; Sat, 28 Apr 2012 22:52:43 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [199.192.164.235]) by mx1.freebsd.org (Postfix) with ESMTP id A03268FC17 for ; Sat, 28 Apr 2012 22:52:43 +0000 (UTC) Received: from glorfindel.gritton.org (c-174-52-130-208.hsd1.ut.comcast.net [174.52.130.208]) (authenticated bits=0) by m2.gritton.org (8.14.4/8.14.4) with ESMTP id q3SMqcXn007234; Sat, 28 Apr 2012 16:52:39 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <4F9C74B4.70308@FreeBSD.org> Date: Sat, 28 Apr 2012 16:52:36 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.24) Gecko/20120129 Thunderbird/3.1.16 MIME-Version: 1.0 To: Devin Teske References: <4F99AB0E.4090805@FreeBSD.org> <4F9B6E8F.8070708@erdgeist.org> <4F9C00E2.3070205@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Jail Subject: Re: New jail(8) committed X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2012 22:52:43 -0000 I don't know about wrapping a utility around it, but it would be nice to have in a library. If it could be made to work for not only jail, but apmd and devd as well, then we could make some existing code cleaner. - Jamie On 04/28/12 10:52, Devin Teske wrote: > On Apr 28, 2012, at 7:38 AM, Jamie Gritton wrote: > >> The main reason I didn't consider a jail.d approach is just that I >> haven't - such things are a little off the radar for me. It seemed very >> natural to use a configuration file format that other programs already >> use (e.g. named, apmd, devd). I suppose it's true that the "foo.d" >> approach is also in use by other programs, though I mostly seem to see >> those on Linux. And if I did opt for a directory approach, the files >> within the directory would still need a format - you can't get away from >> the fact that a config file needs a format. >> >> It would be nice to have a general parser for C-style config files, and >> I looked for such a library when I started on this. But such a library >> doesn't seem to exist.Perhaps it's time to make one. >> > > The config file format that you've chosen is remarkably identical to config files for which I've already written parsers. > > So, I guess I'm saying that I'm willing to help out in this area. > > My parser is written in C, it's very small and light-weight, and it's called figpar (con[fig par]ser). > > I can dust if off, slap a BSD license on it, wrap a utility around it and we could have something like sysrc (which operates on the collection of rc.conf(5) files). > > Alternatively, I could rewrite it in something like sh(1) if C is not desired.