From owner-p4-projects@FreeBSD.ORG Mon Jan 5 23:47:45 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 5E7371065674; Mon, 5 Jan 2009 23:47:45 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 018581065672 for ; Mon, 5 Jan 2009 23:47:45 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id E1C8D8FC14 for ; Mon, 5 Jan 2009 23:47:44 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n05Nli6S019770 for ; Mon, 5 Jan 2009 23:47:44 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n05NliTs019768 for perforce@freebsd.org; Mon, 5 Jan 2009 23:47:44 GMT (envelope-from rene@FreeBSD.org) Date: Mon, 5 Jan 2009 23:47:44 GMT Message-Id: <200901052347.n05NliTs019768@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Cc: Subject: PERFORCE change 155689 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 23:47:46 -0000 http://perforce.freebsd.org/chv.cgi?CH=155689 Change 155689 by rene@rene_self on 2009/01/05 23:47:43 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#13 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/introduction/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/share/sgml/trademarks.ent#2 integrate .. //depot/projects/docproj_nl/www/en/cgi/man.cgi#7 integrate .. //depot/projects/docproj_nl/www/en/releases/7.1R/errata.html#3 integrate .. //depot/projects/docproj_nl/www/en/security/security.sgml#4 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#13 (text+ko) ==== @@ -12,7 +12,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1104 2008/12/24 10:32:40 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1106 2009/01/05 15:44:57 remko Exp $ 1995 @@ -29,6 +29,7 @@ 2006 2007 2008 + 2009 The &os; Documentation Project ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#13 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -21,7 +21,7 @@ - How to set up IEEE 802.11 and &bluetooth; devices. + How to set up &ieee; 802.11 and &bluetooth; devices. @@ -700,7 +700,7 @@ Wireless Networking Basics - Most wireless networks are based on the IEEE 802.11 + Most wireless networks are based on the &ieee; 802.11 standards. A basic wireless network consists of multiple stations communicating with radios that broadcast in either the 2.4GHz or 5GHz band (though this varies according to the @@ -720,7 +720,7 @@ network. 802.11 networks were first deployed in the 2.4GHz band - using protocols defined by the IEEE 802.11 and 802.11b + using protocols defined by the &ieee; 802.11 and 802.11b standard. These specifications include the operating frequencies, MAC layer characteristics including framing and transmission rates (communication can be done at various @@ -740,7 +740,7 @@ to communicate. This scheme was shown to be easily broken and is now rarely used except to discourage transient users from joining networks. Current security practice is given by the - IEEE 802.11i specification that defines new cryptographic + &ieee; 802.11i specification that defines new cryptographic ciphers and an additional protocol to authenticate stations to an access point and exchange keys for doing data communication. Further, cryptographic keys are periodically @@ -1378,7 +1378,7 @@ - Here, we use RSN (IEEE 802.11i) protocol, i.e., + Here, we use RSN (&ieee; 802.11i) protocol, i.e., WPA2. @@ -3216,7 +3216,7 @@ - failover + Failover Sends and receives traffic only through the master port. If the @@ -3226,15 +3226,15 @@ - fec + &cisco; Fast ðerchannel; - Supports Cisco EtherChannel. This is a static setup and does not + &cisco; Fast ðerchannel; (FEC), is a static setup and does not negotiate aggregation with the peer or exchange frames to monitor the - link, if the switch supports LACP then that should be used + link. If the switch supports LACP then that should be used instead. - Balances outgoing traffic across the active ports based on hashed + FEC balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port. The hash includes the Ethernet source and destination address, and, if available, the VLAN tag, and the IPv4/IPv6 source @@ -3242,20 +3242,20 @@ - lacp + LACP - Supports the IEEE 802.3ad Link Aggregation Control Protocol + The &ieee; 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol. LACP will negotiate a set of aggregable links with the peer in to one or more Link Aggregated - Groups. Each LAG is composed of ports of the same speed, set to + Groups (LAG). Each LAG is composed of ports of the same speed, set to full-duplex operation. The traffic will be balanced across the ports in the LAG with the greatest total speed, in most cases there will - only be one LAG which contains all ports. In the event of changes in + only be one LAG which contains all ports. In the event of changes in physical connectivity, Link Aggregation will quickly converge to a new configuration. - Balances outgoing traffic across the active ports based on hashed + LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port. The hash includes the Ethernet source and destination address, and, if available, the VLAN tag, and the IPv4/IPv6 source @@ -3263,19 +3263,19 @@ - loadbalance + Loadbalance - This is an alias of fec mode. + This is an alias of FEC mode. - roundrobin + Round-robin Distributes outgoing traffic using a round-robin scheduler through all active ports and accepts incoming traffic from any active - port. This mode will violate Ethernet frame ordering and should be + port. This mode violates Ethernet Frame ordering and should be used with caution. @@ -3286,7 +3286,7 @@ Examples - LACP aggregation with a Cisco switch + LACP aggregation with a &cisco; Switch This example connects two interfaces on a &os; machine to the switch as a single load balanced and fault tolerant link. More interfaces @@ -3297,23 +3297,31 @@ much information as it can to distinguish different traffic flows and balance across the available interfaces. - On the Cisco switch add the interfaces to the channel group. + On the &cisco; switch add the + FastEthernet0/1 and + FastEthernet0/2 interfaces to the + channel-group 1: - interface FastEthernet0/1 - channel-group 1 mode active - channel-protocol lacp + interface FastEthernet0/1 + channel-group 1 mode active + channel-protocol lacp ! -interface FastEthernet0/2 - channel-group 1 mode active - channel-protocol lacp -! +interface FastEthernet0/2 + channel-group 1 mode active + channel-protocol lacp - On the &os; machine create the lagg interface. + On the &os; machine create the &man.lagg.4; interface using + fxp0 and + fxp1: - &prompt.root; ifconfig lagg0 create -&prompt.root; ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1 + &prompt.root; ifconfig lagg0 create +&prompt.root; ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1 - View the interface status from ifconfig; ports marked as + View the interface status by running: + + &prompt.root; ifconfig lagg0 + + Ports marked as ACTIVE are part of the active aggregation group that has been negotiated with the remote switch and traffic will be transmitted and received. Use the verbose output of &man.ifconfig.8; @@ -3328,8 +3336,8 @@ laggport: fxp1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> laggport: fxp0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> - The switch will show which ports are active. For more detail use - show lacp neighbor detail. + To see the port status on the switch, use show + lacp neighbor: switch# show lacp neighbor Flags: S - Device is requesting Slow LACPDUs @@ -3345,17 +3353,27 @@ Fa0/1 SA 32768 0005.5d71.8db8 29s 0x146 0x3 0x3D Fa0/2 SA 32768 0005.5d71.8db8 29s 0x146 0x4 0x3D + For more detail use the show lacp neighbor + detail command. Failover mode - Failover mode can be used to switch over to another interface if - the link is lost on the master. + Failover mode can be used to switch over to a secondary interface if + the link is lost on the master interface. Create and configure the + lagg0 interface, with + fxp0 as the master interface and + fxp1 as the secondary interface: + + &prompt.root; ifconfig lagg0 create +&prompt.root; ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 - &prompt.root; ifconfig lagg0 create -&prompt.root; ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 + The interface will look something like this, the major + differences will be the MAC address and the + device names: - lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + &prompt.root; ifconfig lagg0 +lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8<VLAN_MTU> ether 00:05:5d:71:8d:b8 media: Ethernet autoselect @@ -3365,8 +3383,8 @@ laggport: fxp0 flags=5<MASTER,ACTIVE> Traffic will be transmitted and received on - fxp0. If the link is lost on - fxp0 then fxp1 will + fxp0. If the link is lost on + fxp0 then fxp1 will become the active link. If the link is restored on the master interface then it will once again become the active link. ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/introduction/chapter.sgml#14 (text+ko) ==== @@ -1,7 +1,7 @@ 3Com and HomeConnect are registered @@ -86,7 +86,9 @@ Cisco, Catalyst, and IOS are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries."> +Cisco"> Catalyst"> +EtherChannel"> IOS"> Corel and WordPerfect are trademarks @@ -151,6 +153,7 @@ IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and Electronics Engineers, Inc. in the United States."> +IEEE"> POSIX"> ==== //depot/projects/docproj_nl/www/en/cgi/man.cgi#7 (text+ko) ==== @@ -34,7 +34,7 @@ # Dual CGI/Plexus mode and new interface by sanders@bsdi.com 9/22/1995 # # $Id: man.cgi,v 1.172 2007/11/28 18:51:29 hrs Exp $ -# $FreeBSD: www/en/cgi/man.cgi,v 1.226 2008/12/21 23:04:17 wosch Exp $ +# $FreeBSD: www/en/cgi/man.cgi,v 1.227 2009/01/05 20:46:44 hrs Exp $ ############################################################################ # !!! man.cgi is stale perl4 code !!! @@ -159,19 +159,22 @@ ); $manLocalDir = '/usr/local/www/bsddoc/man'; -$manPathDefault = 'FreeBSD 7.0-RELEASE'; +$manPathDefault = 'FreeBSD 7.1-RELEASE'; %manPath = ( - 'FreeBSD 7.0-RELEASE and Ports', + 'FreeBSD 7.1-RELEASE and Ports', "$manLocalDir/FreeBSD-7.0-RELEASE/man:$manLocalDir/FreeBSD-7.0-RELEASE/openssl/man:$manLocalDir/FreeBSD-ports", 'FreeBSD 6.4-RELEASE and Ports', "$manLocalDir/FreeBSD-6.4-RELEASE/man:$manLocalDir/FreeBSD-6.4-RELEASE/openssl/man:$manLocalDir/FreeBSD-ports", 'FreeBSD 8-current', "$manLocalDir/FreeBSD-8-current/man:$manLocalDir/FreeBSD-8-current/openssl/man", - 'FreeBSD 7.0-stable', "$manLocalDir/FreeBSD-7.0-stable", - 'FreeBSD 7.0-RELEASE', -"$manLocalDir/FreeBSD-7.0-RELEASE/man:$manLocalDir/FreeBSD-7.0-RELEASE/openssl/man", + + 'FreeBSD 7.1-stable', "$manLocalDir/FreeBSD-7.1-stable", + 'FreeBSD 7.1-RELEASE', "$manLocalDir/FreeBSD-7.1-RELEASE/man:$manLocalDir/FreeBSD-7.1-RELEASE/openssl/man", + 'FreeBSD Ports 7.1-RELEASE', "$manLocalDir/FreeBSD-ports-7.1-RELEASE", + + 'FreeBSD 7.0-RELEASE', "$manLocalDir/FreeBSD-7.0-RELEASE/man:$manLocalDir/FreeBSD-7.0-RELEASE/openssl/man", 'FreeBSD Ports 7.0-RELEASE', "$manLocalDir/FreeBSD-ports-7.0-RELEASE", 'FreeBSD 6.4-stable', "$manLocalDir/FreeBSD-6.4-stable", @@ -461,15 +464,15 @@ # keywords must be in lower cases. %manPathAliases = ( - 'freebsd', 'FreeBSD 7.0-RELEASE', - 'freebsd-release', 'FreeBSD 7.0-RELEASE', + 'freebsd', 'FreeBSD 7.1-RELEASE', + 'freebsd-release', 'FreeBSD 7.1-RELEASE', - 'freebsd-stable', 'FreeBSD 7.0-stable', - 'freebsd-stable7', 'FreeBSD 7.0-stable', + 'freebsd-stable', 'FreeBSD 7.1-stable', + 'freebsd-stable7', 'FreeBSD 7.1-stable', 'freebsd-stable6', 'FreeBSD 6.4-stable', 'freebsd-current', 'FreeBSD 8-current', - 'freebsd-release-ports', 'FreeBSD 7.0-RELEASE and Ports', + 'freebsd-release-ports', 'FreeBSD 7.1-RELEASE and Ports', 'slackware', 'Linux Slackware 3.1', 'redhat', 'Red Hat Linux/i386 9', @@ -1375,7 +1378,7 @@ } local $id = - '$FreeBSD: www/en/cgi/man.cgi,v 1.226 2008/12/21 23:04:17 wosch Exp $'; + '$FreeBSD: www/en/cgi/man.cgi,v 1.227 2009/01/05 20:46:44 hrs Exp $'; return qq{\ 
 Copyright (c) 1996-2008 Wolfram Schneider

