Closed withinboredom closed 10 years ago
The chmod 777
was introduced on https://github.com/fgrehm/vagrant-cachier/commit/0dd1b20053a35ce6ee9ef92152e01eb33cf341df in order to fix GH-74 so I'm not sure if we can get rid of that.
Which provider are you using over there? We might be able to change the code to skip the chmod
if an specific synced folder implementation or provider gets detected.
I'm using hyperv— Sent from Mailbox
On Mon, Jun 23, 2014 at 10:02 PM, Fabio Rehm notifications@github.com wrote:
The
chmod 777
was introduced on https://github.com/fgrehm/vagrant-cachier/commit/0dd1b20053a35ce6ee9ef92152e01eb33cf341df in order to fix GH-74 so I'm not sure if we can get rid of that.Which provider are you using over there? We might be able to change the code to skip the
chmod
if an specific synced folder implementation or provider gets detected.Reply to this email directly or view it on GitHub: https://github.com/fgrehm/vagrant-cachier/issues/107#issuecomment-46924402
This was fixed in git, a new release will come out with it as soon as I'm done with the stuff tagged with the v1.0.0 milestone
Vagrant fails on
This is due to the fact that you cannot chmod an smb folder. File permissions are set at mount time with options
This may be for another ticket, but is 777 really necessary for package storage?