From owner-freebsd-current@FreeBSD.ORG Fri Jan 16 06:05:17 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E569DBF1; Fri, 16 Jan 2015 06:05:17 +0000 (UTC) Received: from dyslexicfish.net (dyslexicfish.net [91.109.5.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85EFCC6C; Fri, 16 Jan 2015 06:05:17 +0000 (UTC) Received: from dyslexicfish.net (dyslexicfish.net [91.109.5.35]) by dyslexicfish.net (8.14.5/8.14.5) with ESMTP id t0G658OV014007; Fri, 16 Jan 2015 06:05:08 GMT (envelope-from jamie@dyslexicfish.net) Received: (from jamie@localhost) by dyslexicfish.net (8.14.5/8.14.5/Submit) id t0G6581D014006; Fri, 16 Jan 2015 06:05:08 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201501160605.t0G6581D014006@dyslexicfish.net> Date: Fri, 16 Jan 2015 06:05:07 +0000 To: lev@freebsd.org, decke@bluelife.at Subject: Re: DigitalOcean offers VMs with FreeBSD! References: <54B7A494.50205@FreeBSD.org> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: emulation@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 06:05:18 -0000 Bernhard Fröhlich wrote: > 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. I use http://www.vultr.com/ for FreeBSD - their packages are similarly or better priced than DO. With Vultr, you can run their automated install, (which in itself just automates a typical FreeBSD install - there are no OS hacks) or just install off an ISO etc. I don't know what's unusual with the DO virtualisation, but vultr just works like a normal server (though they do restrict to virtio devices where applicable rather than emulated harware) You can even install a windows ISO (as long as you've sideloaded virtio drivers onto the install disk), or with FreeBSD, "it just works" Cheers, Jamie