runtime-config-linux: One sentence per line for opening two paragraphs
I touched these paragraphs while removing trailing whitespace in the previous commit. Since I was touching them in this branch, it seemed better to rewrap them using the "Markdown style" suggestions in the README. I also added a missing period after the namespaces(7) link. Signed-off-by: W. Trevor King <wking@tremily.us>
This commit is contained in:
parent
a48397b9eb
commit
9f758db92f
|
@ -1,13 +1,11 @@
|
||||||
## Linux namespaces
|
## Linux namespaces
|
||||||
|
|
||||||
A namespace wraps a global system resource in an abstraction that makes it
|
A namespace wraps a global system resource in an abstraction that makes it appear to the processes within the namespace that they have their own isolated instance of the global resource.
|
||||||
appear to the processes within the namespace that they have their own isolated
|
Changes to the global resource are visible to other processes that are members of the namespace, but are invisible to other processes.
|
||||||
instance of the global resource. Changes to the global resource are visible to
|
For more information, see [the man page](http://man7.org/linux/man-pages/man7/namespaces.7.html).
|
||||||
other processes that are members of the namespace, but are invisible to other
|
|
||||||
processes. For more information, see [the man page](http://man7.org/linux/man-pages/man7/namespaces.7.html)
|
|
||||||
|
|
||||||
Namespaces are specified in the spec as an array of entries. Each entry has a
|
Namespaces are specified in the spec as an array of entries.
|
||||||
type field with possible values described below and an optional path element.
|
Each entry has a type field with possible values described below and an optional path element.
|
||||||
If a path is specified, that particular file is used to join that type of namespace.
|
If a path is specified, that particular file is used to join that type of namespace.
|
||||||
|
|
||||||
```json
|
```json
|
||||||
|
|
Loading…
Reference in New Issue