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

umask not taking? #866

Closed
jdalton opened this issue Aug 11, 2016 · 4 comments
Closed

umask not taking? #866

jdalton opened this issue Aug 11, 2016 · 4 comments

Comments

@jdalton
Copy link

jdalton commented Aug 11, 2016

I noticed when I touch a.js it's created with the default permissions of -rwxrwxrwx and I'm wanting to change that to -rw-r--r--. I tried using umask 022 but it's not seeming to make a difference.

touch a.js
ls -l a.js
-rwxrwxrwx a.js
umask 022
touch b.js
ls -l b.js
-rwxrwxrwx b.js
@jdalton
Copy link
Author

jdalton commented Aug 11, 2016

It looks like this is only an issue in folders in /mnt/c/ as umask is respected within my home directory.

@aseering
Copy link
Contributor

I think this is a symptom of a more general issue -- AFAIK file permissions in general aren't fully supported on DrvFS (ie., /mnt/*)

@rodrymbo
Copy link

Well, NTFS file permissions are supported and enforced, they just aren't translated to the usual linux attributes. Apparently, the only way to find out if you have permission to do something (from within WSL) on a file in DriveFS is to try it and see if it works.

@neurogenesis
Copy link

@jdalton : this is possibly a duplicate of #352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants