From owner-freebsd-hackers Wed Sep 27 07:46:32 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA02581 for hackers-outgoing; Wed, 27 Sep 1995 07:46:32 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA02573 ; Wed, 27 Sep 1995 07:46:22 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA17104; Wed, 27 Sep 1995 08:47:36 -0600 Date: Wed, 27 Sep 1995 08:47:36 -0600 From: Nate Williams Message-Id: <199509271447.IAA17104@rocky.sri.MT.net> To: Bruce Evans Cc: nate@rocky.sri.MT.net, roberto@keltia.freenix.fr, bde@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Diskslice naming convention? In-Reply-To: <199509270910.TAA14492@godzilla.zeta.org.au> References: <199509270910.TAA14492@godzilla.zeta.org.au> Sender: owner-hackers@FreeBSD.org Precedence: bulk Bruce Evans writes: > >> BTW - Are slices named 1-4 or 0-3? > > >1-4, 0 is the compatibility slice. > > There is no slice named 0. Slice _number_ 0 is the compatibility slice. > Slice _number_ 1 is the whole disk. The slices that are _numbered_ 2-31 > are _named_ 1-30. Whoa. I'm lost now w/regards to the compatability slice. How exactly is the compatability slice named, and how does it fit into the 'slice' paradigm? Nate