==== //depot/projects/docproj_nl/www/en/releases/7.1R/errata.html#3 (text+ko) ====

@@ -19,7 +19,7 @@
 
Copyright © 2008, 2009 The FreeBSD Documentation Project

 
 
$FreeBSD: stable/7/release/doc/en_US.ISO8859-1/errata/article.sgml
-186764 2009-01-05 08:56:45Z hrs $

+186782 2009-01-05 15:38:45Z hrs $

 

 
 

@@ -142,6 +142,15 @@
 
4 Late-Breaking News and
 Corrections

 
+
[20090105] The Release Notes for 7.1-RELEASE should have mentioned that the 
+procstat(1)
+utility has been added. This is a process inspection utility which provides both some of
+the missing functionality from 
+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 ae(4) driver has been

==== //depot/projects/docproj_nl/www/en/security/security.sgml#4 (text+ko) ====

@@ -1,12 +1,12 @@
 
-
+
 
 
  %developers;
 
 ]>
-
+
 
 
   &header;
@@ -208,10 +208,18 @@
     
Normal

     
Releases which are published from a -STABLE branch will be
       supported by the Security Officer for a minimum of 12 months after the
-      release.

+      release, and for sufficient additional time (if needed) to ensure
+      that there is a newer release for at least 3 months before the
+      older Normal relase expires.
+    
     
Extended

-    
Selected releases will be supported by the Security Officer for a
-      minimum of 24 months after the release.

+    
Selected releases (normally every second release plus the last
+      release from each -STABLE branch) will be supported by the
+      Security Officer for a minimum of 24 months after the release,
+      and for sufficient additional time (if needed) to ensure that
+      there is a newer Extended release for at least 3 months before the
+      older Extended release expires.
+    

   
 
   
@@ -269,7 +277,14 @@
       7.0-RELEASE
       Normal
       February 27, 2008
-      February 28, 2009
+      April 30, 2009
+    
+    
+      RELENG_7_1
+      7.1-RELEASE
+      Extended
+      January 4, 2009
+      January 31, 2011