To answer your question about my goals (it's more like a wish, I can't see how I have the time to do all of this):
Basically, Linux from scratch, from Slack 3.2, .. onward. I'd like to chain these "environments", by sharing virtual disks, whereby, one environment, is building the subsequent environment. What's the point? I learned a lot from LFS. I learned a lot from Slackware (early kernels). Ideally, on my Mac, I create a qcow2 file. Use Docker container, mount the disk image, extract Slackware files, and then use Slackware floppy disks, or qemu -kernel to boot the environment. Then, I would create a new disk image, mount that (from the build environment), and build the next environment. Ultimately, I've heard of kernel developers or device driver developers whom have a test-harness (of cross-compilation toolchains and environments) where they test their code. It would be nice if I can ssh into any kernel version I want. -- 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/1d4af4db-602c-4eb3-822b-1a310aa79b9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
