Part of your objection to the way Vagrant works appears to be due to a 
misunderstanding. One directory, one Vagrantfile, can serve as a home for 
as many machines as you would care to name. The "up", "halt" etc 
subcommands will take a machine name as a parameter. The Vagrantfile can 
refer to your own personal "box" files, not just to the published ones (but 
you may need to become familiar with the "packer" command to properly set 
up your own box files so they will work properly with Vagrant).

Whether this current implementation will serve all of your purposes, I 
can't say. It's certainly possible to use Docker images as a way to deploy 
a packaged cross-compilation environment; it's not likely to support very 
many aspects of kernel development simultaneously with providing the 
cross-compilation environment. It _is_ one way to answer the "hell" of 
conflicting library versions, since a container does not necessarily 
require all its libraries to be at the same version as every other 
container it communicates with. I would like to think that it's possible to 
sequence up the compilation environment of old versions of Linux separately 
from sequencing up the kernels. Both qemu and virtualbox, last I knew, can 
successfully run DOS or FreeDOS, as well as very old Linux kernels. Once 
you figure out the "glue" steps needed to get from one artifact to its 
successor, you should be on your way.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/5a46ef02-a468-41a5-b900-ced4082df4e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to