From owner-svn-doc-projects@FreeBSD.ORG Mon Apr 22 13:43:25 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D94FD5FC; Mon, 22 Apr 2013 13:43:25 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id CB95C1C22; Mon, 22 Apr 2013 13:43:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3MDhP83062330; Mon, 22 Apr 2013 13:43:25 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3MDhP1w062329; Mon, 22 Apr 2013 13:43:25 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304221343.r3MDhP1w062329@svn.freebsd.org> From: Dru Lavigne Date: Mon, 22 Apr 2013 13:43:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41467 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/kernelconfig X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 13:43:25 -0000 Author: dru Date: Mon Apr 22 13:43:24 2013 New Revision: 41467 URL: http://svnweb.freebsd.org/changeset/doc/41467 Log: Delete ADAPTIVE_GIANT option and fix duplicate colon and an extra space. Submitted by: ryusuke Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml Sun Apr 21 17:51:16 2013 (r41466) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml Mon Apr 22 13:43:24 2013 (r41467) @@ -195,7 +195,7 @@ psm0: model Generic PS/2 mouse, device I The flag, when passed to &man.man.1; can be used to provide useful information. For example, to display a list of manual pages which contain the specified - word:: + word: &prompt.root; man -k Atheros @@ -693,7 +693,7 @@ options NFS_ROOT # NFS Adds support for GUID - Partition Tables (GPT. GPT + Partition Tables (GPT). GPT provides the ability to have a large number of partitions per disk, 128 in the standard configuration. @@ -776,29 +776,6 @@ options NFS_ROOT # NFS device nodes in /dev. - options ADAPTIVE_GIANT # Giant mutex is adaptive. - - Giant is the name of a mutual exclusion mechanism, a - sleep mutex, that protects a large set of kernel resources. - Today, this is an unacceptable performance bottleneck which - is actively being replaced with locks that protect individual - resources. The ADAPTIVE_GIANT option causes - Giant to be included in the set of mutexes adaptively spun on. - When a thread wants to lock the Giant mutex, but it is already - locked by a thread on another CPU, the first thread will keep - running and wait for the lock to be released. Normally, the - thread would instead go back to sleep and wait for its next - chance to run. If unsure, leave this in. - - - Beginning with &os; 8.0, all mutexes are adaptive by - default, unless explicitly set to non-adaptive by compiling - with the NO_ADAPTIVE_MUTEXES option. As a - result, Giant is adaptive by default now, and the - ADAPTIVE_GIANT option has been removed - from the kernel configuration. - - kernel options SMP @@ -1439,7 +1416,7 @@ device fwe # Ethernet mechanism for recovering from incompatible kernels. Simply choose the kernel to boot from at the &os; boot loader. This can be accessed when the system boot menu - appears by selecting the Escape to a loader + appears by selecting the Escape to a loader prompt option. At the prompt, type boot kernel.old, or From owner-svn-doc-projects@FreeBSD.ORG Mon Apr 22 16:14:28 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EDA608EF; Mon, 22 Apr 2013 16:14:28 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DF3CC1445; Mon, 22 Apr 2013 16:14:28 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3MGESgS010236; Mon, 22 Apr 2013 16:14:28 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3MGESLI010235; Mon, 22 Apr 2013 16:14:28 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304221614.r3MGESLI010235@svn.freebsd.org> From: Dru Lavigne Date: Mon, 22 Apr 2013 16:14:28 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41470 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 16:14:29 -0000 Author: dru Date: Mon Apr 22 16:14:28 2013 New Revision: 41470 URL: http://svnweb.freebsd.org/changeset/doc/41470 Log: Initial patch which fixes the following: - &os; - missing PPP, PPPoE, PPPoA, and ISP acronym tags - small grammo fixes I happened to notice in the paragraphs affected by those tags (most of these paragraphs still need rewording) Subsequent patches will format ppp as a command more consistently and work on outstanding grammo, rewording, and formatting fixes. This chapter needs a lot of work. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Apr 22 14:43:01 2013 (r41469) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Apr 22 16:14:28 2013 (r41470) @@ -29,25 +29,25 @@ SLIP - FreeBSD has a number of ways to link one computer to - another. To establish a network or Internet connection through - a dial-up modem, or to allow others to do so through you, - requires the use of PPP. This chapter describes setting - up these modem-based communication services in detail. + &os; has a number of ways to link one computer to another. + To establish a network or Internet connection through a dial-up + modem, or to allow others to do so through that modem, requires + the use of PPP. This chapter details how + to set up modem-based communication services. After reading this chapter, you will know: - How to set up user PPP. + How to configure PPP. - How to set up PPPoE (PPP over - Ethernet). + How to set up PPPoE + (PPP over Ethernet). - How to set up PPPoA (PPP over - ATM). + How to set up PPPoA + (PPP over ATM). @@ -55,10 +55,6 @@ PPP user PPP - - PPP - kernel PPP - PPP over Ethernet @@ -72,7 +68,7 @@ Understand the basics and purpose of a dialup connection - and PPP. + and PPP. @@ -110,10 +106,10 @@ - Using User PPP + Using <acronym>PPP</acronym> - User PPP + User <acronym>PPP</acronym> Assumptions @@ -128,18 +124,20 @@ PPP - An account with an Internet Service Provider (ISP) - which you connect to using PPP. + An account with an Internet Service Provider + (ISP) which you connect to using + PPP. - A modem or - other device connected to your system and properly - configured to allow you to connect to your ISP. + A modem or other device connected to the &os; system + and properly configured to connect to the + ISP. - The dial-up number(s) of your ISP. + The dial-up number(s) of the + ISP. @@ -170,26 +168,29 @@ The IP address of one or more name servers. Normally, you will be given two IP addresses by your - ISP to use for this. If they have not given you at - least one, then you can use the enable - dns command in ppp.conf - and ppp will set the name - servers for you. This feature depends on your ISPs - PPP implementation supporting DNS negotiation. + ISP. If they have not given you at + least one, use the enable dns command + in ppp.conf and + ppp will set the name + servers. This feature depends on the + ISP's PPP + implementation supporting DNS negotiation. - The following information may be supplied by your ISP, - but is not completely necessary: + The following information may be supplied by the + ISP, but is not completely + necessary: - The IP address of your ISP's gateway. The gateway - is the machine to which you will connect and will be - set up as your default route. If - you do not have this information, we can make one up - and your ISP's PPP server will tell us the correct value - when we connect. + The IP address of your ISP's + gateway. The gateway is the machine to which you will + connect and will be set up as your default + route. If you do not have this + information, we can make one up and your + ISP's PPP server + will tell us the correct value when we connect. This IP number is referred to as HISADDR by @@ -197,8 +198,9 @@ - The netmask you should use. If your ISP has not - provided you with one, you can safely use The netmask you should use. If the + ISP has not provided you with one, + you can safely use 255.255.255.255. @@ -207,15 +209,14 @@ static IP address - If your ISP provides you with a static IP address - and hostname, you can enter it. Otherwise, we simply - let the peer assign whatever IP address it sees - fit. + If the ISP provides a static IP + address and hostname, enter it. Otherwise, let the peer + assign whatever IP address it sees fit. If you do not have any of the required information, - contact your ISP. + contact your ISP. Throughout this section, many of the examples showing @@ -229,7 +230,7 @@ - Automatic <application>PPP</application> + <title>Automatic <acronym>PPP</acronym> Configuration @@ -245,13 +246,14 @@ Configuring ppp requires that you edit a number of files, depending on your requirements. What you put in them depends to some extent on whether your - ISP allocates IP addresses statically (i.e., you get given - one IP address, and always use that one) or dynamically - (i.e., your IP address changes each time you connect to - your ISP). + ISP allocates IP addresses statically + (i.e., you get given one IP address, and always use that + one) or dynamically (i.e., your IP address changes each time + you connect). - PPP and Static IP Addresses + <acronym>PPP</acronym> and Static IP + Addresses PPP @@ -318,12 +320,11 @@ Line 3: - Tells PPP how to identify itself to the peer. - PPP identifies itself to the peer if it has any - trouble negotiating and setting up the link, - providing information that the peers administrator - may find useful when investigating such - problems. + Tells PPP how to identify + itself to the peer if it has any trouble negotiating + and setting up the link. This information may be + useful to the peer's administrator when + investigating such problems. @@ -360,10 +361,10 @@ user PPP - The dial string. User PPP uses an expect-send - syntax similar to the &man.chat.8; program. Refer - to the manual page for information on the features - of this language. + The dial string. PPP uses an + expect-send syntax similar to the one used by + &man.chat.8;. Refer to &man.chat.8; for information + on the features of this language. Note that this command continues onto the next line for readability. Any command in @@ -387,9 +388,10 @@ Line 9: - Tells PPP to ask the peer to confirm the local - resolver settings. If you run a local name server, - this line should be commented out or removed. + Tells PPP to ask the peer to + confirm the local resolver settings. When running a + local name server, this line should be commented out + or removed. @@ -398,7 +400,7 @@ A blank line for readability. Blank lines are - ignored by PPP. + ignored by PPP. @@ -506,18 +508,17 @@ protocol: ppp replaced by the IP address that your provider has allocated to you. The string y.y.y.y should be - replaced by the IP address that your ISP indicated - for their gateway (the machine to which you - connect). If your ISP has not given you a gateway - address, use ISP's gateway. If the ISP has + not given you a gateway address, use 10.0.0.2/0. If you need to use a guessed address, make sure that you create an entry in /etc/ppp/ppp.linkup as per the instructions for PPP and Dynamic IP - addresses. If this line is omitted, - ppp cannot run in + linkend="userppp-dynamicIP">PPP + and Dynamic IP addresses. If this line is + omitted, ppp cannot run in mode. @@ -526,10 +527,11 @@ protocol: ppp Line 18: - Adds a default route to your ISP's gateway. The - special word HISADDR is replaced - with the gateway address specified on line 17. It - is important that this line appears after line 17, + Adds a default route to the + ISP's gateway. The special word + HISADDR is replaced with the + gateway address specified on line 17. It is + important that this line appears after line 17, otherwise HISADDR will not yet be initialized. @@ -555,7 +557,8 @@ protocol: ppp - PPP and Dynamic IP Addresses + <acronym>PPP</acronym> and Dynamic IP + Addresses PPP @@ -573,8 +576,9 @@ protocol: ppp ppp to set it up correctly using the IP Configuration Protocol (IPCP) after connecting. The ppp.conf configuration is the same as - PPP and Static IP - Addresses, with the following change: + PPP + and Static IP Addresses, with the following + change: 17 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 @@ -594,14 +598,14 @@ protocol: ppp above example will always work. The last argument (0.0.0.0) - tells PPP to start negotiations using address - 0.0.0.0 rather than - 10.0.0.1 and is - necessary for some ISPs. Do not use - 0.0.0.0 as the first argument - to set ifaddr as it prevents - PPP from setting up an initial route in - mode. + tells PPP to start negotiations + using address 0.0.0.0 + rather than 10.0.0.1 + and is necessary for some ISPs. + Do not use 0.0.0.0 as the first + argument to set ifaddr as it + prevents PPP from setting up an + initial route in mode. @@ -680,7 +684,7 @@ protocol: ppp Which getty? - Configuring FreeBSD for + Configuring &os; for Dial-up Services provides a good description on enabling dial-up services using &man.getty.8;. @@ -698,8 +702,8 @@ protocol: ppp Later versions of mgetty (from 0.99beta onwards) also support the automatic detection of - PPP streams, allowing your clients script-less access to - your server. + PPP streams, allowing your clients + script-less access to your server. Refer to Mgetty and AutoPPP for more information on @@ -707,7 +711,7 @@ protocol: ppp - <application>PPP</application> Permissions + <acronym>PPP</acronym> Permissions The ppp command must normally be run as the root user. If however, @@ -730,7 +734,8 @@ protocol: ppp - PPP Shells for Dynamic-IP Users + <acronym>PPP</acronym> Shells for Dynamic-IP + Users PPP shells @@ -763,7 +768,7 @@ exec /usr/sbin/ppp -direct $IDENTYou should use this script as the shell for all of your dialup users. This is an example from /etc/passwd - for a dialup PPP user with username + for a dialup PPP user with username pchilds (remember do not directly edit the password file, use &man.vipw.8;). @@ -782,7 +787,8 @@ exec /usr/sbin/ppp -direct $IDENT - PPP Shells for Static-IP Users + <acronym>PPP</acronym> Shells for Static-IP + Users PPP shells @@ -894,10 +900,11 @@ mary: role="package">comms/mgetty+sendfax port comes with the AUTO_PPP option enabled allowing mgetty to detect the LCP - phase of PPP connections and automatically spawn off a - ppp shell. However, since the default login/password - sequence does not occur it is necessary to authenticate - users using either PAP or CHAP. + phase of PPP connections and + automatically spawn off a ppp shell. However, since the + default login/password sequence does not occur it is + necessary to authenticate users using either PAP or + CHAP. This section assumes the user has successfully compiled, and installed the This will tell mgetty to run the ppp-pap-dialup script for detected - PPP connections. + PPP connections. Create a file called /etc/ppp/ppp-pap-dialup containing @@ -964,18 +971,21 @@ exec /usr/sbin/ppp -direct pap$IDENTMicrosoft extensions - It is possible to configure PPP to supply DNS and - NetBIOS nameserver addresses on demand. - - To enable these extensions with PPP version 1.x, the - following lines might be added to the relevant section - of /etc/ppp/ppp.conf. + It is possible to configure PPP to + supply DNS and NetBIOS nameserver addresses on + demand. + + To enable these extensions with PPP + version 1.x, the following lines might be added to the + relevant section of + /etc/ppp/ppp.conf. enable msext set ns 203.14.100.1 203.14.100.2 set nbns 203.14.100.5 - And for PPP version 2 and above: + And for PPP version 2 and + above: accept dns set dns 203.14.100.1 203.14.100.2 @@ -986,8 +996,8 @@ set nbns 203.14.100.5 host. In version 2 and above, if the - set dns line is omitted, PPP will - use the values found in + set dns line is omitted, + PPP will use the values found in /etc/resolv.conf. @@ -996,12 +1006,13 @@ set nbns 203.14.100.5 PAP CHAP - Some ISPs set their system up so that the - authentication part of your connection is done using - either of the PAP or CHAP authentication mechanisms. If - this is the case, your ISP will not give a - login: prompt when you connect, but will - start talking PPP immediately. + Some ISPs set their system up so + that the authentication part of the connection is done + using either the PAP or CHAP authentication mechanism. If + this is the case, the ISP will not give + a login: prompt when you connect, but + will start talking PPP + immediately. PAP is less secure than CHAP, but security is not normally an issue here as passwords, although being sent @@ -1010,11 +1021,11 @@ set nbns 203.14.100.5 to eavesdrop. Referring back to the PPP and Static IP - addresses or PPP and Dynamic IP - addresses sections, the following alterations must - be made: + linkend="userppp-staticIP">PPP and + Static IP addresses or PPP and + Dynamic IP addresses sections, the following + alterations must be made: 13 set authname MyUserName 14 set authkey MyPassword @@ -1057,10 +1068,10 @@ set nbns 203.14.100.5 Line 15: - Your ISP will not normally require that you log - into the server if you are using PAP or CHAP. You - must therefore disable your set login - string. + Your ISP will not normally + require you to log into the server when using PAP or + CHAP. You must therefore disable your set + login string. @@ -1077,9 +1088,9 @@ set nbns 203.14.100.5 set server /var/run/ppp-tun%d DiagnosticPassword 0177 - This will tell PPP to listen to the specified - &unix; domain socket, asking clients for the specified - password before allowing access. The + This will tell PPP to listen to the + specified &unix; domain socket, asking clients for the + specified password before allowing access. The %d in the name is replaced with the tun device number that is in use. @@ -1091,23 +1102,23 @@ set nbns 203.14.100.5 - Using PPP Network Address Translation - Capability + Using <acronym>PPP</acronym> Network Address + Translation Capability PPPNAT - PPP has ability to use internal NAT without kernel - diverting capabilities. This functionality may be enabled - by the following line in + PPP has the ability to use internal + NAT without kernel diverting capabilities. This + functionality may be enabled by the following line in /etc/ppp/ppp.conf: nat enable yes - Alternatively, PPP NAT may be enabled by command-line - option -nat. There is also - /etc/rc.conf knob named + Alternatively, PPP NAT may be enabled + by command-line option -nat. There is + also /etc/rc.conf knob named ppp_nat, which is enabled by default. @@ -1140,14 +1151,15 @@ nat port tcp 10.0.0.2:http httphostname="foo.example.com" - If your ISP has supplied you with a static IP address - and name, it is probably best that you use this name as your - host name. + If the ISP has supplied a static IP + address and name, it is probably best that you use this name + as your host name. Look for the network_interfaces variable. If you want to configure your system to dial your - ISP on demand, make sure the tun0 - device is added to the list, otherwise remove it. + ISP on demand, make sure the + tun0 device is added to the list, + otherwise remove it. network_interfaces="lo0 tun0" ifconfig_tun0= @@ -1223,9 +1235,9 @@ ifconfig_tun0= &prompt.root; ppp and then dial provider to start the - PPP session, or, if you want ppp to - establish sessions automatically when there is outbound - traffic (and you have not created the + PPP session, or, if you want + ppp to establish sessions automatically + when there is outbound traffic (and you have not created the start_if.tun0 script), type: &prompt.root; ppp -auto provider @@ -1256,7 +1268,7 @@ ifconfig_tun0= Create an entry in /etc/ppp/ppp.conf. The pmdemand example should suffice - for most ISPs. + for most ISPs. @@ -1342,9 +1354,10 @@ ifconfig_tun0= This section covers a few issues which may arise when - using PPP over a modem connection. For instance, perhaps you - need to know exactly what prompts the system you are dialing - into will present. Some ISPs present the + using PPP over a modem connection. For + instance, perhaps you need to know exactly what prompts the + system you are dialing into will present. Some + ISPs present the ssword prompt, and others will present password; if the ppp script is not written accordingly, the login attempt will @@ -1609,7 +1622,8 @@ nameserver y.y.y.y - Using PPP over Ethernet (PPPoE) + Using <acronym>PPP</acronym> over Ethernet + (<acronym>PPPoE</acronym>) PPP @@ -1621,15 +1635,15 @@ nameserver y.y.y.yPPP, over Ethernet - This section describes how to set up PPP over Ethernet - (PPPoE). + This section describes how to set up PPP + over Ethernet (PPPoE). Configuring the Kernel - No kernel configuration is necessary for PPPoE any longer. - If the necessary netgraph support is not built into the - kernel, it will be dynamically loaded by + No kernel configuration is necessary for + PPPoE. If the necessary netgraph support + is not built into the kernel, it will be dynamically loaded by ppp. @@ -1675,34 +1689,35 @@ ppp_profile="name_of_service_provider" - Using a PPPoE Service Tag + Using a <acronym>PPPoE</acronym> Service Tag Sometimes it will be necessary to use a service tag to establish your connection. Service tags are used to - distinguish between different PPPoE servers attached to a - given network. + distinguish between different PPPoE servers + attached to a given network. You should have been given any required service tag - information in the documentation provided by your ISP. If - you cannot locate it there, ask your ISP's tech support - personnel. + information in the documentation provided by the + ISP. If you cannot locate it there, ask + your ISP's tech support personnel. As a last resort, you could try the method suggested by the Roaring - Penguin PPPoE program which can be found in the Ports Collection. Bear in mind - however, this may de-program your modem and render it useless, - so think twice before doing it. Simply install the program - shipped with the modem by your provider. Then, access the - System menu from the program. The name - of your profile should be listed there. It is usually - ISP. - - The profile name (service tag) will be used in the PPPoE - configuration entry in ppp.conf as the - provider part of the set device command - (see the &man.ppp.8; manual page for full details). It should - look like this: + Penguin PPPoE program which can be + found in the Ports Collection. + Bear in mind however, this may de-program your modem and + render it useless, so think twice before doing it. Simply + install the program shipped with the modem by your provider. + Then, access the System menu from the + program. The name of your profile should be listed there. It + is usually ISP. + + The profile name (service tag) will be used in the + PPPoE configuration entry in + ppp.conf as the provider part of the + set device command (see the &man.ppp.8; + manual page for full details). It should look like + this: set device PPPoE:xl1:ISP @@ -1717,7 +1732,7 @@ ppp_profile="name_of_service_provider" Cheaper - Broadband with FreeBSD on DSL by Renaud + Broadband with &os; on DSL by Renaud Waldura. @@ -1725,21 +1740,22 @@ ppp_profile="name_of_service_provider" - PPPoE with a &tm.3com; + <title><acronym>PPPoE</acronym> with a &tm.3com; <trademark class="registered">HomeConnect</trademark> ADSL Modem Dual Link This modem does not follow RFC 2516 - (A Method for transmitting PPP over Ethernet - (PPPoE), written by L. Mamakos, K. Lidl, J. Evarts, - D. Carrel, D. Simone, and R. Wheeler). Instead, different - packet type codes have been used for the Ethernet frames. - Please complain to A Method for transmitting PPP + over Ethernet (PPPoE), written + by L. Mamakos, K. Lidl, J. Evarts, D. Carrel, D. Simone, and + R. Wheeler). Instead, different packet type codes have been + used for the Ethernet frames. Please complain to 3Com if you think it - should comply with the PPPoE specification. + should comply with the PPPoE + specification. - In order to make FreeBSD capable of communicating with + In order to make &os; capable of communicating with this device, a sysctl must be set. This can be done automatically at boot time by updating /etc/sysctl.conf: @@ -1751,17 +1767,17 @@ ppp_profile="name_of_service_provider"&prompt.root; sysctl net.graph.nonstandard_pppoe=1 Unfortunately, because this is a system-wide setting, - it is not possible to talk to a normal PPPoE client or server - and a &tm.3com; HomeConnect ADSL Modem at - the same time. + it is not possible to talk to a normal + PPPoE client or server and a &tm.3com; + HomeConnect ADSL + Modem at the same time. Using <application>PPP</application> over ATM - (PPPoA) + (PPPoA) PPP @@ -1773,17 +1789,20 @@ ppp_profile="name_of_service_provider"PPP, over ATM - The following describes how to set up PPP over ATM (PPPoA). - PPPoA is a popular choice among European DSL providers. + The following describes how to set up PPP + over ATM (PPPoA). PPPoA + is a popular choice among European DSL providers. - Using PPPoA with the Alcatel &speedtouch; USB + Using <acronym>PPPoA</acronym> with the Alcatel + &speedtouch; USB - PPPoA support for this device is supplied as a port in - FreeBSD because the firmware is distributed under PPPoA support for this device is + supplied as a port in &os; because the firmware is distributed + under Alcatel's license agreement and can not be redistributed freely - with the base system of FreeBSD. + with the base system of &os;. To install the software, simply use the Ports Collection. Install the @@ -1890,10 +1909,12 @@ adsl: - The username used to authenticate with your ISP. + The username used to authenticate with the + ISP. - The password used to authenticate with your ISP. + The password used to authenticate with the + ISP. @@ -1944,8 +1965,8 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNIN Using pptpclient - It is also possible to use FreeBSD to connect to other - PPPoA services using It is also possible to use &os; to connect to other + PPPoA services using net/pptpclient. To use net/pptpclient @@ -1991,14 +2012,14 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNIN - This will open a tunnel for a PPP session to your DSL - router. Ethernet DSL modems have a preconfigured LAN IP - address which you connect to. In the case of the Alcatel - &speedtouch; Home this address is 10.0.0.138. Your router - documentation should tell you which address your device - uses. To open the tunnel and start a PPP session execute - the following command: + This will open a tunnel for a PPP + session to the DSL router. Ethernet DSL modems have a + preconfigured LAN IP address which you connect to. In the + case of the Alcatel &speedtouch; Home, this address is 10.0.0.138. The router + documentation should tell you which address the device + uses. To open the tunnel and start a PPP + session execute the following command: &prompt.root; pptp address adsl From owner-svn-doc-projects@FreeBSD.ORG Mon Apr 22 18:01:08 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 757036BE; Mon, 22 Apr 2013 18:01:08 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 674C11AD3; Mon, 22 Apr 2013 18:01:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3MI18L1043891; Mon, 22 Apr 2013 18:01:08 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3MI182f043890; Mon, 22 Apr 2013 18:01:08 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304221801.r3MI182f043890@svn.freebsd.org> From: Dru Lavigne Date: Mon, 22 Apr 2013 18:01:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41471 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 18:01:08 -0000 Author: dru Date: Mon Apr 22 18:01:07 2013 New Revision: 41471 URL: http://svnweb.freebsd.org/changeset/doc/41471 Log: Make formatting for ppp command more consistent. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Apr 22 16:14:28 2013 (r41470) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Apr 22 18:01:07 2013 (r41471) @@ -171,7 +171,7 @@ ISP. If they have not given you at least one, use the enable dns command in ppp.conf and - ppp will set the name + ppp will set the name servers. This feature depends on the ISP's PPP implementation supporting DNS negotiation. @@ -194,7 +194,7 @@ This IP number is referred to as HISADDR by - ppp. + ppp. @@ -296,7 +296,8 @@ Identifies the default entry. Commands in this - entry are executed automatically when ppp is + entry are executed automatically when + ppp is run. @@ -535,8 +536,8 @@ protocol: ppp otherwise HISADDR will not yet be initialized. - If you do not wish to run ppp in - , this line should be moved + If you do not wish to run ppp + in , this line should be moved to the ppp.linkup file. @@ -544,11 +545,12 @@ protocol: ppp It is not necessary to add an entry to ppp.linkup when you have a static - IP address and are running ppp in - mode as your routing table entries are already correct - before you connect. You may however wish to create an - entry to invoke programs after connection. This is - explained later with the sendmail example. + IP address and are running ppp in + mode as your routing table entries + are already correct before you connect. You may however + wish to create an entry to invoke programs after + connection. This is explained later with the sendmail + example. Example configuration files can be found in the The number after the / character is the number of bits of the address that - ppp will insist on. You may wish to use IP numbers - more appropriate to your circumstances, but the - above example will always work. + ppp will insist on. You may wish + to use IP numbers more appropriate to your + circumstances, but the above example will always + work. The last argument (0.0.0.0) tells PPP to start negotiations @@ -668,7 +671,7 @@ protocol: ppp receiving incoming calls - When you configure ppp to + When you configure ppp to receive incoming calls on a machine connected to a LAN, you must decide if you wish to forward packets to the LAN. If you do, you should allocate the peer an IP number from @@ -869,7 +872,8 @@ mary: should also contain routing information for each static IP user if required. The line below would add a route for the 203.14.101.0/24 - network via the client's ppp link. + network via the client's PPP + link. fred: add 203.14.101.0 netmask 255.255.255.0 HISADDR @@ -901,10 +905,10 @@ mary: comes with the AUTO_PPP option enabled allowing mgetty to detect the LCP phase of PPP connections and - automatically spawn off a ppp shell. However, since the - default login/password sequence does not occur it is - necessary to authenticate users using either PAP or - CHAP. + automatically spawn off a ppp shell. + However, since the default login/password sequence does + not occur it is necessary to authenticate users using + either PAP or CHAP. This section assumes the user has successfully compiled, and installed the ppp -auto mysystem This script is executed at network configuration time, - starting your ppp daemon in automatic mode. If you have - a LAN for which this machine is a gateway, you may also - wish to use the switch. Refer - to the manual page for further details. + starting your ppp daemon in automatic + mode. If you have a LAN for which this machine is a + gateway, you may also wish to use the + switch. Refer to the manual page + for further details. Make sure that the router program is set to @@ -1208,7 +1213,8 @@ ifconfig_tun0= The downside of this is that you must force sendmail to re-examine the mail queue - whenever the ppp link is up by typing: + whenever the PPP link is up by + typing: &prompt.root; /usr/sbin/sendmail -q @@ -1247,7 +1253,7 @@ ifconfig_tun0= Summary To recap, the following steps are necessary when setting - up ppp for the first time: + up PPP for the first time: Client side: @@ -1544,8 +1550,8 @@ OK command mode, which is usually a negotiation error where the ISP is waiting for your side to start negotiating. At this point, using the ~p - command will force ppp to start sending the configuration - information. + command will force ppp to start + sending the configuration information. If you never obtain a login prompt, then most likely you need to use PAP or @@ -1644,7 +1650,7 @@ nameserver y.y.y.yNo kernel configuration is necessary for PPPoE. If the necessary netgraph support is not built into the kernel, it will be dynamically loaded by - ppp. + ppp. @@ -1668,7 +1674,7 @@ name_of_service_provider: - Running <application>ppp</application> + Running <command>ppp</command> As root, you can run: @@ -1677,7 +1683,7 @@ name_of_service_provider: - Starting <application>ppp</application> at Boot + Starting <command>ppp</command> at Boot Add the following to your /etc/rc.conf file: @@ -1831,7 +1837,7 @@ ppp_profile="name_of_service_provider"usbd_enable="YES" It is also possible to set up - ppp to dial up at startup. To do + ppp to dial up at startup. To do this add the following lines to /etc/rc.conf. Again, for this procedure you will need to be logged in as the root @@ -1975,8 +1981,8 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNIN need to be root to perform both of these operations. An example section of ppp.conf is given below. For further information on - ppp.conf options consult the - ppp manual page, &man.ppp.8;. + ppp.conf options consult + &man.ppp.8;. adsl: set log phase chat lcp ipcp ccp tun command @@ -2033,7 +2039,7 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNIN A tun virtual tunnel device will be created for interaction between the pptp and - ppp processes. Once you have been + ppp processes. Once you have been returned to your prompt, or the pptp process has confirmed a connection you can examine the tunnel like so: @@ -2048,7 +2054,7 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNI telnet or with a web browser. If you still cannot connect you should examine the output of the pptp command and the contents of the - ppp log file, + ppp log file, /var/log/ppp.log for clues. From owner-svn-doc-projects@FreeBSD.ORG Mon Apr 22 20:19:11 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 587B7D94; Mon, 22 Apr 2013 20:19:11 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by mx1.freebsd.org (Postfix) with ESMTP id D614B1290; Mon, 22 Apr 2013 20:19:10 +0000 (UTC) X-AuditID: 1209190e-b7f4f6d000005142-26-51759a0b48ef Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 23.03.20802.B0A95715; Mon, 22 Apr 2013 16:14:03 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r3MKE2Ej002003; Mon, 22 Apr 2013 16:14:03 -0400 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r3MKE1Ts006684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Apr 2013 16:14:02 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r3MKE0Vb016065; Mon, 22 Apr 2013 16:14:00 -0400 (EDT) Date: Mon, 22 Apr 2013 16:14:00 -0400 (EDT) From: Benjamin Kaduk To: Dru Lavigne Subject: Re: svn commit: r41471 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip In-Reply-To: <201304221801.r3MI182f043890@svn.freebsd.org> Message-ID: References: <201304221801.r3MI182f043890@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNIsWRmVeSWpSXmKPExsUixG6nrss9qzTQYN5nTYsfHw8xWXQ1qVos PLOa2YHZY8an+SwBjFFcNimpOZllqUX6dglcGW237jIV3BevuP8huYHxgVAXIyeHhICJxLz2 HYwQtpjEhXvr2boYuTiEBPYxSuydvowZwtnIKHHq0yVWCOcQk8TPtzOgMg2MEssPzWQC6WcR 0JZoOrgUbBabgIrEzDcb2UBsEQFFiadf94LFmQVsJCY8WMAOYgsLZEscu9ANFucUsJLYNWUT 0BwODl4BB4kVO8VBwkIClhJtj5rAxogK6Eis3j+FBcTmFRCUODnzCQvESEuJf2t/sU5gFJyF JDULSWoBI9MqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXWO93MwSvdSU0k2MoDDllOTbwfj1oNIh RgEORiUeXgH30kAh1sSy4srcQ4ySHExKorx7ZwCF+JLyUyozEosz4otKc1KLDzFKcDArifCK 5gPleFMSK6tSi/JhUtIcLErivFdSbvoLCaQnlqRmp6YWpBbBZGU4OJQkeJVmAjUKFqWmp1ak ZeaUIKSZODhBhvMADecDqeEtLkjMLc5Mh8ifYlSUEuddDnKRAEgiozQPrheWRl4xigO9Isxr B9LOA0xBcN2vgAYzAQ3OTCgBGVySiJCSamCM+KjIwRLw9qpT+aYvS6w8DkhcXLSYZWOt7MmX LrpzHk9VEXrJu2jDgtevQk/H9O059e+Yk6gus9tmCan+JQ4e+seObYu/y/7m1i6W87+qdJls 3Au6eDWz2hLS1A0fzb9gcexRqeY27d/KUud+Gm3ac1R5z7ddr/2/Sf/6+sWi3L7t8W2nx37d SizFGYmGWsxFxYkAR937J/4CAAA= Cc: svn-doc-projects@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 20:19:11 -0000 On Mon, 22 Apr 2013, Dru Lavigne wrote: > Make formatting for ppp command more consistent. > > Approved by: bcr (mentor) > > Modified: > projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml > > Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml > ============================================================================== > --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Apr 22 16:14:28 2013 (r41470) > +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Apr 22 18:01:07 2013 (r41471) > @@ -535,8 +536,8 @@ protocol: ppp > otherwise HISADDR will not yet > be initialized. > > - If you do not wish to run ppp in > - , this line should be moved > + If you do not wish to run ppp > + in , this line should be moved This should take 'mode' per the next chunk. > to the ppp.linkup file. > > > @@ -544,11 +545,12 @@ protocol: ppp > > It is not necessary to add an entry to > ppp.linkup when you have a static > - IP address and are running ppp in > - mode as your routing table entries are already correct > - before you connect. You may however wish to create an > - entry to invoke programs after connection. This is > - explained later with the sendmail example. > + IP address and are running ppp in > + mode as your routing table entries > + are already correct before you connect. You may however However is probably not needed but if present should be set off by commas. > + wish to create an entry to invoke programs after > + connection. This is explained later with the sendmail > + example. > > Example configuration files can be found in the > @@ -1173,10 +1177,11 @@ ifconfig_tun0= > ppp -auto mysystem > > This script is executed at network configuration time, > - starting your ppp daemon in automatic mode. If you have > - a LAN for which this machine is a gateway, you may also > - wish to use the switch. Refer > - to the manual page for further details. > + starting your ppp daemon in automatic > + mode. If you have a LAN for which this machine is a This should be mode for consistency with the above. -Ben > + gateway, you may also wish to use the > + switch. Refer to the manual page > + for further details. > > > Make sure that the router program is set to From owner-svn-doc-projects@FreeBSD.ORG Tue Apr 23 19:25:28 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 77844833; Tue, 23 Apr 2013 19:25:28 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6A02C1A53; Tue, 23 Apr 2013 19:25:28 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3NJPS1W061376; Tue, 23 Apr 2013 19:25:28 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3NJPSIs061374; Tue, 23 Apr 2013 19:25:28 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304231925.r3NJPSIs061374@svn.freebsd.org> From: Dru Lavigne Date: Tue, 23 Apr 2013 19:25:28 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41478 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 19:25:28 -0000 Author: dru Date: Tue Apr 23 19:25:27 2013 New Revision: 41478 URL: http://svnweb.freebsd.org/changeset/doc/41478 Log: Fix formatting of -auto mode. Next patch will address overuse of "you". Submitted by: bjk Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Tue Apr 23 17:11:13 2013 (r41477) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Tue Apr 23 19:25:27 2013 (r41478) @@ -537,8 +537,9 @@ protocol: ppp be initialized. If you do not wish to run ppp - in , this line should be moved - to the ppp.linkup file. + in mode, this line should be + moved to the ppp.linkup + file. @@ -1177,9 +1178,9 @@ ifconfig_tun0= ppp -auto mysystem This script is executed at network configuration time, - starting your ppp daemon in automatic - mode. If you have a LAN for which this machine is a - gateway, you may also wish to use the + starting your ppp daemon in + mode. If you have a LAN for which + this machine is a gateway, you may also wish to use the switch. Refer to the manual page for further details. From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 24 20:49:20 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3AF99D85; Wed, 24 Apr 2013 20:49:20 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB7F1DE1; Wed, 24 Apr 2013 20:49:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3OKnKYi021362; Wed, 24 Apr 2013 20:49:20 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3OKnKKW021361; Wed, 24 Apr 2013 20:49:20 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304242049.r3OKnKKW021361@svn.freebsd.org> From: Dru Lavigne Date: Wed, 24 Apr 2013 20:49:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41492 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 20:49:20 -0000 Author: dru Date: Wed Apr 24 20:49:19 2013 New Revision: 41492 URL: http://svnweb.freebsd.org/changeset/doc/41492 Log: Initial content fixup, more patches to follow. The next patch will fix the whitespace. Fixes &os;, you, and obvious grammos. The technical content has not yet been reviewed to see if it is still relevant. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 20:11:30 2013 (r41491) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 20:49:19 2013 (r41492) @@ -21,70 +21,64 @@ Synopsis - FreeBSD supports a wide variety of sound cards, allowing you - to enjoy high fidelity output from your computer. This includes + &os; supports a wide variety of sound cards, allowing users + to enjoy high fidelity output from a &os; system. This includes the ability to record and playback audio in the MPEG Audio Layer - 3 (MP3), WAV, and Ogg Vorbis formats as well as many other - formats. The FreeBSD Ports Collection also contains - applications allowing you to edit your recorded audio, add sound - effects, and control attached MIDI devices. - - With some experimentation, &os; can support - playback of video files and DVDs. The number of applications - to encode, convert, and playback various video media is more - limited than the number of sound applications. For example as - of this writing, there are no good re-encoding applications - in the FreeBSD Ports Collection that could be used to convert - between formats, as there is with audio/sox. However, the software - landscape in this area is changing rapidly. - - This chapter will describe the necessary steps to configure - your sound card. The configuration and installation of X11 - () has already taken care of the - hardware issues for your video card, though there may be some - tweaks to apply for better playback. + 3 (MP3), Waveform Audio File + (WAV), Ogg Vorbis, and other + formats. The &os; Ports Collection contains many + applications for editing recorded audio, adding sound + effects, and controlling attached MIDI devices. + + &os; also supports the playback of video files and DVDs. + The &os; Ports Collection contains applications to encode, + convert, and playback various video media. + + This chapter describes how to configure + sound cards, video + playback, TV tuner cards, and scanners on &os;. It also + describes some of the applications which are available for + using these devices. - After reading this chapter, you will know: + After reading this chapter, you will know how to: - How to configure your system so that your sound card - is recognized. + Configure a sound card + on os;. - Methods to test whether your card is working. + Troubleshoot the sound setup. - How to troubleshoot your sound setup. + Playback and encode MP3s and other audio. - How to playback and encode MP3s and other audio. + Prepare a &os; system for video playback. - How video is supported by the X server. + Playback DVDs, .mpg, and + .avi files. - Some video player/encoder ports which give good - results. + Rip CD and DVD content into files. - How to playback DVDs, .mpg and - .avi files. + Configure a TV card. - How to rip CD and DVD content into files. + Install and setup MythTV on &os; - How to configure a TV card. + Configure an image scanner. @@ -100,10 +94,9 @@ - Trying to mount audio CDs with the &man.mount.8; command - will result in an error, at least, and a kernel - panic, at worst. These media have specialized - encodings which differ from the usual ISO-filesystem. + Audio CDs have specialized encodings which differ from the + usual ISO-filesystem. This means that they should not be + mounted using &man.mount.8;. @@ -134,101 +127,101 @@ Configuring the System PCI - ISA sound cards - Before you begin, you should know the model of the card - you have, the chip it uses, and whether it is a PCI or ISA - card. FreeBSD supports a wide variety of both PCI and ISA - cards. Check the supported audio devices list of the Hardware Notes to - see if your card is supported. The Hardware Notes will - also mention which driver supports your card. + Before beginning the configuration, determine the model of + the sound card and the chip it uses. &os; supports a wide + variety of sound cards. Check the supported audio devices + list of the Hardware + Notes to see if the card is supported and which &os; + driver it uses. kernel configuration - To use your sound device, you will need to load the proper - device driver. This may be accomplished in one of two ways. - The easiest way is to simply load a kernel module for your - sound card with &man.kldload.8; which can either be done from - the command line: + In order to use the sound device, +the proper + device driver must be loaded. This may be accomplished in +one of two ways. + The easiest way is to load a kernel module for the + sound card with &man.kldload.8;. This example loads the +driver + for a Creative &soundblaster; Live! sound card: &prompt.root; kldload snd_emu10k1 - or by adding the appropriate line to the file - /boot/loader.conf like this: + To automate the loading of this driver at boot time, add the + driver to + /boot/loader.conf. The line for + this driver is: snd_emu10k1_load="YES" - These examples are for a Creative &soundblaster; Live! sound - card. Other available loadable sound modules are listed in + Other available sound modules are listed in /boot/defaults/loader.conf. - If you are not sure which driver to use, you may try to load + When unsure which driver to use, load the snd_driver module: &prompt.root; kldload snd_driver - This is a metadriver loading the most common device drivers - at once. This speeds up the search for the correct driver. It - is also possible to load all sound drivers via the - /boot/loader.conf facility. - - If you wish to find out the driver selected for your - soundcard after loading the snd_driver - metadriver, you may check the /dev/sndstat - file with the cat /dev/sndstat - command. - - A second method is to statically - compile in support for your sound card in your kernel. The - section below provides the information you need to add support - for your hardware in this manner. For more information about - recompiling your kernel, please see This is a metadriver which loads all of the most common +sound drivers + and can be used to speed up the search for the correct driver. +It + is also possible to load all sound drivers by adding the +metadriver to + /boot/loader.conf. + + To determine which driver was selected for the + sound card after loading the snd_driver + metadriver, type cat /dev/sndstat. + + Users who prefer to statically + compile in support for the sound card in a custom kernel should +refer to the instructions in the next + section. For more information about + recompiling a kernel, refer to . Configuring a Custom Kernel with Sound Support - The first thing to do is add the audio framework driver - &man.sound.4; to the kernel; for that you will need to - add the following line to the kernel configuration file: + When using a custom kernel to provide sound support, make + sure that the audio framework driver +exists in the custom kernel configuration file: device sound - Next, you have to add the support for your sound card. + Next, add support for the sound card. Therefore, you need to know which driver supports the card. - Check the supported audio devices list of the Hardware Notes, to - determine the correct driver for your sound card. For - example, a Creative &soundblaster; Live! sound card is - supported by the &man.snd.emu10k1.4; driver. To add the support - for this card, use the following: + To + continue the example of the Creative &soundblaster; Live! + sound card from the previous section, use the following line + in the custom kernel configuration file: device snd_emu10k1 Be sure to read the manual page of the driver for the syntax to use. The explicit syntax for the kernel configuration of every supported sound driver can also be - found in the /usr/src/sys/conf/NOTES - file. + found in /usr/src/sys/conf/NOTES. - Non-PnP ISA sound cards may require you to provide the - kernel with information on the card settings (IRQ, I/O port, - etc), as is true of all non-PnP ISA cards. This is done via - the /boot/device.hints file. During the - boot process, the &man.loader.8; will read this file and pass + Non-PnP ISA sound cards may require the IRQ and I/O port + settings of the card to be added +to /boot/device.hints. During the + boot process, &man.loader.8; reads this file and passes the settings to the kernel. For example, an old Creative &soundblaster; 16 ISA non-PnP card will use the &man.snd.sbc.4; driver in conjunction with - snd_sb16. For this card the following + snd_sb16. For this card, the following lines must be added to the kernel configuration file: device snd_sbc device snd_sb16 - and these to + If the card uses the 0x220 I/O port and + IRQ 5, these lines must also be added to /boot/device.hints: hint.sbc.0.at="isa" @@ -240,14 +233,14 @@ hint.sbc.0.flags="0x15" In this case, the card uses the 0x220 I/O port and the IRQ 5. - The syntax used in the - /boot/device.hints file is covered in the - &man.sound.4; driver manual page and the manual page - for the driver in question. + The syntax used in + /boot/device.hints is described in + &man.sound.4; and the manual page + for the driver of the sound card. The settings shown above are the defaults. In some - cases, you may need to change the IRQ or the other settings to - match your card. See the &man.snd.sbc.4; manual page for more + cases, the IRQ or other settings may need to be changed to + match the card. Refer to &man.snd.sbc.4; for more information about this card. @@ -255,16 +248,17 @@ hint.sbc.0.flags="0x15" Testing the Sound Card - After rebooting with the modified kernel, or after loading - the required module, the sound card should appear in your system - message buffer (&man.dmesg.8;) as something like: + After rebooting into the custom kernel, or after loading + the required module, the sound card should appear in the system + message buffer. Run &man.dmesg.8; and look for a message +like: pcm0: <Intel ICH3 (82801CA)> port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: <Cirrus Logic CS4205 AC97 Codec> - The status of the sound card may be checked via the - /dev/sndstat file: + The status of the sound card may also be checked +using this command: &prompt.root; cat /dev/sndstat FreeBSD Audio Driver (newpcm) @@ -272,46 +266,47 @@ Installed devices: pcm0: <Intel ICH3 (82801CA)> at io 0xd800, 0xdc80 irq 5 bufsz 16384 kld snd_ich (1p/2r/0v channels duplex default) - The output from your system may vary. If no + The output may vary between systems. If no pcm devices are listed, go back and - review what was done earlier. Go through your kernel - configuration file again and make sure the correct + review the kernel configuration file and make sure the correct device driver was chosen. Common problems are listed in . - If all goes well, you should now have a functioning sound - card. If your CD-ROM or DVD-ROM drive's audio-out pins are - properly connected to your sound card, you can put a CD in the + If all goes well, the sound + card should now work in os;. If the CD-ROM or DVD-ROM drive's +audio-out pins are + properly connected to the sound card, one can insert an audio CD +in the drive and play it with &man.cdcontrol.1;: &prompt.user; cdcontrol -f /dev/acd0 play 1 Various applications, such as audio/workman can provide a - friendlier interface. You may want to install an application - such as audio/mpg123 to + role="package">audio/workman provide a + friendlier interface. The audio/mpg123 port can be installed to listen to MP3 audio files. - Another quick way to test the card is sending data - to /dev/dsp, like this: + Another quick way to test the card is to send data + to /dev/dsp: &prompt.user; cat filename > /dev/dsp where filename can - be any file. This command line should produce some noise, - confirming the sound card is actually working. + be any file. This command should produce some noise, + confirming that the sound card is actually working. - The device nodes /dev/dsp* will be - created automatically when needed. If they are not used, they + The /dev/dsp* device nodes will +be + created automatically as needed. When not in use, they do not exist and will not appear in the output of &man.ls.1;. - Sound card mixer levels can be changed via the &man.mixer.8; - command. More details can be found in the &man.mixer.8; manual - page. + Sound card mixer levels can be changed using &man.mixer.8;. + More details can be found in &man.mixer.8;. Common Problems @@ -370,8 +365,8 @@ kld snd_ich (1p/2r/0v channels duplex de 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 + sometimes be enumerated before the sound card and the + sound card 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 @@ -397,16 +392,17 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi 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: + ALC889). To use the sound card as the default +playback + device, change hw.snd.default_unit to the + unit that should be used for playback: &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 + device to use. In this example, it should be +4. + Make this change permanent by adding the following line to /etc/sysctl.conf: hw.snd.default_unit=4 @@ -426,20 +422,15 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Utilizing Multiple Sound Sources It is often desirable to have multiple sources of sound that - are able to play simultaneously, such as when - esound or - artsd do not support sharing of the - sound device with a certain application. - - FreeBSD lets you do this through Virtual Sound - Channels, which can be enabled with the - &man.sysctl.8; facility. Virtual channels allow you to - multiplex your sound card's playback by mixing sound in the + are able to play simultaneously. &os; uses +Virtual Sound + Channels, which can be enabled using + &man.sysctl.8;. Virtual channels allow one to + multiplex the sound card's playback by mixing sound in the kernel. - To set the number of virtual channels, there are three - sysctl knobs which, if you are the root - user, can be set like this: + To set the number of virtual channels, three + &man.sysctl.8; knobs are available: &prompt.root; sysctl dev.pcm.0.play.vchans=4 &prompt.root; sysctl dev.pcm.0.rec.vchans=4 @@ -450,19 +441,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi dev.pcm.0.play.vchans=4 and dev.pcm.0.rec.vchans=4 are the number of virtual channels pcm0 has for playback - and recording, and are configurable once a device has been + and recording, and are configurable after a device has been attached. hw.snd.maxautovchans is the number of virtual channels a new audio device is given when it is attached using &man.kldload.8;. Since the pcm module can be loaded independently of the hardware drivers, hw.snd.maxautovchans - can store how many virtual channels any devices which are - attached later will be given. Refer to &man.pcm.4; manual page + indicates how many virtual channels will be given to devices +when they are attached. Refer to &man.pcm.4; for more information. - You cannot change the number of virtual channels for a - device while it is in use. First close any programs using + The number of virtual channels for a + device cannot be changed while it is in use. First, close any +programs using the device, such as music players or sound daemons. @@ -486,18 +478,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Setting Default Values for Mixer Channels The default values for the different mixer channels are - hardcoded in the sourcecode of the &man.pcm.4; driver. There + hardcoded in the source code of the &man.pcm.4; driver. There are many different applications and daemons that allow - you to set values for the mixer that are remembered between + values to be set for the mixer that are remembered between invocations, but this is not a clean solution. It is possible - to set default mixer values at the driver level — this + to set default mixer values at the driver level. This is accomplished by defining the appropriate values in - /boot/device.hints, e.g.: + /boot/device.hints, as seen in this +example: hint.pcm.0.vol="50" This will set the volume channel to a default value of - 50 when the &man.pcm.4; module is loaded. + 50 when the &man.pcm.4; module is +loaded. @@ -515,18 +509,18 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi MP3 Audio - MP3 (MPEG Layer 3 Audio) accomplishes near CD-quality sound, - leaving no reason to let your FreeBSD workstation fall short of - its offerings. + This section describes some MP3 + players available for &os;, how to rip audio CD tracks, and + how to encode and decode MP3s. MP3 Players - By far, the most popular X11 MP3 player is - XMMS (X Multimedia System). + A popular graphical MP3 player is + XMMS. Winamp skins can be used with XMMS since - the GUI is almost identical to that of Nullsoft's + the interface is almost identical to that of Nullsoft's Winamp. XMMS also has native plug-in support. @@ -541,14 +535,17 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi XMMS simple to use. The audio/mpg123 port - is an alternative, command-line MP3 player. + provides an alternative, command-line MP3 +player. mpg123 can be run by specifying - the sound device and the MP3 file on the command line. - Assuming your audio device is - /dev/dsp1.0 and you want to play the - MP3 file Foobar-GreatestHits.mp3 - you would enter the following: + the sound device and the MP3 file on the +command line. + Assuming the audio device is + /dev/dsp1.0 and the + MP3 file is +Foobar-GreatestHits.mp3, + enter the following to play the file: &prompt.root; mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. @@ -567,22 +564,32 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz Ripping CD Audio Tracks - Before encoding a CD or CD track to MP3, the audio data on - the CD must be ripped onto the hard drive. This is done by - copying the raw CDDA (CD Digital Audio) data to WAV + Before encoding a CD or CD track to +MP3, the audio data on + the CD must be ripped to the hard drive. This is done by + copying the raw CD + Digital Audio (CDDA) data to +WAV files. - The cdda2wav tool, which is a part of + The cdda2wav tool, which is installed +with the sysutils/cdrtools suite, is used for ripping audio information from CDs and the information associated with them. With the audio CD in the drive, the following command can - be issued (as root) to rip an entire CD - into individual (per track) WAV files: + be issued as root to rip an entire CD + into individual (per track) WAV +files: &prompt.root; cdda2wav -D 0,1,0 -B + The + indicates the SCSI device 0,1,0, + which corresponds to the output of cdrecord + -scanbus. + cdda2wav will support ATAPI (IDE) CDROM drives. To rip from an IDE drive, specify the device name in place of the SCSI unit numbers. For @@ -590,40 +597,35 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz &prompt.root; cdda2wav -D /dev/acd0 -t 7 - The - indicates the SCSI device 0,1,0, - which corresponds to the output of cdrecord - -scanbus. - To rip individual tracks, make use of the - option as shown: + as shown: &prompt.root; cdda2wav -D 0,1,0 -t 7 This example rips track seven of the audio CDROM. To rip - a range of tracks, for example, track one to seven, specify a + a range of tracks, such as track one to seven, specify a range: &prompt.root; cdda2wav -D 0,1,0 -t 1+7 - The utility &man.dd.1; can also be used to extract audio - tracks on ATAPI drives, read for more information on - that possibility. + &man.dd.1; can also be used to extract audio + tracks on ATAPI drives, as described in . Encoding MP3s - Nowadays, the mp3 encoder of choice is - lame. - Lame can be found at - audio/lame in the ports - tree. - - Using the ripped WAV files, the following command will - convert + + Lame is a popular +MP3 encoder which can be installed from the + audio/lame port. Due to + licensing restrictions, a package is not available. + + The following command will + convert the ripped + WAV files audio01.wav to audio01.mp3: @@ -637,25 +639,29 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz --tg "Genre" \ audio01.wav audio01.mp3 - 128 kbits seems to be the standard MP3 bitrate in - use. Many enjoy the higher quality 160, or 192. The higher - the bitrate, the more disk space the resulting MP3 will - consume--but the quality will be higher. The - option turns on the higher quality + 128 kbits is a standard MP3 +bitrate. The 160 and 192 bitrates provide higher quality. The higher + the bitrate, the larger the size of the resulting + MP3. + turns on the higher quality but a little slower mode. The options beginning with indicate ID3 tags, which usually contain - song information, to be embedded within the MP3 file. - Additional encoding options can be found by consulting the - lame man page. + song information, to be embedded within the +MP3 file. + Additional encoding options can be found in the + lame manual page. Decoding MP3s - In order to burn an audio CD from MP3s, they must be - converted to a non-compressed WAV format. Both + In order to burn an audio CD from MP3s, +they must first be + converted to a non-compressed WAV format. +Both XMMS and - mpg123 support the output of MP3 + mpg123 support the output of +MP3 to an uncompressed file format. Writing to Disk in XMMS: @@ -666,12 +672,12 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - Right-click on the window to bring up the + Right-click the window to bring up the XMMS menu. - Select Preference under + Select Preferences under Options. @@ -685,26 +691,31 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - Enter (or choose browse) a directory to write the + Enter or browse to a directory to write the uncompressed files to. - Load the MP3 file into XMMS + Load the MP3 file into +XMMS as usual, with volume at 100% and EQ settings turned off. - Press Play — + Press Play. The XMMS will appear as if it is - playing the MP3, but no music will be heard. It is - actually playing the MP3 to a file. + playing the MP3, but no music will be +heard. It is + actually playing the MP3 to a +file. - Be sure to set the default Output Plugin back to what - it was before in order to listen to MP3s again. + When finished, be sure to set the default Output +Plugin back to what + it was before in order to listen to +MP3s again. @@ -719,22 +730,28 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - XMMS writes a file in the WAV + XMMS writes a file in the +WAV format, while mpg123 converts the - MP3 into raw PCM audio data. Both of these formats can be + MP3 into raw PCM audio data. Both of these +formats can be used with cdrecord to create audio - CDs. You have to use raw PCM with &man.burncd.8;. If you - use WAV files, you will notice a small tick sound at the - beginning of each track, this sound is the header of the WAV - file. You can simply remove the header of a WAV file with - the utility SoX (it can be + CDs, whereas &man.burncd.8; requires a raw Pulse-Code +Modulation (PCM. When using + WAV files, there will be a small tick +sound at the + beginning of each track. This sound is the header of the +WAV + file. One can remove the header with + SoX, which can be installed from the audio/sox port or package): + role="package">audio/sox port or package: &prompt.user; sox -t wav -r 44100 -s -w -c 2 track.wav track.raw - Read for more information - on using a CD burner in FreeBSD. + Refer to for more +information + on using a CD burner in &os;. @@ -752,43 +769,45 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz Video Playback - Video playback is a very new and rapidly developing - application area. Be patient. Not everything is going to work - as smoothly as it did with sound. - - Before you begin, you should know the model of the video - card you have and the chip it uses. While + Before configuring video playback, determine the model +of the video + card and the chip it uses. While &xorg; supports a wide variety of video cards, fewer give good playback performance. To obtain - a list of extensions supported by the X server using your card - use the command &man.xdpyinfo.1; while X11 is running. - - It is a good idea to have a short MPEG file which can be - treated as a test file for evaluating various players and - options. Since some DVD players will look for DVD media in - /dev/dvd by default, or have this device - name hardcoded in them, you might find it useful to make + a list of extensions supported by the +&xorg; server using the card, run + &man.xdpyinfo.1; while &xorg; is +running. + + It is a good idea to have a short MPEG test file for +evaluating various players and + options. Since some DVD applications look for DVD media in + /dev/dvd by default, or +have this device + name hardcoded in them, it might be useful to make symbolic links to the proper devices: &prompt.root; ln -sf /dev/acd0 /dev/dvd &prompt.root; ln -sf /dev/acd0 /dev/rdvd - Note that due to the nature of &man.devfs.5;, - manually created links like these will not persist if you reboot - your system. In order to create the symbolic links - automatically whenever you boot your system, add the following + Due to the nature of &man.devfs.5;, + manually created links will not persist after a system reboot. + In order to create the symbolic links + automatically when the system boots, add the following lines to /etc/devfs.conf: link acd0 dvd link acd0 rdvd - Additionally, DVD decryption, which requires invoking - special DVD-ROM functions, requires write permission on the DVD + DVD decryption invokes + special DVD-ROM functions and requires write permission on the +DVD devices. - To enhance the shared memory X11 interface, it is - recommended that the values of some &man.sysctl.8; variables - should be increased: + To enhance the shared memory +&xorg; interface, it is + recommended to increase the values of these &man.sysctl.8; +variables: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 @@ -800,32 +819,34 @@ kern.ipc.shmall=32768 SDL DGA - There are several possible ways to display video under X11. - What will really work is largely hardware dependent. Each + There are several possible ways to display video under +&xorg;. + What works is largely hardware dependent. Each method described below will have varying quality across - different hardware. Secondly, the rendering of video in X11 - is a topic receiving a lot of attention lately, and with each - version of &xorg;, there may be - significant improvement. + different hardware. - A list of common video interfaces: + Common video interfaces include: - X11: normal X11 output using shared memory. + &xorg;: normal output +using shared memory. - XVideo: an extension to the X11 interface which supports - video in any X11 drawable. + XVideo: an extension to the +&xorg; interface which supports + video in any drawable object. - SDL: the Simple Directmedia Layer. + SDL: the Simple Directmedia +Layer. - DGA: the Direct Graphics Access. + DGA: the Direct Graphics +Access. @@ -837,9 +858,10 @@ kern.ipc.shmall=32768 XVideo &xorg; has an extension called - XVideo (aka Xvideo, aka Xv, aka xv) which + XVideo, also known as Xvideo, +Xv, and xv. It allows video to be directly displayed in drawable objects - through a special acceleration. This extension provides very + through a special acceleration. This extension provides good quality playback even on low-end machines. To check whether the extension is running, use @@ -847,7 +869,7 @@ kern.ipc.shmall=32768 &prompt.user; xvinfo - XVideo is supported for your card if the result looks + XVideo is supported for the card if the result looks like: X-Video Extension version 2.2 @@ -919,7 +941,7 @@ kern.ipc.shmall=32768 depth: 1 red, green, blue masks: 0x0, 0x0, 0x0 - Also note that the formats listed (YUV2, YUV12, etc) are + The formats listed, such as YUV2 and YUV12, are not present with every implementation of XVideo and their absence may hinder some players. @@ -929,46 +951,48 @@ kern.ipc.shmall=32768 screen #0 no adaptors present - Then XVideo is probably not supported for your card. - - If XVideo is not supported for your card, this only means - that it will be more difficult for your display to meet the - computational demands of rendering video. Depending on your - video card and processor, though, you might still be able to - have a satisfying experience. You should probably read about - ways of improving performance in the advanced reading . + XVideo is probably not supported for the card. This +means + that it will be more difficult for the display to meet the + computational demands of rendering video. Depending on the + video card and processor, one might still be able to + have a satisfying experience. Simple Directmedia Layer - The Simple Directmedia Layer, SDL, was intended to be a - porting layer between µsoft.windows;, BeOS, and &unix;, - allowing cross-platform applications to be developed which made - efficient use of sound and graphics. The SDL layer provides a + SDL is intended to be a + porting layer between µsoft.windows; and &unix;, + allowing cross-platform applications to be developed which make + efficient use of sound and graphics. The SDL +layer provides a low-level abstraction to the hardware which can sometimes be - more efficient than the X11 interface. + more efficient than the &xorg; +interface. - The SDL can be found at devel/sdl12. + SDL can be installed using the devel/sdl12 package or port. Direct Graphics Access - Direct Graphics Access is an X11 extension which allows - a program to bypass the X server and directly alter the - framebuffer. Because it relies on a low level memory mapping to - effect this sharing, programs using it must be run as + DGA is an +&xorg; extension which allows + a program to bypass the &xorg; server +and directly alter the + framebuffer. Because it relies on a low level memory mapping, +programs using it must be run as root. - The DGA extension can be tested and benchmarked by + The DGA extension can be tested and +benchmarked using &man.dga.1;. When dga is running, it changes the colors of the display whenever a key is pressed. To - quit, use q. + quit, press q. @@ -979,17 +1003,16 @@ no adaptors present video ports video packages - This section discusses the software available from the - FreeBSD Ports Collection which can be used for video playback. - Video playback is a very active area of software development, - and the capabilities of various applications are bound to - diverge somewhat from the descriptions given here. *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 24 21:47:20 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 82DB7274; Wed, 24 Apr 2013 21:47:20 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 74F1B100E; Wed, 24 Apr 2013 21:47:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3OLlJsw042168; Wed, 24 Apr 2013 21:47:19 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3OLlJTN042167; Wed, 24 Apr 2013 21:47:19 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304242147.r3OLlJTN042167@svn.freebsd.org> From: Dru Lavigne Date: Wed, 24 Apr 2013 21:47:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41493 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 21:47:20 -0000 Author: dru Date: Wed Apr 24 21:47:19 2013 New Revision: 41493 URL: http://svnweb.freebsd.org/changeset/doc/41493 Log: Fix extra in r41492. Approved by: gjb (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 20:49:19 2013 (r41492) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 21:47:19 2013 (r41493) @@ -845,7 +845,7 @@ Layer. - DGA: the Direct Graphics + DGA: the Direct Graphics Access. From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 24 22:34:32 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E92BEDC6; Wed, 24 Apr 2013 22:34:32 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DABCF11A9; Wed, 24 Apr 2013 22:34:32 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3OMYW62059046; Wed, 24 Apr 2013 22:34:32 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3OMYWFp059045; Wed, 24 Apr 2013 22:34:32 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304242234.r3OMYWFp059045@svn.freebsd.org> From: Dru Lavigne Date: Wed, 24 Apr 2013 22:34:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41494 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 22:34:33 -0000 Author: dru Date: Wed Apr 24 22:34:32 2013 New Revision: 41494 URL: http://svnweb.freebsd.org/changeset/doc/41494 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 21:47:19 2013 (r41493) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 22:34:32 2013 (r41494) @@ -25,17 +25,16 @@ to enjoy high fidelity output from a &os; system. This includes the ability to record and playback audio in the MPEG Audio Layer 3 (MP3), Waveform Audio File - (WAV), Ogg Vorbis, and other - formats. The &os; Ports Collection contains many - applications for editing recorded audio, adding sound - effects, and controlling attached MIDI devices. + (WAV), Ogg Vorbis, and other formats. The + &os; Ports Collection contains many applications for editing + recorded audio, adding sound effects, and controlling attached + MIDI devices. &os; also supports the playback of video files and DVDs. The &os; Ports Collection contains applications to encode, convert, and playback various video media. - This chapter describes how to configure - sound cards, video + This chapter describes how to configure sound cards, video playback, TV tuner cards, and scanners on &os;. It also describes some of the applications which are available for using these devices. @@ -44,8 +43,7 @@ - Configure a sound card - on os;. + Configure a sound card on os;. @@ -140,65 +138,56 @@ configuration - In order to use the sound device, -the proper - device driver must be loaded. This may be accomplished in -one of two ways. - The easiest way is to load a kernel module for the - sound card with &man.kldload.8;. This example loads the -driver - for a Creative &soundblaster; Live! sound card: + In order to use the sound device, the proper device driver + must be loaded. This may be accomplished in one of two ways. + The easiest way is to load a kernel module for the sound card + with &man.kldload.8;. This example loads the driver for a + Creative &soundblaster; Live! sound card: &prompt.root; kldload snd_emu10k1 To automate the loading of this driver at boot time, add the - driver to - /boot/loader.conf. The line for + driver to /boot/loader.conf. The line for this driver is: snd_emu10k1_load="YES" Other available sound modules are listed in - /boot/defaults/loader.conf. - When unsure which driver to use, load - the snd_driver module: + /boot/defaults/loader.conf. When unsure + which driver to use, load the snd_driver + module: &prompt.root; kldload snd_driver This is a metadriver which loads all of the most common -sound drivers - and can be used to speed up the search for the correct driver. -It - is also possible to load all sound drivers by adding the -metadriver to + sound drivers and can be used to speed up the search for the + correct driver. It is also possible to load all sound drivers + by adding the metadriver to /boot/loader.conf. - To determine which driver was selected for the - sound card after loading the snd_driver - metadriver, type cat /dev/sndstat. - - Users who prefer to statically - compile in support for the sound card in a custom kernel should -refer to the instructions in the next - section. For more information about - recompiling a kernel, refer to . + To determine which driver was selected for the sound card + after loading the snd_driver metadriver, + type cat /dev/sndstat. + + Users who prefer to statically compile in support for the + sound card in a custom kernel should refer to the instructions + in the next section. For more information about recompiling a + kernel, refer to . Configuring a Custom Kernel with Sound Support When using a custom kernel to provide sound support, make - sure that the audio framework driver -exists in the custom kernel configuration file: + sure that the audio framework driver exists in the custom kernel + configuration file: device sound - Next, add support for the sound card. - Therefore, you need to know which driver supports the card. - To - continue the example of the Creative &soundblaster; Live! - sound card from the previous section, use the following line - in the custom kernel configuration file: + Next, add support for the sound card. Therefore, you need + to know which driver supports the card. To continue the example + of the Creative &soundblaster; Live! sound card from the + previous section, use the following line in the custom kernel + configuration file: device snd_emu10k1 @@ -208,10 +197,10 @@ exists in the custom kernel configuratio found in /usr/src/sys/conf/NOTES. Non-PnP ISA sound cards may require the IRQ and I/O port - settings of the card to be added -to /boot/device.hints. During the - boot process, &man.loader.8; reads this file and passes - the settings to the kernel. For example, an old Creative + settings of the card to be added to + /boot/device.hints. During the boot + process, &man.loader.8; reads this file and passes the + settings to the kernel. For example, an old Creative &soundblaster; 16 ISA non-PnP card will use the &man.snd.sbc.4; driver in conjunction with snd_sb16. For this card, the following @@ -235,13 +224,13 @@ hint.sbc.0.flags="0x15" The syntax used in /boot/device.hints is described in - &man.sound.4; and the manual page - for the driver of the sound card. + &man.sound.4; and the manual page for the driver of the sound + card. The settings shown above are the defaults. In some cases, the IRQ or other settings may need to be changed to - match the card. Refer to &man.snd.sbc.4; for more - information about this card. + match the card. Refer to &man.snd.sbc.4; for more information + about this card. @@ -251,14 +240,14 @@ hint.sbc.0.flags="0x15" After rebooting into the custom kernel, or after loading the required module, the sound card should appear in the system message buffer. Run &man.dmesg.8; and look for a message -like: + like: pcm0: <Intel ICH3 (82801CA)> port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: <Cirrus Logic CS4205 AC97 Codec> - The status of the sound card may also be checked -using this command: + The status of the sound card may also be checked using this + command: &prompt.root; cat /dev/sndstat FreeBSD Audio Driver (newpcm) @@ -272,35 +261,31 @@ kld snd_ich (1p/2r/0v channels duplex de device driver was chosen. Common problems are listed in . - If all goes well, the sound - card should now work in os;. If the CD-ROM or DVD-ROM drive's -audio-out pins are - properly connected to the sound card, one can insert an audio CD -in the + If all goes well, the sound card should now work in os;. If + the CD-ROM or DVD-ROM drive's audio-out pins are properly + connected to the sound card, one can insert an audio CD in the drive and play it with &man.cdcontrol.1;: &prompt.user; cdcontrol -f /dev/acd0 play 1 Various applications, such as audio/workman provide a - friendlier interface. The audio/mpg123 port can be installed to - listen to MP3 audio files. + role="package">audio/workman provide a friendlier + interface. The audio/mpg123 + port can be installed to listen to MP3 audio files. - Another quick way to test the card is to send data - to /dev/dsp: + Another quick way to test the card is to send data to + /dev/dsp: &prompt.user; cat filename > /dev/dsp where filename can - be any file. This command should produce some noise, - confirming that the sound card is actually working. + be any file. This command should produce some noise, confirming + that the sound card is actually working. The /dev/dsp* device nodes will -be - created automatically as needed. When not in use, they + be created automatically as needed. When not in use, they do not exist and will not appear in the output of &man.ls.1;. @@ -351,9 +336,8 @@ be xxx: can't open /dev/dsp! Check with fstat | grep - dsp - if another application is holding the device open. - Noteworthy troublemakers are + dsp if another application is holding the + device open. Noteworthy troublemakers are esound and KDE's sound support. @@ -365,9 +349,9 @@ be 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 sound card and the - sound card will subsequently not be used as the default - playback device. To check if this is the case, run + sometimes be enumerated before the sound card and the sound + card 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: @@ -393,16 +377,15 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Here the graphics card (NVidia) has been enumerated before the sound card (Realtek ALC889). To use the sound card as the default -playback - device, change hw.snd.default_unit to the - unit that should be used for playback: + playback device, change hw.snd.default_unit + to the unit that should be used for playback: &prompt.root; sysctl hw.snd.default_unit=n Here, n is the number of the sound device to use. In this example, it should be -4. - Make this change permanent by adding the following line to + 4. Make this change permanent by adding + the following line to /etc/sysctl.conf: hw.snd.default_unit=4 @@ -422,12 +405,10 @@ playback Utilizing Multiple Sound Sources It is often desirable to have multiple sources of sound that - are able to play simultaneously. &os; uses -Virtual Sound - Channels, which can be enabled using - &man.sysctl.8;. Virtual channels allow one to - multiplex the sound card's playback by mixing sound in the - kernel. + are able to play simultaneously. &os; uses Virtual + Sound Channels, which can be enabled using + &man.sysctl.8;. Virtual channels allow one to multiplex the + sound card's playback by mixing sound in the kernel. To set the number of virtual channels, three &man.sysctl.8; knobs are available: @@ -448,20 +429,19 @@ playback pcm module can be loaded independently of the hardware drivers, hw.snd.maxautovchans indicates how many virtual channels will be given to devices -when they are attached. Refer to &man.pcm.4; - for more information. + when they are attached. Refer to &man.pcm.4; for more + information. - The number of virtual channels for a - device cannot be changed while it is in use. First, close any -programs using + The number of virtual channels for a device cannot be + changed while it is in use. First, close any programs using the device, such as music players or sound daemons. The correct pcm device will - automatically be allocated transparently to a program - that requests /dev/dsp0. + automatically be allocated transparently to a program that + requests /dev/dsp0. @@ -479,19 +459,19 @@ programs using The default values for the different mixer channels are hardcoded in the source code of the &man.pcm.4; driver. There - are many different applications and daemons that allow - values to be set for the mixer that are remembered between - invocations, but this is not a clean solution. It is possible - to set default mixer values at the driver level. This - is accomplished by defining the appropriate values in + are many different applications and daemons that allow values to + be set for the mixer that are remembered between invocations, + but this is not a clean solution. It is possible to set default + mixer values at the driver level. This is accomplished by + defining the appropriate values in /boot/device.hints, as seen in this -example: + example: hint.pcm.0.vol="50" This will set the volume channel to a default value of 50 when the &man.pcm.4; module is -loaded. + loaded. @@ -536,16 +516,15 @@ loaded. The audio/mpg123 port provides an alternative, command-line MP3 -player. + player. mpg123 can be run by specifying the sound device and the MP3 file on the -command line. - Assuming the audio device is + command line. Assuming the audio device is /dev/dsp1.0 and the MP3 file is -Foobar-GreatestHits.mp3, - enter the following to play the file: + Foobar-GreatestHits.mp3, enter the + following to play the file: &prompt.root; mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. @@ -565,23 +544,20 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz Ripping CD Audio Tracks Before encoding a CD or CD track to -MP3, the audio data on - the CD must be ripped to the hard drive. This is done by - copying the raw CD + MP3, the audio data on the CD must be + ripped to the hard drive. This is done by copying the raw CD Digital Audio (CDDA) data to -WAV - files. + WAV files. The cdda2wav tool, which is installed -with - the sysutils/cdrtools + with the sysutils/cdrtools suite, is used for ripping audio information from CDs and the information associated with them. With the audio CD in the drive, the following command can be issued as root to rip an entire CD into individual (per track) WAV -files: + files: &prompt.root; cdda2wav -D 0,1,0 -B @@ -590,10 +566,10 @@ files: which corresponds to the output of cdrecord -scanbus. - cdda2wav will support - ATAPI (IDE) CDROM drives. To rip from an IDE drive, specify - the device name in place of the SCSI unit numbers. For - example, to rip track 7 from an IDE drive: + cdda2wav will support ATAPI + (IDE) CDROM drives. To rip from an IDE drive, specify the + device name in place of the SCSI unit numbers. For example, + to rip track 7 from an IDE drive: &prompt.root; cdda2wav -D /dev/acd0 -t 7 @@ -608,8 +584,8 @@ files: &prompt.root; cdda2wav -D 0,1,0 -t 1+7 - &man.dd.1; can also be used to extract audio - tracks on ATAPI drives, as described in &man.dd.1; can also be used to extract audio tracks on + ATAPI drives, as described in . @@ -619,12 +595,11 @@ files: Lame is a popular -MP3 encoder which can be installed from the + MP3 encoder which can be installed from the audio/lame port. Due to licensing restrictions, a package is not available. - The following command will - convert the ripped + The following command will convert the ripped WAV files audio01.wav to @@ -640,29 +615,26 @@ files: audio01.wav audio01.mp3 128 kbits is a standard MP3 -bitrate. The 160 and 192 bitrates provide higher quality. The higher - the bitrate, the larger the size of the resulting - MP3. - turns on the higher quality - but a little slower mode. The options beginning with - indicate ID3 tags, which usually contain - song information, to be embedded within the -MP3 file. - Additional encoding options can be found in the - lame manual page. + bitrate. The 160 and 192 bitrates provide higher quality. + The higher the bitrate, the larger the size of the resulting + MP3. turns on the + higher quality but a little slower mode. The + options beginning with indicate ID3 tags, + which usually contain song information, to be embedded within + the MP3 file. Additional encoding options + can be found in the lame manual + page. Decoding MP3s In order to burn an audio CD from MP3s, -they must first be - converted to a non-compressed WAV format. -Both + they must first be converted to a non-compressed + WAV format. Both XMMS and mpg123 support the output of -MP3 - to an uncompressed file format. + MP3 to an uncompressed file format. Writing to Disk in XMMS: @@ -697,25 +669,22 @@ Both Load the MP3 file into -XMMS - as usual, with volume at 100% and EQ settings turned - off. + XMMS as usual, with volume at + 100% and EQ settings turned off. Press Play. The XMMS will appear as if it is playing the MP3, but no music will be -heard. It is - actually playing the MP3 to a -file. + heard. It is actually playing the MP3 + to a file. When finished, be sure to set the default Output -Plugin back to what - it was before in order to listen to -MP3s again. + Plugin back to what it was before in order to listen to + MP3s again. @@ -731,27 +700,23 @@ Plugin back to what XMMS writes a file in the -WAV - format, while mpg123 converts the + WAV format, while + mpg123 converts the MP3 into raw PCM audio data. Both of these -formats can be - used with cdrecord to create audio - CDs, whereas &man.burncd.8; requires a raw Pulse-Code -Modulation (PCM. When using + formats can be used with cdrecord + to create audio CDs, whereas &man.burncd.8; requires a raw + Pulse-Code Modulation (PCM. When using WAV files, there will be a small tick -sound at the - beginning of each track. This sound is the header of the -WAV - file. One can remove the header with - SoX, which can be + sound at the beginning of each track. This sound is the + header of the WAV file. One can remove the + header with SoX, which can be installed from the audio/sox port or package: &prompt.user; sox -t wav -r 44100 -s -w -c 2 track.wav track.raw Refer to for more -information - on using a CD burner in &os;. + information on using a CD burner in &os;. @@ -770,44 +735,39 @@ information Video Playback Before configuring video playback, determine the model -of the video - card and the chip it uses. While + of the video card and the chip it uses. While &xorg; supports a wide variety of video cards, fewer give good playback performance. To obtain a list of extensions supported by the -&xorg; server using the card, run + &xorg; server using the card, run &man.xdpyinfo.1; while &xorg; is -running. + running. It is a good idea to have a short MPEG test file for -evaluating various players and - options. Since some DVD applications look for DVD media in - /dev/dvd by default, or -have this device - name hardcoded in them, it might be useful to make + evaluating various players and options. Since some DVD + applications look for DVD media in /dev/dvd by default, or have this + device name hardcoded in them, it might be useful to make symbolic links to the proper devices: &prompt.root; ln -sf /dev/acd0 /dev/dvd &prompt.root; ln -sf /dev/acd0 /dev/rdvd - Due to the nature of &man.devfs.5;, - manually created links will not persist after a system reboot. - In order to create the symbolic links - automatically when the system boots, add the following - lines to /etc/devfs.conf: + Due to the nature of &man.devfs.5;, manually created links + will not persist after a system reboot. In order to create the + symbolic links automatically when the system boots, add the + following lines to /etc/devfs.conf: link acd0 dvd link acd0 rdvd - DVD decryption invokes - special DVD-ROM functions and requires write permission on the -DVD - devices. + DVD decryption invokes special DVD-ROM functions and + requires write permission on the DVD devices. To enhance the shared memory -&xorg; interface, it is + &xorg; interface, it is recommended to increase the values of these &man.sysctl.8; -variables: + variables: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 @@ -820,33 +780,32 @@ kern.ipc.shmall=32768 DGA There are several possible ways to display video under -&xorg;. - What works is largely hardware dependent. Each - method described below will have varying quality across - different hardware. + &xorg;. What works is largely + hardware dependent. Each method described below will have + varying quality across different hardware. Common video interfaces include: - &xorg;: normal output -using shared memory. + &xorg;: normal output using + shared memory. XVideo: an extension to the -&xorg; interface which supports + &xorg; interface which supports video in any drawable object. SDL: the Simple Directmedia -Layer. + Layer. DGA: the Direct Graphics -Access. + Access. @@ -858,9 +817,8 @@ Access. XVideo &xorg; has an extension called - XVideo, also known as Xvideo, -Xv, and xv. It - allows video to be directly displayed in drawable objects + XVideo, also known as Xvideo, Xv, and xv. + It allows video to be directly displayed in drawable objects through a special acceleration. This extension provides good quality playback even on low-end machines. @@ -941,9 +899,9 @@ Xv, and xv. It depth: 1 red, green, blue masks: 0x0, 0x0, 0x0 - The formats listed, such as YUV2 and YUV12, are - not present with every implementation of XVideo and their - absence may hinder some players. + The formats listed, such as YUV2 and YUV12, are not present + with every implementation of XVideo and their absence may hinder + some players. If the result looks like: @@ -951,26 +909,24 @@ Xv, and xv. It screen #0 no adaptors present - XVideo is probably not supported for the card. This -means + XVideo is probably not supported for the card. This means that it will be more difficult for the display to meet the computational demands of rendering video. Depending on the - video card and processor, one might still be able to - have a satisfying experience. + video card and processor, one might still be able to have a + satisfying experience. Simple Directmedia Layer - SDL is intended to be a - porting layer between µsoft.windows; and &unix;, - allowing cross-platform applications to be developed which make - efficient use of sound and graphics. The SDL -layer provides a + SDL is intended to be a porting layer + between µsoft.windows; and &unix;, allowing cross-platform + applications to be developed which make efficient use of sound + and graphics. The SDL layer provides a low-level abstraction to the hardware which can sometimes be more efficient than the &xorg; -interface. + interface. SDL can be installed using the devel/sdl12 package or port. @@ -981,18 +937,16 @@ interface. Direct Graphics Access DGA is an -&xorg; extension which allows - a program to bypass the &xorg; server -and directly alter the - framebuffer. Because it relies on a low level memory mapping, -programs using it must be run as + &xorg; extension which allows a + program to bypass the &xorg; server + and directly alter the framebuffer. Because it relies on a low + level memory mapping, programs using it must be run as root. The DGA extension can be tested and -benchmarked using - &man.dga.1;. When dga is running, it - changes the colors of the display whenever a key is pressed. To - quit, press q. + benchmarked using &man.dga.1;. When dga is + running, it changes the colors of the display whenever a key is + pressed. To quit, press q. @@ -1004,15 +958,13 @@ benchmarked using video packages This section introduces some of the software available from -the - &os; Ports Collection which can be used for video -playback. - - Many of the video - applications which run on &os; were developed as &linux; - applications. Many of these applications are still - beta-quality. Some of the problems commonly encountered with - video packages on &os; include: + the &os; Ports Collection which can be used for video + playback. + + Many of the video applications which run on &os; were + developed as &linux; applications. Many of these applications + are still beta-quality. Some of the problems commonly + encountered with video packages on &os; include: @@ -1052,13 +1004,12 @@ playback. Many applications may also exhibit - &linux;-isms. There may be issues - resulting from the way some standard libraries are - implemented in the &linux; distributions, or some features of - the &linux; kernel which have been assumed by the authors of the - applications. These issues are not always noticed and worked - around by the port maintainers, which can lead to problems like - these: + &linux;-isms. There may be issues resulting from + the way some standard libraries are implemented in the &linux; + distributions, or some features of the &linux; kernel which have + been assumed by the authors of the applications. These issues + are not always noticed and worked around by the port + maintainers, which can lead to problems like these: @@ -1073,7 +1024,7 @@ playback. Relies on software which is not yet available in the -&os; Ports Collection. + &os; Ports Collection. @@ -1093,21 +1044,20 @@ playback. making MPlayer is available as a -package or port in multimedia/mplayer. -Several compile options are available and a variety of hardware + package or port in multimedia/mplayer. Several + compile options are available and a variety of hardware checks occur during the build process. For these reasons, some users prefer to build the port rather than install the - package. The available options will be displayed in - a menu after these commands are input: + package. The available options will be displayed in a + menu after these commands are input: &prompt.root; cd /usr/ports/multimedia/mplayer &prompt.root; make The menu options should be reviewed to determine the -type of - support to compile into the port. If an option is not - selected, MPlayer will not be + type of support to compile into the port. If an option is + not selected, MPlayer will not be able to display that type of video format. Use the arrow keys and spacebar to select the required formats. When finished, press Enter to continue the port @@ -1175,8 +1125,8 @@ type of including the WITH_DVD_DEVICE=/path/to/desired/device option. By default, the device is - /dev/acd0. More - details can be found in the port's + /dev/acd0. More details can be found + in the port's Makefile.options. @@ -1185,21 +1135,20 @@ type of -h, or read the manual page. Additional playback options include - , which engages fullscreen -mode, + , which engages fullscreen mode, and , which helps performance. Each user can add commonly used options to their ~/.mplayer/config like so: - + vo=xv fs=yes zoom=yes - mplayer can be used to rip a - DVD title to a .vob. To dump - the second title from a DVD: + mplayer can be used to rip a DVD + title to a .vob. To dump the second + title from a DVD: &prompt.root; mplayer -dumpstream -dumpfile out.vob dvd://2 -dvd-device /dev/dvd @@ -1226,13 +1175,12 @@ zoom=yes Before using mencoder, it is a good idea to become familiar with the options described in the -HTML - documentation. There are - innumerable ways to improve quality, lower bitrate, and - change formats, and some of these options may make the - difference between good or bad performance. Improper -combinations of command line options + HTML + documentation. There are innumerable ways to + improve quality, lower bitrate, and change formats, and some + of these options may make the difference between good or bad + performance. Improper combinations of command line options can yield output files that are unplayable even by mplayer. @@ -1240,8 +1188,7 @@ combinations of command line options &prompt.user; mencoder input.avi -oac copy -ovc copy -o output.avi - To rip - to a file, use with + To rip to a file, use with mplayer. To convert @@ -1255,17 +1202,15 @@ combinations of command line options -ovc lavc -lavcopts vcodec=mpeg4:vhq -o output.avi This will produce output playable by applications such -as - mplayer and + as mplayer and xine. input.avi can be replaced with and run as root to re-encode a DVD title directly. Since it may take a few -tries to get the desired result, - it is recommended to dump the title to a file and to work on - the file. + tries to get the desired result, it is recommended to dump + the title to a file and to work on the file. @@ -1274,20 +1219,19 @@ tries to get the desired result, The <application>xine</application> Video Player xine is a video player with a -reusable base library - and a modular executable which can be extended with plugins. - It can be installed using the multimedia/xine package or -port. - - In practice, xine - requires either a fast CPU with a fast video card, or support - for the XVideo extension. The xine - video player performs best on XVideo interfaces. + reusable base library and a modular executable which can be + extended with plugins. It can be installed using the + multimedia/xine package or + port. + + In practice, xine requires + either a fast CPU with a fast video card, or support for the + XVideo extension. The xine video + player performs best on XVideo interfaces. By default, the xine player - starts a graphical user interface. The menus can then - be used to open a specific file. + starts a graphical user interface. The menus can then be used + to open a specific file. Alternatively, xine may be invoked to play a file immediately without the graphical @@ -1301,21 +1245,21 @@ port. &prompt.user; xine -g -p mymovie.avi The + url="http://dvd.sourceforge.net/xine-howto/en_GB/html/howto.html"> xine HOWTO contains a chapter on performance improvement which is general to all players. The <application>transcode</application> -Utilities + Utilities transcode provides a suite of -tools for re-encoding video and audio - files. transcode can be used - to merge video files or repair broken files using - command line tools with stdin/stdout - stream interfaces. + tools for re-encoding video and audio files. + transcode can be used to merge + video files or repair broken files using command line tools + with stdin/stdout stream + interfaces. transcode can be installed using the Enter to continue the port compile and installation. - This example demonstrates how to convert a DivX file into + This example demonstrates how to convert a DivX file into a PAL MPEG-1 file (PAL VCD): &prompt.user; transcode -i @@ -1339,15 +1283,13 @@ tools for re-encoding video and audio The resulting MPEG file, output_vcd.mpg, is ready to be played with MPlayer. - The file can be burned on a CD-R media to create a -Video - CD. In this, install and use the -multimedia/vcdimager and sysutils/cdrdao programs. In addition to the manual page for -transcode, refer to the transcode, refer to the transcode wiki for further information and examples. @@ -1383,34 +1325,29 @@ Video Introduction TV cards allow can be used to watch broadcast or cable TV on -a - computer. Most cards accept composite video via an RCA or - S-video input and some cards include a FM radio - tuner. *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Fri Apr 26 16:44:44 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96B822A5; Fri, 26 Apr 2013 16:44:44 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 89B541225; Fri, 26 Apr 2013 16:44:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3QGii70058835; Fri, 26 Apr 2013 16:44:44 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3QGii5I058834; Fri, 26 Apr 2013 16:44:44 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304261644.r3QGii5I058834@svn.freebsd.org> From: Dru Lavigne Date: Fri, 26 Apr 2013 16:44:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41506 - projects/ISBN_1-57176-407-0/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 16:44:44 -0000 Author: dru Date: Fri Apr 26 16:44:44 2013 New Revision: 41506 URL: http://svnweb.freebsd.org/changeset/doc/41506 Log: Add missing Kerberos entities. Approved by: gjb (mentor) Modified: projects/ISBN_1-57176-407-0/share/xml/man-refs.ent Modified: projects/ISBN_1-57176-407-0/share/xml/man-refs.ent ============================================================================== --- projects/ISBN_1-57176-407-0/share/xml/man-refs.ent Fri Apr 26 12:28:24 2013 (r41505) +++ projects/ISBN_1-57176-407-0/share/xml/man-refs.ent Fri Apr 26 16:44:44 2013 (r41506) @@ -292,6 +292,7 @@ kbdcontrol1"> kbdmap1"> kcon1"> +kdestroy1"> kdump1"> kenv1"> kerberos1"> @@ -303,6 +304,8 @@ kgdb1"> kill1"> killall1"> +kinit1"> +klist1"> ksu1"> ktrace1"> lam1"> @@ -4415,6 +4418,7 @@ jls8"> joy8"> k5su8"> +kadmin8"> kadmind8"> kernbb8"> keyserv8"> @@ -4426,6 +4430,7 @@ kldstat8"> kldunload8"> kldxref8"> +kstash8"> ktrdump8"> kzip8"> l2control8">