Files
kubernetes/docs
qiaolei 1bee049475 Change "chmod +X" to "chmod +x" in prereqs.md
Change `chmod +X` to `chmod +x`, since `+X` does not take affect when there is no  execute permission bit already set (either user, group or other).

```console
# ls -l /usr/bin/kubectl
-rw-r--r-- 1 root root 14190181 Aug 10 16:16 /usr/bin/kubectl
# chmod +X /usr/bin/kubectl
# ls -l /usr/bin/kubectl
-rw-r--r-- 1 root root 14190181 Aug 10 16:16 /usr/bin/kubectl
```

Please refer to [chmod](https://en.wikipedia.org/wiki/Chmod "chmod") for more details.
>which is not a permission in itself but rather can be used instead of x. It applies execute permissions to directories regardless of their current permissions and **applies execute permissions to a file which already has at least one execute permission bit already set (either user, group or other)**. It is only really useful when used with '+' and usually in combination with the -R option for giving group or other access to a big directory tree without setting execute permission on normal files (such as text files), which would normally happen if you just used "chmod -R a+rx .", whereas with 'X' you can do "chmod -R a+rX ." instead
2015-08-27 18:46:14 +08:00
..
2015-08-24 14:55:31 -04:00
2015-07-30 20:41:30 -04:00
2015-07-23 16:15:04 -07:00
2015-08-09 14:18:06 -04:00

WARNING WARNING WARNING WARNING WARNING

PLEASE NOTE: This document applies to the HEAD of the source tree

If you are using a released version of Kubernetes, you should refer to the docs that go with that version.

The latest 1.0.x release of this document can be found [here](http://releases.k8s.io/release-1.0/docs/README.md).

Documentation for other releases can be found at releases.k8s.io.

Kubernetes Documentation: releases.k8s.io/HEAD

Analytics