Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Oct 2012 15:09:34 +0000 (UTC)
From:      Eitan Adler <eadler@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r39865 - head/en_US.ISO8859-1/books/faq
Message-ID:  <201210301509.q9UF9YTI016839@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: eadler
Date: Tue Oct 30 15:09:34 2012
New Revision: 39865
URL: http://svn.freebsd.org/changeset/doc/39865

Log:
  These specific BIOS manufacturers are not known to have these problems
  recently; also 53C8xx is hardly popular anymore.
  
  Approved by:	bcr (mentor)

Modified:
  head/en_US.ISO8859-1/books/faq/book.xml

Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml	Tue Oct 30 15:09:31 2012	(r39864)
+++ head/en_US.ISO8859-1/books/faq/book.xml	Tue Oct 30 15:09:34 2012	(r39865)
@@ -4574,11 +4574,8 @@ kern.sched.name: ULE</screen>
 	    they are getting in contact with such a disk, or even worse,
 	    they might damage the BSD bootstrap without even asking or
 	    notifying you.  In addition, the <quote>dangerously
-	    dedicated</quote> disk's layout is known to confuse many
-	    BIOSes, including those from AWARD (e.g. as found in HP
-	    Netserver and Micronics systems as well as many others) and
-	    Symbios/NCR (for the popular 53C8xx range of SCSI
-	    controllers).  This is not a complete list, there are more.
+	    dedicated</quote> disk's layout is known to confuse some
+	    BIOSes.
 	    Symptoms of this confusion include the <errorname>read
 	    error</errorname> message printed by the &os; bootstrap when
 	    it cannot find itself, as well as system lockups when



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210301509.q9UF9YTI016839>