On Thu, Jul 30, 2015 at 5:19 AM, Robert A Ensink <[email protected]> wrote: > This looks like a bug somewhere in Vagrant - especially considering that > :linux is the default value.
Hello Robert, Vagrant provide guest discovery, so in my particular case I have never been in the need to specify that parameter. For vagrant tasks, if the OS is well known, vagrant will identify correctly and execute the code its' required. which is nice. When this doesn't work, I think the best is open an issue on Vagrant if the code is on the core, and add what's required .. ie: a new linux guest require new discover, or because RedHat 7 use different XYZ the command is different, etc in that way, everyone benefit of the addition. Even when your ruby-fu or vagrant-core-fu is low, having the issue on the radar with a reproductible case, helps, since someone else can finish that Thanks! Alvaro. -- 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/CAHqq0ez3n03V1qtbs%3DKt%3DPjz0tenzyuCXhwPrs0CXkZopdEi1Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
