On Fri, Feb 21, 2020 at 2:21 AM qi.fuli(a)fujitsu.com <qi.fuli(a)fujitsu.com> wrote:
On 2/20/20 5:28 AM, Verma, Vishal L wrote:
> On Wed, 2020-02-19 at 12:09 -0800, Dan Williams wrote:
>>>> Let's do a compromise, because users also hate nonsensical legacy
>>>> they can't avoid. How about an environment variable,
>>>> "NDCTL_LIST_LINT", that users can set to opt into the latest
>>>> cleanest output format with the understanding that the clean up may
>>>> regress scripts that were dependent on the old bugs.
>>> Hm, this sounds good in concept, but how about waiting for this cleanup
>>> to go in after the (yes, long pending) config rework. Then this can just
>>> be a global config setting, and we won't have config things coming from
>>> the environment as well (which this would be a first of).
>> That does make some sense, but I notice that git deals with
>> environment variables (GIT_EDITOR, GIT_PAGER, etc) in addition to its
>> config file. So if we're borrowing from git, I'd also borrow that
>> config vs environment logic.
> True, that's reasonable. I guess I was hoping to avoid, if we can,
> suddenly having a multitude of config sources, but env variables are
> pretty standard and it should be fine to add them.
I am sorry for suspending the ndctl global config patch for such a long
time. If it is not urgent, I would like to implement it.
It's getting more and more urgent, especially as more people are
trying to use the DIMM security features and finding it difficult to
contend with the command-line interface.
The goal is to import the git config system. Specifically one of the
features of the git config syntax that are useful for DIMM security
(and in the future Namespace security) is the ability to have named
sub-sections. From the git config man page:
Sections can be further divided into subsections. To begin a
subsection put its name in double
quotes, separated by space from the section name, in the
section header, like in the example
With that capability policy can be established by a named object
instance. dimm.<dimm_id>.<attribute>, or