Date: Wed, 22 Nov 2000 22:08:48 -0700 (MST) From: Fred Clift <fclift@verio.net> To: John Baldwin <jhb@FreeBSD.ORG> Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, roelof@eboa.com, stable@FreeBSD.ORG, Cy.Schubert@uumail.gov.bc.ca, bfoz@glue.umd.edu, imp@village.org Subject: Re: Dangerously Dedicated Message-ID: <Pine.BSF.4.21.0011222206570.1193-100000@vespa.orem.iserver.com> In-Reply-To: <XFMail.001120125602.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> and you don't have problems with the geometry of the drive and the MBR being > out of sync. Our bogus MBR in boot1 that is used by dangerously dedicated mode > breaks this though, resulting in machines whose BIOS get a divide by zero fault > when they try to read from the disk. Another thing that can be fixed with 30 seconds of fdisk. It seems that MOST of the problems with incompatability that people experience lately (ie with 'new' hardware) are due to the bogus, but easily fixable values in boot1 that get put on the mbr. Does anyone have hardware that cant run in dedicated mode, which has had a valid fdisk table put in it? I'm sure there is some box out there like it but I bet they are very uncommon, and getting less common. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011222206570.1193-100000>