summaryrefslogtreecommitdiff
path: root/website
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2017-04-14 14:52:09 +0200
committerLudovic Courtès <ludo@gnu.org>2017-04-14 14:52:09 +0200
commitbf7054bf5d25605a8b961333e76e092ba7be8f01 (patch)
tree5fef2356edc984079c7f53c7b4dec47bdb32de46 /website
parent912b1b6efe8c6f6eef55038fcfe279d136a00d44 (diff)
downloadguix-artwork-bf7054bf5d25605a8b961333e76e092ba7be8f01.tar
guix-artwork-bf7054bf5d25605a8b961333e76e092ba7be8f01.tar.gz
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.
Diffstat (limited to 'website')
-rw-r--r--website/posts/running-services-in-containers.md2
1 files changed, 1 insertions, 1 deletions
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)