support/misc: Adding Vagrant file for provisioning
PATCH 1/1 support/misc: Adding Vagrant file for provisioning
This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms (Linux/Mac/Windows).
---
Changelog:
* Upgraded windows one liner to be compatible with all powershell versions
* Added a link to Vagrant homepage in doc and website
RFC
v2->v3:
* Downloading latest buildroot version only on first run
* Better handling of machine name and options
v1->v2:
* Autodetecting of latest buildroot version from CHANGES file.
* Better documentation
docs/manual/getting.txt | 14 +++++++++++++ docs/website/download.html | 17 ++++++++++++++++ support/misc/Vagrantfile | 51 ++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 82 insertions(+) create mode 100644 support/misc/Vagrantfile
docs/manual/getting.txt +14 -0
@@ -10,6 +10,20 @@ November. Release numbers are in the format YYYY.MM, so for example Release tarballs are available at http://buildroot.org/downloads/[]. +An official https://www.vagrantup.com/[Vagrantfile] is distributed within buildroot for your needs. +If you want to setup an isolated buildroot environment on Linux or +Mac Os X, paste this line onto your terminal: + +-------------------- +curl -O http://git.buildroot.net/buildroot/plain/support/misc/Vagrantfile; vagrant up +-------------------- + +If you are on Windows, paste this into your powershell: + +-------------------- +(new-object System.Net.WebClient).DownloadFile("http://git.buildroot.net/buildroot/plain/support/misc/Vagrantfile","Vagrantfile"); vagrant up +-------------------- + If you want to follow development, you can use the daily snapshots or make a clone of the Git repository. Refer to the http://buildroot.org/download[Download page] of the Buildroot website
docs/website/download.html +17 -0
@@ -32,6 +32,23 @@ This and earlier releases (and their PGP signatures) can always be downloaded fr <p> +<p> +An official <a href="https://www.vagrantup.com/">Vagrantfile</a> +is distributed within buildroot for your needs. +If you want to setup an isolated buildroot environment on Linux or +Mac Os X, paste this line onto your terminal: + +<pre> +curl -O http://git.buildroot.net/buildroot/plain/support/misc/Vagrantfile; vagrant up +</pre> + +If you are on Windows, paste this into your powershell: + +<pre> +(new-object System.Net.WebClient).DownloadFile("http://git.buildroot.net/buildroot/plain/support/misc/Vagrantfile","Vagrantfile"); vagrant up +</pre> +</p> + You can also obtain daily snapshots of the latest Buildroot source tree if you want to follow development, but cannot or do not wish to use Git.
support/misc/Vagrantfile new file +51 -0
51 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 1/1 support/misc: Adding Vagrant file for provisioning
Quoted 5 lines · Angelo Compagnucci
This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms (Linux/Mac/Windows).
Signed-off-by Angelo Compagnucci <[email protected]>
[snip]
Quoted 6 lines
support/misc/Vagrantfile new file +0
-0
support/misc/Vagrantfile line 9
Quoted 9 lines
support/misc/Vagrantfile new file +9
-0@@ -0,0 +1,51 @@ +################################################################################ +# +# Vagrantfile +# +################################################################################ + +### Change here for more memory/cores ### +VM_MEMORY=1024 +VM_CORES=1
Do we need to do that? And if we do, shouldn't it be higher? 1GB will not allow
you to build v8 and all its derivatives (webkit, webengine).
support/misc/Vagrantfile line 12
Quoted 3 lines
support/misc/Vagrantfile new file +3
-0+ +Vagrant.configure('2') do |config| + config.vm.box = 'ubuntu/trusty64'
Is there a way to make it match the host, i.e. run a 32-bit system on a 32-bit
host?
Quoted 7 lines
support/misc/Vagrantfile new file +7
-0+ + config.vm.provider :vmware_fusion do |v, override| + v.vmx['memsize'] = VM_MEMORY + v.vmx['numvcpus'] = VM_CORES + end + + config.vm.provider :virtualbox do |v, override|
support/misc/Vagrantfile line 29
Quoted 10 lines
support/misc/Vagrantfile new file +10
-0+ v.customize ['modifyvm', :id, '--memory', VM_MEMORY] + v.customize ['modifyvm', :id, '--cpus', VM_CORES] + end + + config.vm.provision 'shell' do |s| + s.inline = 'echo Setting up machine name' + + require 'open-uri' + open('http://git.buildroot.net/buildroot/plain/CHANGES') do |f| + $buildroot_version=f.read.lines.first.split(',')[0]
That's not at all reliable, this version will for instance change to an rc just
before a release. And for instance the 2015.08.1 is not in master's CHANGES.
I think it's better if we add a buildroot-latest.tar.bz2 symlink to the
downloads directory, then we can just use that.
Failing that, it's better to scrape it from http://buildroot.org/download.html
Quoted 5 lines
support/misc/Vagrantfile new file +5
-0+ end + + config.vm.provider :vmware_fusion do |v, override| + v.vmx['displayname'] = "Buildroot #{$buildroot_version}" + end
support/misc/Vagrantfile line 44
Quoted 10 lines
support/misc/Vagrantfile new file +10
-0+ + config.vm.provider :virtualbox do |v, override| + v.customize ['modifyvm', :id, '--name', "Buildroot #{$buildroot_version}"] + end + end + + config.vm.provision 'shell', inline: + "sudo apt-get -q update + sudo apt-get -q -y install build-essential libncurses5-dev \ + git bzr cvs mercurial subversion
I would also include libqt4-dev for xconfig, and the dependencies for the
manual and for the graphs: asciidoc, w3m, dblatex, graphviz, python, python-matplotlib. And rsync, is that included by default?
Regards,
Arnout
Quoted 8 lines
support/misc/Vagrantfile new file +7
-0+ sudo apt-get -q -y autoremove" + + config.vm.provision 'shell', privileged: false, inline: + "echo 'Downloading and extracting buildroot #{$buildroot_version}' + wget -q -c http://buildroot.org/downloads/buildroot-#{$buildroot_version}.tar.gz + tar axf buildroot-#{$buildroot_version}.tar.gz" +end
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 support/misc: Adding Vagrant file for provisioning
Dear Arnout Vandecappelle,
2015-09-20 23:18 GMT+02:00 Arnout Vandecappelle <[email protected]>:
Quoted 17 lines · Angelo Compagnucci
Quoted 5 lines
This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms (Linux/Mac/Windows).
Signed-off-by Angelo Compagnucci <[email protected]>[snip]
Quoted 10 lines
support/misc/Vagrantfile new file +4
-0@@ -0,0 +1,51 @@ +################################################################################ +# +# Vagrantfile +#
Quoted 8 lines
support/misc/Vagrantfile line 9
Quoted 5 lines
support/misc/Vagrantfile new file +5
-0+################################################################################ + +### Change here for more memory/cores ### +VM_MEMORY=1024 +VM_CORES=1Do we need to do that? And if we do, shouldn't it be higher? 1GB will not allow
you to build v8 and all its derivatives (webkit, webengine).
Nope. Raising this numbers means freezing the machine of a user with a low end laptop. Probably we could add some notes on the documentation, but Vagrant has it's own documentation and this is the standard de facto way to set memory/cores of a vagrant VM. This file should be a starting point for people wanting to try buildroot and not a one shop stop for all their problems.
Quoted 6 lines
support/misc/Vagrantfile line 12
Quoted 3 lines
support/misc/Vagrantfile new file +3
-0+ +Vagrant.configure('2') do |config| + config.vm.box = 'ubuntu/trusty64'Is there a way to make it match the host, i.e. run a 32-bit system on a 32-bit
host?
Honestly I don't think there are 32bit cpus which could run Buildroot compilation inside a VM. For me no problem here, all the cpus with virt instructions are 64bits and therefore could run a 64bit host.
Quoted 20 lines
Quoted 6 lines
support/misc/Vagrantfile new file +6
-0+ config.vm.provider :vmware_fusion do |v, override| + v.vmx['memsize'] = VM_MEMORY + v.vmx['numvcpus'] = VM_CORES + end + + config.vm.provider :virtualbox do |v, override|support/misc/Vagrantfile line 29
Quoted 10 lines
support/misc/Vagrantfile new file +10
-0+ v.customize ['modifyvm', :id, '--memory', VM_MEMORY] + v.customize ['modifyvm', :id, '--cpus', VM_CORES] + end + + config.vm.provision 'shell' do |s| + s.inline = 'echo Setting up machine name' + + require 'open-uri' + open('http://git.buildroot.net/buildroot/plain/CHANGES') do |f| + $buildroot_version=f.read.lines.first.split(',')[0]That's not at all reliable, this version will for instance change to an rc just
before a release. And for instance the 2015.08.1 is not in master's CHANGES.
Quoted 2 lines
I think it's better if we add a buildroot-latest.tar.bz2 symlink to the
downloads directory, then we can just use that.
Of course! I falled back to this method cause I cannot find find a more reliable one.
Quoted 1 line
Failing that, it's better to scrape it from http://buildroot.org/download.html
It's really strange that there is not an easy way to get the builroot version string easily.
Quoted 9 lines
Quoted 9 lines
support/misc/Vagrantfile new file +9
-0+ end + + config.vm.provider :vmware_fusion do |v, override| + v.vmx['displayname'] = "Buildroot #{$buildroot_version}" + end + + config.vm.provider :virtualbox do |v, override| + v.customize ['modifyvm', :id, '--name', "Buildroot #{$buildroot_version}"] + end
Quoted 8 lines
support/misc/Vagrantfile line 44
Quoted 6 lines
support/misc/Vagrantfile new file +6
-0+ end + + config.vm.provision 'shell', inline: + "sudo apt-get -q update + sudo apt-get -q -y install build-essential libncurses5-dev \ + git bzr cvs mercurial subversionI would also include libqt4-dev for xconfig,
Why? On windows there is not an X server to run the ssh x forwarding and the dependencies are really big ones. Nobody stops you to install them manually, it's an Ubuntu after all!
Quoted 3 lines
and the dependencies for the
manual and for the graphs: asciidoc, w3m, dblatex, graphviz, python, python-matplotlib.
Do you think we should force users to download a complete tex distribution only for compiling docs? As stated before users could install themselves if needed.
I prefer having a vagrant up setup time as small as possible to be operative as soon as possible!
Quoted 1 line
And rsync, is that included by default?
Yes, it's included in Ubuntu.
Sincerely, Angelo.
Quoted 22 lines
Regards,
Arnoutsupport/misc/Vagrantfile line 51
Quoted 8 lines
support/misc/Vagrantfile new file +7
-0+ sudo apt-get -q -y autoremove" + + config.vm.provision 'shell', privileged: false, inline: + "echo 'Downloading and extracting buildroot #{$buildroot_version}' + wget -q -c http://buildroot.org/downloads/buildroot-#{$buildroot_version}.tar.gz + tar axf buildroot-#{$buildroot_version}.tar.gz" +end--
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo
PATCH 1/1 support/misc: Adding Vagrant file for provisioning
Quoted 30 lines · Angelo Compagnucci
Dear Arnout Vandecappelle,
2015-09-20 23:18 GMT+02:00 Arnout Vandecappelle <[email protected]>:
Quoted 17 lines · Angelo Compagnucci
Quoted 5 lines
This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms (Linux/Mac/Windows).
Signed-off-by Angelo Compagnucci <[email protected]>[snip]
Quoted 10 lines
support/misc/Vagrantfile new file +4
-0@@ -0,0 +1,51 @@ +################################################################################ +# +# Vagrantfile +#Quoted 8 lines
support/misc/Vagrantfile line 9
Quoted 5 lines
support/misc/Vagrantfile new file +5
-0+################################################################################ + +### Change here for more memory/cores ### +VM_MEMORY=1024 +VM_CORES=1Do we need to do that? And if we do, shouldn't it be higher? 1GB will not allow
you to build v8 and all its derivatives (webkit, webengine).
Quoted 2 lines
Nope. Raising this numbers means freezing the machine of a user with a low end laptop.
Fair enough.
Quoted 13 lines
Probably we could add some notes on the documentation,
but Vagrant has it's own documentation and this is the standard de facto way to set memory/cores of a vagrant VM. This file should be a starting point for people wanting to try buildroot and not a one shop stop for all their problems.Quoted 6 lines
support/misc/Vagrantfile line 12
Quoted 3 lines
support/misc/Vagrantfile new file +3
-0+ +Vagrant.configure('2') do |config| + config.vm.box = 'ubuntu/trusty64'Is there a way to make it match the host, i.e. run a 32-bit system on a 32-bit
host?
Quoted 3 lines
Honestly I don't think there are 32bit cpus which could run Buildroot compilation inside a VM. For me no problem here, all the cpus with virt instructions are 64bits and therefore could run a 64bit host.
It's not for 32-bit CPUs, it's for 64-bit hardware running 32-bit OS.
Though of course you're right, the VM can still run a 64-bit OS.
Quoted 24 lines
Quoted 21 lines
Quoted 7 lines
support/misc/Vagrantfile new file +6
-0+ config.vm.provider :vmware_fusion do |v, override| + v.vmx['memsize'] = VM_MEMORY + v.vmx['numvcpus'] = VM_CORES + end + + config.vm.provider :virtualbox do |v, override|support/misc/Vagrantfile line 29
Quoted 10 lines
support/misc/Vagrantfile new file +10
-0+ v.customize ['modifyvm', :id, '--memory', VM_MEMORY] + v.customize ['modifyvm', :id, '--cpus', VM_CORES] + end + + config.vm.provision 'shell' do |s| + s.inline = 'echo Setting up machine name' + + require 'open-uri' + open('http://git.buildroot.net/buildroot/plain/CHANGES') do |f| + $buildroot_version=f.read.lines.first.split(',')[0]That's not at all reliable, this version will for instance change to an rc just
before a release. And for instance the 2015.08.1 is not in master's CHANGES.Quoted 2 lines
I think it's better if we add a buildroot-latest.tar.bz2 symlink to the
downloads directory, then we can just use that.
Quoted 7 lines
Of course! I falled back to this method cause I cannot find find a more reliable one.
Quoted 1 line
Failing that, it's better to scrape it from http://buildroot.org/download.html
It's really strange that there is not an easy way to get the builroot version string easily.
Well, the easy way would be
sed -n '/^export BR2_VERSION := /s///p' Makefile
but it's just a bad idea to take the latest git version as a basis of finding the 'current' version of buildroot.
You could also take the latest tag:
git tag -l | grep '^20[0-9][0-9]\.[0-9][0-9]\.[0-9.]*' | sort -n | tail -1
But overall, I think scraping from the website makes the most sense. Or even
better would be if the current version was recorded somewhere in a file that is used with SSI in downloads.html
Quoted 27 lines
Quoted 10 lines
Quoted 10 lines
support/misc/Vagrantfile new file +9
-0+ end + + config.vm.provider :vmware_fusion do |v, override| + v.vmx['displayname'] = "Buildroot #{$buildroot_version}" + end + + config.vm.provider :virtualbox do |v, override| + v.customize ['modifyvm', :id, '--name', "Buildroot #{$buildroot_version}"] + endQuoted 8 lines
support/misc/Vagrantfile line 44
Quoted 6 lines
support/misc/Vagrantfile new file +6
-0+ end + + config.vm.provision 'shell', inline: + "sudo apt-get -q update + sudo apt-get -q -y install build-essential libncurses5-dev \ + git bzr cvs mercurial subversionI would also include libqt4-dev for xconfig,
Why? On windows there is not an X server to run the ssh x forwarding and the dependencies are really big ones. Nobody stops you to install them manually, it's an Ubuntu after all!
Quoted 3 lines
and the dependencies for the
manual and for the graphs: asciidoc, w3m, dblatex, graphviz, python, python-matplotlib.
Quoted 6 lines
Do you think we should force users to download a complete tex distribution only for compiling docs? As stated before users could install themselves if needed.
I prefer having a vagrant up setup time as small as possible to be operative as soon as possible!
Okay.
One more thing I would add though: the 32-bit compatibility libraries needed
for Sourcery toolchains. It's not that heavy and a bit tricky to find the right ones.
Regards,
Arnout
Quoted 32 lines
Quoted 2 lines
And rsync, is that included by default?
Yes, it's included in Ubuntu.
Sincerely, Angelo.
Quoted 22 lines
Regards,
Arnoutsupport/misc/Vagrantfile line 51
Quoted 8 lines
support/misc/Vagrantfile new file +7
-0+ sudo apt-get -q -y autoremove" + + config.vm.provision 'shell', privileged: false, inline: + "echo 'Downloading and extracting buildroot #{$buildroot_version}' + wget -q -c http://buildroot.org/downloads/buildroot-#{$buildroot_version}.tar.gz + tar axf buildroot-#{$buildroot_version}.tar.gz" +end--
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 support/misc: Adding Vagrant file for provisioning
Dear Arnout Vandecappelle,
2015-09-21 18:57 GMT+02:00 Arnout Vandecappelle <[email protected]>:
Quoted 91 lines · Angelo Compagnucci
Quoted 30 lines
Dear Arnout Vandecappelle,
2015-09-20 23:18 GMT+02:00 Arnout Vandecappelle <[email protected]>:
Quoted 17 lines · Angelo Compagnucci
Quoted 5 lines
This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms (Linux/Mac/Windows).
Signed-off-by Angelo Compagnucci <[email protected]>[snip]
Quoted 10 lines
support/misc/Vagrantfile new file +4
-0@@ -0,0 +1,51 @@ +################################################################################ +# +# Vagrantfile +#Quoted 8 lines
support/misc/Vagrantfile line 9
Quoted 5 lines
support/misc/Vagrantfile new file +5
-0+################################################################################ + +### Change here for more memory/cores ### +VM_MEMORY=1024 +VM_CORES=1Do we need to do that? And if we do, shouldn't it be higher? 1GB will not allow
you to build v8 and all its derivatives (webkit, webengine).Quoted 2 lines
Nope. Raising this numbers means freezing the machine of a user with a low end laptop.
Fair enough.
Quoted 13 lines
Probably we could add some notes on the documentation,
but Vagrant has it's own documentation and this is the standard de facto way to set memory/cores of a vagrant VM. This file should be a starting point for people wanting to try buildroot and not a one shop stop for all their problems.Quoted 6 lines
support/misc/Vagrantfile line 12
Quoted 3 lines
support/misc/Vagrantfile new file +3
-0+ +Vagrant.configure('2') do |config| + config.vm.box = 'ubuntu/trusty64'Is there a way to make it match the host, i.e. run a 32-bit system on a 32-bit
host?Quoted 3 lines
Honestly I don't think there are 32bit cpus which could run Buildroot compilation inside a VM. For me no problem here, all the cpus with virt instructions are 64bits and therefore could run a 64bit host.
It's not for 32-bit CPUs, it's for 64-bit hardware running 32-bit OS.
Though of course you're right, the VM can still run a 64-bit OS.
Quoted 24 lines
Quoted 21 lines
Quoted 7 lines
support/misc/Vagrantfile new file +6
-0+ config.vm.provider :vmware_fusion do |v, override| + v.vmx['memsize'] = VM_MEMORY + v.vmx['numvcpus'] = VM_CORES + end + + config.vm.provider :virtualbox do |v, override|support/misc/Vagrantfile line 29
Quoted 10 lines
support/misc/Vagrantfile new file +10
-0+ v.customize ['modifyvm', :id, '--memory', VM_MEMORY] + v.customize ['modifyvm', :id, '--cpus', VM_CORES] + end + + config.vm.provision 'shell' do |s| + s.inline = 'echo Setting up machine name' + + require 'open-uri' + open('http://git.buildroot.net/buildroot/plain/CHANGES') do |f| + $buildroot_version=f.read.lines.first.split(',')[0]That's not at all reliable, this version will for instance change to an rc just
before a release. And for instance the 2015.08.1 is not in master's CHANGES.Quoted 2 lines
I think it's better if we add a buildroot-latest.tar.bz2 symlink to the
downloads directory, then we can just use that.Quoted 7 lines
Of course! I falled back to this method cause I cannot find find a more reliable one.
Quoted 1 line
Failing that, it's better to scrape it from http://buildroot.org/download.html
It's really strange that there is not an easy way to get the builroot version string easily.
Well, the easy way would be
Quoted 8 lines
sed -n '/^export
BR2_VERSION:= /s///p'Makefilebut it's just a bad idea to take the latest git version as a basis of finding the 'current' version of buildroot.
You could also take the latest tag:
git tag -l | grep '^20[0-9][0-9]\.[0-9][0-9]\.[0-9.]*' | sort -n | tail -1
Both these options are not feasible cause I've not a git downloaded to search on before the vagrant up.
The only viable option could be scraping from website.
Quoted 3 lines
But overall, I think scraping from the website makes the most sense. Or even
better would be if the current version was recorded somewhere in a file that is used with SSI in downloads.html
I would try to scrape the website for current buildroot version.
Quoted 30 lines
Quoted 30 lines
Quoted 9 lines
Quoted 9 lines
support/misc/Vagrantfile new file +9
-0+ end + + config.vm.provider :vmware_fusion do |v, override| + v.vmx['displayname'] = "Buildroot #{$buildroot_version}" + end + + config.vm.provider :virtualbox do |v, override| + v.customize ['modifyvm', :id, '--name', "Buildroot #{$buildroot_version}"] + endQuoted 8 lines
support/misc/Vagrantfile line 44
Quoted 6 lines
support/misc/Vagrantfile new file +6
-0+ end + + config.vm.provision 'shell', inline: + "sudo apt-get -q update + sudo apt-get -q -y install build-essential libncurses5-dev \ + git bzr cvs mercurial subversionI would also include libqt4-dev for xconfig,
Why? On windows there is not an X server to run the ssh x forwarding and the dependencies are really big ones. Nobody stops you to install them manually, it's an Ubuntu after all!
Quoted 3 lines
and the dependencies for the
manual and for the graphs: asciidoc, w3m, dblatex, graphviz, python, python-matplotlib.Do you think we should force users to download a complete tex distribution only for compiling docs? As stated before users could install themselves if needed.
Quoted 8 lines
Quoted 2 lines
I prefer having a vagrant up setup time as small as possible to be operative as soon as possible!
Okay.
One more thing I would add though: the 32-bit compatibility libraries needed
for Sourcery toolchains. It's not that heavy and a bit tricky to find the right ones.
Nice catch!
Sincerely, Angelo
Quoted 46 lines
Regards,
ArnoutQuoted 32 lines
Quoted 2 lines
And rsync, is that included by default?
Yes, it's included in Ubuntu.
Sincerely, Angelo.
Quoted 22 lines
Regards,
Arnoutsupport/misc/Vagrantfile line 51
Quoted 8 lines
support/misc/Vagrantfile new file +7
-0+ sudo apt-get -q -y autoremove" + + config.vm.provision 'shell', privileged: false, inline: + "echo 'Downloading and extracting buildroot #{$buildroot_version}' + wget -q -c http://buildroot.org/downloads/buildroot-#{$buildroot_version}.tar.gz + tar axf buildroot-#{$buildroot_version}.tar.gz" +end--
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF--
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo