-
Notifications
You must be signed in to change notification settings - Fork 18k
x/website: clarify Linux installation instructions regarding root/sudo permissions #73300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Related Issues
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
I've noticed that similar issues have been closed before, perhaps due to requests to change the command itself. |
Your suggested alternative sounds good. Please go ahead and send the change. See https://go.dev/doc/contribute. One minor suggestion, since that is a complete sentence inside the parentheses, let's also move the period to be inside. |
Thanks for the clarification! That makes perfect sense. I’ll apply the suggestion and send the change later today. |
Change https://go.dev/cl/664597 mentions this issue: |
What is the URL of the page with the issue?
https://go.dev/doc/install
What is your user agent?
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36
Screenshot
No response
What did you do?
Follow the official installation instructions for Go on Linux: https://go.dev/doc/install
They attempt to run the command with a single sudo prefix, e.g.:
sudo rm -rf /usr/local/go && tar -C /usr/local -xzf go1.24.2.linux-amd64.tar.gz
rm
command runs with elevated permissions, buttar
does not, leading to permission denied errors.What did you see happen?
The Linux installation instructions may confuse new users into running a combined
rm && tar
command with a singlesudo
, causing permission errors during extraction.The documentation currently says:
This can be confusing, as new users often try to run both steps with a single
sudo
, which only applies to the first command. A small rewording could improve clarity without changing the overall tone.What did you expect to see?
The Go installation completes successfully without permission errors.
Suggested alternative:
This makes it clearer that both commands might require elevated permissions individually.
I'd be happy to submit a PR with this change, if appropriate, as a first contribution.
The text was updated successfully, but these errors were encountered: