Date: Sun, 09 Dec 2001 21:39:05 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "David W. Chapman Jr." <dwcjr@inethouston.net> Cc: current@freebsd.org Subject: Re: "Dangerously dedicated" yet again (was: cvs commit: src/sys/kern subr_diskmbr.c) Message-ID: <3C144A79.D63EB257@mindspring.com> References: <44735.1007899299@verdi.nethelp.no> <XFMail.20011209225258.doconnor@gsoft.com.au> <20011210105025.H83634@monorchid.lemis.com> <3C142200.1746FFA2@mindspring.com> <20011210051454.GA49775@leviathan.inethouston.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"David W. Chapman Jr." wrote: > On Sun, Dec 09, 2001 at 06:46:24PM -0800, Terry Lambert wrote: > > It's because you have to reinstall, should you want to add a second > > OS at a later date (e.g. Linux, or Windows). > > I think it has more to do with the drive going on a new motherboard > that might not boot with dangerously dedicated than the above. The concept of "dangerously dedicated" significantly predates BIOS being unable to boot such drives, either because of "antivirus" checks, or because of automatic fictitious geometry determination by Adaptec or NCR (now Symbios) controllers, which end up getting "divide by zero" errors when parsing the fictitious partition table that the FreeBSD "dangerously dedicate" mode includes in its boot block. In fact, I remember installing 386BSD "dangerously dedicated" on an AT&T WGS 386 ESDI drive, back in 1992. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C144A79.D63EB257>