Date: Thu, 15 Jan 2015 19:40:06 +0100 From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= <decke@bluelife.at> To: lev@freebsd.org Cc: "freebsd-emulation@freebsd.org" <emulation@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: DigitalOcean offers VMs with FreeBSD! Message-ID: <CAE-m3X3Gy=dzT7nHfDnZ53oOKQda3NAihXd7OZdFT3x%2Bo%2Bmnrg@mail.gmail.com> In-Reply-To: <54B7A494.50205@FreeBSD.org> References: <54B7A494.50205@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 15, 2015 at 12:29 PM, Lev Serebryakov <lev@freebsd.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > https://www.digitalocean.com/company/blog/presenting-freebsd-how-we-made-it-happen/ > > I didn't see this news on mailing lists :) I had a quick look at it and the result is quite poor considering the time it took them to get it done. They had to install quite a few packages (perl, python27, libX11, avahi ...) and modified the stock FreeBSD image quite a bit. At startup they send an arping otherwise you do not even have network access in their network. This looks all a bit hackish and error prone. I am really wondering how long it will take that a regular update breaks their scripts and let's you back with a non accessible box. -- Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X3Gy=dzT7nHfDnZ53oOKQda3NAihXd7OZdFT3x%2Bo%2Bmnrg>