[vagrant-up] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع

[fayez joell]

US Congressional Hearing of

 Saudi billionaire" maan  Al Sanea "

 and Money Laundering

with bank of America



With Arabic Subtitles





http://www.youtube.com/watch?v=mIBNnQvhU8s






*موقع اليوتيوب الذي عرض فيديوهات جلسة استماع الكونجرس الأمريكي *

* لمتابعة نشاطات غسل الأموال ونشاطات*



*السعودي معن عبدالواحد الصانع*

*مالك مستشفى  وشركة سعد  ومدارس سعد بالمنطقة الشرقية** بالسعودية * * ورئيس
مجلس ادارة بنك اوال البحريني*



 *وتعليق محطة سي ان بي سي التلفزيونية*



*مترجم باللغة العربية*


http://www.youtube.com/watch?v=mIBNnQvhU8s

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAJNWts0eRGQuhCF74c-eOO_UPn0pJ1k6qnHyTo1Y9iMwko5p4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Re: ALT platforms guests with /etc/net support

[Evgeny Sinelnikov]

Hello,

thanks to Chris Roberts for first review and useful recommendations to
add test coverage on new guest for ALT platforms. I did it and it was
very helpful for some important fixes. But this time new tags added -
pr/needs-tests and pr/reviewed. What can I do to overcome it?


2017-07-03 22:06 GMT+04:00 Evgeny Sinelnikov :
> Hello,
>
> I prepare pull request for ALT platforms guest support with /etc/net as
> network configuration system:
> https://github.com/mitchellh/vagrant/pull/8746
>
> Could anybody review patch with this this enhancment?



-- 
Sin (Sinelnikov Evgeny)

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAK42-Go9-QzPUVOy87tavBZfveXM4OjWZcVGUUeereKE0a%3Dutw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Re: Vagrant 'running triggers after up...' = connection closed & vv create only creates 3 files..

[Blake Geraci]

Hey, 

Did either of you guys ever figure out the answer? I'm stuck here as well. 

On Thursday, March 30, 2017 at 4:16:10 PM UTC-4, Jonathon Pawlick wrote:
>
> Hey, just wondering if you figured out the issue? I am getting the same 
> issue and have tried doing `vagrant destroy` and re-running `vagrant up 
> --provision`
>
> Everything looks fine, except then it just closes the connection after 
> saying `Running triggers after up...` same as you.
>
> On Saturday, March 11, 2017 at 10:00:45 AM UTC-7, Elliot Byrne wrote:
>>
>> Hi guys,
>>
>> Just trying to get vagrant (version 1.9.2) up and running on my Macbook 
>> (running OS Sierra).
>>
>> Although when I use 'vagrant up' it gets through everything okay until it 
>> gets to:
>>
>> *==> default: Running provisioner: shell...*
>>
>> default: Running: inline script
>>
>> *==> default:  * Restarting nginx nginx*
>>
>> *==> default:...done.*
>>
>> *==> default: Running triggers after up...*
>>
>> Connection to 127.0.0.1 closed.
>>
>> Does anyone know what could be causing the connection to close and how to 
>> fix it? 
>>
>> I assume this error is related to why when I use 'vv create' it only 
>> creates 'vvv-hosts' 'vvv-init.sh' and 'wp-cli-yml. So it doesn't create a 
>> htdocs, any wordpress files etc..
>>
>>
>> Any help would be appreciated, thank you!
>>
>

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/3c17f05d-773e-4566-a699-35df6b12b8fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] config.vm.synced_folder ignored in default Vagrantfile

[Krist van Besien]

I've been using Vagrant extensively. So I know the difference between init 
and up.

My problem is the following:

- I created a box myself, by packaging an image, together with a 
Vagrantfile and a Metadata.json file.
- In that Vagrantfile I have the following content:

Vagrant.configure("2") do |config|
config.vm.provider :libvirt do |libvirt|
  libvirt.disk_bus = 'virtio'
end
config.vm.synced_folder  ".", "/vagrant", disabled: true
end

So I tarred/ziped those three files in to a new box, and imported that in 
to Vagrant.

Then I tested this. I created a new directory, and in that directory I did:

vagrant init newbox
vagrant up

What I expected to happen:

The box is started, but no synced folder is setup.

What I got:

Box is started, and vagrant attempts to setup a synced folder, which fails 
on this particular image. (and this is why I want it to be disabled by 
default)

In other words, I expect (and the documentation has led me to expect this) 
that the config you put in the Vagrantfile you package in a box is 
interpreted as a default for that box, and that this config is merged with 
the Vagrantfile created by vagrant init in your working directory. In other 
words, I expect to be able to set defaults in a box.

Are my expectations incorrect? Or did I do something wrong? Or is this a 
bug?







On Friday, 7 July 2017 17:47:38 UTC+1, Salty Vagrant wrote:
>
> I suspect this is simply a misunderstanding of the vagrant commands.
>
> Once you have your edited Vagrantfile (with the synced_folder disabled) 
> you should use ‘vagrant up’ NOT ‘vagrant init’.
>
> ‘vagrant init’ creates a new Vagrantfile and sets the vm/box to the value 
> you provide on the command line (this will overwrite the one you previously 
> created).
>
> ‘vagrant up’ on the other hand will start the VM specified by the 
> Vagrantfile.
>
> On 7 Jul 2017, at 16:44, Krist van Besien wrote:
>
> Hello all,
>
> I created my own box, and the box, and the Vagrantfile included in the box 
> has the following content:
>
> Vagrant.configure("2") do |config|
> config.vm.provider :libvirt do |libvirt|
>   libvirt.disk_bus = 'virtio'
> end
> config.vm.synced_folder  ".", "/vagrant", disabled: true
> end
>
>
> However this setting is ignored. After doing a "vagrant init " I 
> need to edit the Vagrantfile manually to again disable the synced folder.
>
> Why is that? 
>
>
>
>
>
>
> -- 
> 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 vagrant-up+...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vagrant-up/317ab26a-7323-4b15-98a7-69d97a6d11bd%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/5345e486-c18f-4d34-93a3-62b03e557dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.