Thoughts about kenv emulating sysctl

[Garrett Cooper]

Hi Hackers,
    I've been asked to write up a script to analyze tunables via kenv for archival purposes an to establish a baseline set of static variables.
    In order to make life easier (and be able to do all the grunt work in a shell one-liner instead of introducing a bug prone tunable parser) I have written up a patch which would make kenv function a bit more like sysctl, wrt the fact that sysctl -n suppresses suffixing a value with the variable name when executed like so:

# kenv LINES
LINES="24"
# kenv -n LINES
24

    I've also considered keeping the functional defaults and instead do the following...

# kenv -v LINES
LINES="24"
# kenv LINES
24

    Pro of the first form is that it matches sysctl, pro of the second form is that it doesn't break backwards 'compatibility'.
    I know kenv isn't a widely used utility (albeit, I have seen it used in a few spots outside of FreeBSD proper), but I was wondering if anyone could see any potential pitfalls or would have a large degree of heartburn over changing the default to match sysctl.
Thanks!
-Garrett