It is not urgent at all. Thank you.
On Wednesday, June 8, 2016 at 12:57:16 PM UTC-5, LinuxDan wrote:
>
> Depending how time critical this is, I would be willing to help you whip
> up an appropriate box.
> Can it hold until the weekend ?
>
> Dan White | d_e_...@icloud.com
>
Depending how time critical this is, I would be willing to help you whip up an
appropriate box.
Can it hold until the weekend ?
Dan White | d_e_wh...@icloud.com
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
The reason for testing is due to breaking package dependency changes that
appeared in v6.8, creating the need to test on as virgin a copy of CentOS
v6.8 as I could find. The resulting image from upgrading v6.6 to v6.8 is
somewhat different.
Thanks for pointing me to the packer repo.
On
Simple to update the VM (just did it)
The obvious : yum -y update
The not-so-obvious: VirtualBox uses kernel modules that need updating
http://www.virtualbox.org/manual/ch02.html#externalkernelmodules
and
http://ulyssesonline.com/2011/08/30/fix-virtualbox-after-kernel-upgrade/
and
Ben,
I think https://github.com/puppetlabs/puppetlabs-packer is what you are
looking for.
HTH
On Wed, Jun 8, 2016 at 9:54 AM, Ben West wrote:
> I was hoping to test out CentOS v6.8, but the Puppetlabs Vagrant images
> published only go up to v6.6:
>
I was hoping to test out CentOS v6.8, but the Puppetlabs Vagrant images
published only go up to v6.6:
https://atlas.hashicorp.com/puppetlabs
Is there a repo, or other such info somewhere, providing details about how
these images are rolled? I.e. so I could create my own CentOS v6.8 image
to