In a bidirectional sync, this will almost always lead to a conflict, though, so I'd only advise this for an rsync-style approach. Synchronizing package manager data will only make sense if you do a full sync of almost everything, perhaps with a few well-considered exceptions.Synchronizing your home directory should be no problem at all, and should synchronize most of your daily work I presume.Results when run inside the VM will greatly depend on what you sync. Running the sync outside the VM will have the problems you describe. It will work both ways, and tell you what it is going to do before doing so, and also detect files manipulated concurrently on both sides. Using rsync for bidirectional operations is difficult I'd suggest you look at unison as an alternative. Would that work without messing up package management? Would I need to do anything manually besides updates like new kernel or drivers? Are there any other solution that could work better? The next option would be rsyncing the running machines to each other. ![]() But that would be infeasible: it would stop me from ever working separately on the VMs, because rsync would have no way to detect conflicts and merge them properly without knowledge of the filesystems that lie inside the containers. My tool of choice would be rsync, more specifically the Cygwin version of it, using the -inplace option to reduce writes as much as possible. My first thought was synchronizing the virtual disk files themselves. The host operating system is Windows 7 on both computers, running VirtualBox 4. Having recently bought a notebook, I want to be able to take my Ubuntu virtual machine with me, and have the changes I do on the notebook propagate to the desktop, and vice-versa, when I arrive/leave home. I've been using VirtualBox on my desktop for quite a while.
0 Comments
Leave a Reply. |