|author||Lutz Justen <firstname.lastname@example.org>||Fri Jul 13 11:21:19 2018|
|committer||chrome-bot <email@example.com>||Thu Aug 16 20:14:37 2018|
sandboxing.md: Document daemon store mounts Documents a new way to set up Cryptohome daemon store folders, so that the Cryptohome mount event propagates into mount namespaces. This allows daemons that run inside a mount namespaces to securely use per-user daemon storage ('user' in the sense of Chrome OS user account, not Linux user). CQ-DEPEND=CL:1127665 BUG=chromium:738433 TEST=Viewed in VSCode built-in MD viewer Change-Id: I16563f298bd427e0c6fa4d531669b26f3f964396 Reviewed-on: https://chromium-review.googlesource.com/1136440 Commit-Ready: Lutz Justen <firstname.lastname@example.org> Tested-by: Lutz Justen <email@example.com> Reviewed-by: Mike Frysinger <firstname.lastname@example.org>
Markdown documents must follow the style guide.
This repository is managed by the repo tool, so you can make changes to it using the same techniques that you'd use for any other repositories in the project. Feel free to bypass the commit queue and commit changes immediately after they are reviewed.
You can also make changes to this repository without using the repo tool. This comes in handy when you don't have a Chromium OS checkout:
git clone https://chromium.googlesource.com/chromiumos/docs curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg chmod +x .git/hooks/commit-msg cd docs git checkout -b changes (make some changes) git commit -a git push origin HEAD:refs/for/master
The above steps will upload a patch to chromium-review.googlesource.com where you can get your patch reviewed, and submit.
You can preview your local changes using
You can also use md_browser, which is entirely local and does not require refs/sandbox/ push permission, but has somewhat inaccurate rendering:
# at top of Chromium OS checkout ./chromium/src/tools/md_browser/md_browser.py -d docs
Then browse to e.g. http://localhost:8080/README.md.
To review someone else's changes, apply them locally first, or just click the
gitiles link near the top of a Gerrit file diff page.