Date: Fri, 29 Mar 2002 20:43:43 -0800 (PST) From: "Bruce A. Mah" <bmah@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 8653 for review Message-ID: <200203300443.g2U4hhR20660@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://people.freebsd.org/~peter/p4db/chv.cgi?CH=8653 Change 8653 by bmah@bmah_intruder on 2002/03/29 20:43:14 Add testing guide section, as well as a few items for other sections. Wordsmith, fix typos. Affected files ... ... //depot/releng/5_dp1/src/release/doc/en_US.ISO8859-1/errata/article.sgml#5 edit Differences ... ==== //depot/releng/5_dp1/src/release/doc/en_US.ISO8859-1/errata/article.sgml#5 (text+ko) ==== @@ -46,11 +46,18 @@ <!-- XXX Change release.current to release.prev when there's --> <!-- XXX a release on this branch. --> - <para>This document lists known errata items for &os; + <para>This document lists known issues for &os; &release.current;. This information includes information relating to the software or documentation that could affect its - operation or usability. Please note that &os; &release.current; - is not an officially supported release of FreeBSD.</para> + operation or usability. Also included is a list of areas of the + base system that could benefit from some extra testing.</para> + + <para>Please note that &os; &release.current; + is not an officially supported release of FreeBSD. Unlike + supported releases, this errata file will not be updated. + Testers of &os; &release.current; should subscribe to the + &a.current; to stay informed about late-breaking issues and + developments.</para> </abstract> @@ -61,14 +68,14 @@ <listitem><para>Serial GDB is broken.</para></listitem> <listitem><para>LOMAC doesn't protect against a certain class of - inter-process activities such as signalling, since the MAC + inter-process activities such as signaling, since the MAC hooks those checks rely on aren't in the base tree yet.</para></listitem> <listitem><para><command>gcc -O</command> is known to be broken.</para></listitem> - <listitem><para>There are two different pccard implementations, + <listitem><para>There are two different PCCARD implementations, OLDCARD and NEWCARD. NEWCARD has support for Cardbus, but has PCCARD problems.</para></listitem> @@ -81,6 +88,11 @@ infrastructure is not merged; the documentation and library may be removed before 5.0 depending on strategy decisions not yet made.</para></listitem> + + <listitem><para>NFS client locking does not interact well with + &man.chroot.2; environments; locking only works for processes + sharing the same root as the locking daemon.</para></listitem> + </itemizedlist> </sect1> @@ -109,6 +121,12 @@ <listitem><para>UFS2 (essentially, UFS with extended attributes in inodes) is not yet ready for inclusion in the snapshot.</para></listitem> + <listitem> + <para><application>XFree86</application> 4.2.0 is not yet + integrated into &man.sysinstall.8;, although this is planned + to be finished for the next developer preview.</para> + </listitem> + </itemizedlist> </sect1> @@ -117,8 +135,12 @@ <itemizedlist> - <listitem><para>Kernels with debugging features enabled are very slow; this is a - natural product of the debugging code in these kernels. Those + <listitem><para>&os; &release.current; has a number of debugging + features enabled. These generally have a negative impact on + performance. One notable example is that the user-level + &man.malloc.3; functions behave, by default, as though the + <literal>AJ</literal> debugging flags were set. + Those benchmarking the system should be sure to run without debugging features enabled.</para></listitem> @@ -136,11 +158,14 @@ <filename>/boot/kernel</filename>.</para></listitem> <listitem><para>When upgrading a system, make sure to pay - attention to the <filename>pam.conf</filename> -> - <filename>pam.d</filename> change. Likewise, there has been a - <filename>libpam</filename> version bump as well as new PAM modules introduced: + attention to the change from an + <filename>/etc/pam.conf</filename> configure file to multiple files in + <filename>/etc/pam.d/</filename>. + Likewise, <application>OpenPAM</application> has replaced + <application>LinuxPAM</application>, + and new PAM modules have been introduced; this may result in warnings from older authentication-related - applications compiled under <literal>RELENG_4</literal>, such + applications compiled under <literal>RELENG_4</literal>, such as <application>xdm</application>, <application>kdm</application>, and <application>gdm</application>.</para></listitem> @@ -148,4 +173,54 @@ </sect1> + <sect1> + <title>Testing Guide</title> + + <para>While testing reports of all aspects of &os; + &release.current; are welcomed, there are several areas which + could benefit from some extra testing:</para> + + <itemizedlist> + <listitem> + <para>Basic kernel functionality. The changes for SMPng are + still in progress, and have some far-reaching effects + throughout many parts of the kernel. Testing the kernel's + stability on both UP and SMP machines will help find any + regressions that may have come about.</para> + </listitem> + <listitem> + <para>The PAM infrastructure has undergone significant + changes, including a replacement of <application>Linux + PAM</application> with + <application>OpenPAM</application>.</para> + </listitem> + <listitem> + <para>FFS snapshots and background &man.fsck.8;. The latter + feature is enabled by default; a reasonable test for + snapshots is to do backups by creating a snapshot using the + instructions in + <filename>src/sys/ufs/ffs/README.snapshot</filename> and + performing a &man.dump.8; of the snapshot.</para> + </listitem> + <listitem> + <para>Because of API changes, a number of ports in the &os; + Ports Collection are broken under &os; &release.branch;. + Frequently, there are straightforward fixes for these ports; + submitting these fixes will improve the state of buildable + ports and packages that can be shipped with &os; + &release.next;.</para> + </listitem> + <listitem> + <para>NFS has undergone some significant code reorganization, + although it is believed to be fairly stable. NFS client + locking is a new feature.</para> + </listitem> + <listitem> + <para>The sparc64 platform support is new, and could use + testing on a wider variety of hardware.</para> + </listitem> + </itemizedlist> + + </sect1> + </article> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-releng" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203300443.g2U4hhR20660>