From owner-freebsd-jail@FreeBSD.ORG Wed Jan 28 14:06:27 2015 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 285FAB09 for ; Wed, 28 Jan 2015 14:06:27 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E929C883 for ; Wed, 28 Jan 2015 14:06:26 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 97DF6207DA for ; Wed, 28 Jan 2015 09:06:25 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Wed, 28 Jan 2015 09:06:25 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=WONeNPuhmfyOkFE1AZi+ZOZH /DY=; b=E2MdGaM9FbyDJMJ/XbqcZBh3eyohe2f+RM3tGv1yaZDCyIfoZUCRLTHg EES8gFqNy7R2HQMCG9kCCik57yXgVryH/zbdgJcs9gCZHGaPo4O7uO1td3ubWnsa TFoK2+U6poJrqTDwjNfeJdzorzsUBbstyrJZKI47AFvz1BjcZ48= Received: by web3.nyi.internal (Postfix, from userid 99) id 6C0BD110E67; Wed, 28 Jan 2015 09:06:25 -0500 (EST) Message-Id: <1422453985.507433.219992653.382EEAD3@webmail.messagingengine.com> X-Sasl-Enc: wls+WUvn2efLcfqLuDqaZqTqk2+o6RYeUjxF/f+wbWeF 1422453985 From: Mark Felder To: freebsd-jail@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-46f3f2c7 In-Reply-To: <54C80BBB.50806@freebsd.org> References: <20150127012347.GA4940@lonesome.com> <20150127141239.V77290@sola.nimnet.asn.au> <54C7958B.40007@gmail.com> <54C7C828.4070703@erdgeist.org> <1422379391.4042797.219588169.1818EA41@webmail.messagingengine.com> <54C80BBB.50806@freebsd.org> Subject: Re: Future of jail(8) [WAS: preferred jail management tool] Date: Wed, 28 Jan 2015 08:06:25 -0600 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2015 14:06:27 -0000 On Tue, Jan 27, 2015, at 16:05, Allan Jude wrote: > On 2015-01-27 12:23, Mark Felder wrote: > > > > > > On Tue, Jan 27, 2015, at 11:17, Dirk Engling wrote: > >> On 27.01.15 14:41, Ernie Luzar wrote: > >> > >>> I hope the ezjail author takes this thread as incentive to keep his > >>> utility up to date and not let it die due to changing software in Freebsd > >>> base code. All I am doing is pointing out the facts here. > >> > >> I am reading the thread. And I have been following the discussion for a > >> long time. > >> > >> I have been served the jail.conf file format and offered my help > >> improving the jail(8) tool to allow for manipulation of the jail.conf, > >> because ezjail as a shell tool can not parse the format and keeping a > >> shadow config with potentially conflicting information is not a stable > >> way to maintain ones config > >> > >> A short summary is here: > >> > >> https://elektropost.org/ezjail/msg00149.html > >> > >> I also heard rumors that the jail.conf format is an intermediate format > >> only, and/or there's gonna be a library to parse and manipulate all kind > >> of structured config in FreeBSD. > >> > >> So I'd be very interested in keeping up with the base system's > >> development, but regarding jail configs it looks like I'm stuck with the > >> "use your vi to configure your jails" approach for 3 years now. > >> > >> Is there anyone feeling responsible for the jail(8) tool at the moment > >> willing to accept patches and discuss development? > >> > > > > This makes sense to be broken out into its own thread. And I agree -- > > patches to jail(8) or a tool like sysrc(8) for editing jail.conf would > > be a great way to allow third party tools to manage jail.conf cleanly > > and effectively. > > _______________________________________________ > > 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" > > > > I am working on such a tool, and hope to make it available via the ports > tree after a few more tweaks. > > https://github.com/allanjude/uclcmd > > I have presented a little about the UCL config format at MeetBSD: > http://www.slideshare.net/iXsystems/ucl-all-of-the-things-meetbsd-california-2014-lightning-talk > > And I am planning to present about my tool, and the ucl config format in > general, at AsiaBSDCon and probably BSDCan (I submitted 2 topics). > > I have a prototype of newsyslog converted to a UCL based config file as > well. > > The jail.conf file may need a little tweaking (UCL uses the dot > delimiter differently, so the name or structure of some of the variables > may need to change slightly) > > As with my change to newsyslog, the new config format will use a > 'version sentinel' at the top of the file, if that is not present, the > config file will be parsed with the legacy code. > Fantastic. Look forward to seeing your hard work in the tree!