From bf7054bf5d25605a8b961333e76e092ba7be8f01 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Fri, 14 Apr 2017 14:52:09 +0200 Subject: website: services-in-containers: "single view" of the resources. * website/posts/running-services-in-containers.md (tags): "single view" instead of "unique view". Suggested by Andy Wingo. --- website/posts/running-services-in-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/posts/running-services-in-containers.md b/website/posts/running-services-in-containers.md index d8c6a41..b18d133 100644 --- a/website/posts/running-services-in-containers.md +++ b/website/posts/running-services-in-containers.md @@ -44,7 +44,7 @@ The operating system side of things is less bright. Although the has been well-known in operating system circles for a long time, it remains foreign to Unix and GNU/Linux. Processes run with the full authority of their user. On top of that, until recent changes to the -Linux kernel, resources were global and there was essentially a unique +Linux kernel, resources were global and there was essentially a single view of the file system, of the process hierarchy, and so on. So when a remote-code-execution vulnerability affects a system service—like [in the BitlBee instant messaging gateway (CVE-2016-10188)](https://bugs.bitlbee.org/ticket/1281) -- cgit v1.2.3