From owner-freebsd-jail@FreeBSD.ORG Tue Jan 27 17:23:13 2015 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 278F8695 for ; Tue, 27 Jan 2015 17:23:13 +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 E9EA8A1C for ; Tue, 27 Jan 2015 17:23:12 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id E674E213DD for ; Tue, 27 Jan 2015 12:23:11 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Tue, 27 Jan 2015 12:23:11 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to:cc :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=jNenpreKhy52Yb9azFumyGqY JIQ=; b=edRUHvVPKuULEt7nicRsP4ib9vmEwmvqUkF9VF78inUKAdbfPlkNvXdJ 2YMdgcwbEDX8tQmOCc1uMbYlB3JsMwOxKInn19Ygx9hbAMd4LeL/kvPRpg+HyUpf sGkkTS3FjCASqXiKmnfKcGKinJ06byW/j89cUwdkYrDt7E19NEo= Received: by web3.nyi.internal (Postfix, from userid 99) id AF4E510C715; Tue, 27 Jan 2015 12:23:11 -0500 (EST) Message-Id: <1422379391.4042797.219588169.1818EA41@webmail.messagingengine.com> X-Sasl-Enc: lF4J/Joytv5alb3g7Memp96+d0IhOFrpYZd4j70xhUvW 1422379391 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: <54C7C828.4070703@erdgeist.org> References: <20150127012347.GA4940@lonesome.com> <20150127141239.V77290@sola.nimnet.asn.au> <54C7958B.40007@gmail.com> <54C7C828.4070703@erdgeist.org> Subject: Future of jail(8) [WAS: preferred jail management tool] Date: Tue, 27 Jan 2015 11:23:11 -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: Tue, 27 Jan 2015 17:23:13 -0000 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.