freebsd-vagrant
freebsd-vagrant copied to clipboard
xironix
FreeBSD 9.1 UFS and ZFS on root Vagrant boxes
s3 links don't work. google cloud storage links not up? is this project dead?
When I add a FreeBSD ZFS box vagrant spits out an error message that the box can't be untared. ``` $ vagrant box add FreeBSD-ZFS https://s3.amazonaws.com/vagrant_boxen/freebsd_amd64_zfs.box [vagrant] Downloading with Vagrant::Downloaders::HTTP......
My cpu activity pegs for about 10 seconds after the waiting for boot message shows up, indicating it is indeed booting up. But vagrant never moves on to the next...
Please, add instructions how to use your boxes for Vagrant newbies. It seems the following is required: ``` mkdir randomname cd randomname vagrant init xironix-freebsd-9.1-amd64-ufs https://s3.amazonaws.com/vagrant_boxen/freebsd_amd64_ufs.box vagrant up ```
The exports line you provided in the readme is only applicable for linux based systems. OSX does not provide those options in their NFS daemon. A valid exports entry looks...
First, ruby gives a syntax error in the vagrantfile itself:  Ruby version: ``` ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin11.0] ``` Then, when running vagrant up anyway, I receive: ```...
This is likely because I failed to include `nfs_client_enable="YES"` in `/etc/rc.conf`.
The following ports will be added: - `shells/bash-completion` as per #7 - `devel/doxygen` - `graphics/graphviz` The following changes will be made: - `nfs_client_enable="YES"` to `/etc/rc.conf` as per #6 - `function...
After a fresh install of the FreeBSD box I get a: ``` [tcp] 10.0.2.2:/SOURCE/DIR: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out ``` Any ideas why this is? How...
By automatically detecting the number of CPUs in `/etc/make.conf` with `MAKE_JOBS_NUMBER= $(sysctl -a | grep hw.ncpu | awk '{print $2"*2"}' | bc)` causes any port that uses cmake to fail....