config: linux: remove supported kernel versions

Since distributions do backporting, it doesn't make sense for us to inshrine the history of the kernel in the spec. Signed-off-by: Aleksa Sarai <[email protected]>
opencontainers · Jun 3, 2016 · 4eb65e7 · 4eb65e7
1 parent 3ce281c
commit 4eb65e7
Showing 1 changed file with 7 additions and 7 deletions.
diff --git a/config-linux.md b/config-linux.md
@@ -27,13 +27,13 @@ Namespaces are specified as an array of entries inside the `namespaces` root fie
 The following parameters can be specified to setup namespaces:
 
 * **`type`** *(string, required)* - namespace type. The following namespaces types are supported:
-    * **`pid`** processes inside the container will only be able to see other processes inside the same container. Support for this was added in Linux 2.6.24.
-    * **`network`** the container will have its own network stack. Support for this was added in Linux 2.6.24.
-    * **`mount`** the container will have an isolated mount table. Support for this was added in Linux 2.4.19.
-    * **`ipc`** processes inside the container will only be able to communicate to other processes inside the same container via system level IPC. Support for this was added in Linux 2.6.19.
-    * **`uts`** the container will be able to have its own hostname and domain name. Support for this was added in Linux 2.6.19.
-    * **`user`** the container will be able to remap user and group IDs from the host to local users and groups within the container. Support for this was added in Linux 3.8.
-    * **`cgroup`** the container will have an isolated view of the cgroup hierarchy. Support for this was added in Linux 4.6.
+    * **`pid`** processes inside the container will only be able to see other processes inside the same container.
+    * **`network`** the container will have its own network stack.
+    * **`mount`** the container will have an isolated mount table.
+    * **`ipc`** processes inside the container will only be able to communicate to other processes inside the same container via system level IPC.
+    * **`uts`** the container will be able to have its own hostname and domain name.
+    * **`user`** the container will be able to remap user and group IDs from the host to local users and groups within the container.
+    * **`cgroup`** the container will have an isolated view of the cgroup hierarchy.
 
 * **`path`** *(string, optional)* - path to namespace file in the [runtime mount namespace](glossary.md#runtime-namespace)