Date: Sat, 28 Apr 2012 16:52:36 -0600 From: Jamie Gritton <jamie@FreeBSD.org> To: Devin Teske <devin.teske@fisglobal.com> Cc: FreeBSD-Jail <freebsd-jail@FreeBSD.org> Subject: Re: New jail(8) committed Message-ID: <4F9C74B4.70308@FreeBSD.org> In-Reply-To: <E57CC666-8847-4348-BAF7-245928DA41F8@fisglobal.com> References: <4F99AB0E.4090805@FreeBSD.org> <4F9B6E8F.8070708@erdgeist.org> <4F9C00E2.3070205@FreeBSD.org> <E57CC666-8847-4348-BAF7-245928DA41F8@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F9C74B4.70308>