From owner-freebsd-questions@FreeBSD.ORG Mon Nov 19 11:18:32 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 812DFD72 for ; Mon, 19 Nov 2012 11:18:32 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id 3BB0F8FC08 for ; Mon, 19 Nov 2012 11:18:31 +0000 (UTC) Received: from r56.edvax.de (port-92-195-8-72.dynamic.qsc.de [92.195.8.72]) by mx01.qsc.de (Postfix) with ESMTP id 3A7FF3CC34 for ; Mon, 19 Nov 2012 12:18:31 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id qAJBIWhC002791 for ; Mon, 19 Nov 2012 12:18:32 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Mon, 19 Nov 2012 12:18:32 +0100 From: Polytropon To: freebsd-questions@freebsd.org Subject: Re: Anybody use the Dell 3010?? Message-Id: <20121119121832.de248106.freebsd@edvax.de> In-Reply-To: <20121119060029.76b85120@scorpio> References: <20121118085838.GA7267@ethic.thought.org> <50AA00BA.1040007@bnrlabs.com> <20121119114306.ff21baa9.freebsd@edvax.de> <20121119060029.76b85120@scorpio> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 11:18:32 -0000 On Mon, 19 Nov 2012 06:00:29 -0500, Jerry wrote: > On Mon, 19 Nov 2012 11:43:06 +0100 > Polytropon articulated: > > > Allow me to provide just one example: > > > > More in the series of bizarre UEFI bugs > > http://mjg59.dreamwidth.org/20187.html > > That doesn't appear to be a bug. It appears that the code is doing > exactly what the designer wanted it to do. At best this was an > oversight by the designer; at worse just plain incompetence. That's quite possible. We've seen poorly implemented ACPI behaviour in "modern" BIOS as well, or manufacturers intendedly going "their way" to limit hardware in what it can do or what it will support. It's just my fear that UEFI won't do better per se, and that lazy or incompetent people will screw it up, and make it worse. The article mentions "legacy boot" to restore a somewhat "normal" behaviour... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...