Hello, the trick on udev run an script.. so you can do
umount /media/sf_vagrant mount -t vboxsf -o "options_here" vagrant /vagrant second, vagrant on start (up/reload) clear all the shared folders and create the ones defined on vagrantfile so, vagrant doesn't suffer this problem, and is done as I see it to remove any shared folder that may have been left in the vm (not sure if possible at all), and to process changes you may have done . as I see your problem, you have a VM you want to distribute to 2 different end users.. Vagrant, and non-vagrant if you look at packer,io you can use that with virtualbox-ovf and start with a pre-existing vm, and use the output/post-processor to create 2 vms.. one OVA for double click, gui, on.. experience and one BOX for vagrant perhaps that will help you to control more the distribution of the VMs Alvaro. On Fri, Mar 20, 2015 at 11:04 PM, Dieter Menne <[email protected]> wrote: > Thanks for the pointer, I had see that before. It is applicable to cases > where the vagrant folder is required for some operation, which is not the > case in my example. > > For my example, it is ok to remount later because the the synced folders are > not required for startup. One way out is to totally omit synced folders from > Vagrantfile, and to do everthing explicitly in rc.local or similar. > > I just could not believe that there is no mechanism that makes the shared > folders persistent. After restart, everything is shared in the wrong > folders, i.e. /media/.... > > Dieter > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
