From owner-freebsd-virtualization@FreeBSD.ORG Fri Jan 24 10:53:20 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E79C96 for ; Fri, 24 Jan 2014 10:53:20 +0000 (UTC) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id D0016101D for ; Fri, 24 Jan 2014 10:53:19 +0000 (UTC) Received: (qmail 35034 invoked by uid 89); 24 Jan 2014 10:53:18 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.181.240) by mail.grem.de with ESMTPA; 24 Jan 2014 10:53:18 -0000 Date: Fri, 24 Jan 2014 11:53:17 +0100 From: Michael Gmelin To: Michael Dexter Subject: Re: Public Service Announcement: The name is "bhyve" Message-ID: <20140124115317.3b3b2258@bsd64.grem.de> In-Reply-To: <52E2446E.9090909@callfortesting.org> References: <52E23DDB.5040007@callfortesting.org> <20140124114143.3730a864@bsd64.grem.de> <52E2446E.9090909@callfortesting.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 10:53:20 -0000 On Fri, 24 Jan 2014 02:46:06 -0800 Michael Dexter wrote: > On 1/24/14 2:41 AM, Michael Gmelin wrote: > >> Haters gonna hate? > >> > > Lack of attention to detail != hate. > > I guess you didn't see the phoronix.com article on bhyve a few months > ago. :) They pulled the worst of it. > > The whole "BSD is dying" or "is poo" in their case FUD is still very > active in various circles and you never know. > Oh I've seen it and I usually ignore Phoronix and its comments for exactly this reason, but in this case serverwatch reported on the topic in a factual/neutral way and just got the details wrong. It doesn't seem like a high margin website to me, so they probably didn't spend much time on it ;) Recent bhyve progress is quite impressive by the way. -- Michael Gmelin