Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!news.jsums.edu!despina.neptune.com!usenet.eel.ufl.edu!news.mathworks.com!fu-berlin.de!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: undoing dangerous dedication Date: 7 Dec 1995 21:36:22 GMT Organization: Private BSD site, Dresden Lines: 29 Message-ID: <4a7mom$jns@uriah.heep.sax.de> References: <49osqd$7ma@agate.berkeley.edu> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 mconst@soda.CSUA.Berkeley.EDU (Michael Constant) writes: > The "dangerously dedicated" option in the FreeBSD install isn't so > dangerous! [...] > > [...] I ran "fdisk /mbr" to > refresh my boot record, and now DOS works fine (well, inasmuch as DOS > works in the first place). This was about what i've been expecting (and we had to do just this also meanwhile, for a machine that has been running a Real Operating System just for a fair). The option is only ``dangerous'' for people who don't know about the impact, and that's why it hasn't been made the default. (Another reason is that i cannot overlook the impact on hypermodern EIDE crap^H^H^H^Hdisks with it's various crocks that attempt to work around BIOS design flaws, like ``disk managers''.) I would encourage all people who are going to install True FreeBSD Machines, preferably with SCSI disk, to use the ``dangerously'' dedicated option, however. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)