From owner-freebsd-hackers Sat Mar 23 11:46:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA06633 for hackers-outgoing; Sat, 23 Mar 1996 11:46:10 -0800 (PST) Received: from kachina.jetcafe.org (kachina.jetcafe.org [206.117.70.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA06628 for ; Sat, 23 Mar 1996 11:46:09 -0800 (PST) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.6.10/8.6.6) with SMTP id LAA12669; Sat, 23 Mar 1996 11:44:44 -0800 Message-Id: <199603231944.LAA12669@kachina.jetcafe.org> To: J Wunsch cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: Adding a damn 2nd disk Date: Sat, 23 Mar 1996 11:44:39 -0800 From: Dave Hayes Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: >Andreas was wrong here. Fdisk needs the geometry the BIOS is using -- >not the geometry the disk claims to be. (The latter is largely >irrelevant, that's why it's hidden by default. Anyways, it cannot be >expressed in plain C/H/S for any modern disk.) Given the nature of the dissention about what this geometry really means, isn't there a sufficiently powerful abstraction one can use to represent the information that fdisk and disklabel need...one that covers all drives? If you have that, writing any user inferface is MUCH easier. ------ >>> Dave Hayes - Altadena CA, USA - dave@jetcafe.org <<< If you have built castles in the air, your work need not be lost; that is where they should be. Now put the foundations under them. -Henry David Thoreau