Date: Fri, 22 Mar 2002 11:55:34 -0800 (PST) From: "Bruce A. Mah" <bmah@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 8212 for review Message-ID: <200203221955.g2MJtYS79976@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://people.freebsd.org/~peter/p4db/chv.cgi?CH=8212 Change 8212 by bmah@bmah_intruder on 2002/03/22 11:55:12 Whitespace. Affected files ... ... //depot/releng/5_dp1/src/release/doc/en_US.ISO8859-1/errata/article.sgml#4 edit Differences ... ==== //depot/releng/5_dp1/src/release/doc/en_US.ISO8859-1/errata/article.sgml#4 (text+ko) ==== @@ -61,26 +61,26 @@ <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 - hooks those checks rely on aren't in the base tree - yet.</para></listitem> + inter-process activities such as signalling, 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> + broken.</para></listitem> <listitem><para>There are two different pccard implementations, - OLDCARD and NEWCARD. NEWCARD has support for Cardbus, but has - PCCARD problems.</para></listitem> + OLDCARD and NEWCARD. NEWCARD has support for Cardbus, but has + PCCARD problems.</para></listitem> <listitem><para>Kernels may have to be built with - <literal>-DNO_WERROR=yes</literal> due to warning handling in the build - infrastructure.</para></listitem> + <literal>-DNO_WERROR=yes</literal> due to warning handling in the build + infrastructure.</para></listitem> <listitem><para>The system documentation indicates that there is - support for POSIX.1e capabilities, but the kernel - infrastructure is not merged; the documentation and library - may be removed before 5.0 depending on strategy decisions not - yet made.</para></listitem> + support for POSIX.1e capabilities, but the kernel + infrastructure is not merged; the documentation and library + may be removed before 5.0 depending on strategy decisions not + yet made.</para></listitem> </itemizedlist> </sect1> @@ -94,20 +94,20 @@ <itemizedlist> <listitem><para>The lock-pushdown for fine-grained kernel - threading is in-process, and not complete in this snapshot. - As a result, the full benefits are not yet - realized.</para></listitem> + threading is in-process, and not complete in this snapshot. + As a result, the full benefits are not yet + realized.</para></listitem> <listitem><para>Scheduler activation support exists only in the - kernel, not in the userland thread library, and in this - snapshot, threads from the same process using KSE can execute - on only one processor at a time.</para></listitem> + kernel, not in the userland thread library, and in this + snapshot, threads from the same process using KSE can execute + on only one processor at a time.</para></listitem> <listitem><para>Mandatory access control support from the - TrustedBSD branch is not yet merged.</para></listitem> + TrustedBSD branch is not yet merged.</para></listitem> <listitem><para>UFS2 (essentially, UFS with extended attributes in inodes) is not yet ready for inclusion in the - snapshot.</para></listitem> + snapshot.</para></listitem> </itemizedlist> </sect1> @@ -118,32 +118,32 @@ <itemizedlist> <listitem><para>Kernels with debugging features enabled are very slow; this is a - natural product of the debugging code in these kernels. Those - benchmarking the system should be sure to run without - debugging features enabled.</para></listitem> + natural product of the debugging code in these kernels. Those + benchmarking the system should be sure to run without + debugging features enabled.</para></listitem> <listitem><para>Interrupt latency is high due to on-going SMP - work, this will be fixed prior to the final release.</para></listitem> + work, this will be fixed prior to the final release.</para></listitem> <listitem><para>Tighter enforcement of <literal>#include</literal> file deprecation - results in a number of common applications failing to build. - In particular, if you <literal>#include <malloc.h></literal>, you now get a - <literal>#error</literal> instead of a <literal>#warning</literal>.</para></listitem> + results in a number of common applications failing to build. + In particular, if you <literal>#include <malloc.h></literal>, you now get a + <literal>#error</literal> instead of a <literal>#warning</literal>.</para></listitem> <listitem><para>The kernel is no longer installed as - <filename>/kernel</filename> and - <filename>/modules</filename>, these have moved to - <filename>/boot/kernel</filename>.</para></listitem> + <filename>/kernel</filename> and + <filename>/modules</filename>, these have moved to + <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: - this may result in warnings from older authentication-related - applications compiled under <literal>RELENG_4</literal>, such - <application>xdm</application>, - <application>kdm</application>, and - <application>gdm</application>.</para></listitem> + 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: + this may result in warnings from older authentication-related + applications compiled under <literal>RELENG_4</literal>, such + <application>xdm</application>, + <application>kdm</application>, and + <application>gdm</application>.</para></listitem> </itemizedlist> </sect1> 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?200203221955.g2MJtYS79976>