From owner-p4-projects@FreeBSD.ORG Mon Sep 6 17:34:36 2010 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 1AEAC10656D9; Mon, 6 Sep 2010 17:34:36 +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 D0E0810656AA for ; Mon, 6 Sep 2010 17:34:35 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id BD2608FC1F for ; Mon, 6 Sep 2010 17:34:35 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id o86HYZSV001730 for ; Mon, 6 Sep 2010 17:34:35 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id o86HYZhY001727 for perforce@freebsd.org; Mon, 6 Sep 2010 17:34:35 GMT (envelope-from rene@FreeBSD.org) Date: Mon, 6 Sep 2010 17:34:35 GMT Message-Id: <201009061734.o86HYZhY001727@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 183438 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 17:34:36 -0000 http://p4web.freebsd.org/@@183438?ac=10 Change 183438 by rene@rene_acer on 2010/09/06 17:34:15 IFC (resolve conflicts due to direct cvs commit) Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#69 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#50 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#24 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#15 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/jails/chapter.sgml#7 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#87 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#43 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/Makefile#16 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#49 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/config/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#36 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#26 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/disks/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/install/chapter.sgml#17 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/jails/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.sgml#35 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#30 integrate .. //depot/projects/docproj_nl/share/pgpkeys/dim.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/gjb.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#44 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#41 integrate .. //depot/projects/docproj_nl/share/pgpkeys/swills.key#1 branch .. //depot/projects/docproj_nl/share/sgml/mirrors.xml#21 integrate .. //depot/projects/docproj_nl/www/en/cgi/mirror.cgi#2 integrate .. //depot/projects/docproj_nl/www/en/cgi/url.cgi#2 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#41 integrate .. //depot/projects/docproj_nl/www/en/docproj/translations.sgml#9 integrate .. //depot/projects/docproj_nl/www/en/docs/webresources.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/internal/Makefile#3 integrate .. //depot/projects/docproj_nl/www/en/internal/internal.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/internal/photos.sgml#2 delete .. //depot/projects/docproj_nl/www/share/sgml/events.xml#31 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#88 integrate .. //depot/projects/docproj_nl/www/share/sgml/usergroups.xml#15 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#69 (text+ko) ==== @@ -1,4 +1,4 @@ - + + @@ -908,9 +908,9 @@ about the wireless device in the boot messages, like this: - ath0: <Atheros 5212> mem 0xff9f0000-0xff9fffff irq 17 at device 2.0 on pci2 -ath0: Ethernet address: 00:11:95:d5:43:62 -ath0: mac 7.9 phy 4.5 radio 5.6 + ath0: <Atheros 5212> mem 0x88000000-0x8800ffff irq 11 at device 0.0 on cardbus1 +ath0: [ITHREAD] +ath0: AR2413 mac 7.9 RF2413 phy 4.5 @@ -939,7 +939,7 @@ &prompt.root; ifconfig wlan0 create wlandev ath0 &prompt.root; ifconfig wlan0 up scan -SSID BSSID CHAN RATE S:N INT CAPS +SSID/MESH ID BSSID CHAN RATE S:N INT CAPS dlinkap 00:13:46:49:41:76 11 54M -90:96 100 EPS WPA WME freebsdap 00:11:95:c3:0d:ac 1 54M -83:96 100 EPS WPA @@ -1211,7 +1211,7 @@ point: wlans_ath0="wlan0" -ifconfig_wlan0="ssid your_ssid_here inet 192.168.1.100 netmask 255.255.255.0" +ifconfig_wlan0="inet 192.168.1.100 netmask 255.255.255.0 ssid your_ssid_here" @@ -1716,8 +1716,8 @@ ifconfig: &prompt.root; ifconfig wlan0 create wlandev ath0 -&prompt.root; ifconfig wlan0 ssid my_net wepmode on weptxkey 3 wepkey 3:0x3456789012 \ - inet 192.168.1.100 netmask 255.255.255.0 +&prompt.root; ifconfig wlan0 inet 192.168.1.100 netmask 255.255.255.0 \ + ssid my_net wepmode on weptxkey 3 wepkey 3:0x3456789012 @@ -1782,16 +1782,17 @@ On the box A: - &prompt.root; ifconfig wlan0 create wlandev ath0 -&prompt.root; ifconfig wlan0 ssid freebsdap mediaopt adhoc inet 192.168.0.1 netmask 255.255.255.0 + &prompt.root; ifconfig wlan0 create wlandev ath0 wlanmode adhoc +&prompt.root; ifconfig wlan0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap &prompt.root; ifconfig wlan0 - wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 + wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 00:11:95:c3:0d:ac inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 - media: IEEE 802.11 Wireless Ethernet autoselect <adhoc> (autoselect <adhoc>) - status: associated - ssid freebsdap channel 2 bssid 02:11:95:c3:0d:ac - authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100 + media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <adhoc> + status: running + ssid freebsdap channel 2 (2417 Mhz 11g) bssid 02:11:95:c3:0d:ac + country US ecm authmode OPEN privacy OFF txpower 21.5 scanvalid 60 + protmode CTS wme burst The adhoc parameter indicates the interface is running in the IBSS mode. @@ -1799,25 +1800,26 @@ On B, we should be able to detect A: - &prompt.root; ifconfig wlan0 up scan - SSID BSSID CHAN RATE S:N INT CAPS - freebsdap 02:11:95:c3:0d:ac 2 54M -90:-96 100 IS + &prompt.root; ifconfig wlan0 create wlandev ath0 wlanmode adhoc +&prompt.root; ifconfig wlan0 up scan + SSID/MESH ID BSSID CHAN RATE S:N INT CAPS + freebsdap 02:11:95:c3:0d:ac 2 54M -64:-96 100 IS WME The I in the output confirms the machine A is in ad-hoc mode. We just have to configure B with a different IP address: - &prompt.root; ifconfig wlan0 create wlandev ath0 -&prompt.root; ifconfig wlan0 ssid freebsdap mediaopt adhoc inet 192.168.0.2 netmask 255.255.255.0 + &prompt.root; ifconfig wlan0 inet 192.168.0.2 netmask 255.255.255.0 ssid freebsdap &prompt.root; ifconfig wlan0 - wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 + wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 00:11:95:d5:43:62 inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 - media: IEEE 802.11 Wireless Ethernet autoselect <adhoc> (autoselect <adhoc>) - status: associated - ssid freebsdap channel 2 bssid 02:11:95:c3:0d:ac - authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100 + media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <adhoc> + status: running + ssid freebsdap channel 2 (2417 Mhz 11g) bssid 02:11:95:c3:0d:ac + country US ecm authmode OPEN privacy OFF txpower 21.5 scanvalid 60 + protmode CTS wme burst Both A and B are now ready to exchange informations. @@ -1851,43 +1853,54 @@ check if your wireless device supports the host-based access point mode (also know as hostap mode): - &prompt.root; ifconfig ath0 list caps -ath0=783ed0f<WEP,TKIP,AES,AES_CCM,IBSS,HOSTAP,AHDEMO,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,TKIPMIC,WPA1,WPA2,BURST,WME> + &prompt.root; ifconfig wlan0 create wlandev ath0 +&prompt.root; ifconfig wlan0 list caps +drivercaps=6f85edc1<STA,FF,TURBOP,IBSS,HOSTAP,AHDEMO,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,MBSS,WPA1,WPA2,BURST,WME,WDS,BGSCAN,TXFRAG> +cryptocaps=1f<WEP,TKIP,AES,AES_CCM,TKIPMIC> This output displays the card capabilities; the HOSTAP word confirms this wireless card can act as an Access Point. Various supported ciphers are - also mentioned: WEP, TKIP, WPA2, etc., these informations + also mentioned: WEP, TKIP, AES, etc., these informations are important to know what security protocols could be set on the Access Point. - The wireless device can now be put into hostap mode and - configured with the correct SSID and IP address: + The wireless device can only be put into hostap mode + during the creation of the network pseudo-device, so a + previously created device must be destroyed first: + + &prompt.root; ifconfig wlan0 destroy + + then regenerated with the correct option before setting + the other parameters: - &prompt.root; ifconfig ath0 ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.255.255.0 + &prompt.root; ifconfig wlan0 create wlandev ath0 wlanmode hostap +&prompt.root; ifconfig wlan0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap mode 11g channel 1 Use again ifconfig to see the status - of the ath0 interface: + of the wlan0 interface: - &prompt.root; ifconfig ath0 - ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 + &prompt.root; ifconfig wlan0 + wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + ether 00:11:95:c3:0d:ac inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 - inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4 - ether 00:11:95:c3:0d:ac media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap> - status: associated - ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac - authmode OPEN privacy OFF txpowmax 38 bmiss 7 protmode CTS burst dtimperiod 1 bintval 100 + status: running + ssid freebsdap channel 1 (2412 Mhz 11g) bssid 00:11:95:c3:0d:ac + country US ecm authmode OPEN privacy OFF txpower 21.5 scanvalid 60 + protmode CTS wme burst dtimperiod 1 -dfs The hostap parameter indicates the interface is running in the host-based access point mode. The interface configuration can be done automatically at - boot time by adding the following line to + boot time by adding the following lines to /etc/rc.conf: - ifconfig_ath0="ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.255.255.0" + wlans_ath0="wlan0" +create_args_wlan0="wlanmode hostap" +ifconfig_wlan0="inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap mode 11g channel 1" @@ -1903,23 +1916,25 @@ possible from another wireless machine to initiate a scan to find the AP: - &prompt.root; ifconfig ath0 up scan -SSID BSSID CHAN RATE S:N INT CAPS -freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 ES + &prompt.root; ifconfig wlan0 create wlandev ath0 +&prompt.root; ifconfig wlan0 up scan +SSID/MESH ID BSSID CHAN RATE S:N INT CAPS +freebsdap 00:11:95:c3:0d:ac 1 54M -66:-96 100 ES WME The client machine found the Access Point and can be associated with it: - &prompt.root; ifconfig ath0 ssid freebsdap inet 192.168.0.2 netmask 255.255.255.0 -&prompt.root; ifconfig ath0 - ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 - inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1 + &prompt.root; ifconfig wlan0 inet 192.168.0.2 netmask 255.255.255.0 ssid freebsdap +&prompt.root; ifconfig wlan0 + wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + ether 00:11:95:d5:43:62 inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 - ether 00:11:95:d5:43:62 - media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) + media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated - ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac - authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100 + ssid freebsdap channel 1 (2412 Mhz 11g) bssid 00:11:95:c3:0d:ac + country US ecm authmode OPEN privacy OFF txpower 21.5 bmiss 7 + scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 + roam:rate 5 protmode CTS wme burst @@ -1957,7 +1972,7 @@ The configuration is done in the /etc/hostapd.conf file: - interface=ath0 + interface=wlan0 debug=1 ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel @@ -2041,8 +2056,8 @@ &prompt.root /etc/rc.d/hostapd forcestart - &prompt.root; ifconfig ath0 - ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2290 + &prompt.root; ifconfig wlan0 + wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2290 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4 ether 00:11:95:c3:0d:ac @@ -2055,7 +2070,7 @@ associated with it, see for more details. It is possible to see the stations associated with the AP using - the ifconfig ath0 list + the ifconfig wlan0 list sta command. @@ -2073,8 +2088,9 @@ The wireless device can now be put into hostap mode and configured with the correct SSID and IP address: - &prompt.root; ifconfig ath0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g mediaopt hostap \ - inet 192.168.0.1 netmask 255.255.255.0 + &prompt.root; ifconfig wlan0 create wlandev ath0 wlanmode hostap +&prompt.root; ifconfig wlan0 inet 192.168.0.1 netmask 255.255.255.0 \ + ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g @@ -2096,22 +2112,23 @@ Use again ifconfig to see the status - of the ath0 interface: + of the wlan0 interface: - &prompt.root; ifconfig ath0 - ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 + &prompt.root; ifconfig wlan0 + wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + ether 00:11:95:c3:0d:ac inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 - inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4 - ether 00:11:95:c3:0d:ac media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap> - status: associated - ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac - authmode OPEN privacy ON deftxkey 3 wepkey 3:40-bit txpowmax 36 protmode CTS dtimperiod 1 bintval 100 + status: running + ssid freebsdap channel 4 (2427 Mhz 11g) bssid 00:11:95:c3:0d:ac + country US ecm authmode OPEN privacy ON deftxkey 3 wepkey 3:40-bit + txpower 21.5 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs From another wireless machine, it is possible to initiate a scan to find the AP: - &prompt.root; ifconfig ath0 up scan + &prompt.root; ifconfig wlan0 create wlandev ath0 +&prompt.root; ifconfig wlan0 up scan SSID BSSID CHAN RATE S:N INT CAPS freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#11 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -828,16 +828,18 @@ dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38 000ff irq 15 at device 11.0 on pci0 +miibus0: <MII bus> on dc0 +bmtphy0: <BCM5201 10/100baseTX PHY> PHY 1 on miibus0 +bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:a0:cc:da:da:da -miibus0: <MII bus> on dc0 -ukphy0: <Generic IEEE 802.3u media interface> on miibus0 -ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto +dc0: [ITHREAD] dc1: <82c169 PNIC 10/100BaseTX> port 0x9800-0x98ff mem 0xd3000000-0xd30 000ff irq 11 at device 12.0 on pci0 +miibus1: <MII bus> on dc1 +bmtphy1: <BCM5201 10/100baseTX PHY> PHY 1 on miibus1 +bmtphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: Ethernet address: 00:a0:cc:da:da:db -miibus1: <MII bus> on dc1 -ukphy1: <Generic IEEE 802.3u media interface> on miibus1 -ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto +dc1: [ITHREAD] In this example, we see that two cards using the &man.dc.4; driver are present on the system. @@ -950,7 +952,7 @@ produce a kernel module in the current directory which can be loaded as follows: - &prompt.root; kldload ./W32DRIVER.ko + &prompt.root; kldload ./W32DRIVER_SYS.ko In addition to the generated kernel module, you must load the ndis.ko and @@ -983,12 +985,12 @@ You can configure the system to load the NDIS modules at boot time in the same way as with any other module. First, copy the generated module, - W32DRIVER.ko, to the W32DRIVER_SYS.ko, to the /boot/modules directory. Then, add the following line to /boot/loader.conf: - W32DRIVER_load="YES" + W32DRIVER_SYS_load="YES" @@ -1009,30 +1011,26 @@ your system, enter the following command: &prompt.user; ifconfig -dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 +dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + options=80008<VLAN_MTU,LINKSTATE> + ether 00:a0:cc:da:da:da inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 - ether 00:a0:cc:da:da:da media: Ethernet autoselect (100baseTX <full-duplex>) status: active -dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 +dc1: flags=8802<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 + options=80008<VLAN_MTU,LINKSTATE> + ether 00:a0:cc:da:da:db inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 - ether 00:a0:cc:da:da:db media: Ethernet 10baseT/UTP status: no carrier -lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 -lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 +plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500 +lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 + options=3<RXCSUM,TXCSUM> + inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 + inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 -tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 + nd6 options=3<PERFORMNUD,ACCEPT_RTADV> - - Old versions of &os; may require the - option following &man.ifconfig.8;, for more details about the - correct syntax of &man.ifconfig.8;, please refer to the manual - page. Note also that entries concerning IPv6 - (inet6 etc.) were omitted in this - example. - - In this example, the following devices were displayed: @@ -1048,18 +1046,14 @@ - lp0: The parallel port - interface + plip0: The parallel port + interface (if a parallel port is present on the + machine) lo0: The loopback device - - - tun0: The tunnel device used by - ppp - &os; uses the driver name followed by the order in @@ -1121,8 +1115,11 @@ If the &man.ifconfig.8; output had shown something similar to: -dc0: flags=8843<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 - ether 00:a0:cc:da:da:da +dc0: flags=8843<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 + options=80008<VLAN_MTU,LINKSTATE> + ether 00:a0:cc:da:da:da + media: Ethernet autoselect (100baseTX <full-duplex>) + status: active it would indicate the card has not been configured. @@ -1159,6 +1156,15 @@ addresses of various machines of the LAN, if they are not already there. For more information please refer to &man.hosts.5; and to /usr/share/examples/etc/hosts. + + + If access to the Internet is planned with the + machine, you also have to manually set up the default + gateway and the nameserver: + + &prompt.root; echo 'defaultrouter="your_default_router"' >> /etc/rc.conf +&prompt.root; echo 'nameserver your_DNS_server' >> /etc/resolv.conf + @@ -1168,9 +1174,20 @@ /etc/rc.conf, you should reboot your system. This will allow the change(s) to the interface(s) to be applied, and verify that the system restarts without any - configuration errors. + configuration errors. Alternatively you can just relaunch the + networking system: + + &prompt.root; /etc/rc.d/netif restart + + + If a default gateway has been set in + /etc/rc.conf, use also this + command: + + &prompt.root; /etc/rc.d/routing restart + - Once the system has been rebooted, you should test the + Once the networking system has been relaunched, you should test the network interfaces. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#20 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -683,7 +683,8 @@ a fetch operation, the Ports Collection and subsequent patches exist on the local system that have passed verification. The first time portsnap is executed, - use extract to install the updated files: + you have to use extract to install the + downloaded files: &prompt.root; portsnap extract /usr/ports/.cvsignore @@ -699,8 +700,8 @@ /usr/ports/Mk/bsd.cmake.mk ... - For subsequent runs of portsnap fetch, - update should be used instead: + To update an already installed Ports Collection use the command + portsnap update: &prompt.root; portsnap update @@ -712,6 +713,10 @@ shown in the following example: &prompt.root; portsnap fetch update + + This command will download the latest version of the + Ports Collection and update your local version under + /usr/ports. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#15 (text+ko) ==== @@ -1,6 +1,6 @@ @@ -225,6 +225,25 @@ url="http://www.freebsdfoundation.org/downloads/java.shtml">, and install it with &man.pkg.add.1;. + + The above site does not provide binary packages for + &os; 8.X. It is however possible + to use the packages for &os; 7.X + on an 8.X system. Simply install the + misc/compat7x port before + installing the package. + Alternatively, Diablo &jre; + (as well as Diablo &jdk;) may be + installed using the Ports Collection (the relevant ports are + java/diablo-jre16 and + java/diablo-jdk16). + Installing from the Ports Collection requires the source files + (distfiles) to be downloaded manually due to licensing issues. + Specific download instructions are provided when the + make install command + is invoked. + + Start your browser, enter about:plugins in the location bar and press Enter. A page listing the installed plugins ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#9 (text+ko) ==== @@ -1,6 +1,6 @@ @@ -706,11 +706,10 @@ Journaling - With the release of &os; 7.0, the long awaited feature - of UFS journals has been implemented. The - implementation itself is provided through the - GEOM subsystem and is easily configured - via the &man.gjournal.8; utility. + With the release of &os; 7.0, the long awaited feature + of journals has been implemented. The implementation itself is + provided through the GEOM subsystem and is + easily configured via the &man.gjournal.8; utility. What is journaling? Journaling capability stores a log of file system transactions, i.e.: changes that make up a complete @@ -733,7 +732,7 @@ To enable support for gjournal, the &os; kernel must have the following option - which is the - default on 7.X systems: + default on &os; 7.0 and later systems: options UFS_GJOURNAL @@ -756,7 +755,7 @@ disk: &prompt.root; gjournal load - &prompt.root; gjournal label /dev/da4 +&prompt.root; gjournal label /dev/da4 At this point, there should be a /dev/da4 device node and a @@ -766,8 +765,7 @@ &prompt.root; newfs -O 2 -J /dev/da4.journal The previously issued command will create a - UFS2 file system with journaling being made - active. + UFS2 file system on the journaled device. Effectively mount the device at the desired point with: @@ -780,11 +778,10 @@ ad4s1 and ad4s2 are both slices, then gjournal will create ad4s1.journal and - ad4s2.journal. In the case of the command - being run twice, the result will be journals. + ad4s2.journal. - Under some circumstances, keeping the journal on another disk + For better performance, keeping the journal on another disk may be desired. For these cases, the journal provider or storage device should be listed after the device to enable journaling on. Journaling may also be enabled on current file systems by ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#10 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -4318,7 +4318,7 @@ To modify these media to boot into a serial console, follow - these steps (If you wan to use a CDROM you can skip the first + these steps (If you want to use a CDROM you can skip the first step): @@ -4627,7 +4627,7 @@ ) as necessary. - Use the image of disc1 if you want to + Use the image of dvd1 if you want to install a &os; release and want a reasonable selection of third-party packages on the disc as well. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/jails/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -320,6 +320,11 @@ jail_enable="YES" # Set to NO to disable starting of any jails jail_list="www" # Space separated list of names of jails + + + Jail names in jail_list should + contain alphanumeric characters only. + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#20 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -196,12 +196,12 @@ single IP address from requesting any service more than 60 times in any given minute. - Novice users may be pleased to note that - these parameters usually do not need to be modified, - although we mention the rate-limiting options below as - they be useful should you find that you are receiving an - excessive amount of connections. A full list of options - can be found in the &man.inetd.8; manual. + Although we mention rate-limiting options below, novice + users may be pleased to note that these parameters usually do + not need to be modified. These options may be useful should you + find that you are receiving an excessive amount of connections. + A full list of options can be found in the &man.inetd.8; + manual. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#87 (text+ko) ==== @@ -1,7 +1,7 @@ patch-file and patch-file2 both changing - WRKSRC/foobar.c). + WRKSRC/foobar.c). + Note that if the path of a patched file contains an underscore + (_) character, the patch needs to have two + underscores instead in its name. For example, to patch a file + named src/freeglut_joystick.c, the + corresponding patch should be named + patch-src-freeglut__joystick.c. Please only use characters [-+._a-zA-Z0-9] for naming your patches. Do not use any other characters besides them. @@ -735,6 +741,14 @@ USE_DOS2UNIX= yes DOS2UNIX_REGEX= .*\.(c|cpp|h) + >>> TRUNCATED FOR MAIL (1000 lines) <<<