[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: How to make a FreeBSD vm in virtualbox.
From:       Garrett Cooper <yaneurabeya () gmail ! com>
Date:       2014-12-31 19:26:05
Message-ID: A7587A80-B226-4DB4-B999-B317F09D8416 () gmail ! com
[Download RAW message or body]

On Dec 31, 2014, at 11:06, Alfred Perlstein <alfred@freebsd.org> wrote:

> On 12/31/14 11:03 AM, Garrett Cooper wrote:
> > On Dec 31, 2014, at 10:57, Alfred Perlstein <alfred@freebsd.org> wrote:
> > 
> > > On 12/31/14 10:40 AM, Garrett Cooper wrote:
> > > > On Dec 31, 2014, at 10:12, Adrian Chadd <adrian@freebsd.org> wrote:
> > > > 
> > > > > I'm confused by this discussion.
> > > > > 
> > > > > The basic image generation doesn't need to use any third-party tools.
> > > > > 
> > > > > We can always have a transformation step /after/ those images are
> > > > > generated that uses third party tools to generate other images. Much
> > > > > like Alfred's shell script.
> > > > > 
> > > > > I know it sucks, but unless someone wants to write BSD versions of all
> > > > > of those configuration pieces, we're going to be stuck using external
> > > > > tools to do things. And those things will get eyeballs.
> > > > 
> > > > It’s really unfortunate that the VMware option requires linux compat (at \
> > > > least) in order to work: 
> > > > https://my.vmware.com/web/vmware/details?productId=352&downloadGroup=OVFTOOL350
> > > >  
> > > > Is there anyone who’s been working with VMware directly to add FreeBSD \
> > > > support? If so, I think that opensourcing this tool (or at least having a \
> > > > binary) would potentially be the best win of all in the short-term. 
> > > > Thanks!
> > > > 
> > > 
> > > https://my.vmware.com/web/vmware/details?productId=353&downloadGroup=OVFTOOL350_OSS
> > > 
> > 
> > That works too! Now all we need to do is make that into a port...
> > 
> 
> Actually we need to figure out how that file is actually the google-url library \
> instead.... wat... 
> ~/tmp % tar xzvf ../ovftools-3.0.1-and-3.5.0-OSS.tar.gz
> x google-url-r147/
> x google-url-r147/LICENSE.txt
> x google-url-r147/third_party/
> x google-url-r147/third_party/icu/
> x google-url-r147/third_party/icu/build/
> x google-url-r147/third_party/icu/build/using_icu.vsprops
> x google-url-r147/README.txt
> x google-url-r147/src/
> x google-url-r147/src/url_parse_file.cc
> ...
> 
> I'll ping some folks over there and see what's up.

Probably VMware disclosing their modifications to source code as well as what they \
statically compile into the tool *shrugs*.

If I need to I’ll try some internal channels; it’s just a few hops to get to the \
VMware folks for folks on Benno’s team because we don’t work in the same geographical \
area as the folks do in SC.

Thanks!


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUpE3NAAoJEMZr5QU6S73emu8H/Rx/1yaFpQbvY01dGaRa84Up
z/chVIxrGmrtIabHWEcSZeMa+Lryc8wH077guYjxFk1q2tMyqHx+ur2mTuIeEGQo
r5b4Prma4zc4/zxBdlv8lEXEs32Ema4FPckxll7gqxjWzoO4IkYJ21OVEX0l90mH
oodcTufUP4E6zUvMxbKbtpaEm6w9mgPRjjcTWov5E8fIZnqIEqqy3NxAkdSg7n16
9H44GaWtiJiTZJ+jKZlgYMj3vmsOBFXFk8RG0OnUJjPKpr45UtqLqkQjCThJtzvm
V/V7vuOFM2rdPhyGFub++AHIEsMe/NlNaCzLDl9+v4wW0WsauaQgH+t/evlzpw4=
=tavd
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread]