From pepper@reppep.com Wed Nov 10 03:13:41 2004 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E92FB16A4CE; Wed, 10 Nov 2004 03:13:40 +0000 (GMT) Received: from www.reppep.com (www.reppep.com [66.92.104.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F9E143D4C; Wed, 10 Nov 2004 03:13:39 +0000 (GMT) (envelope-from pepper@reppep.com) Received: by www.reppep.com (Postfix, from userid 501) id 5EB97FE4C; Tue, 9 Nov 2004 22:13:38 -0500 (EST) Message-Id: <20041110031338.5EB97FE4C@www.reppep.com> Date: Tue, 9 Nov 2004 22:13:38 -0500 (EST) From: Chris Pepper Reply-To: Chris Pepper To: FreeBSD-gnats-submit@freebsd.org Cc: hrs@freebsd.org Subject: English clean-up for 5.3-RELEASE Errata X-Send-Pr-Version: 3.113 X-GNATS-Notify: >Number: 73756 >Category: docs >Synopsis: English clean-up for 5.3-RELEASE Errata >Confidential: no >Severity: non-critical >Priority: medium >Responsible: hrs >State: closed >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Nov 10 03:20:23 GMT 2004 >Closed-Date: Wed Nov 10 04:49:10 GMT 2004 >Last-Modified: Wed Nov 10 04:49:10 GMT 2004 >Originator: Chris Pepper >Release: FreeBSD 4.10-STABLE i386 >Organization: >Environment: System: FreeBSD www.reppep.com 4.10-STABLE FreeBSD 4.10-STABLE #16: Wed Jul 21 18:25:39 EDT 2004 root@www.reppep.com:/usr/obj/usr/src/sys/REPPEP i386 >Description: 5.3-RELEASE Errata (v1.69.2.7, visible on the website): English nits Lots of English clean-up, like s/drivers can become poor/drivers may beave poorly/ & s/re-insert a media/re-insert the media/ >How-To-Repeat: >Fix: Apply this patch: --- article.sgml.patch begins here --- --- article.sgml.1.69.2.7 Tue Nov 9 00:33:54 2004 +++ article.sgml.pepper Tue Nov 9 22:09:51 2004 @@ -99,35 +99,35 @@ Open Issues - (31 Oct 2004) Sometimes the performance of the &man.re.4; and &man.em.4; - drivers can become poor under heavy load. Especially, there are + (31 Oct 2004) The &man.re.4; and &man.em.4; + drivers may behave poorly under heavy load. In particular, there are reports of &man.em.4; on the IBM ThinkPad T40 locking up under such conditions. (31 Oct 2004) There are reports of the &man.sk.4; driver - locking up under heavy load, especially when on-board NICs - of ASUStek motherboards are used. To clear the condition, + locking up under heavy load, especially when ASUStek on-board NICs + are used. To clear the condition, bringing the interface down then back up and/or rebooting - the system are needed. + the system may be needed. (31 Oct 2004) The &man.burncd.8; utility is functional but may behave erratically on some systems. Reported symptoms include that &man.burncd.8; - can appear to hang up and never complete while the operation actually + can appear to hang and never complete while the operation actually does complete, and the progress indicator does not show the correct value. Workarounds include: - Eject and re-insert a media after burning a CD. + Eject and re-insert the media after burning a CD. Press Ctrl-C when &man.burncd.8; appears to hang up - in spite the access LED goes inactive. + while the access LED goes inactive. - (31 Oct 2004) When the user/group rule modificators in &man.pf.4; and &man.ipfw.4; + (31 Oct 2004) When the user/group rule clauses in &man.pf.4; and &man.ipfw.4; are used, the loader tunable debug.mpsafenet must be set to 0 (this is 1 by default). For example, the following rules are affected: @@ -149,28 +149,28 @@ More specifically, the group and user filter parameters in &man.pf.4;, and the gid, jail, and uid rule options - in &man.ipfw.4; are relevant. + in &man.ipfw.4; are affected. If debug.mpsafenet is set to 1, - the system can hang up when the rule is evaluated due to a lock order + the system can hang when the rule is evaluated due to a lock order reversal with the socket layer. More details can be found in the &man.ipfw.8; and &man.pf.conf.5; manual pages. (31 Oct 2004) The &man.vinum.4; subsystem - works fine on 5.3, but it can cause a system panic at boot time. + works on 5.3, but it can cause a system panic at boot time. As a workaround you can add vinum_load="YES" to /boot/loader.conf. - As an alternative you can also use the new, &man.geom.4;-based + As an alternative you can also use the new &man.geom.4;-based &man.vinum.4; subsystem. To activate the &man.geom.4;-aware vinum at boot time, add geom_vinum_load="YES" to /boot/loader.conf. - While some sort of uncommon configurations such as - multiple vinum drives in a disk are not supported, - it is basically backward compatible. - Note that for the &man.geom.4;-aware vinum the new userland - control program, gvinum should be used, - and it still lacks some functionality. + While some uncommon configurations, such as + multiple vinum drives on a disk, are not supported, + it is generally backward compatible. + Note that for the &man.geom.4;-aware vinum, its new userland + control program, gvinum, should be used, + and it is not yet feature-complete. (31 Oct 2004) The results of netstat -m can become incorrect on SMP systems when debug.mpsafenet @@ -182,7 +182,7 @@ For &os;/i386 and &os;/amd64, when installing &os; 5.3 using an USB keyboard the keyboard will stop working once the kernel boots, because a PS/2 keyboard is - always attached. As a workaround, select + always considered to be attached. As a workaround, select Escape to loader prompt in the boot loader menu and enter the following lines at the prompt: @@ -192,37 +192,36 @@ Note that if you use the boot floppies, this is set by default. - After the installation, add the following line into + After the installation, add the following line to /boot/loader.conf: hint.atkbd.0.flags="0x1" - (1 Nov 2004) The ULE scheduler described in the release note + (1 Nov 2004) The ULE scheduler described in the release notes has been completely disabled to discourage its use because it has - several stability problems. + stability problems. (1 Nov 2004) Programs linked with libpthread may not report any CPU usage statistics according to &man.top.1;, - while ones linked with libthr have + while those linked with libthr show the correct statistics. - (1 Nov 2004) When CMD649 or SiI0680 ATA controller is used, - the ATA RAID support of &man.ata.4; (ataraid) on 5.3 can corrupt - the existing RAID configuration which was created on 5.2 or prior. - The ATA RAID support for these controllers is non-functional - for this release. + (1 Nov 2004) ATA RAID support for the CMD649 and SiI0680 ATA + controllers is non-functional in this release. When such a + controller is brough up under &man.ata.4; (ataraid) on 5.3, the + RAID configuration stored under 5.2 or prior may be corrupted. - (3 Nov 2004) For &os;/i386 and &os;/amd64, the SMP support + (3 Nov 2004) For &os;/i386 and &os;/amd64, SMP support in the GENERIC kernel has been disabled by default because the SMP kernel can degrade the performance - on UP machines. A kernel configuration file SMP - which can be used to enable the SMP support has been added. - More details on building the custom kernel can be found in + on UP machines. A kernel configuration file SMP, + which can be used to enable SMP support, has been added. + More details on building the custom kernel can be found at . - (4 Nov 2004) The &man.tar.1; (also known as &man.bsdtar.1;) utility - does not detect the end of a recording medium such as a tape - and a floppy disk properly when it is specified in the + (4 Nov 2004) The &man.tar.1; utility (also known as &man.bsdtar.1;) + does not detect the end of media such as tape and + floppy disk properly when it is specified with the option. As an alternative &man.gtar.1; (GNU tar) can be used. --- article.sgml.patch ends here --- >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-doc->hrs Responsible-Changed-By: hrs Responsible-Changed-When: Wed Nov 10 04:20:57 GMT 2004 Responsible-Changed-Why: I'll handle this. http://www.freebsd.org/cgi/query-pr.cgi?pr=73756 State-Changed-From-To: open->closed State-Changed-By: hrs State-Changed-When: Wed Nov 10 04:48:48 GMT 2004 State-Changed-Why: Committed, thanks a lot! http://www.freebsd.org/cgi/query-pr.cgi?pr=73756 >Unformatted: