From owner-freebsd-current@freebsd.org Tue Apr 25 23:23:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B2C9D50E64 for ; Tue, 25 Apr 2017 23:23:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 54AB4C68 for ; Tue, 25 Apr 2017 23:23:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 54136D50E63; Tue, 25 Apr 2017 23:23:16 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53C1AD50E62 for ; Tue, 25 Apr 2017 23:23:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 29E21C66 for ; Tue, 25 Apr 2017 23:23:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3PNNEtC030867 for ; Tue, 25 Apr 2017 23:23:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 218849] Remove rc.conf jail configuration via jail_* variables Date: Tue, 25 Apr 2017 23:23:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: qjail1@a1poweruser.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 26 Apr 2017 00:22:33 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2017 23:23:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218849 --- Comment #16 from Joe Barbish --- This is my objection to waiting for 12.0 before doing this. When 10.0 came = out the removal of the rc.conf method was scheduled to happen at 11.0. Now 3+ y= ears later 11.0 is out and the rc.conf method is still supported. Now your talki= ng about waiting for 12.0 to remove the the rc.conf method. In 3-4 years this = same problem will still not be fixed and again we will be talking about waiting = for 13.0 to do it. What you really talking about is holding up os deployment based on a 3rd-pa= rty tool. That's just plain crazy. I purpose this solution.=20 I believe that the /etc/rc.d/jail script is the single place where the curr= ent 11.0 system issues that warning message and processes the rc.conf method fr= om. The removing of the rc.conf method will mean changing only that script. Som= eone else should verify this. Inspecting the current version of the ezjail-admin script shows the start/s= top commands launches a custom script /usr/local/etc/ezjail. After a bunch of grinding it finally launches /etc/rc.d/jail which does the actual start/stop work. This /etc/rc.d/jail script is part of the base os release. Change the custom /usr/local/etc/ezjail script to launch /usr/local/etc/ezjail-jail instead of /etc/rc.d/jail. This is a one line change. Then populate the ezjail-jail script with the contents of the 11.0 /etc/rc.d/jail script. Make these changes to the port source and the corresponding changes to the port makefiles and bingo you have given ezjail= the ability to internally use the rc.conf method for ever forward. Now with this single show stopper fixed the removal of the rc.conf method c= an proceed to be scheduled for 11.1. --=20 You are receiving this mail because: You are on the CC list for the bug.=