From owner-freebsd-hackers Mon Jan 6 14:13:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03977 for hackers-outgoing; Mon, 6 Jan 1997 14:13:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03963 for ; Mon, 6 Jan 1997 14:13:29 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12726; Mon, 6 Jan 1997 15:03:52 -0700 From: Terry Lambert Message-Id: <199701062203.PAA12726@phaeton.artisoft.com> Subject: Re: more than 32 disks? To: dufault@hda.com (Peter Dufault) Date: Mon, 6 Jan 1997 15:03:52 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199701031410.JAA24455@hda.hda.com> from "Peter Dufault" at Jan 3, 97 09:10:43 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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. I have suggested a hierarchy of devices, based on device type, instance, and partitioning in the past. There is no inhernet reason (except unwarranted love of the past) that this could not be implemented. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.