From owner-freebsd-current  Tue May 25  3: 4:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 8316714BE1
	for <freebsd-current@FreeBSD.ORG>; Tue, 25 May 1999 03:04:40 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA13651;
	Tue, 25 May 1999 20:02:54 +1000
Date: Tue, 25 May 1999 20:02:54 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199905251002.UAA13651@godzilla.zeta.org.au>
To: mike@smith.net.au, starr3@gccs.com.au
Subject: Re: disk slices and MAKEDEV confusion
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> SO! Why does "sh MAKEDEV all" NOT make the partition entries for the
>> slice(s) ???
>> 
>> ie, "sh MAKEDEV all" only makes the "compatability" slice entries -- da0s1,
>> da0s2 etc.
>
>da0s1 is not a "compatibility slice" entry.  That would be da0a, etc.
>
>The problem is that if you made all of the nodes for all of the 
>supported slices, /dev would be incredibly bloated.  There are 8
>potential nodes per slice, and 20 potential slices per disk, plus the 
                                30
>compatability slice, so that's 168 node pairs (raw and buffered) 
                    plus the whole disk slice
                    times 2 for character devices
                                (8 * 31 + 1) * 2 = 498
>_per_disk_.

However, this should have been considered before changing the default
configuration from using the compatibility slice to using a real slice.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message