Per https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/irLAQ8f8uGk

Initial migration of wiki content over to src/docs

There will be a follow-up CL to ensure docs are following chromium’s style guide, links are fixed, etc. The file auditing was becoming too much for a single change and per Nico’s suggestion, it seems to be better to do

+ Bulk import with initial prune.
+ Follow-up CLs to clean up the documentation.

So that each CL has its own purpose.

BUG=none

Review URL: https://codereview.chromium.org/1309473002

Cr-Commit-Position: refs/heads/master@{#345186}
diff --git a/docs/linux_suid_sandbox_development.md b/docs/linux_suid_sandbox_development.md
new file mode 100644
index 0000000..950460d
--- /dev/null
+++ b/docs/linux_suid_sandbox_development.md
@@ -0,0 +1,61 @@
+(For context see [LinuxSUIDSandbox](http://code.google.com/p/chromium/wiki/LinuxSUIDSandbox))
+
+We need a SUID helper binary to turn on the sandbox on Linux.
+
+In most cases, you can run **build/update-linux-sandbox.sh** and it'll install the proper sandbox for you in /usr/local/sbin and tell you to update your .bashrc if needed.
+
+### Installation instructions for developers
+
+  * If you have no setuid sandbox at all, you will see a message such as:
+```
+Running without the SUID sandbox!
+```
+  * If your setuid binary is out of date, you will get messages such as:
+```
+The setuid sandbox provides API version X, but you need Y
+```
+```
+You are using a wrong version of the setuid binary!
+```
+
+Run the script mentioned above, or do something such as:
+
+  * Build chrome\_sandbox whenever you build chrome ("ninja -C xxx chrome chrome\_sandbox" instead of "ninja -C xxx chrome")
+  * After building, run something similar to (or use the provided update-linux-sandbox.sh):
+```
+sudo cp out/Debug/chrome_sandbox /usr/local/sbin/chrome-devel-sandbox #needed if you build on NFS!
+sudo chown root:root /usr/local/sbin/chrome-devel-sandbox
+sudo chmod 4755 /usr/local/sbin/chrome-devel-sandbox
+```
+
+  * Put this line in your ~/.bashrc (or .zshenv etc):
+```
+export CHROME_DEVEL_SANDBOX=/usr/local/sbin/chrome-devel-sandbox
+```
+
+### Try bots and waterfall
+
+If you're installing a new bot, always install the setuid sandbox (the instructions are different than for developers, contact the Chrome troopers). If  something does need to run without the setuid sandbox, use the --disable-setuid-sandbox command line flag.
+
+The SUID sandbox must be enabled on the try bots and the waterfall. If you don't use it locally, things might appear to work for you, but break on the bots.
+
+(Note: as a temporary, stop gap measure, setting CHROME\_DEVEL\_SANDBOX to an empty string is equivalent to --disable-setuid-sandbox)
+
+### Disabling the sandbox
+
+If you are certain that you don't want the setuid sandbox, use --disable-setuid-sandbox. There should be very few cases like this.
+So if you're not absolutely sure, run with the setuid sandbox.
+
+### Installation instructions for "[Raw builds of Chromium](https://commondatastorage.googleapis.com/chromium-browser-continuous/index.html)"
+
+If you're using a "raw" build of Chromium, do the following:
+```
+sudo chown root:root chrome_sandbox && sudo chmod 4755 chrome_sandbox && export CHROME_DEVEL_SANDBOX="$PWD/chrome_sandbox"
+./chrome
+```
+
+You can also make such an installation more permanent by following the [steps above](#Installation_instructions_for_developers.md) and installing chrome\_sandbox to a more permanent location.
+
+### System-wide installations of Chromium
+
+The CHROME\_DEVEL\_SANDBOX variable is intended for developers and won't work for a system-wide installation of Chromium. Package maintainers should make sure the setuid binary is installed and defined in GYP as linux\_sandbox\_path.
\ No newline at end of file