Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WSL container is now available for public preview

devblogs.microsoft.com

Post reply on HN
Print view View original

1–10 of 12 posts

Re: WSL container is now available for public preview

#5

Post by tuwtuwtuwtuw »

Let's say I clone a git repo onto my NTFS drive. After that, I open that as a dev container in VS Code. Would +x permissions on shell scripts work then? In this scenario, the +x attribute is set on the file in git.

I know NTFS doesn't support it, and trying to understand what the workflow looks like.

Re: WSL container is now available for public preview

#8

Post by baby_souffle »

tuwtuwtuwtuw wrote: post #5

Let's say I clone a git repo onto my NTFS drive. After that, I open that as a dev container in VS Code. Would +x permissions on shell scripts work then? In this scenario, the +x attribute is set on the file in git. I know NTFS doesn't support it, and trying to understand what the workflow looks like.

Ntfs supports alternative data streams so they probably use that to record the unix permission byres

Re: WSL container is now available for public preview

#9

Post by Neywiny »

tuwtuwtuwtuw wrote: post #5

Let's say I clone a git repo onto my NTFS drive. After that, I open that as a dev container in VS Code. Would +x permissions on shell scripts work then? In this scenario, the +x attribute is set on the file in git. I know NTFS doesn't support it, and trying to understand what the workflow looks like.

My recommendation is that sadly it's just not worth it. NTFS not being case sensitive has caused me uncountable lost hours for why repos wouldn't compile. I don't understand people choosing to rely on case sensitivity for anything because it's a readability issue for me, but people do. The amount of times I've just re-cloned in the wsl drive and my weirdness goes away is too high
Post reply on HN