From owner-freebsd-current Fri Aug 25 17:13:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id RAA10984 for current-outgoing; Fri, 25 Aug 1995 17:13:57 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id RAA10978 for ; Fri, 25 Aug 1995 17:13:56 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA13420; Fri, 25 Aug 95 18:15:36 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9508260015.AA13420@cs.weber.edu> Subject: Re: another 2.0.5 installation report To: freebsd-current@FreeBSD.org Date: Fri, 25 Aug 95 18:15:35 MDT In-Reply-To: <199508252317.BAA06388@uriah.heep.sax.de> from "J Wunsch" at Aug 26, 95 01:17:40 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > o the decision whether a file system is acceptable as a root fs should > be made based on the fdisk slot #, and not on the physical location > on the disk That's impossible. You must always consider a file system unacceptable as a root fs if it spans or exceeds BIOS cylinder 1023. This is because the BIOS must read the kernel, and to do that, the kernel's blocks must be located in an area of the disk addressable by BIOS. If you are willing to throw out the ROM firmware for booting on your PC and replaces it with something that uses absolute sector rather than C/H/S values, well then, the limit goes up to 2^32 512 blocks, or at-or-below the 2TB range. If you do replace the boot firmware, may I suggest you implement OpenFirmware or Motorolla's "BUG" firmware? 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.