From owner-freebsd-current Wed May 10 15:58:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA08316 for current-outgoing; Wed, 10 May 1995 15:58:38 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA08310 for ; Wed, 10 May 1995 15:58:38 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA26509; Wed, 10 May 1995 15:58:30 -0700 From: Poul-Henning Kamp Message-Id: <199505102258.PAA26509@ref.tfs.com> Subject: Re: problem with new biosboot? To: mark@linus.demon.co.uk (Mark Valentine) Date: Wed, 10 May 1995 15:58:30 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505102240.XAA00336@linus.demon.co.uk> from "Mark Valentine" at May 10, 95 11:40:37 pm Content-Type: text Content-Length: 1042 Sender: current-owner@FreeBSD.org Precedence: bulk > > Modified: sys/i386/boot/biosboot disk.c > > Log: > > Make disk.c smart enough to handle disk with "OnTrack Disk manager". > > Make it complain if people try to boot from a partition which extends > > past 1024 cylinders. This is better than a random reset... > > Since these boot blocks now tell me that my "partition is out of reach from > the bios", I guess I'd better try to understand what might be wrong with my > slice/partition configuration. However, I can't follow the code... The rule is simple: For the boot-bloks to work, no sector needed to read the kernel must be past cylinder 1023, because we use the bios to read in the kernel. This is uncheckable, and undeterministic, so the check is: the filesystem from which the kernel is read, must have no blocks past cylider 1023. Partition 2 is the entire slice, always. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'