-
Notifications
You must be signed in to change notification settings - Fork 44
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
Use symbolic linker to create hard link? #17
Comments
Yes. Are you able to check out and build the project with Xcode? |
Sorry, I’m only vaguely familiar with Xcode.
I wanted to create a hard link to a folder, but further research has enlightened me that creating a hard link to a folder is not possible.
I wanted to be able to create a link that would follow the folder. I.e. if I moved the original file, the link would still connect to the folder.
Thank you for your prompt reply.
D
On Nov 18, 2021, at 7:48 PM, Nick Zitzmann ***@***.******@***.***>> wrote:
Yes. Are you able to check out and build the project with Xcode?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#17 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARUUSRPO7F7MF7PRVNKF3ZDUMWNGPANCNFSM5IJ67YNQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Oh, yeah, hard links to folders aren't allowed by the POSIX.1 standard. The HFS+ file system supports them anyway, but it's non-standard, and just about everyone using macOS has moved on to APFS. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
symbolic linker is great for creating soft links. However I need to create hard links. Is there a change I can make to have symbolic linker create hard links?
The text was updated successfully, but these errors were encountered: