From owner-freebsd-hackers Thu Jan 9 16:54:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA03117 for hackers-outgoing; Thu, 9 Jan 1997 16:54:38 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA03108 for ; Thu, 9 Jan 1997 16:54:34 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.4/8.7.3) with SMTP id QAA23680; Thu, 9 Jan 1997 16:54:07 -0800 (PST) Date: Thu, 9 Jan 1997 16:54:07 -0800 (PST) From: Jaye Mathisen To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: 2.2-BETA install report, minor problems. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Jan 1997, J Wunsch wrote: > > 2) The box I was installing on had BSD/OS installed on it. For whatever > > BSD/OS uses a totally `weird' bootstrap if used in dedicated mode > (withouth an fdisk table). This is something like our `dangerously > dedicated' mode, and BSDi should probably warn about its dangers as > well. You just felt it... I submit that if I'm selecting that FreeBSD use the entire disk, and I insiste that it use the entire disk this way, and "Yes, I don't want to be compatible with any type of OS co-existence", that then the exhibited behaviour is a bug. Maybe freebsd needs to zero the disklabel or something itself. I know Alpha's under Digital UNIX had a -z option to disklabel to zero it out. There should be a way to zero out the partition table as well. BSD/OS does warn about the dangers, but since I'm not co-existing, I'm replacing, then I think our stuff should be able to handle it.