Skip to content
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

RFC: split up fs::soft_link into os::unix::fs::symlink and os::windows::fs::{symlink_file, symlink_dir} #1048

Merged
merged 4 commits into from
Apr 17, 2015
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix link formatting
  • Loading branch information
lambda committed Apr 14, 2015
commit d509d1ad426a08fb1608ef35c9cb4195c60ae03d
2 changes: 1 addition & 1 deletion text/0000-rename-soft-link-to-symlink.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ so; while on Unix, ordinary users can create symlinks, and any additional
security policy (such as [Grsecurity][2]) generally restricts
whether applications follow symlinks, not whether a user can create them.

[1]: (https://technet.microsoft.com/en-us/library/cc766301%28WS.10%29.aspx) in order to be able to do
[1]: https://technet.microsoft.com/en-us/library/cc766301%28WS.10%29.aspx
[2]: https://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Linking_restrictions

Thus, there needs to be a way to distinguish between the two operations on
Expand Down