From owner-freebsd-current Sat Aug 26 23:22:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA09925 for current-outgoing; Sat, 26 Aug 1995 23:22:40 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA09907 for ; Sat, 26 Aug 1995 23:22:37 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA25907 for ; Sun, 27 Aug 1995 08:22:35 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA01613 for freebsd-current@FreeBSD.org; Sun, 27 Aug 1995 08:22:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id HAA21575 for freebsd-current@FreeBSD.org; Sun, 27 Aug 1995 07:51:07 +0200 From: J Wunsch Message-Id: <199508270551.HAA21575@uriah.heep.sax.de> Subject: Re: another 2.0.5 installation report To: freebsd-current@FreeBSD.org Date: Sun, 27 Aug 1995 07:51:07 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <9508262139.AA16296@cs.weber.edu> from "Terry Lambert" at Aug 26, 95 03:39:29 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1781 Sender: current-owner@FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > > It's an IDE translation, btw. > > I guess the question here is "how is FreeBSD supposed to know the BIOS > translation being used so that it can enforce the right behaviour". The > answer is "it can't unless it does it's own I/O via the BIOS instead of > a protected mode driver -- it can only guess". No, it does this part totally right. The only translation happens inside the disk, any geometry data as seen outside the disk are consistent (BIOS, Linux, FreeBSD, nonexistent DOS). The notebook is several years old, it does not have any mystics here. Terry, this is _not_ a geometry problem... > I don't recognize the term "compatability slice". I assume you mean Yeah, that's your (and sysinstall's) problem. > that it newfs'ed the DOS slice or something? The above linear search > and disklabel timestamp would mostly fix this case, though you would > potentially be screwed on a reinstall. It refers to the `shortcut' device names: sliced name for the root device: wd0s2a sliced name for my intented swap: wd0s3b compat name: wd0a (no compat name for swap available, it's not on the compat slice) The first slice with ID 0xa5 becomes the `compat slice', and our current boot code can only load from there (so the root file system will always be mounted from the compat slice). Sysinstall apparently knows this and wants to tell me that i could not place my root file system on wd0s3a (since there has been a FreeBSD wd0s2 slice). Anyway, it got its decision wrong, it did it based on the order of the tracks on the disk, instead of the order in the fdisk slots. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)