From dd2eb38ebc9c457e7888ae9e75ba952721f5b5a7 Mon Sep 17 00:00:00 2001 From: hrs Date: Sat, 25 Apr 2009 21:10:38 +0000 Subject: [PATCH] Trim errata document for 7.2. Approved by: re (implicit) git-svn-id: svn://svn.freebsd.org/base/releng/7.2@191495 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f --- .../doc/en_US.ISO8859-1/errata/article.sgml | 183 +----------------- 1 file changed, 2 insertions(+), 181 deletions(-) diff --git a/release/doc/en_US.ISO8859-1/errata/article.sgml b/release/doc/en_US.ISO8859-1/errata/article.sgml index f4b8d232..39e80baa 100644 --- a/release/doc/en_US.ISO8859-1/errata/article.sgml +++ b/release/doc/en_US.ISO8859-1/errata/article.sgml @@ -163,191 +163,12 @@ Open Issues - [20090105] As in the Announcement of 7.1-RELEASE, certain Intel NICs - will come up as &man.igb.4; instead of &man.em.4; in this - release. There are only 3 PCI ID's that should have - their name changed from &man.em.4; to &man.igb.4;: - - - - 0x10A78086 - - - - 0x10A98086 - - - - 0x10D68086 - - - - You should be able to determine if your card will - change names by running the following command: - - &prompt.user; pciconf -l -. . . -em0@pci0:0:25:0: class=0x020000 card=0x02381028 chip=0x10c08086 rev=0x02 hdr=0x00 - - and for the line representing your NIC (should be named - em on older systems, - e.g. em0 or em1, etc) - check the fourth column. If that says - chip=0x10a78086 (or one of the other two IDs - given above) you will have the adapter's name change. + Late-Breaking News and Corrections - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned that the &man.procstat.1; utility has been added. - This is a process inspection utility which provides both some of - the missing functionality from &man.procfs.5; and new - functionality for monitoring and debugging specific - processes. - - [20090105] The Release Notes for 7.1-RELEASE should have mentioned - changes that the &man.ae.4; driver has been added to provide support - for the Attansic/Atheros L2 FastEthernet controllers. - This driver is not enabled in GENERIC - kernels for this release. - - [20090105] The Release Notes for 7.1-RELEASE included the - following misdescriptions: - - - - In the entry of &man.linux.4; ABI support, - get_setaffinity() should have been - sched_setaffinity(). - - - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned changes that the &man.jme.4; driver has been added to - provide support for PCIe adapters based on JMicron JMC250 - gigabit Ethernet and JMC260 fast Ethernet controllers. - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned changes that the &man.age.4; driver has been added to - provide support for Attansic/Atheros L1 gigabit Ethernet - controller. - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned changes that the &man.malo.4; driver has been added to - provide support for Marvell Libertas 88W8335 based PCI network - adapters. - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned changes that the bm(4) driver has been added to - provide support for Apple Big Mac (BMAC) Ethernet controller, - found on various Apple G3 models. - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned changes that the et(4) driver has been added to - provide support for Agere ET1310 10/100/Gigabit Ethernet - controller. - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned changes that the &man.glxsb.4; driver has been added - to provide support for the Security Block in AMD Geode LX - processors. - - [20090105] The Release Notes for 7.1-RELEASE should have - mentioned that &os; now supports multiple routing tables. To - enable this, the following steps are needed: - - - - Add the following kernel configuration option and - rebuild the kernel. The 2 is the number - of FIB (Forward Information Base, synonym for a routing - table here). The maximum value is 16. - - options ROUTETABLES=2 - - The procedure for rebuilding the &os; kernel is - described in the &os; - Handbook. - - This number can be modified on boot time. To do so, add - the following to /boot/loader.conf and - reboot the system: - - net.fibs=6 - - - - Set a loader tunable net.my_fibnum if - needed. This means the default number of routing tables. - If not specified, 0 will be used. - - - - Set a loader tunable - net.add_addr_allfibs if needed. This - enables to add routes to all FIBs for new interfaces by - default. When this is set to 0, it will - only allocate routes on interface changes for the FIB of the - caller when adding a new set of addresses to an interface. - Note that this tunable is set to 1 by - default. - - - - To select one of the FIBs, the new &man.setfib.1; utility - can be used. This set an associated FIB with the process. For - example: - - &prompt.root; setfib -3 ping target.example.com - - The FIB #3 will be used for the &man.ping.8; command. - - The FIB which the packet will be associated with will be - determined in the following rules: - - - - All packets which have a FIB associated with them will - use the FIB. If not, FIB #0 will be used. - - - - A packet received on an interface for forwarding uses - FIB #0. - - - - A TCP listen socket associated with an FIB will generate - accept sockets which are associated with the same FIB. - - - - A packet generated in response to other packet uses the - FIB associated with the packet being responded to. - - - - A packet generated on tunnel interfaces such as - &man.gif.4; and &man.tun.4; will be encapsulated using the - FIB of the process which set up the tunnel. - - - - Routing messages will be associated with the process's - FIB. - - - - Also, the &man.ipfw.8; now supports an action rule - setfib. The following action: - - setfib fibnum - - will make the matched packet use the FIB specified in - fibnum. The rule processing - continues at the next rule. + -- 2.42.0