[Bug 218849] Remove rc.conf jail configuration via jail_* variables

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 26 Apr 2017 16:34:05 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849

Jamie Gritton <jamie_at_FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jamie_at_FreeBSD.org

--- Comment #24 from Jamie Gritton <jamie_at_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 default
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 that
would allow (among other things) those DOS-like files that shell scripts seem
to like.  What's the latest on that?  Jail.conf in particular had some sticking
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 for 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wed Apr 26 2017 - 14:34:07 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:11 UTC