From owner-freebsd-stable@FreeBSD.ORG Fri Jan 21 13:05:07 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C4411065672 for ; Fri, 21 Jan 2011 13:05:07 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 540C28FC1C for ; Fri, 21 Jan 2011 13:05:07 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PgGfp-0000O9-L4 for freebsd-stable@freebsd.org; Fri, 21 Jan 2011 14:05:05 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Jan 2011 14:05:05 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Jan 2011 14:05:05 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Fri, 21 Jan 2011 14:03:38 +0100 Lines: 5 Message-ID: References: <57200BF94E69E54880C9BB1AF714BBCBDD3043@w2003s01.double-l.local> <57200BF94E69E54880C9BB1AF714BBCBDD3056@w2003s01.double-l.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCBDD3056@w2003s01.double-l.local> X-Enigmail-Version: 1.1.2 Subject: Re: Gpart and gmirror 8.2 from 18 januari X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2011 13:05:07 -0000 On 21/01/2011 13:56, Johan Hendriks wrote: > Ok the funny thing is, i get the same error on 8.1 Release (the corrupt error), but it boots, and all seems to work. Maybe the boot process was made to be more standard-compliant :)