From owner-freebsd-current Thu Jul 6 11: 6:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id EE2B837B875; Thu, 6 Jul 2000 11:06:07 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA264682; Thu, 6 Jul 2000 14:06:04 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 6 Jul 2000 14:07:01 -0400 To: John Galt From: Garance A Drosihn Subject: Re: subtle problem du jour.... Cc: Mike Smith , mjacob@feral.com, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:50 AM -0600 7/6/00, John Galt wrote: >Is there a quick and dirty way for the label editor to detect if >a BIOS is using LBA? This actually sounds like a setup in which >the error condition should be alerted on placing / on a cylinder >higher than 1024 rather than long after you can do anything about >it. The loader error might be a good extra, but the real place >the user should be notified of the error condition is upon creation. In theory I agree with you. In my specific case, I was trying to do something "clever" (ahem), and as such it's pretty much my own fault that the partition ended up past the 8-gig mark. The label editor would have had to have been mighty smart to realize what I was up to. So, based on the sample of what I myself was doing, I don't really think it's possible to detect this problem at creation time. A clearer message at boot time would have been appreciated, though. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message