From owner-freebsd-current Mon May 24 9:21:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles504.castles.com [208.214.165.68]) by hub.freebsd.org (Postfix) with ESMTP id 963EB1515D for ; Mon, 24 May 1999 09:21:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA22046; Mon, 24 May 1999 09:18:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905241618.JAA22046@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Harry Starr" Cc: "current" Subject: Re: disk slices and MAKEDEV confusion In-reply-to: Your message of "Sun, 23 May 1999 23:28:12 +1000." <006901bea520$1b41dbb0$0a9811cb@gccs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 May 1999 09:18:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am confused! > > The /boot/loader is "announcing" that it wants the root device to be > "da0s1a". > > It appears that the "normal" fstab entries want "sliced" versions as well, > eg. > # Device Mountpoint FStype Options Dump > Pass# > /dev/da0s1b none swap sw 0 0 > /dev/da0s1a / ufs rw 1 1 > > 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 compatability slice, so that's 168 node pairs (raw and buffered) _per_disk_. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message