From owner-freebsd-hackers Wed Jul 12 01:08:32 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA24946 for hackers-outgoing; Wed, 12 Jul 1995 01:08:32 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA24934 for ; Wed, 12 Jul 1995 01:08:28 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id BAA17549 for freebsd-hackers@freebsd.org; Wed, 12 Jul 1995 01:08:29 -0700 From: "Rodney W. Grimes" Message-Id: <199507120808.BAA17549@gndrsh.aac.dev.com> Subject: Re: A problem with disklabel & "use entire disk" on 2.0.5R. To: freebsd-hackers@freebsd.org Date: Wed, 12 Jul 1995 01:08:29 -0700 (PDT) In-Reply-To: <199507120604.IAA09165@uriah.heep.sax.de> from "J Wunsch" at Jul 12, 95 08:04:27 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2064 Sender: hackers-owner@freebsd.org Precedence: bulk > > As Thomas David Rivers wrote: > > > > > > Well - the real story is that the installation assumed I didn't want > > the BIOS translated geometry (as translated by the Adaptec 1542B) - and > > I went through the entire install using the SCSI geometry... only to > > find the system wouldn't boot. > > > > I *had* to use the translated geometry to get anything to boot. > > This comes up over and over again. In Usenet. In private mails/talks > i'm getting. I'm not very happy that the slice code broke *many* > systems that used to run before with their dedicated disks. IMHO, we > should have an option to disable the slice code in case somebody > wishes to use a disk dedicated to FreeBSD (perhaps even a non-bootable > disk, so the BIOS braindeadness is in no way a valid reason). There > are many people like me that have "mental" problems with lying about > their disk geometry too much (i.e., forcing a gratuitous number like > 63/31/...) when they know it (at least, partially) better, and the > disk is never to see anything else than (Free)BSD in this life. Be carefull with doing that, DOS 6.22 install is not very friendly about partition tables that are incorrect and will kindly fdisk/format your FreeBSD right into oblivia with 2 taps of enter after booting the install disk :-(. I've been having fun today with DOS and Netware and boy has Microsloft ever messed up what was once a reasonably simple install. It is so braindamaged now and likes to go do things for you with out asking if that is okay that I would like to throw a few more stones at this place 200 miles due north of me in Washington. It politly partitioned and formated my D: drive for me while installing DOS to C: :-( Please, valid and correct partition tables are _critical_ to making sure Microslop code does not wipe you out!!! I think I'll down grade to DOS 5.0, at least that install had a clue :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD