From owner-freebsd-hackers  Sat Jan  4 01:53:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA09292
          for hackers-outgoing; Sat, 4 Jan 1997 01:53:41 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA09283
          for <hackers@FreeBSD.ORG>; Sat, 4 Jan 1997 01:53:36 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA30811; Sat, 4 Jan 1997 20:48:31 +1100
Date: Sat, 4 Jan 1997 20:48:31 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701040948.UAA30811@godzilla.zeta.org.au>
To: dufault@hda.com, hackers@FreeBSD.ORG
Subject: Re: more than 32 disks?
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>A related question: are there issues (regarding booting, etc) with
>removing all partition/slice/ file system code from the different
>device drivers and having a single "dk" device that gets wired to
>the other block devices? Essentially have the base device be a
>trusting client of a dk device that handles all that stuff.

It makes things a little easier for the boot code.  I think the main
problems are that dk0 (sd0) gets would get renumbered to dk1 (sd0)
when wd0 is also installed :-), and if you fix this by wiring down
the drive numbers then you may lose uniformity by encoding the
driver names in the device names.

Bruce