From owner-freebsd-hackers Wed Aug 30 14:07:51 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA01267 for hackers-outgoing; Wed, 30 Aug 1995 14:07:51 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA01259 for ; Wed, 30 Aug 1995 14:07:43 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA19197; Wed, 30 Aug 1995 14:04:43 -0700 From: Terry Lambert Message-Id: <199508302104.OAA19197@phaeton.artisoft.com> Subject: Re: /etc/disktab and stuff To: bde@zeta.org.au (Bruce Evans) Date: Wed, 30 Aug 1995 14:04:43 -0700 (MST) Cc: hackers@FreeBSD.ORG, jdl@chrome.onramp.net In-Reply-To: <199508301951.FAA19689@godzilla.zeta.org.au> from "Bruce Evans" at Aug 31, 95 05:51:22 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1308 Sender: hackers-owner@FreeBSD.ORG Precedence: bulk > >Does it make sense to attempt to collect people's /etc/disktab entries > >and make them more available in the (next) released /etc/disktab? > > No. You would need a hundred entries for each of a few hundred disks > to get a reasonable coverage. No; it would be best to have calculated defaults with minimum values for partitions built into the disklabel program instead. The options of: 1) Device considered a single slice 2) Device considered multiple slices (has label) and exports slices as multiple pseudo type #1 devices. 3) Device considered as boot device with multiple slices (has label and boot code) and exports slices as multiple pseudo type #1 devices. 4) Device considered as DOS partitioned device. Eaxp DOS partition or extended partition exported as #1, #2, or #3, above (has DOS parititon table and boot sector -- PReP and OpenFirmware's so-called "DOS compatability area"). Should all be built into the tools and detectable via the drive contents themselves rather than needing a /etc/disktab. This would require coding defaults for slice vs. label vs. boot+label base on device name/attributes (what was the major # prior to devfs). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.