From owner-p4-projects@FreeBSD.ORG Sun Jun 19 13:06:24 2011 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id B9180106566C; Sun, 19 Jun 2011 13:06:24 +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 7B0F4106564A for ; Sun, 19 Jun 2011 13:06:24 +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 66CF08FC0A for ; Sun, 19 Jun 2011 13:06:24 +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 p5JD6O4M012978 for ; Sun, 19 Jun 2011 13:06:24 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id p5JD6N7K012975 for perforce@freebsd.org; Sun, 19 Jun 2011 13:06:23 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 19 Jun 2011 13:06:23 GMT Message-Id: <201106191306.p5JD6N7K012975@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 194971 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, 19 Jun 2011 13:06:25 -0000 http://p4web.freebsd.org/@@194971?ac=10 Change 194971 by rene@rene_acer on 2011/06/19 13:05:51 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#40 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#93 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#62 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/hubs/article.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#35 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#37 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#27 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#21 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#8 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#38 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#27 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#18 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#107 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#56 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#41 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/disks/chapter.sgml#28 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.sgml#15 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/jails/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#60 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.sgml#20 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.sgml#40 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#21 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/glossary/freebsd-glossary.sgml#11 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/teams.ent#6 integrate .. //depot/projects/docproj_nl/share/pgpkeys/brix.key#3 integrate .. //depot/projects/docproj_nl/share/pgpkeys/erwin.key#2 integrate .. //depot/projects/docproj_nl/share/pgpkeys/jlaffaye.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#55 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#52 integrate .. //depot/projects/docproj_nl/share/pgpkeys/ray.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/stephen.key#1 branch .. //depot/projects/docproj_nl/share/sgml/man-refs.ent#30 integrate .. //depot/projects/docproj_nl/share/sgml/mirrors.xml#26 integrate .. //depot/projects/docproj_nl/www/en/FAQ/index.html#2 integrate .. //depot/projects/docproj_nl/www/en/Makefile#2 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#57 integrate .. //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#27 integrate .. //depot/projects/docproj_nl/www/en/handbook/index.html#2 integrate .. //depot/projects/docproj_nl/www/en/index.xsl#8 integrate .. //depot/projects/docproj_nl/www/en/ipv6/IPv6-badge-blue-128-trans.png#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/IPv6-badge-blue-256-trans.png#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/Makefile#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/Makefile.inc#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/index.sgml#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/ipv6.ent#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/ipv6only.sgml#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/w6d-www-stats-large.png#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/w6d-www-stats-v6-large.png#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/w6d-www-stats-v6.png#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/w6d-www-stats.png#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/w6d-www-stats.sgml#1 branch .. //depot/projects/docproj_nl/www/en/ipv6/w6d.sgml#1 branch .. //depot/projects/docproj_nl/www/en/java/install.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/layout/css/layout.css#2 integrate .. //depot/projects/docproj_nl/www/en/multimedia/multimedia-input.xml#8 integrate .. //depot/projects/docproj_nl/www/en/news/2000/press.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/2001/news.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/2001/press.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2001-07.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2002-11-2002-12.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2003-03-2003-09.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2004-07-2004-12.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2005-03-2005-06.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2005-07-2005-10.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2005-10-2005-12.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2006-01-2006-03.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2006-04-2006-06.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2006-06-2006-10.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2007-04-2007-06.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2007-07-2007-10.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2007-10-2007-12.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2008-01-2008-03.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2008-04-2008-06.xml#2 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2009-04-2009-09.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2009-10-2009-12.xml#5 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2010-01-2010-03.xml#3 integrate .. //depot/projects/docproj_nl/www/en/news/status/report-2010-04-2010-06.xml#2 integrate .. //depot/projects/docproj_nl/www/en/platforms/ia64/todo.xsl#4 integrate .. //depot/projects/docproj_nl/www/en/portmgr/policies_eol.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/projects/c99/index.sgml#5 integrate .. //depot/projects/docproj_nl/www/en/projects/cvsweb.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/projects/ideas/ideas.xml#13 integrate .. //depot/projects/docproj_nl/www/en/projects/summerofcode-2007.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/projects/summerofcode-2008.sgml#4 integrate .. //depot/projects/docproj_nl/www/en/projects/summerofcode.xsl#9 integrate .. //depot/projects/docproj_nl/www/en/releases/7.0R/relnotes.html#2 integrate .. //depot/projects/docproj_nl/www/en/search/web.atoz#6 integrate .. //depot/projects/docproj_nl/www/nl/Makefile#15 integrate .. //depot/projects/docproj_nl/www/nl/administration.sgml#32 integrate .. //depot/projects/docproj_nl/www/share/sgml/advisories.xml#22 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.consult.xml#29 integrate .. //depot/projects/docproj_nl/www/share/sgml/events.xml#40 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#110 integrate .. //depot/projects/docproj_nl/www/share/sgml/usergroups.xml#23 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#40 (text+ko) ==== @@ -9,7 +9,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.299 2011/05/14 20:44:31 hrs Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.300 2011/06/16 19:40:12 simon Exp $ 1999 @@ -60,52 +60,44 @@ + + - Main CVS Repository Host - ncvs.FreeBSD.org - - - - Main Subversion Repository Host - svn.FreeBSD.org - - - Login Methods &man.ssh.1;, protocol 2 only - Main CVSROOT - - ncvs.FreeBSD.org:/home/ncvs (although also see ). - + Main Shell Host + freefall.FreeBSD.org Main Subversion Root - svn+ssh://svn.FreeBSD.org/base (although also see ). + svn+ssh://svn.FreeBSD.org/base (see also ). - Main &a.cvsadm; - &a.peter; and &a.simon;, as well as &a.joe; and &a.marcus; for - ports/ + Main CVSROOT's + + + dcvs.FreeBSD.org:/home/dcvs, + pcvs.FreeBSD.org:/home/pcvs + (see also ). + + - &a.bugmeister; - &a.gavin; &a.linimon;, &a.remko;, and &a.vwe . - + Internal Mailing Lists - - Mailing Lists - &a.doc-developers;, &a.doc-committers;; - &a.ports-developers;, &a.ports-committers;; - &a.src-developers;, &a.src-committers;. (Each project + developers (technically called all-developers), + doc-developers, doc-committers, ports-developers, + ports-committers, src-developers, src-committers. + (Each project repository has its own -developers and -committers mailing lists. Archives for these lists may be found in files /home/mail/repository-name-developers-archive @@ -125,11 +117,10 @@ - Noteworthy CVSup Tags - - RELENG_7 (7.X-STABLE), - RELENG_8 (8.X-STABLE), - HEAD (-CURRENT) + Ports Management Team monthly + reports + /home/portmgr/public/monthly-reports + on the FreeBSD.org cluster. @@ -146,16 +137,24 @@ - It is required that you use &man.ssh.1; or &man.telnet.1; - with Kerberos 5 to connect to the project hosts. For - &man.ssh.1; only protocol 2 is allowed. - These are generally more secure than plain &man.telnet.1; or - &man.rlogin.1; since credential negotiation will always be - encrypted. All traffic is encrypted by default with &man.ssh.1;. - With utilities like &man.ssh-agent.1; and &man.scp.1; also - available, &man.ssh.1; is also far more convenient. If you do + It is required that you use &man.ssh.1; + to connect to the project hosts. + If you do not know anything about &man.ssh.1;, please see . + + Useful links: + + + FreeBSD + Project Internal Pages + + FreeBSD + Project Hosts + + FreeBSD + Project Administrative Groups + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#93 (text+ko) ==== @@ -1,4 +1,4 @@ - + + @@ -252,30 +252,27 @@ A number of strategies may be applied in clustered applications to separate site-wide configuration from system-specific configuration in order to keep administration - overhead down. The recommended approach is to place site-wide - configuration into another file, - such as /etc/rc.conf.site, and then include - this file into /etc/rc.conf, which will - contain only system-specific information. + overhead down. The recommended approach is to place + system-specific configuration into the + /etc/rc.conf.local file. For + example: + + + /etc/rc.conf: + + sshd_enable="YES" +keyrate="fast" +defaultrouter="10.1.1.254" - As rc.conf is read by &man.sh.1; it is - trivial to achieve this. For example: + /etc/rc.conf.local: - - rc.conf: - . /etc/rc.conf.site - hostname="node15.example.com" - network_interfaces="fxp0 lo0" - ifconfig_fxp0="inet 10.1.1.1" - rc.conf.site: - defaultrouter="10.1.1.254" - saver="daemon" - blanktime="100" +hostname="node1.example.org" +ifconfig_fxp0="inet 10.1.1.1/8" - The rc.conf.site file can then be + The rc.conf file can then be distributed to every system using rsync or a - similar program, while the rc.conf file + similar program, while the rc.conf.local file remains unique. Upgrading the system using &man.sysinstall.8; @@ -283,6 +280,13 @@ rc.conf file, so system configuration information will not be lost. + + The /etc/rc.conf configuration file + is parsed by &man.sh.1;. This allows system operators to + add a certain amount of logic to this file, which may help to + create very complex configuration scenarios. Please see + &man.rc.conf.5; for further information on this topic. + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#27 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -302,18 +302,18 @@ load the new binaries into memory. The freebsd-update utility can - automatically update the GENERIC kernel only. + automatically update the GENERIC kernel only. If a custom kernel is in use, it will have to be rebuilt and reinstalled after freebsd-update finishes installing the rest of the updates. However, freebsd-update will detect and update the - GENERIC kernel in GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. It is a good idea to always keep a copy of the - GENERIC kernel in GENERIC kernel in /boot/GENERIC. It will be helpful in diagnosing a variety of problems, and in performing version upgrades using freebsd-update as described in @@ -366,24 +366,24 @@ manual intervention during the build process. If a custom kernel is in use, the upgrade process is slightly - more involved. A copy of the GENERIC kernel is + more involved. A copy of the GENERIC kernel is needed, and it should be placed in /boot/GENERIC. If the - GENERIC kernel is not already present in the + GENERIC kernel is not already present in the system, it may be obtained using one of the following methods: If a custom kernel has only been built once, the kernel in /boot/kernel.old is - actually the GENERIC one. Simply rename this + actually the GENERIC one. Simply rename this directory to /boot/GENERIC. Assuming physical access to the machine is possible, a copy - of the GENERIC kernel can be installed from + of the GENERIC kernel can be installed from the CD-ROM media. Insert your installation disc and use the following commands: @@ -394,12 +394,12 @@ Replace X.Y-RELEASE with the actual version of the release you are using. The - GENERIC kernel will be installed in GENERIC kernel will be installed in /boot/GENERIC by default. - Failing all the above, the GENERIC kernel + Failing all the above, the GENERIC kernel may be rebuilt and installed from the sources: &prompt.root; cd /usr/src @@ -407,16 +407,16 @@ &prompt.root; mv /boot/GENERIC/boot/kernel/* /boot/GENERIC &prompt.root; rm -rf /boot/GENERIC/boot - For this kernel to be picked up as GENERIC + For this kernel to be picked up as GENERIC by freebsd-update, the - GENERIC configuration file must not have been + GENERIC configuration file must not have been modified in any way. It is also suggested that it is built without any other special options (preferably with an empty /etc/make.conf). - Rebooting to the GENERIC kernel is not + Rebooting to the GENERIC kernel is not required at this stage. Major and minor version updates may be performed by @@ -464,7 +464,7 @@ before running "/usr/sbin/freebsd-update install" This warning may be safely ignored at this point. The updated - GENERIC kernel will be used as an intermediate + GENERIC kernel will be used as an intermediate step in the upgrade process. After all patches have been downloaded to the local @@ -504,13 +504,13 @@ &prompt.root; nextboot -k GENERIC - Before rebooting with the GENERIC kernel, + Before rebooting with the GENERIC kernel, make sure it contains all drivers required for your system to boot properly (and connect to the network, if the machine that is being updated is accessed remotely). In particular, if the previously running custom kernel contained built-in functionality usually provided by kernel modules, make sure to temporarily load these - modules into the GENERIC kernel using the + modules into the GENERIC kernel using the /boot/loader.conf facility. You may also wish to disable non-essential services, disk and network mounts, etc. until the upgrade process is complete. @@ -557,7 +557,7 @@ &prompt.root; freebsd-update install - If the GENERIC kernel was temporarily used, + If the GENERIC kernel was temporarily used, this is the time to build and install a new custom kernel in the usual way. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#21 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -200,8 +200,9 @@ 2^32-1 and a length of no more than 2^32-1, limiting partitions to 2TB and disks to 4TB in most cases. The &man.sunlabel.8; format is limited to 2^32-1 sectors per partition and 8 partitions for - a total of 16TB. For larger disks, &man.gpt.8; partitions may be - used. + a total of 16TB. For larger disks, &man.gpart.8; may be used to + create GPT partitions. GPT + has the added benefit of not being limited to 4 slices. Using &man.sysinstall.8; @@ -3024,7 +3025,7 @@ Some administrators will use a snapshot file for backup purposes, - because the snapshot can be transfered to CDs or tape. + because the snapshot can be transferred to CDs or tape. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#13 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1494,10 +1494,8 @@ the &os; boot loader. You can access this when the system boot menu appears. Select the Escape to a loader prompt option, number six. At the prompt, type - unload kernel - and then type - boot /boot/kernel.old/kernel, - or the filename of any other kernel that will boot properly. + boot kernel.old, + or the name of any other kernel that will boot properly. When reconfiguring a kernel, it is always a good idea to keep a kernel that is known to work on hand. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#8 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -321,6 +321,10 @@ courier-imap; + + + dovecot; + @@ -345,8 +349,9 @@ username and password credentials in clear-text. This means that if you wish to secure the transmission of information across these protocols, you should consider tunneling - sessions over &man.ssh.1;. Tunneling sessions is - described in . + sessions over &man.ssh.1; or using SSL. Tunneling sessions is + described in and SSL is + described in . ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#38 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -232,12 +232,6 @@ mirror site (especially if you decide to set up some sort of mirror site). - The &os; mirror - sites database is more accurate than the mirror listing in the - Handbook, as it gets its information from the DNS rather than relying on - static lists of hosts. - Additionally, &os; is available via anonymous FTP from the following mirror sites. If you choose to obtain &os; via anonymous FTP, please try to use a site near you. The mirror sites listed as @@ -3221,6 +3215,20 @@ + Sweden + + + rsync://ftp4.se.freebsd.org/ + + Available collections: + + &os;: A full mirror of the &os; FTP + server. + + + + + Taiwan ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml#13 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -353,6 +353,47 @@ + + Another issue is that modern graphics cards often come with their + own sound driver, for use with HDMI and similar. + This sound device will sometimes be enumerated before the actual + soundcard and the soundcard will subsequently not be used as the + default playback device. To check if this is the case, run + dmesg and look for pcm. + The output looks something like this: + +... +hdac0: HDA Driver Revision: 20100226_0142 +hdac1: HDA Driver Revision: 20100226_0142 +hdac0: HDA Codec #0: NVidia (Unknown) +hdac0: HDA Codec #1: NVidia (Unknown) +hdac0: HDA Codec #2: NVidia (Unknown) +hdac0: HDA Codec #3: NVidia (Unknown) +pcm0: <HDA NVidia (Unknown) PCM #0 DisplayPort> at cad 0 nid 1 on hdac0 +pcm1: <HDA NVidia (Unknown) PCM #0 DisplayPort> at cad 1 nid 1 on hdac0 +pcm2: <HDA NVidia (Unknown) PCM #0 DisplayPort> at cad 2 nid 1 on hdac0 +pcm3: <HDA NVidia (Unknown) PCM #0 DisplayPort> at cad 3 nid 1 on hdac0 +hdac1: HDA Codec #2: Realtek ALC889 +pcm4: <HDA Realtek ALC889 PCM #0 Analog> at cad 2 nid 1 on hdac1 +pcm5: <HDA Realtek ALC889 PCM #1 Analog> at cad 2 nid 1 on hdac1 +pcm6: <HDA Realtek ALC889 PCM #2 Digital> at cad 2 nid 1 on hdac1 +pcm7: <HDA Realtek ALC889 PCM #3 Digital> at cad 2 nid 1 on hdac1 +... + + Here the graphics card (NVidia) has been + enumerated before the sound card (Realtek ALC889). + To use the sound card as default playback device, change + hw.snd.default_unit to the unit that should be used + for playback, enter the following: + + &prompt.root; sysctl hw.snd.default_unit=n + + Here, n is the number of the sound device to + use, in this example 4. You can make this change + permanent by adding the following line to + /etc/sysctl.conf: + + hw.snd.default_unit=4 ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#27 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -3643,7 +3643,7 @@ 10800 ; Refresh 3600 ; Retry 604800 ; Expire - 300 ; Negative Reponse TTL + 300 ; Negative Response TTL ) ; DNS Servers @@ -3727,7 +3727,7 @@ 10800 ; Refresh after 3 hours 3600 ; Retry after 1 hour 604800 ; Expire after 1 week - 300 ) ; Negative Reponse TTL + 300 ) ; Negative Response TTL @@ -3839,7 +3839,7 @@ 10800 ; Refresh 3600 ; Retry 604800 ; Expire - 300 ) ; Negative Reponse TTL + 300 ) ; Negative Response TTL IN NS ns1.example.org. IN NS ns2.example.org. @@ -3872,6 +3872,333 @@ + <acronym + role="Doman Name Security Extensions">DNSSEC</acronym> + + BIND + DNS security extensions + + + Domain Name System Security Extensions, or DNSSEC for short, is a + suite of specifications to protect resolving name servers from forged + DNS data, such as spoofed DNS + records. By using digital signatures, a resolver can verify the + integrity of the record. Note that DNSSEC only provides + integrity via digitally signing the Resource Records (RRs). It provides neither + confidentiality nor protection against false end-user assumptions. + This means that it cannot protect against people going to example.net instead of example.com. The only thing + DNSSEC does is authenticate that the data has not + been compromised in transit. The security of DNS is >>> TRUNCATED FOR MAIL (1000 lines) <<<