From owner-freebsd-arch@FreeBSD.ORG  Tue May 10 14:47:37 2011
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 923B8106566C
	for <freebsd-arch@FreeBSD.org>; Tue, 10 May 2011 14:47:37 +0000 (UTC)
	(envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id C3F528FC19
	for <freebsd-arch@FreeBSD.org>; Tue, 10 May 2011 14:47:36 +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 RAA15494
	for <freebsd-arch@freebsd.org>; Tue, 10 May 2011 17:47:34 +0300 (EEST)
	(envelope-from avg@FreeBSD.org)
Message-ID: <4DC95006.1020404@FreeBSD.org>
Date: Tue, 10 May 2011 17:47:34 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: FreeBSD Arch <freebsd-arch@FreeBSD.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: 
Subject: arch-independent disks in sys/boot, libstand
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 14:47:37 -0000


I would like to ask for an advice about where/how to implement architecture
independent disk type(s) for sys/boot.  The types would be logical disks built on
top of physical architecture-specific disks/partitions.  Possible examples are:
ZFS pools, LVM volumes, etc.

-- 
Andriy Gapon