config-linux: Explicitly allow symlinks for providing devices #873
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.
I'd rather address runtime compliance by breaking this down into explicit checks based on POSIX stat(3) calls. But with that approach rejected, mentioning symlinks here helps motivate runtime-tools' choice of
os.Stat
(which follows symlinks) vs.os.Lstat
(which does not).Spun off as a non-controversial portion of the rejected #829, as requested by @crosbymichael on 2017-06-01 (although that request didn't make it into the log).