From owner-freebsd-hackers Fri Oct 18 00:51:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04193 for hackers-outgoing; Fri, 18 Oct 1996 00:51:53 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA04186 for ; Fri, 18 Oct 1996 00:51:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA10170; Fri, 18 Oct 1996 09:51:27 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA12297; Fri, 18 Oct 1996 09:51:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id JAA25986; Fri, 18 Oct 1996 09:34:44 +0200 (MET DST) From: J Wunsch Message-Id: <199610180734.JAA25986@uriah.heep.sax.de> Subject: Re: 2.2-961014-SNAP install problem To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 18 Oct 1996 09:34:44 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610171327.OAA29987@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Oct 17, 96 02:27:56 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] 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 As Christoph Kukulies wrote: > The partition editor barfed at my disk geometry and > decided to take 2050/64/32 instead of the > native geometry of 3925/10/107. Trying to enforce > the latter (G option) doesn't seem possible. The native geometry of any fairly modern disk is not expressable in plain C/H/S terms. If you're using SCSI disks, they are always translated: the SCSI protocol doesn't know the term `head', `cylinder', or `sector number' in order to address a block on some storage medium. All it knows about is a block number. We've been repeating this over and over again: the only geometry you should use is the same as your disk is known to the BIOS. If your disk is not used by the BIOS at all, you can pick whatever value you want, as long as the total number of blocks (C*H*S) on the medium is not higher than the medium capacity. In this case, the ``dangerously dedicated'' mode is the only mode where you can use all the blocks of the medium (which is normally larger than anything that could be expressed as a product C*H*S where all the elements are integer numbers). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)