From owner-freebsd-arch@FreeBSD.ORG Mon Sep 20 13:18:21 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1951D1065672 for ; Mon, 20 Sep 2010 13:18:21 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFD38FC23 for ; Mon, 20 Sep 2010 13:18:20 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA11757; Mon, 20 Sep 2010 15:59:20 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C975AA8.1040106@icyb.net.ua> Date: Mon, 20 Sep 2010 15:59:20 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100909 Lightning/1.0b2 Thunderbird/3.1.3 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20100917234542.GE1902@garage.freebsd.pl> <16411667@ipt.ru> <20100920124707.GB2410@garage.freebsd.pl> In-Reply-To: <20100920124707.GB2410@garage.freebsd.pl> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: Boris Samorodov , freebsd-arch@freebsd.org, freebsd-current@freebsd.org, krad Subject: Re: gptboot rewrite, bootonce, etc. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 13:18:21 -0000 on 20/09/2010 15:47 Pawel Jakub Dawidek said the following: > No, it doesn't. ZFS works a bit differently. ZFS operate on pools, not > really on partitions. One ZFS file system can span multiple > disks/partitions. I'm not yet sure how to implement it, so it is > intuitive, but I also haven't spend much time thinking about it. We > needed UFS and that is what I implemented. It took me much more time > than I expected anyway:) Maybe reserve some area inside zfs boot2 and put relevant information there. Similarly to how boot0cfg modifies data within boot0. The information could include "nextboot-pool" and "nextboot-fs". -- Andriy Gapon