| commit | 03602d02cb51524db10bb4964ab644399dcda06b | [log] [tgz] |
|---|---|---|
| author | Nicholas Bishop <nicholasbishop@google.com> | Thu Apr 28 12:16:47 2022 -0400 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 28 17:19:04 2022 +0000 |
| tree | 2772a012182f23b4685aaf1856b5950368f938c2 | |
| parent | a4b4ab6532524d1b54db55b7e9f947481ee6c591 [diff] |
Make sudo changes optional Due to the changes in crrev.com/c/36618, disabling tty_tickets is no longer required to run cros_sdk. Making sudo more permissive can still be helpful for workflows outside the chroot though, so change the sudo instructions to make them optional. BUG=None TEST=Verify that `sudo grep -r tty_ticket /etc` has no results TEST=cros_sdk works Change-Id: Ieb67990a8dce0f2cf24683f2a4983899e4539bf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/3611023 Auto-Submit: Nicholas Bishop <nicholasbishop@google.com> Commit-Queue: Nicholas Bishop <nicholasbishop@google.com> Tested-by: Nicholas Bishop <nicholasbishop@google.com> Reviewed-by: Mike Frysinger <vapier@chromium.org>
This directory contains public ChromiumOS project documentation that is automatically rendered by Gitiles. The docs are written in Gitiles-flavored Markdown.
See the Chromium documentation guidelines and Chromium documentation best practices.
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.
See the Contributing guide for more details.
You can preview your local changes using scripts/preview_docs which utilizes Gerrit sandbox branches:
scripts/preview_docs README.md
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 ChromiumOS checkout ./src/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.