Date: Thu, 9 Jan 1997 19:05:44 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: mrcpu@cdsnet.net (Jaye Mathisen) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.org Subject: Re: 2.2-BETA install report, minor problems. Message-ID: <199701100205.TAA19116@phaeton.artisoft.com> In-Reply-To: <Pine.NEB.3.95.970109165119.11087K-100000@mail.cdsnet.net> from "Jaye Mathisen" at Jan 9, 97 04:54:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. The question is not whether we can handle it. The question is whether the Copmaq DeskPro/E can handle it, since its POST code bootstrap checks the boot sector for "validity" (in the DOS'est sense of the word). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701100205.TAA19116>