envfs
envfs copied to clipboard
make filesystem inodes read-only
Some tools can complain about them beeing writable. Since processes cannot write them anyway, that seems like a good default.
Untested. See https://github.com/Mic92/envfs/issues/166
cc @con-f-use
After thinking about it, since I don't know why problem exist in the first place, I would not merge it for now.
I have not seen any symlink implementation that was not using 777 as permissions.