From owner-freebsd-advocacy@FreeBSD.ORG Fri Aug 6 04:31:10 2004 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E43C16A4CE for ; Fri, 6 Aug 2004 04:31:10 +0000 (GMT) Received: from smtp804.mail.sc5.yahoo.com (smtp804.mail.sc5.yahoo.com [66.163.168.183]) by mx1.FreeBSD.org (Postfix) with SMTP id 509DF43D1D for ; Fri, 6 Aug 2004 04:31:10 +0000 (GMT) (envelope-from dr2867@pacbell.net) Received: from unknown (HELO ?192.168.0.248?) (dr2867@pacbell.net@68.126.219.146 with plain) by smtp804.mail.sc5.yahoo.com with SMTP; 6 Aug 2004 04:31:10 -0000 Message-ID: <41130993.20104@pacbell.net> Date: Thu, 05 Aug 2004 21:31:15 -0700 From: Daniel Rudy Organization: SBC Internet Services User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 4.10-RELEASE-p2; en-US; rv:1.7.1) Gecko/20040707 MultiZilla/1.6.2.0c X-Accept-Language: en-us, en, ja MIME-Version: 1.0 To: freebsd-advocacy@freebsd.org References: <4111FE83.9090602@pacbell.net> <20040805202556.GA1712@momo.buza.adamsfamily.xx> In-Reply-To: <20040805202556.GA1712@momo.buza.adamsfamily.xx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Now here's something for FreeBSD advocacy X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dr2867@pacbell.net List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2004 04:31:10 -0000 At about the time of 08/05/2004 13:25, Szilveszter Adam stated the following: > Hello Daniel, > > On Thu, Aug 05, 2004 at 02:31:47AM -0700, Daniel Rudy wrote: > >>FreeBSD does it again. > > > <...> > > Not to ruin your joy over a working hw setup, but in fact pretty much > all decent PC OSs these days (the list is long, but does *not* include > any version of DOS, for example) can do what FreeBSD did in this case > just fine. The BIOS is no longer used by the OS to access the disk, but > the BIOS needs to recognize the drive at least in part in order to be > able to boot the OS from it (obviously). So, the lesson to take home > here is this: unless you want to boot from a disk, you pretty much do > not have to worry about the BIOS these days using eg FreeBSD. This does > not include broken BIOS implementations, that actually crash and refuse > to boot with an overly large drive even if the type is set to NONE. (I > have seen such thing unfortunately) Luckily, there is almost always a > last BIOS update even for older boards from sometime around 1999 because > of the Y2K madness, and these usually include support for larger drives > as well. > This wasn't the boot drive. The 80GB HD is for data storage only. It's mounted as /space. The boot drive is a 13.6GB drive. I have the lastest BIOS from the manufacturer and it does not support harddisks beyond 32GB even though the hardware supports the max of 137GB. If I had to, I have a Promise Ultra133TX or something or another that FreeBSD does recongize if setting the BIOS to none didn't work. >>Kudos to the FreeBSD development teams. > > > Indeed. -- Daniel Rudy