From owner-freebsd-current@FreeBSD.ORG Tue Nov 17 15:47: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 E1DFB106566B for ; Tue, 17 Nov 2009 15:47:10 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9C8A68FC1A for ; Tue, 17 Nov 2009 15:47:10 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NAQGp-0006FJ-1N for freebsd-current@freebsd.org; Tue, 17 Nov 2009 16:47:07 +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 ; Tue, 17 Nov 2009 16:47:07 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Nov 2009 16:47:07 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 17 Nov 2009 16:46:37 +0100 Lines: 25 Message-ID: References: <4B023061.7070203@ish.com.au> <4B02B4BB.30400@ish.com.au> <4B02BDBE.6050307@quip.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.23 (X11/20090928) In-Reply-To: <4B02BDBE.6050307@quip.cz> Sender: news 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:47:11 -0000 Miroslav Lachman wrote: > > > 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. Are you sure it still doesn't do that? I think I saw a recent patch that leaves kernel.old somewhere...