From owner-p4-projects@FreeBSD.ORG Sun Jan 22 12:58:01 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 885681065670; Sun, 22 Jan 2012 12:58:01 +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 4AFD31065672 for ; Sun, 22 Jan 2012 12:58:01 +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 372328FC0A for ; Sun, 22 Jan 2012 12:58:01 +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 q0MCw1K3081851 for ; Sun, 22 Jan 2012 12:58:01 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q0MCw16Y081848 for perforce@freebsd.org; Sun, 22 Jan 2012 12:58:01 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 22 Jan 2012 12:58:01 GMT Message-Id: <201201221258.q0MCw16Y081848@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 204999 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: Sun, 22 Jan 2012 12:58:01 -0000 http://p4web.freebsd.org/@@204999?ac=10 Change 204999 by rene@rene_acer on 2012/01/22 12:57:14 MFen the Dutch Handbook: - eresources 1.216 -> 1.217 - firewalls 1.97 -> 1.98 - ppp-and-slip 1.196 -> 1.197 - security 1.342 -> 1.343 - mailing-lists.ent 1.87 -> 1.88 Affected files ... .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.sgml#49 edit .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#28 edit .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#27 edit .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#25 edit .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/mailing-lists.ent#43 edit Differences ... ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.sgml#49 (text+ko) ==== @@ -5,7 +5,7 @@ Vertaald door: Siebrand Mazeland / Rene Ladan %SOURCE% en_US.ISO8859-1/books/handbook/eresources/chapter.sgml - %SRCID% 1.216 + %SRCID% 1.217 --> @@ -685,6 +685,12 @@ Overbrengen en onderhouden van XFCE voor &os; + + + &a.zope.name; + Zope voor &os; — + overbrengen en onderhouden + @@ -2075,6 +2081,23 @@ in het volgen van de technische discussie zijn ook welkom. + + + &a.zope.name; + + + Zope + + Dit is een forum voor discussies die verwant zijn aan het + brengen van de Zope-omgeving naar &os;. + Dit is een technische mailinglijst. Het is bedoeld voor + individuen die actief werken aan het overbrengen van + Zope naar &os;, om problemen aan te + dragen of alternatieve oplossingen te bespreken. Individuen die + geïnteresseerd zijn in het volgen van de technische discussie + zijn ook welkom. + + ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#28 (text+ko) ==== @@ -4,7 +4,7 @@ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml,v 1.18 2011/10/21 22:11:27 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml - %SRCID% 1.97 + %SRCID% 1.98 --> @@ -1591,13 +1591,13 @@ Het bestand /etc/services kan gebruikt worden om onbekende poortnummers op te zoeken. Ook kan + url="http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers"> worden bezocht en het poortnummer worden opgezocht om het doel van een bepaalde poort uit te vinden. Op de volgende link worden poortnummers van Trojans beschreven: . + url="http://www.sans.org/security-resources/idfaq/oddports.php">. De onderstaande set regels is een complete en erg veilige inclusieve set met regels voor een firewall die is @@ -3035,10 +3035,10 @@ pakketten gelogd worden met een onbekend poortnummer, dan is de functie van dat poortnummer na te zoeken in /etc/services of op . + url="http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers">. Op de volgende link worden poortnummers van Trojans beschreven: . + url="http://www.sans.org/security-resources/idfaq/oddports.php">. ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#27 (text+ko) ==== @@ -4,7 +4,7 @@ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.8 2011/05/11 18:58:09 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml - %SRCID% 1.196 + %SRCID% 1.197 --> @@ -2363,13 +2363,6 @@ Broadband with FreeBSD on DSL door Renaud Waldura. - - - - Nutzung von T-DSL und T-Online mit FreeBSD - door Udo Erdelhoff (in het Duits). - ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#25 (text+ko) ==== @@ -4,7 +4,7 @@ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml,v 1.23 2011/06/19 14:48:42 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/security/chapter.sgml - %SRCID% 1.342 + %SRCID% 1.343 --> @@ -1300,6 +1300,7 @@ Using MD5 to compute responses. Enter new secret pass phrase: Again new secret pass phrase: + ID unfurl OTP key is 499 to4268 MOS MALL GOAT ARM AVID COED @@ -1336,11 +1337,11 @@ Updating unfurl: You need the response from an OTP generator. Old secret pass phrase: - otp-md5 498 to4268 ext - Response: GAME GAG WELT OUT DOWN CHAT + otp-md5 498 to4268 ext + Response: GAME GAG WELT OUT DOWN CHAT New secret pass phrase: - otp-md5 499 to4269 - Response: LINE PAP MILK NELL BUOY TROY + otp-md5 499 to4269 + Response: LINE PAP MILK NELL BUOY TROY ID mark OTP key is 499 gr4269 LINE PAP MILK NELL BUOY TROY @@ -1612,8 +1613,8 @@ # De andere daemons zijn beschermd. ALL : ALL \ - : severity auth.info \ - : twist /bin/echo "You are not welcome to use %d from %h." + : severity auth.info \ + : twist /bin/echo "You are not welcome to use %d from %h." Dit voorbeeld geeft aan dat het bericht You are not allowed to use daemon from @@ -1644,9 +1645,9 @@ # Geen verbindingen van example.com: ALL : .example.com \ - : spawn (/bin/echo %a from %h attempted to access %d >> \ - /var/log/connections.log) \ - : deny + : spawn (/bin/echo %a from %h attempted to access %d >> \ + /var/log/connections.log) \ + : deny Hiermee worden alle verbindingen van het domein *.example.com geweigerd. @@ -2900,7 +2901,7 @@ options IPSEC #IP-beveiliging -device crypto +device crypto kernelopties @@ -3332,7 +3333,7 @@ van &os;. sshd is ingeschakeld als de volgende regel voorkomt in rc.conf: - sshd_enable="YES" + sshd_enable="YES" Hierdoor wordt &man.sshd.8; geladen, het daemonprogramma voor OpenSSH, als het systeem de @@ -3340,7 +3341,7 @@ &man.rc.8;-script /etc/rc.d/sshd te gebruiken om OpenSSH te starten: - /etc/rc.d/sshd start + &prompt.root; /etc/rc.d/sshd start ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/mailing-lists.ent#43 (text+ko) ==== @@ -5,7 +5,7 @@ Vertaald door: Siebrand Mazeland / Rene Ladan %SOURCE% en_US.ISO8859-1/share/sgml/mailing-lists.ent - %SRCID% 1.87 + %SRCID% 1.88 --> @@ -551,6 +551,10 @@ XFCE voor &os; mailinglijst"> freebsd-xfce"> + +Zope voor &os; mailinglijst"> +freebsd-zope"> + bug-followup@FreeBSD.org"> @@ -574,4 +578,3 @@ &os; symmetric multiprocessing mailinglijst"> freebsd-smp"> - From owner-p4-projects@FreeBSD.ORG Sun Jan 22 16:33:40 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 13C96106567B; Sun, 22 Jan 2012 16:33:40 +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 A41DB1065670 for ; Sun, 22 Jan 2012 16:33:39 +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 918AC8FC0A for ; Sun, 22 Jan 2012 16:33:39 +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 q0MGXd9f025627 for ; Sun, 22 Jan 2012 16:33:39 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q0MGXdDj025624 for perforce@freebsd.org; Sun, 22 Jan 2012 16:33:39 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 22 Jan 2012 16:33:39 GMT Message-Id: <201201221633.q0MGXdDj025624@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 205007 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: Sun, 22 Jan 2012 16:33:40 -0000 http://p4web.freebsd.org/@@205007?ac=10 Change 205007 by rene@rene_acer on 2012/01/22 16:33:17 Remove the instructions in case mergemaster(8) has no -p option, the oldest supported release (7.3) has it. Idea from http://wiki.freebsd.org/DocIdeaList Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#30 edit Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#30 (text+ko) ==== @@ -2122,13 +2122,7 @@ pre-buildworld mode by providing the option. This will compare only those files that are essential for the success of buildworld or - installworld. If your old version of - mergemaster does not support , - use the new version in the source tree when running for the first - time: - - &prompt.root; cd /usr/src/usr.sbin/mergemaster -&prompt.root; ./mergemaster.sh -p + installworld. If you are feeling particularly paranoid, you can check your From owner-p4-projects@FreeBSD.ORG Tue Jan 24 20:23:52 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id D7C3F1065677; Tue, 24 Jan 2012 20:23:51 +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 99BDE106566C for ; Tue, 24 Jan 2012 20:23:51 +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 84CF48FC08 for ; Tue, 24 Jan 2012 20:23:51 +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 q0OKNp1i053311 for ; Tue, 24 Jan 2012 20:23:51 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q0OKNp0p053308 for perforce@freebsd.org; Tue, 24 Jan 2012 20:23:51 GMT (envelope-from rene@FreeBSD.org) Date: Tue, 24 Jan 2012 20:23:51 GMT Message-Id: <201201242023.q0OKNp0p053308@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 205104 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: Tue, 24 Jan 2012 20:23:52 -0000 http://p4web.freebsd.org/@@205104?ac=10 Change 205104 by rene@rene_acer on 2012/01/24 20:23:40 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#123 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/arch-handbook/boot/chapter.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#35 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#124 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#71 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/book.sgml#19 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/config/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.sgml#50 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#29 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/introduction/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#68 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.sgml#22 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#28 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#26 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/mailing-lists.ent#44 integrate .. //depot/projects/docproj_nl/www/en/donations/donors.sgml#45 integrate .. //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#29 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2011-10-2011-12.xml#1 branch .. //depot/projects/docproj_nl/www/en/releases/9.0R/hardware.html#2 integrate .. //depot/projects/docproj_nl/www/en/search/web.atoz#9 integrate .. //depot/projects/docproj_nl/www/nl/index.xsl#21 integrate .. //depot/projects/docproj_nl/www/nl/share/sgml/navibar.l10n.ent#23 integrate .. //depot/projects/docproj_nl/www/nl/where.sgml#35 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#27 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#123 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -881,7 +881,7 @@ The DATA_SET() macro expands to a MAKE_SET(), and that macro is the point - where the all sysinit magic is hidden: + where all the sysinit magic is hidden: /usr/include/linker_set.h: #define MAKE_SET(set, sym) \ ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml#5 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -75,9 +75,14 @@ handled by setting the dumpdev variable in &man.rc.conf.5; to the path of the swap device (the recommended way to extract a kernel dump) or - AUTO to use the first configured swap - device. AUTO is the default as of - &os; 6.0. + AUTO to use the first configured swap + device. The default for dumpdev is + AUTO in HEAD, and changed to + NO on RELENG_* branches (except for RELENG_7, + which was left set to AUTO). + On &os; 9.0-RELEASE and later versions, + bsdinstall will ask whether crash dumps + should be enabled on the target system during the install process. Check /etc/fstab or &man.swapinfo.8; for a list of swap devices. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#35 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -180,7 +180,7 @@ Both of these groups (local network hosts and local subnets) have their routes automatically configured by a daemon called routed. If this is not run, then only - routes which are statically defined (i.e. entered explicitly) will + routes which are statically defined (i.e., entered explicitly) will exist. The host1 line refers to our host, which it @@ -627,7 +627,7 @@ sites are unable to connect to you. Perhaps the most useful command for trying to figure out where routing is breaking down is the &man.traceroute.8; command. It is equally useful if you cannot seem - to make a connection to a remote machine (i.e. &man.ping.8; + to make a connection to a remote machine (i.e., &man.ping.8; fails). The &man.traceroute.8; command is run with the name of the remote @@ -1660,7 +1660,7 @@ The ca_cert field indicates the pathname of the CA certificate file. This file - is needed to verify the server certificat. + is needed to verify the server certificate. @@ -1911,7 +1911,7 @@ - Host-based Access Point without Authentication or + <title>Host-based Access Point Without Authentication or Encryption Although it is not recommended to run an AP without any @@ -2147,7 +2147,7 @@ - Using both wired and wireless connection + Using Both Wired and Wireless Connection Wired connection provides better performance and reliability, while wireless connection provides flexibility and mobility, @@ -2256,7 +2256,7 @@ Networks are usually formed ad-hoc from portable devices such as cellular phones, handhelds and laptops. Unlike the other popular wireless technology, Wi-Fi, Bluetooth offers higher level service - profiles, e.g. FTP-like file servers, file pushing, voice transport, + profiles, e.g., FTP-like file servers, file pushing, voice transport, serial line emulation, and more. The Bluetooth stack in &os; is implemented using the Netgraph @@ -2322,7 +2322,7 @@ control registers. This interface provides a uniform method of accessing the Bluetooth baseband capabilities. HCI layer on the Host exchanges data and commands with the HCI firmware on the Bluetooth hardware. - The Host Controller Transport Layer (i.e. physical bus) driver provides + The Host Controller Transport Layer (i.e., physical bus) driver provides both HCI layers with the ability to exchange information with each other. @@ -2771,7 +2771,7 @@ Troubleshooting - A remote device cannot connect + A Remote Device Cannot Connect Some older Bluetooth devices do not support role switching. By default, when &os; is accepting a new connection, it tries to perform a role switch and become master. Devices, which do not @@ -2786,7 +2786,7 @@ - Something is going wrong, can I see what exactly is happening? + Something is Going Wrong, Can I See What Exactly is Happening? Yes, you can. Use the third-party package hcidump, which is available as comms/hcidump port. @@ -3152,7 +3152,7 @@ - Address limits + Address Limits The number of unique source MAC addresses behind an interface can be limited. Once the limit is reached packets @@ -3356,7 +3356,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 @@ -3439,7 +3439,7 @@ - Failover mode + Failover Mode Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. Bring the underlying @@ -3484,7 +3484,7 @@ - Failover mode between wired and wireless interfaces + Failover Mode Between Wired and Wireless Interfaces For laptop users, it is usually desirable to make wireless as a secondary interface, which is to be used when the wired connection @@ -3934,7 +3934,7 @@ role="package">net/etherboot package or port. You can change the Etherboot - configuration (i.e. to use TFTP instead of + configuration (i.e., to use TFTP instead of NFS) by editing the Config file in the Etherboot source directory. @@ -4001,7 +4001,7 @@ Create a directory from which tftpd - will serve the files, e.g. /tftpboot. + will serve the files, e.g., /tftpboot. @@ -4127,7 +4127,7 @@ dhcpd.conf. - Using <command>make world</command> to populate root + Using <command>make world</command> to Populate Root This method is quick and will install a complete virgin system (not only the root file system) @@ -4223,7 +4223,7 @@ - PXE Booting with an NFS root file system + PXE Booting with an NFS Root File System The &intel; Preboot eXecution Environment (PXE) allows booting the operating system over the network. @@ -4248,7 +4248,7 @@ the &os; booting process. - Setting Up the <command>chroot</command> Environment for the NFS Root File system + Setting Up the <command>chroot</command> Environment for the NFS Root File System @@ -4349,7 +4349,7 @@ &prompt.root; chroot ${NFSROOTDIR} &prompt.root; passwd This will set the root password for client machines - which are PXE booting. + which are PXE booting. @@ -4375,7 +4375,7 @@ - Configuring Memory File Systems used by <filename>/etc/rc.initdiskless</filename> + Configuring Memory File Systems Used by <filename>/etc/rc.initdiskless</filename> If you boot from an NFS root volume, /etc/rc @@ -4453,7 +4453,7 @@ - Configuring the PXE client and Debugging Connection Problems + Configuring the PXE Client and Debugging Connection Problems @@ -5522,7 +5522,7 @@ by multicast addresses in IPv6. - Reserved IPv6 addresses + Reserved IPv6 Addresses @@ -5696,7 +5696,7 @@ - Applying the needed changes to <filename>/etc/rc.conf</filename> + Applying the Needed Changes to <filename>/etc/rc.conf</filename> IPv6 Client Settings @@ -5814,7 +5814,7 @@ Asynchronous Transfer Mode (ATM) - Configuring classical IP over ATM (PVCs) + Configuring Classical IP over ATM (PVCs) Classical IP over ATM (CLIP) is the simplest method to use Asynchronous Transfer Mode (ATM) @@ -5824,7 +5824,7 @@ on PVCs. - Fully meshed configurations + Fully Meshed Configurations The first method to set up a CLIP with PVCs is to connect each machine to each other machine in the @@ -6082,7 +6082,7 @@ used to distinguish the host on the network. - Using CARP For Server Availability (CARP) + Using CARP for Server Availability (CARP) One use of CARP, as noted above, is for server availability. This example will provide failover support ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#31 (text+ko) ==== @@ -1,7 +1,7 @@ ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#20 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -382,7 +382,7 @@ To lock an account completely, the &man.pw.8; command should be used: - &prompt.root;pw lock staff + &prompt.root; pw lock staff This will prevent the user from logging in using any mechanism, including &man.ssh.1;. @@ -1204,6 +1204,7 @@ Using MD5 to compute responses. Enter new secret pass phrase: Again new secret pass phrase: + ID unfurl OTP key is 499 to4268 MOS MALL GOAT ARM AVID COED @@ -1240,15 +1241,14 @@ Updating unfurl: You need the response from an OTP generator. Old secret pass phrase: - otp-md5 498 to4268 ext - Response: GAME GAG WELT OUT DOWN CHAT + otp-md5 498 to4268 ext + Response: GAME GAG WELT OUT DOWN CHAT New secret pass phrase: - otp-md5 499 to4269 - Response: LINE PAP MILK NELL BUOY TROY + otp-md5 499 to4269 + Response: LINE PAP MILK NELL BUOY TROY ID mark OTP key is 499 gr4269 -LINE PAP MILK NELL BUOY TROY - +LINE PAP MILK NELL BUOY TROY To accept the default seed press Return. Then before entering an access password, move over to your @@ -1258,8 +1258,7 @@ Using the MD5 algorithm to compute response. Reminder: Don't use opiekey from telnet or dial-in sessions. Enter secret pass phrase: -GAME GAG WELT OUT DOWN CHAT - +GAME GAG WELT OUT DOWN CHAT Now switch back over to the insecure connection, and copy the one-time password generated over to the relevant @@ -1513,8 +1512,8 @@ # The rest of the daemons are protected. ALL : ALL \ - : severity auth.info \ - : twist /bin/echo "You are not welcome to use %d from %h." + : severity auth.info \ + : twist /bin/echo "You are not welcome to use %d from %h." This example shows that the message, You are not allowed to use daemon @@ -2775,8 +2774,7 @@ options IPSEC #IP security -device crypto - +device crypto kernel options @@ -3199,7 +3197,7 @@ &os;. To see if sshd is enabled, check the rc.conf file for: - sshd_enable="YES" + sshd_enable="YES" This will load &man.sshd.8;, the daemon program for OpenSSH, the next time your @@ -3207,7 +3205,7 @@ /etc/rc.d/sshd &man.rc.8; script to start OpenSSH: - /etc/rc.d/sshd start + &prompt.root; /etc/rc.d/sshd start @@ -3269,8 +3267,8 @@ &prompt.root; scp user@example.com:/COPYRIGHT COPYRIGHT user@example.com's password: ******* -COPYRIGHT 100% |*****************************| 4735 -00:00 +COPYRIGHT 100% |*****************************| 4735 +00:00 &prompt.root; Since the fingerprint was already saved for this host in @@ -3324,8 +3322,7 @@ Your identification has been saved in /home/user/.ssh/id_dsa. Your public key has been saved in /home/user/.ssh/id_dsa.pub. The key fingerprint is: -bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com - +bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com &man.ssh-keygen.1; will create a public and private key pair for use in authentication. The private key is stored ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#124 (text+ko) ==== @@ -1,7 +1,7 @@ This is a Mitre + url="http://www.cve.mitre.org/">MITRE CVE identifier. ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#71 (text+ko) ==== @@ -1,7 +1,7 @@ + @@ -49,7 +49,7 @@ + title="&os; Projectnieuws" href="&enbase;/news/rss.xml" /> ja
  • - nl + nl
  • ru @@ -237,10 +237,10 @@ @@ -263,7 +263,7 @@ @@ -286,7 +286,7 @@ ==== //depot/projects/docproj_nl/www/nl/share/sgml/navibar.l10n.ent#23 (text+ko) ==== @@ -1,4 +1,4 @@ - ==== //depot/projects/docproj_nl/www/nl/where.sgml#35 (text+ko) ==== @@ -1,5 +1,5 @@ + ==== //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#27 (text+ko) ==== @@ -1,12 +1,12 @@ - + - $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.70 2011/12/08 14:41:15 jkois Exp $ + $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.71 2012/01/23 18:45:11 jkois Exp $ @@ -74,6 +74,17 @@ + + BeastieCLOUD + http://www.beastiecloud.de + + BeastieCLOUD offers high quality FreeBSD hosting solutions in + german speaking territories (D-A-CH). We provide individual + server configurations to match any demand of our customers. + "Good isn't good enough if there is a way to do it better!" + + + Bewide Internet Service Provider http://www.bewide.com From owner-p4-projects@FreeBSD.ORG Tue Jan 24 21:05:32 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id CCBCC1065675; Tue, 24 Jan 2012 21:05:31 +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 8F95C106566B for ; Tue, 24 Jan 2012 21:05:31 +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 62ED38FC17 for ; Tue, 24 Jan 2012 21:05:31 +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 q0OL5VLN060596 for ; Tue, 24 Jan 2012 21:05:31 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q0OL5VCo060593 for perforce@freebsd.org; Tue, 24 Jan 2012 21:05:31 GMT (envelope-from rene@FreeBSD.org) Date: Tue, 24 Jan 2012 21:05:31 GMT Message-Id: <201201242105.q0OL5VCo060593@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 205106 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: Tue, 24 Jan 2012 21:05:32 -0000 http://p4web.freebsd.org/@@205106?ac=10 Change 205106 by rene@rene_acer on 2012/01/24 21:04:41 MFen the Dutch Handbook: - advanced-networking 1.443 -> 1.444 - cutting-edge 1.256 -> 1.257 Affected files ... .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#72 edit .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#46 edit Differences ... ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#72 (text+ko) ==== @@ -4,7 +4,7 @@ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.34 2012/01/19 21:21:56 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml - %SRCID% 1.443 + %SRCID% 1.444 --> @@ -4722,7 +4722,7 @@ &prompt.root; passwd Dit stelt het root-wachtwoord in voor cliëntmachines die - over PXE opstarten. + over PXE opstarten. ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#46 (text+ko) ==== @@ -4,7 +4,7 @@ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.28 2011/12/18 20:05:49 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml - %SRCID% 1.256 + %SRCID% 1.257 --> @@ -2296,9 +2296,6 @@ het succes van buildworld of installworld: - &prompt.root; cd /usr/src/usr.sbin/mergemaster -&prompt.root; ./mergemaster.sh -p - In paranoide beheerdersmodus kan er gecontroleerd worden welke bestanden op een systeem eigendom From owner-p4-projects@FreeBSD.ORG Sat Jan 28 22:46:49 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 60C0B1065677; Sat, 28 Jan 2012 22:46:49 +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 2298D1065675 for ; Sat, 28 Jan 2012 22:46:49 +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 0AACC8FC1C for ; Sat, 28 Jan 2012 22:46:49 +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 q0SMkmKf051745 for ; Sat, 28 Jan 2012 22:46:48 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q0SMkm07051742 for perforce@freebsd.org; Sat, 28 Jan 2012 22:46:48 GMT (envelope-from rene@FreeBSD.org) Date: Sat, 28 Jan 2012 22:46:48 GMT Message-Id: <201201282246.q0SMkm07051742@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 205316 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: Sat, 28 Jan 2012 22:46:49 -0000 http://p4web.freebsd.org/@@205316?ac=10 Change 205316 by rene@rene_acer on 2012/01/28 22:46:01 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributing-ports/article.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#124 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/dev-model/book.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#125 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#73 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#47 integrate .. //depot/projects/docproj_nl/share/misc/docbook.css#8 integrate .. //depot/projects/docproj_nl/share/pgpkeys/delphij.key#3 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd-print.dsl#3 integrate .. //depot/projects/docproj_nl/www/en/administration.sgml#24 integrate .. //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#30 integrate .. //depot/projects/docproj_nl/www/en/internal/new-account.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/Makefile#16 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2011-10-2011-12.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/status.sgml#17 integrate .. //depot/projects/docproj_nl/www/en/platforms/ppc.sgml#9 integrate .. //depot/projects/docproj_nl/www/en/platforms/sparc.sgml#9 integrate .. //depot/projects/docproj_nl/www/en/platforms/sun4v.sgml#2 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#128 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributing-ports/article.sgml#6 (text+ko) ==== @@ -7,13 +7,13 @@ Contributing to the FreeBSD Ports Collection - $FreeBSD: doc/en_US.ISO8859-1/articles/contributing-ports/article.sgml,v 1.9 2011/11/28 15:43:34 ryusuke Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/contributing-ports/article.sgml,v 1.12 2012/01/28 06:15:41 wblock Exp $ Abstract + This article describes the ways in which an individual - can contribute to the FreeBSD Ports Collection. - + can contribute to the FreeBSD Ports Collection. @@ -46,9 +46,9 @@ Anyone can get involved, and there are lots of different ways to do so. Contributing to ports is an excellent way to - help give back something to the project. Whether you are - looking for an ongoing role, or a fun challenge for a rainy day, - we would love to have your help! + help give back something to the project. + Whether you are looking for an ongoing role, or a fun challenge + for a rainy day, we would love to have your help! As a volunteer, what you do is limited only by what you want to do. However, we do ask that you are aware of what other @@ -60,33 +60,32 @@ What you can do to help There are a number of easy ways you can contribute to - keeping the ports tree up to date and in good working order: - + keeping the ports tree up to date and in good working + order: Find some cool or useful software and - create a port for it. - + create a port for + it. There are a large number of ports that have no maintainer. Become a maintainer and - adopt a port. - + adopt a port. If you have created or adopted a port, be aware of what you need to do - as a maintainer. + as a maintainer. When you are looking for a quick challenge you could fix a bug or a broken - port. + port. @@ -95,11 +94,11 @@ Creating a new port There is a separate document available to help guide you - through creating (and upgrading) a port called the - Porter's Handbook. - The Porter's Handbook is the best reference to working with - the ports system. It provides details about how the ports - system operates and discusses recommended practices. + through creating (and upgrading) a port called the Porter's Handbook. + The Porter's Handbook is the best reference to working with the + ports system. It provides details about how the ports system + operates and discusses recommended practices. @@ -115,12 +114,13 @@ ports. It is a good idea to start with adopting a port that you use regularly. - Unmaintained ports have their MAINTAINER - set to ports@FreeBSD.org. A list of - unmaintained ports and their current errors and problem - reports can be seen at the - &os; Ports Monitoring System. - + Unmaintained ports have their + MAINTAINER set to + ports@FreeBSD.org. A list of unmaintained + ports and their current errors and problem reports can be seen + at the &os; + Ports Monitoring System. Some ports affect a large number of others due to dependencies and slave port relationships. Generally, we @@ -130,11 +130,12 @@ You can find out whether or not a port has dependencies or slave ports by looking at a master index of ports called INDEX. (The name of the file varies - by release of &os;; for instance, INDEX-8.) - Some ports have conditional dependencies that are not - included in a default INDEX build. We - expect you to be able to recognize such ports by looking through - other ports' Makefiles. + by release of &os;; for instance, + INDEX-8.) Some ports have conditional + dependencies that are not included in a default + INDEX build. We expect you to be able to + recognize such ports by looking through other ports' + Makefiles. @@ -142,21 +143,21 @@ First make sure you understand your responsibilities as a - maintainer. - Also read the - Porter's Handbook. - Please do not commit yourself to more than you feel - you can comfortably handle. + maintainer. Also read the + Porter's + Handbook. Please do not commit yourself + to more than you feel you can comfortably + handle. You may request maintainership of any unmaintained port as soon as you wish. Simply set MAINTAINER to your own email address and send a PR (Problem Report) with the change. If the port has build errors or needs updating, you may wish to include any other changes in the same PR. - This will help because many committers are less willing to assign - maintainership to someone who does not have a known track record - with &os;. Submitting PRs that fix build errors or - update ports are the best ways to establish one. + This will help because many committers are less willing to + assign maintainership to someone who does not have a known + track record with &os;. Submitting PRs that fix build errors + or update ports are the best ways to establish one. File your PR with category ports and class change-request. A committer will @@ -229,9 +230,9 @@ Part of being a maintainer is taking on a support role. You are not expected to provide general support - (but we welcome it if you choose to do so). What you should - provide is a point of coordination for &os;-specific - issues regarding your ports. + (but we welcome it if you choose to do so). What you + should provide is a point of coordination for + &os;-specific issues regarding your ports. @@ -280,10 +281,10 @@ This section outlines the process to follow to keep your ports up to date. - This is an overview. More information about upgrading a + This is an overview. More information about upgrading a port is available in the - Porter's Handbook. + Porter's Handbook. @@ -343,9 +344,11 @@ Verify your port using &man.portlint.1; as a - guide. See resources - for important information about using - portlint. + guide. See resources for important + information about using + portlint. + Consider whether changes to your port might @@ -356,8 +359,9 @@ case, at the very least, the dependent ports will need to get a PORTREVISION bump so that they will automatically be upgraded by - automated tools such as portmaster - or &man.portupgrade.1;. + automated tools such as + portmaster or + &man.portupgrade.1;. @@ -368,17 +372,18 @@ Send your update by submitting a PR with an explanation of the changes and a patch containing the differences between the original port and the updated - one. Please refer to - Writing FreeBSD Problem Reports - for information on how to write a really good PR. + one. Please refer to Writing FreeBSD + Problem Reports for information on how to + write a really good PR. Please do not submit a &man.shar.1; archive of the - entire port; instead, use &man.diff.1; -ruN. - In this way, committers can much more easily see exactly - what changes are being made. The Porter's Handbook - section on - Upgrading + entire port; instead, use &man.diff.1; + -ruN. In this way, committers can + much more easily see exactly what changes are being + made. The Porter's Handbook section on Upgrading has more information. @@ -387,8 +392,8 @@ Wait At some stage a committer will deal with your PR. - It may take minutes, or it may take weeks — so please - be patient. + It may take minutes, or it may take weeks — so + please be patient. @@ -427,22 +432,23 @@ even better. Since the majority of &os; installations run on - PC-compatible machines (what is termed the i386 - architecture), we expect you to keep the port working on that - architecture. We prefer that ports also work on - the amd64 architecture running native. - It is completely fair to ask for help if you - do not have one of these machines. + PC-compatible machines (what is termed the + i386 architecture), we expect you to keep + the port working on that architecture. We prefer that ports + also work on the amd64 architecture + running native. It is completely fair to ask for help if + you do not have one of these machines. - The usual failure modes for non-i386 - machines are that the original programmers assumed that, for - instance, pointers are ints, or that a - relatively lax older gcc compiler - was being used. More and more, application authors are - reworking their code to remove these assumptions — - but if the author is not actively maintaining their code, - you may need to do this yourself. + The usual failure modes for + non-i386 machines are that the original + programmers assumed that, for instance, pointers are + ints, or that a relatively lax older + gcc compiler was being used. + More and more, application authors are reworking their + code to remove these assumptions — but if the author + is not actively maintaining their code, you may need to do + this yourself. These are the tasks you need to perform to ensure your @@ -452,15 +458,16 @@ Watch for build failures - Regularly check the automated ports building cluster, - pointyhat, - and the - distfiles scanner - to see if any of the ports you maintain are failing to - build or fetch (see resources - for more information about these systems). Reports of - failures may also come to you from other users or - automated systems via email. + Regularly check the automated ports building + cluster, pointyhat, + and the distfiles + scanner to see if any of the ports you + maintain are failing to build or fetch (see resources for more + information about these systems). Reports of failures + may also come to you from other users or automated + systems via email. @@ -469,10 +476,10 @@ Once you are aware of a problem, collect information to help you fix it. Build errors reported by pointyhat are accompanied by logs - which will show you where the build failed. If the failure - was reported to you by a user, ask them to send you - information which may help in diagnosing the problem, - such as: + which will show you where the build failed. If the + failure was reported to you by a user, ask them to send + you information which may help in diagnosing the + problem, such as: @@ -482,7 +489,7 @@ The commands and options used to build the port (including options set in - /etc/make.conf) + /etc/make.conf) @@ -496,13 +503,14 @@ - When their ports collection was last updated - + When their ports collection was last + updated When their INDEX file - was last updated + was last updated + @@ -511,8 +519,9 @@ Unfortunately there is no straightforward process to follow to do this. Remember, though: if you are stuck, - ask for help! The &a.ports; is a good place to start, and - the upstream developers are often very helpful. + ask for help! The &a.ports; is a good place to start, + and the upstream developers are often very + helpful. @@ -520,37 +529,38 @@ Just as with updating a port, you should now incorporate changes, review and test, submit your - changes in a PR, and provide feedback if required. - + changes in a PR, and provide feedback if + required. Send patches to upstream authors - In some cases, you will have to make patches to - the port to make it run on FreeBSD. Some (but not all) + In some cases, you will have to make patches to the + port to make it run on FreeBSD. Some (but not all) upstream authors will accept such patches back into their code for the next release. If so, this may even help their users on other BSD-based systems as well and perhaps save duplicated effort. Please consider sending - any applicable patches to the authors as a courtesy. - + any applicable patches to the authors as a + courtesy. - Investigate bug reports and PRs related to your port - + + Investigate bug reports and PRs related to your + port - This section is about discovering and fixing bugs. - + This section is about discovering and fixing + bugs. &os;-specific bugs are generally caused by assumptions - about the build and runtime environments that do not apply to - &os;. You are less likely to encounter a problem of this - type, but it can be more subtle and difficult to diagnose. - + about the build and runtime environments that do not apply + to &os;. You are less likely to encounter a problem of this + type, but it can be more subtle and difficult to + diagnose. These are the tasks you need to perform to ensure your port continues to work as intended: @@ -560,49 +570,50 @@ Respond to bug reports Bugs may be reported to you through email via the - - GNATS Problem Report database. Bugs may - also be reported directly to you by users. + + GNATS Problem Report database. Bugs may also be + reported directly to you by users. You should respond to PRs and other reports within - 14 days, but please try not to take that long. Try to respond - as soon as possible, even if it is just to say you need some - more time before you can work on the PR. + 14 days, but please try not to take that long. Try to + respond as soon as possible, even if it is just to say + you need some more time before you can work on the + PR. - If you have not responded after 14 days, any committer may - commit from a PR that you have not responded to via a + If you have not responded after 14 days, any + committer may commit from a PR that you have not + responded to via a maintainer-timeout. Collect information - If the person reporting the bug has not also provided - a fix, you need to collect the information that will - allow you to generate one. + If the person reporting the bug has not also + provided a fix, you need to collect the information that + will allow you to generate one. If the bug is reproducible, you can collect most of the required information yourself. If not, ask the person who reported the bug to collect the information - for you, such as: - + for you, such as: A detailed description of their actions, - expected program behavior and actual behavior - + expected program behavior and actual behavior - Copies of input data used to trigger the bug - + Copies of input data used to trigger the + bug Information about their build and execution - environment — for example, a list of installed - packages and the output of &man.env.1; + environment — for example, a list of installed + packages and the output of &man.env.1; @@ -631,8 +642,8 @@ Find a solution - As with build errors, you will need to sort out a fix - to the problem. Again, remember to ask if you are + As with build errors, you will need to sort out a + fix to the problem. Again, remember to ask if you are stuck! @@ -652,35 +663,35 @@ Providing support - Part of being a maintainer is providing support — not - for the software in general — but for the port and any - &os;-specific quirks and problems. Users may contact you with - questions, suggestions, problems and patches. Most of the - time their correspondence will be specific to &os;. + Part of being a maintainer is providing support — + not for the software in general — but for the port and + any &os;-specific quirks and problems. Users may contact + you with questions, suggestions, problems and patches. Most + of the time their correspondence will be specific to + &os;. Occasionally you may have to invoke your skills in diplomacy, and kindly point users seeking general support to - the appropriate resources. Less frequently you will encounter - a person asking why the RPMs are not up to date - or how can they get the software to run under Foo Linux. Take the - opportunity to tell them that your port is up to date (if it - is, of course!), and suggest that they try &os;. - + the appropriate resources. Less frequently you will + encounter a person asking why the RPMs + are not up to date or how can they get the software to run + under Foo Linux. Take the opportunity to tell them that + your port is up to date (if it is, of course!), and suggest + that they try &os;. - Sometimes users and developers will decide that you are a - busy person whose time is valuable and do some of the work for - you. For example, they might: - + Sometimes users and developers will decide that you are + a busy person whose time is valuable and do some of the work + for you. For example, they might: - submit a PR or send you patches to update your port, - + submit a PR or send you patches to update your + port, - investigate and perhaps provide a fix to a PR, or - + investigate and perhaps provide a fix to a PR, + or @@ -689,12 +700,12 @@ In these cases your main obligation is to respond in a - timely manner. Again, the timeout for non-responsive maintainers is - 14 days. After this period changes may be committed - unapproved. They have taken the trouble to do this for you; - so please try to at least respond promptly. Then review, - approve, modify or discuss their changes with them as soon as - possible. + timely manner. Again, the timeout for non-responsive + maintainers is 14 days. After this period changes may be + committed unapproved. They have taken the trouble to do + this for you; so please try to at least respond promptly. + Then review, approve, modify or discuss their changes with + them as soon as possible. If you can make them feel that their contribution is appreciated (and it should be) you will have a better chance @@ -710,21 +721,22 @@ There are two really good places to find a port that needs some attention. - You can use the - web interface - to the Problem Report database to search through and view unresolved - PRs. The majority of ports PRs are updates, but with a little - searching and skimming over synopses you should be able to find - something interesting to work on (the sw-bug - class is a good place to start). - + You can use the web + interface to the Problem Report database to search + through and view unresolved PRs. The majority of ports PRs are + updates, but with a little searching and skimming over synopses + you should be able to find something interesting to work on (the + sw-bug class is a good place to + start). - The other place is the - &os; Ports Monitoring System. - In particular look for unmaintained ports with build errors and - ports that are marked BROKEN. It is OK to send - changes for a maintained port as well, but remember to ask the - maintainer in case they are already working on the problem. + The other place is the &os; Ports Monitoring + System. In particular look for unmaintained ports + with build errors and ports that are marked + BROKEN. It is OK to send changes for a + maintained port as well, but remember to ask the maintainer in + case they are already working on the problem. Once you have found a bug or problem, collect information, investigate and fix! If there is an existing PR, follow up to @@ -741,78 +753,78 @@ longer using a port or have otherwise lost time or interest in being a maintainer. In this way we can go ahead and allow other people to try to work on existing problems with the port without - waiting for your response. Remember, &os; is a volunteer project, - so if maintaining a port is no fun anymore, it is probably time to - let someone else do it! + waiting for your response. Remember, &os; is a volunteer + project, so if maintaining a port is no fun anymore, it is + probably time to let someone else do it! - In any case, the Ports Management Team (portmgr) - reserves the right to reset your maintainership if you have not - actively maintained your port in some time. (Currently, this is - set to 3 months.) By this, we mean that there are unresolved - problems or pending updates that have not been worked on during - that time. + In any case, the Ports Management Team + (portmgr) reserves the right to reset your + maintainership if you have not actively maintained your port in + some time. (Currently, this is set to 3 months.) By this, we + mean that there are unresolved problems or pending updates that + have not been worked on during that time. Resources for ports maintainers and contributors - The - Porter's Handbook - is your hitchhiker's guide to the ports system. Keep it handy! - + The Porter's + Handbook is your hitchhiker's guide to the ports + system. Keep it handy! - Writing FreeBSD Problem Reports - describes how to best formulate and submit a PR. In 2005 more - than eleven thousand ports PRs were submitted! Following this - article will greatly assist us in reducing the time needed to - handle your PRs. + Writing FreeBSD + Problem Reports describes how to best formulate and + submit a PR. In 2005 more than eleven thousand ports PRs were + submitted! Following this article will greatly assist us in + reducing the time needed to handle your PRs. - The - - Problem Report database. + The + Problem Report database. Pointyhat is the ports build cluster. You can use Pointyhat to check port build logs across all architectures and major releases. - The - FreeBSD Ports Monitoring System - can show you cross-referenced information about ports such as - build errors and problem reports. If you are a maintainer you can - use it to check on the build status of your ports. As a - contributor you can use it to find broken and unmaintained ports - that need to be fixed. + The FreeBSD Ports + Monitoring System can show you cross-referenced + information about ports such as build errors and problem + reports. If you are a maintainer you can use it to check on the + build status of your ports. As a contributor you can use it to + find broken and unmaintained ports that need to be fixed. - The - FreeBSD Ports distfile scanner - can show you ports for which the distfiles are not fetchable. You - can check on your own ports or use it to find ports that need their - MASTER_SITES updated. - + The FreeBSD Ports + distfile scanner can show you ports for which the + distfiles are not fetchable. You can check on your own ports or + use it to find ports that need their + MASTER_SITES updated. The ports tinderbox is the most - thorough way to test a port through the entire cycle of installation, - packaging, and deinstallation. It features a command-line - interface but also can be controlled via a web interface. - Please see ports/ports-mgmt/tinderbox. - More documentation is located at the - marcuscom tinderbox home page. - + thorough way to test a port through the entire cycle of + installation, packaging, and deinstallation. It features a + command-line interface but also can be controlled via a web + interface. Please see + ports/ports-mgmt/tinderbox. More + documentation is located at the marcuscom tinderbox home + page. - &man.portlint.1; is an application which can be used to verify - that your port conforms to many important stylistic and functional - guidelines. portlint is a simple - heuristic application, so you should use it only as a - guide. If portlint suggests - changes which seem unreasonable, consult the - Porter's Handbook or - ask for advice. + &man.portlint.1; is an application which can be used to + verify that your port conforms to many important stylistic and + functional guidelines. portlint is a + simple heuristic application, so you should use it + only as a guide. If + portlint suggests changes which seem + unreasonable, consult the Porter's Handbook + or ask for advice. - The &a.ports; is for general ports-related discussion. It is - a good place to ask for help. You can - subscribe, or - read and search the list archives. Reading the archives of - the &a.ports-bugs; and the &a.cvs-ports; may also be of interest. + The &a.ports; is for general ports-related discussion. It + is a good place to ask for help. You can subscribe, or + read and search the list archives. Reading the + archives of the &a.ports-bugs; and the &a.cvs-ports; may also be + of interest. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#124 (text+ko) ==== @@ -1,4 +1,4 @@ - + - Hat currently held by: &a.philip;. + Hat currently held by: &a.gavin;. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#9 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -36,7 +36,8 @@ - Installing &os; 9.<replaceable>x</replaceable> and Later + Installing &os; 9.<replaceable>x</replaceable> and + Later Synopsis @@ -44,12 +45,14 @@ installation &os; comes with a text-based, easy to use installation - program. &os; 9.0-RELEASE and later use an installation program - called bsdinstall, while releases prior - to &os; 9.0-RELEASE using sysinstall for - installation. This chapter describes the use of bsdinstall. - The use of sysinstall - is covered in . + program. &os; 9.0-RELEASE and later use an installation + program called bsdinstall, while + releases prior to &os; 9.0-RELEASE using + sysinstall for installation. This + chapter describes the use of + bsdinstall. The use of + sysinstall is covered in . After reading this chapter, you will know: @@ -64,12 +67,13 @@ - How to start bsdinstall. + How to start + bsdinstall. - The questions bsdinstall will ask - you, what they mean, and how to answer them. + The questions bsdinstall will + ask you, what they mean, and how to answer them. @@ -77,9 +81,9 @@ - Read the supported hardware list that shipped with the version - of &os; you are installing, and verify that your hardware is - supported. + Read the supported hardware list that shipped with the + version of &os; you are installing, and verify that your + hardware is supported. @@ -92,7 +96,6 @@ chapter as a general guide rather than as exact literal instructions. - @@ -104,18 +107,19 @@ The minimal configuration to install &os; varies with the &os; version and the hardware architecture. - A summary of this information is given in the following sections. - Depending on the method you choose to install &os;, you may - also need a supported CDROM drive, and in some - cases a network adapter. This will be covered by . + A summary of this information is given in the following + sections. Depending on the method you choose to install &os;, + you may also need a supported CDROM drive, and in some cases a + network adapter. This will be covered by . &os;/&arch.i386; - &os;/&arch.i386; requires a 486 or better processor and at - least 64 MB of RAM. At least 1.1 GB of free hard - drive space is needed for the most minimal installation. + &os;/&arch.i386; requires a 486 or better processor and + at least 64 MB of RAM. At least 1.1 GB of free + hard drive space is needed for the most minimal + installation. On old computers, increasing RAM and hard drive space @@ -134,12 +138,12 @@ processors. The second class of processors that can use - &os;/&arch.amd64; includes those using the &intel; EM64T - architecture. Examples of these processors include the - &intel; &core; 2 Duo, Quad, Extreme processor - families, the &intel; &xeon; 3000, 5000, and 7000 - sequences of processors, and the &intel; &core; - i3, i5 and i7 processors. + &os;/&arch.amd64; includes those using the + &intel; EM64T architecture. Examples of these + processors include the &intel; &core; 2 Duo, Quad, + Extreme processor families, the &intel; &xeon; 3000, + 5000, and 7000 sequences of processors, and the + &intel; &core; i3, i5 and i7 processors. If you have a machine based on an nVidia nForce3 Pro-150, you must use the BIOS setup to @@ -153,8 +157,8 @@ &os;/&arch.powerpc; &apple; &macintosh; All New World &apple; &macintosh; systems with built-in - USB are supported. SMP is supported on machines with multiple - CPUs. + USB are supported. SMP is supported on machines with + multiple CPUs. A 32-bit kernel can only use the first 2 GB of RAM. &firewire; is not supported on the Blue & White PowerMac @@ -165,11 +169,12 @@ &os;/&arch.sparc64; Systems supported by &os;/&arch.sparc64; are listed at - the - FreeBSD/sparc64 Project. + the + FreeBSD/sparc64 Project. - A dedicated disk is required for &os;/&arch.sparc64;. It - is not possible to share a disk with another operating + A dedicated disk is required for &os;/&arch.sparc64;. + It is not possible to share a disk with another operating system at this time. @@ -182,8 +187,8 @@ HARDWARE.TXT, the file is located in the root directory of the release media. Copies of the supported hardware list are also available on the Release - Information page of the &os; web site. + url="http://www.FreeBSD.org/releases/index.html">Release + Information page of the &os; web site. @@ -210,142 +215,151 @@ layout is useful during the installation. >>> TRUNCATED FOR MAIL (1000 lines) <<<