Date: Mon, 20 Sep 2010 15:59:20 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Pawel Jakub Dawidek <pjd@freebsd.org> Cc: Boris Samorodov <bsam@ipt.ru>, freebsd-arch@freebsd.org, freebsd-current@freebsd.org, krad <kraduk@gmail.com> Subject: Re: gptboot rewrite, bootonce, etc. Message-ID: <4C975AA8.1040106@icyb.net.ua> In-Reply-To: <20100920124707.GB2410@garage.freebsd.pl> References: <20100917234542.GE1902@garage.freebsd.pl> <16411667@ipt.ru> <AANLkTi=giSyr6ZAeMrBs9k-o5iZ0CAgS7Ta4z0DXp5hX@mail.gmail.com> <20100920124707.GB2410@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C975AA8.1040106>