From owner-p4-releng  Sun Oct 20 12:15:37 2002
Delivered-To: p4-releng@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 09B3937B404; Sun, 20 Oct 2002 12:15:36 -0700 (PDT)
Delivered-To: perforce@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AD4B037B401
	for <perforce@freebsd.org>; Sun, 20 Oct 2002 12:15:35 -0700 (PDT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4D35243E88
	for <perforce@freebsd.org>; Sun, 20 Oct 2002 12:15:35 -0700 (PDT)
	(envelope-from bmah@freebsd.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id g9KJFAmV071930
	for <perforce@freebsd.org>; Sun, 20 Oct 2002 12:15:10 -0700 (PDT)
	(envelope-from bmah@freebsd.org)
Received: (from perforce@localhost)
	by repoman.freebsd.org (8.12.6/8.12.6/Submit) id g9KJFA3T071914
	for perforce@freebsd.org; Sun, 20 Oct 2002 12:15:10 -0700 (PDT)
Date: Sun, 20 Oct 2002 12:15:10 -0700 (PDT)
Message-Id: <200210201915.g9KJFA3T071914@repoman.freebsd.org>
X-Authentication-Warning: repoman.freebsd.org: perforce set sender to bmah@freebsd.org using -f
From: "Bruce A. Mah" <bmah@FreeBSD.org>
Subject: PERFORCE change 19709 for review
To: Perforce Change Reviews <perforce@freebsd.org>
Sender: owner-p4-releng@FreeBSD.ORG
Precedence: bulk
List-ID: <p4-releng.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20p4-releng>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20p4-releng>
X-Loop: FreeBSD.ORG

http://perforce.freebsd.org/chv.cgi?CH=19709

Change 19709 by bmah@bmah_intruder on 2002/10/20 12:14:13

	Add a few more caveats about binary upgrades that I thought of
	while trying to test release builds.

Affected files ...

.. //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#3 edit

Differences ...

==== //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#3 (text+ko) ====

@@ -23,7 +23,7 @@
       <corpauthor>The FreeBSD Release Engineering Team</corpauthor>
     </authorgroup>
 
-    <pubdate>$P4: //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#2 $</pubdate>
+    <pubdate>$P4: //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#3 $</pubdate>
 
     <copyright>
       <year>2002</year>
@@ -300,6 +300,28 @@
         cross-major-version upgrades.  Using this feature is not
         recommended.</para>
 
+      <para>On the i386 and pc98 platforms, a UserConfig utility
+        exists on 4-STABLE to allow boot-time configuration of ISA
+        devices when booting from installation media.  Under FreeBSD
+        5.0, this functionality has been replaced in part by the
+        &man.device.hints.5; mechanism (it allows specifying the same
+        parameters, but is not interactive).</para>
+
+      <para>Floppy-based binary installations may require downloading
+        a third, new floppy image holding additional device drivers
+        in kernel modules.  This <filename>drivers.flp</filename>
+        floppy image will generally be found in the same location as
+        the usual <filename>kern.flp</filename> and
+        <filename>mfsroot.flp</filename> floppy images.</para>
+
+      <para>CDROM-based installations on the i386 architecture now use
+        a <quote>no-emulation</quote> boot loader.  This allows, among
+        other things, the use of a <literal>GENERIC</literal> kernel,
+        rather than the stripped-down kernel on the floppy images.  In
+        theory, any system capable of booting the Microsoft Windows NT
+        4 installation CDROMs should be able to cope with the FreeBSD
+        5.0 CDROMs.</para>
+
     </section>
 
     <section>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe p4-releng" in the body of the message