From owner-freebsd-fs@FreeBSD.ORG Tue Nov 24 11:50:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BF05106568D for ; Tue, 24 Nov 2009 11:50:49 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id 144D08FC19 for ; Tue, 24 Nov 2009 11:50:48 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id nAOBokvi067213; Tue, 24 Nov 2009 05:50:47 -0600 (CST) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=HttyUu2lSmOafSAs+F48jiataCVpuG4FuovuKsutjJMib6zw7PxpJUgRHVA8MPO0T VEbn2JkGStcRAANxfy6+bUZK/WW8reoJ1x9sU1kL6X5r5KZLWdyPnMXMdJJsgADvHW3 zmb0Zu+t/MW/n1LizK1o5oP7exbwu+YLb82EiRk= Message-ID: <4B0BC896.8030808@jrv.org> Date: Tue, 24 Nov 2009 05:50:46 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs Subject: Re: Current gptzfsboot limitations X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2009 11:50:49 -0000 I assume that *zfsboot requires that /boot and /boot/kernel be in the boot filesystem and not filesystems of their own. A man page probably ought to say this or someone will be tempted to "zfs create pool/boot/kernel" so they can roll back undesirable kernel installs.