From owner-freebsd-current@FreeBSD.ORG Tue Nov 17 15:14:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A31A106566C for ; Tue, 17 Nov 2009 15:14:10 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 43DB48FC1D for ; Tue, 17 Nov 2009 15:14:10 +0000 (UTC) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id EEA7919E027; Tue, 17 Nov 2009 16:14:08 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 93D8319E023; Tue, 17 Nov 2009 16:14:06 +0100 (CET) Message-ID: <4B02BDBE.6050307@quip.cz> Date: Tue, 17 Nov 2009 16:14:06 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 MIME-Version: 1.0 To: Aristedes Maniatis References: <4B023061.7070203@ish.com.au> <4B02B4BB.30400@ish.com.au> In-Reply-To: <4B02B4BB.30400@ish.com.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: request: LOADER_ZFS_SUPPORT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 17 Nov 2009 15:14:10 -0000 Aristedes Maniatis wrote: > On 17/11/09 9:14 PM, Ivan Voras wrote: [...] > Possibly freebsd-update should be maintained as part of the release > process and not by someone at arm's length to the re team. In recent > times it has broken rebooting after an update twice: once because of the > above issue, and earlier when updating from 7.2 to 8.0-beta it was > impossible to install a new kernel, reboot and then install world. This > wasn't a freebsd-update specific issue (there is an incompatibility > between new ZFS kernel modules and old userland tools), but it will bite > everyone using freebsd-update and ZFS. If we are talking about freebsd-update... It would be nice if freebsd-update leave old kernel available in /boot/ as with source upgrade (/boot/kernel.old) at least until second reboot (in case of upgrade), because if new kernel failed to boot after first reboot, then the machine become unbootable without some kind of LiveFS media. [...] Miroslav Lachman