Because:

1. This section defines the configuration format, and doesn't need to
   be tied to a particular filename.
2. The bundle spec (in bundle.md) already has:

     This REQUIRED file MUST reside in the root of the bundle
     directory and MUST be named `config.json`.

The config.md line may have been useful when it was added (77d44b1,
Update runtime.md, 2015-07-16).  But since the bundle.md line landed
in 106ec2d (Cleanup bundle.md, 2015-10-02, #210), I think it's been
redundant.

Signed-off-by: W. Trevor King <wking@tremily.us>

If the timeout value was zero, the hook would always error, and there
doesn't seem to be much point to that.  And I'm not sure what negative
timeouts would mean.  By adding this restriction, we do not limit
useful hook entries, and we give the validation code grounds to warn
users attempting to validate configs which are poorly defined or have
useless hook entries.

I'd like to remove the pointer from the Go type to comply with our
anti-pointer zero-value style (style.md) now that Go's zero-value is
clearly invalid.  However, there has been maintainer resistance to
removing the pointer [1] (although I don't think this is consistent
with previous maintainer statements that we don't need pointers when
the zero value is invalid [2]).  In order to land the normative spec
change, this commit keeps the current *int for Hook.Timeout and punts
a consistent policy to future work.

[1]: #764 (comment)
[2]: #653 (comment)

Signed-off-by: W. Trevor King <wking@tremily.us>

Signed-off-by: zhouhao <zhouhao@cn.fujitsu.com>

Signed-off-by: zhouhao <zhouhao@cn.fujitsu.com>

Signed-off-by: zhouhao <zhouhao@cn.fujitsu.com>

Signed-off-by: zhouhao <zhouhao@cn.fujitsu.com>

The previous wording hinted at, but did not require, this setting to
be implemented via oom_score_adj.  With the new wording, when proc is
mounted at /proc, the container process can check this value by
looking at /proc/self/oom_score_adj.

Signed-off-by: W. Trevor King <wking@tremily.us>

So we can compliance-test runtimes for these settings.

Also remove the tutorial, since the kernel docs should provide
sufficient documentation on that front.  The kernel can be patched if
they do not, and we do not include tutorials for other config-linux
settings in this spec.

The updated example was recommended by Xiaochen to compensate for the
removed inline tutorial [1].

[1]: #787 (comment)

Signed-off-by: W. Trevor King <wking@tremily.us>

Remove range limit

schema: bug fixes

And fill in some known-good and known-bad examples.  We can make this
as detailed as we want, but this commit just adds enough to know that:

* The full-file spec examples are valid.
* The JSON Schema can distinguish valid examples from invalid JSON.

This will help catch JSON Schema typos like those being addressed by
[1].

[1]: #784

Signed-off-by: W. Trevor King <wking@tremily.us>

config-linux: RFC 2119 wording for intelRdt

config-solaris.md: fix info

schema: Add 'test' target to the Makefile

config-linux: RFC 2119 wording for oomScoreAdj

config: Require strictly-positive timeout values

config: Drop the redundant config.json filename requirement

The only discussion related to this is in [1,2], where the
relationship between oomScoreAdj and disableOOMKiller is raised. But
since 429f936 (Adding cgroups path to the Spec, 2015-09-02, #137)
resources has been tied to cgroups, and oomScoreAdj is not about
cgroups.  For example, we currently have (in config-linux.md):

  You can configure a container's cgroups via the resources field of
  the Linux configuration.

I suggested we move the property from linux.resources.oomScoreAdj to
linux.oomScoreAdj so config authors and runtimes don't have to worry
about what cgroupsPath means if the only entry in resources is
oomScoreAdj.  Michael responded with [4]:

  If anything it should probably go on the process

So that's what this commit does.

I've gone with the four-space indents here to keep Pandoc happy (see
7795661 (runtime.md: Fix sub-bullet indentation, 2016-06-08, #495),
but have left the existing entries in this list unchanged to reduce
churn.

[1]: #236
[2]: #292
[3]: #137
[4]: #782 (comment)

Signed-off-by: W. Trevor King <wking@tremily.us>