From owner-freebsd-stable Sat Sep 2 19: 7: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 0A1FB37B423 for ; Sat, 2 Sep 2000 19:07:05 -0700 (PDT) Received: from [24.217.6.97] (HELO dave) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 17878551; Sat, 02 Sep 2000 22:07:00 -0400 From: David Uhring To: , "Thomas Beauchamp" , , Subject: RE: 4.1-STABLE BOOT SLICE PROBLEM Date: Sat, 2 Sep 2000 20:49:55 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: , References: <000c01c01546$f334ed40$0101a8c0@noproblem.net> In-Reply-To: <000c01c01546$f334ed40$0101a8c0@noproblem.net> MIME-Version: 1.0 Message-Id: <00090221070200.18474@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 02 Sep 2000, Thomas Beauchamp wrote: > Hi! > > My understanding is: > > a 'slice', in FreeBSD lingo is a 'Microsoft's partition', of which you can > only have FOUR (past the MBR and partition table). > FreeBSD partitions exist on a Microsoft slice, and you can have up to 8 > FreeBSD partitions per slice. > So a 'dangerously dedicated disk', having nothing to do with Microsoft, has > essentially no slice, just partitions. Am I right? > > > But I find it confusing that FreeBSD uses the 's' of slice in its naming > terminology : '/dev/da0s1a' for instance, whilst other versions of BSD omit > the 'slice information' and would call the root file system '/dev/da0a' > instead. I understand that FreeBSD support this terminology too > ('compatibility slice naming'), but it's all confusing for me: when > Microsoft 'partitions' are not there AT ALL (as it is the case in a > 'dangerously dedicated disk'), why then use the term 'slice'? > > Thomas Beauchamp > New-B > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Chad R. Larson > Sent: 03 September 2000 01:57 > To: cjclark@alum.mit.edu > Cc: JDBitters@cs.com; freebsd-stable@FreeBSD.ORG > Subject: Re: 4.1-STABLE BOOT SLICE PROBLEM > > > As I recall, Crist J . Clark wrote: > > On Sat, Sep 02, 2000 at 09:02:04AM -0400, JDBitters@cs.com wrote: > >> Recently, I copied a 4.1-20000813-STABLE installation to a larger disk. > >> > >> I used /stand/sysinstall to create a "dangerously dedicated" disk and to > >> custom label it. Thereafter, I mounted the new slices... > > > > Huh? A dangerously dedicated disk has no slices. > > Sure it does. Up to 15 of them. What it doesn't have is > partitions. > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.net > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 See the Handbook, Section 2.4.2, where Microsoft "partitions" are discussed. Even though the BIOS - read Microsoft - partitions are limited to 4 primary partitions, BSD's and Solaris's "slice" tables do not reside in the MBR, but rather in the first sector of the partition on which BSD or Solaris resides. Partitions are configured with fdisk and slices are configured with disklabel. You should see what Linux 2.4.0-test7 reports as the geometry of my primary HD. Until I got rid of Solaris and used its space for FreeBSD and OpenBSD, I had 32 /dev/hda*. Yes, it is confusing that FreeBSD uses 's' to designate partitions. Get used to it. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message