Date: Wed, 26 Apr 2017 16:34:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218849] Remove rc.conf jail configuration via jail_* variables Message-ID: <bug-218849-8-Mm8PZt15br@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218849-8@https.bugs.freebsd.org/bugzilla/> References: <bug-218849-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218849 Jamie Gritton <jamie@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamie@FreeBSD.org --- Comment #24 from Jamie Gritton <jamie@FreeBSD.org> --- The easiest "fix" is certainly to remove the warning that the old method is going away. I wouldn't quite call it "mistaken", but I'll (almost) agree there's no overriding need to take the bits out of rc.d/jail that translate= the old shell variables. Almost, because there are some confusing multiple paths on the kernel side = that I'd would like to have deprecated, namely the security.jail.xxx_allowed and similar sysctls that used to be the only way to (globally) affect a lot of = jail behavior, and are replaced by per-jail parameters but still live on as defa= ult values. But I can't get rid of those because they're part of the old shell-based setup. I remember some talk in the last year or two about a config file library th= at would allow (among other things) those DOS-like files that shell scripts se= em to like. What's the latest on that? Jail.conf in particular had some stic= king points as I recall. Something like that could be enough for ezjail, though I also wouldn't mind= of ezjail just started using the current jail.conf format. Yes, it's harder f= or a shell script to use generally, but it would be possible to keep track of a shell-machine-readable version with a "hands off" comment at the top of it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218849-8-Mm8PZt15br>