Date: Sat, 28 Apr 2012 09:52:56 -0700 From: Devin Teske <devin.teske@fisglobal.com> To: Jamie Gritton <jamie@FreeBSD.org> Cc: FreeBSD-Jail <freebsd-jail@FreeBSD.org> Subject: Re: New jail(8) committed Message-ID: <E57CC666-8847-4348-BAF7-245928DA41F8@fisglobal.com> In-Reply-To: <4F9C00E2.3070205@FreeBSD.org> References: <4F99AB0E.4090805@FreeBSD.org> <4F9B6E8F.8070708@erdgeist.org> <4F9C00E2.3070205@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 > 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. >=20 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 calle= d figpar (con[fig par]ser). I can dust if off, slap a BSD license on it, wrap a utility around it and w= e could have something like sysrc (which operates on the collection of rc.c= onf(5) files). Alternatively, I could rewrite it in something like sh(1) if C is not desir= ed. --=20 Devin > On 04/27/12 22:14, Dirk Engling wrote: >> On 26.04.12 22:07, Jamie Gritton wrote: >>=20 >>> I've finally put my jail(8) changes into HEAD. This new version of jail >>> can create jails from a configuration file - see jail.conf(5) for the >>> format, as well as some additions to jail(8). This doesn't mean you >>> *have* to use jail.conf, but it's a better way to manage jails than the >>> existing rc.conf method. >>=20 >> Out of curiosity, why did you settle for a /etc/jail.conf instead of a >> /etc/jail.d/? Your config file format introduces the dependency into an >> expensive parser while adding little value. Even worse, the user now has >> to struggle with just another format describing the system. >>=20 >> I can foresee that my automated jail management tool ezjail will not be >> able to support the jail.conf format due to the lack of a parser. A look >> into ezjails config directory structure can give you a hint of how to >> achieve some similar clean up with built in tools. >>=20 >> I am not saying, the config directory format is perfect, the current >> redundancy in jail_JAILNAME variables is a mess, but inventing a >> container format where files would do just fine in my opinion is overkil= l. >>=20 >> Regards, >>=20 >> erdgeist > _______________________________________________ > freebsd-jail@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-jail > To unsubscribe, send any mail to "freebsd-jail-unsubscribe@freebsd.org" _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E57CC666-8847-4348-BAF7-245928DA41F8>