man: Correct and clarify things about openfd #692
Conversation
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
LukeShu
force-pushed
the
lukeshu/man-openfd
branch
from
d831fe8 to
636adf3
Compare
LukeShu
force-pushed
the
lukeshu/man-openfd
branch
from
636adf3 to
e784648
Compare
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.
pipe(3), which actually returns anAF_UNIXsocket, not a pipe; so the "no-RDWR" restriction is a lie.unixfdfield of theRopenfdis a lie; and the control-message should be used insteadopenfd(9p)(in addition to the existing call-out in9pclient(3)) that there's no special version string.