Name the hostnames.conf path in the remote-access summary - #35
Merged
Conversation
The two-part summary at the top described what to change without saying where it lives. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The remote access page opens with a two-part summary of what to change, but the
first mention of
/etc/halos/hostnames.confis several sections down. A readerskimming the top learns they need to switch the canonical to an FQDN without
learning where that setting lives, and can reasonably guess at a standard
system file.
Adds the path to the summary's first item. The detailed instructions stay
where they are.
🤖 Generated with Claude Code