From owner-freebsd-current@FreeBSD.ORG Tue Nov 17 14:35:45 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 9279810656A3 for ; Tue, 17 Nov 2009 14:35:45 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 23DB88FC0C for ; Tue, 17 Nov 2009 14:35:44 +0000 (UTC) Received: from [10.29.62.2] (port=54762 helo=Aris-MacBook-Pro.local) by fish.ish.com.au with esmtpa (Exim 4.69) (envelope-from ) id 1NAPIM-0007Wu-1O for freebsd-current@freebsd.org; Wed, 18 Nov 2009 01:44:38 +1100 Message-ID: <4B02B4BB.30400@ish.com.au> Date: Wed, 18 Nov 2009 01:35:39 +1100 From: Aristedes Maniatis User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6pre) Gecko/20091108 Shredder/3.0pre MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4B023061.7070203@ish.com.au> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 14:35:45 -0000 On 17/11/09 9:14 PM, Ivan Voras wrote: > Aristedes Maniatis wrote: >> Is it possible that this flag be set to YES in the FreeBSD 8.0 branch >> before final release? > > Certainly not. The release is around the corner. In that case, there are some other options: 1. Build the binaries that freebsd-update uses with this flag set. That isn't the same thing as changing the flag in the ISOs of the official FreeBSD 8.0 release. 2. Build logic into freebsd-update which detects that the user has LOADER_ZFS_SUPPORT in src.conf, or else that it is trying to replace a working /boot/loader with a 'defective' version without ZFS capability. I had previously thought freebsd-update took hashes of all system files so it knew which ones had changed and what to warn the user about, but I must have misunderstood that. 3. Deprecate freebsd-update as the recommended way to upgrade FreeBSD systems and put source updates back to the top recommended choices. I've noticed that all recent release notices recommend freebsd-update. 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. I suggest there will be a fair few unhappy people when 8.0 is released and people using ZFS for system files upgrade from 7.x. Then when 8.1 whips around and people who followed instructions to boot from ZFS without a UFS partition, will suffer a second round of pain. Ari Maniatis -- --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A