From owner-freebsd-bugs@freebsd.org Wed Apr 26 14:58:23 2017 Return-Path: Delivered-To: freebsd-bugs@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 541DDD507A0 for ; Wed, 26 Apr 2017 14:58:23 +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 2B40515C1 for ; Wed, 26 Apr 2017 14:58:23 +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 v3QEwKF9090809 for ; Wed, 26 Apr 2017 14:58:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218849] Remove rc.conf jail configuration via jail_* variables Date: Wed, 26 Apr 2017 14:58:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: 000.fbsd@quip.cz X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10- mfc-stable11- 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-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 14:58:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218849 --- Comment #23 from Miroslav Lachman <000.fbsd@quip.cz> --- (In reply to Warner Losh from comment #22) I think it turns in to bikeshed now. Are we talking about rc.conf variables= to configure jails or about this as dependency for ezjail? No matter if you have 1 or 5 or 20 jails. The configuration in jail.conf is= as simple as in rc.conf, maybe even easier and more flexible. ## rc.conf style jail_enable=3D"YES" jail_list=3D"alpha" jail_exec_start=3D"/bin/sh /etc/rc" jail_exec_stop=3D"/bin/sh /etc/rc.shutdown" jail_devfs_enable=3D"YES" jail_devfs_ruleset=3D"devfsrules_jail" jail_flags=3D"-l -U root" jail_alpha_rootdir=3D"/vol0/jail/alpha" jail_alpha_hostname=3D"alpha.example.com" jail_alpha_ip=3D"10.11.12.13" ## jail.conf style exec.start =3D "/bin/sh /etc/rc"; exec.stop =3D "/bin/sh /etc/rc.shutdown"; exec.clean; mount.devfs; devfs_ruleset =3D 4; exec.jail_user =3D "root"; path =3D "/vol0/jail/$name"; exec.consolelog =3D "/var/log/jail/$name.console"; mount.fstab =3D "/etc/fstab.$name"; # A typical jail. alpha { host.hostname =3D "alpha.example.com"; ip4.addr =3D 10.11.12.13; } But if we are talking about jails management utility, then we have none in = base but a lot in ports / packages that does not depend on rc.conf style. We migrated all our jails on all machines from rc.conf to jail.conf the fir= st time I have seen the warning after machine upgrade. It was really easy.=20 I agree removing some feature on dot release can be a problem but I really don't understand why we should maintain two different styles for configuring jails in base. --=20 You are receiving this mail because: You are the assignee for the bug.=