From owner-svn-doc-all@FreeBSD.ORG Thu May 15 00:14:10 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B7414FC; Thu, 15 May 2014 00:14:10 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5771D293D; Thu, 15 May 2014 00:14:10 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4F0EAQ6041001; Thu, 15 May 2014 00:14:10 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4F0EAml041000; Thu, 15 May 2014 00:14:10 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405150014.s4F0EAml041000@svn.freebsd.org> From: Dru Lavigne Date: Thu, 15 May 2014 00:14:10 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44838 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2014 00:14:10 -0000 Author: dru Date: Thu May 15 00:14:09 2014 New Revision: 44838 URL: http://svnweb.freebsd.org/changeset/doc/44838 Log: Remove most of the leftover instances of "you". Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 21:45:28 2014 (r44837) +++ head/en_US.ISO8859-1/books/faq/book.xml Thu May 15 00:14:09 2014 (r44838) @@ -6438,37 +6438,33 @@ ATDT1234567 can be displayed using the show hdlc command. - If your link is bad (or if your serial driver is - dropping packets), you will see the occasional FCS error. + If the link is bad or if the serial driver is + dropping packets, it will produce the occasional FCS error. This is not usually worth worrying about although it does - slow down the compression protocols substantially. If you - have an external modem, make sure your cable is properly - shielded from interference — this may eradicate the - problem. - - If your link freezes as soon as you have connected and - you see a large number of FCS errors, this may be because - your link is not 8-bit clean. Make sure your modem is not - using software flow control (XON/XOFF). If your datalink - must use software flow control, use - the command set accmap 0x000a0000 to + slow down the compression protocols substantially. + + If the link freezes as soon as it connects and + produces a large number of FCS errors, make sure the modem is not + using software flow control (XON/XOFF). If the link + must use software flow control, use + set accmap 0x000a0000 to tell &man.ppp.8; to escape the ^Q and ^S characters. - Another reason for seeing too many FCS errors may be + Another reason for too many FCS errors may be that the remote end has stopped talking - PPP. You may want to enable - async logging at this point to + PPP. In this case, enable + async logging to determine if the incoming data is actually a login or - shell prompt. If you have a shell prompt at the remote + shell prompt. If it is a shell prompt at the remote end, it is possible to terminate &man.ppp.8; without - dropping the line by using close lcp (a - following term) will reconnect you to + dropping the line by using close lcp followed by + term) to reconnect to the shell on the remote machine. - If nothing in your log file indicates why the link - might have been terminated, you should ask the remote - administrator (your ISP?) why the session was + If nothing in the log file indicates why the link + was terminated, ask the remote + administrator or ISP why the session was terminated. @@ -6480,12 +6476,11 @@ ATDT1234567 - If all else fails, send as much information as you - can, including your config files, how you are starting - &man.ppp.8;, the relevant parts of your log file and the - output of netstat -rn (before and after - connecting) to the &a.questions; and someone should point - you in the right direction. + If all else fails, send the details of the error, the + configuration files, how + &man.ppp.8; is being started, the relevant parts of the log file, and the + output of netstat -rn, before and after + connecting, to the &a.questions;. @@ -6542,38 +6537,34 @@ ATDT1234567 As the &os; kernel boots, it will probe for the serial - ports in your system for which the kernel was configured. - You can either watch your system closely for the messages - it prints or run this command after your system is up and + ports for which the kernel is configured. + Either watch the boot messages closely + or run this command after the system is up and running: - &prompt.user; dmesg | grep -E "^sio[0-9]" - - Here is some example output from the above - command: - - sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 + &prompt.user; dmesg | grep -E "^sio[0-9]" +sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 -sio1: type 16550A +sio1: type 16550A - This shows two serial ports. The first is on - IRQ 4, is using port address + This example shows two serial ports. The first is on + IRQ4, port address 0x3f8, and has a 16550A-type UART chip. The second uses the same kind of chip but is on - IRQ 3 and is at port address + IRQ3 and is at port address 0x2f8. Internal modem cards are - treated just like serial ports — except that they - always have a modem attached to the + treated just like serial ports, except that they + always have a modem attached to the port. The GENERIC kernel includes support for two serial ports using the same IRQ and port address settings in the above example. If these settings - are not right for your system, or if you have added modem - cards or have more serial ports than your kernel is - configured for, just reconfigure your kernel. See section - about building a kernel + are not right for the system, or if there are more modem + cards or serial ports than the kernel is + configured for, reconfigure using the instructions in + building a kernel for more details. @@ -6584,28 +6575,28 @@ sio1: type 16550A - The third serial port, sio2 (see - &man.sio.4;, known as COM3 in DOS), + The third serial port, sio2, + or COM3, is on /dev/cuad2 for dial-out devices, and on /dev/ttyd2 for dial-in devices. What is the difference between these two classes of devices? - You use ttydX for dial-ins. When + When opening /dev/ttydX in blocking mode, a process will wait for the corresponding cuadX device to become inactive, and then wait for the carrier - detect line to go active. When you open the - cuadX device, it makes sure the + detect line to go active. When the + cuadX device is opened, it makes sure the serial port is not already in use by the ttydX device. If the port is available, it - steals it from the + steals it from the ttydX device. Also, the cuadX device does not care about carrier detect. With this scheme and an auto-answer - modem, you can have remote users log in and you can still + modem, remote users can log in and local users can still dial out with the same modem and the system will take care of all the conflicts. @@ -6613,14 +6604,14 @@ sio1: type 16550A - How do I enable support for a multiport serial + How do I enable support for a multi-port serial card? - Again, the section on kernel configuration provides - information about configuring your kernel. For a - multiport serial card, place an &man.sio.4; line for each + The section on kernel configuration provides + information about configuring the kernel. For a + multi-port serial card, place an &man.sio.4; line for each serial port on the card in the &man.device.hints.5; file. But place the IRQ specifiers on only one of the entries. All of the ports on the card should share one IRQ. For @@ -6688,7 +6679,7 @@ hint.sio.7.irq="12" - You can find this information in the This information is in the Terminals section of the &os; Handbook. @@ -6701,18 +6692,18 @@ hint.sio.7.irq="12" - On your system, the programs &man.tip.1; and - &man.cu.1; can only access the + The built-in &man.tip.1; and + &man.cu.1; utilities can only access the /var/spool/lock directory via user uucp and group - dialer. You - can use the group dialer to control who has - access to your modem or remote systems. Just add yourself - to group dialer. + Use the dialer group to control who has + access to the modem or remote systems by adding user accounts + to dialer. - Alternatively, you can let everyone on your system run + Alternatively, everyone can be configured to run &man.tip.1; and &man.cu.1; by typing: &prompt.root; chmod 4511 /usr/bin/cu @@ -6741,8 +6732,8 @@ hint.sio.7.irq="12" Note that while &os; is proactive in this regard, it does not arbitrarily decide to swap pages when the system - is truly idle. Thus you will not find your system all - paged out when you get up in the morning after leaving it + is truly idle. Thus, the system will not be all + paged out after leaving it idle overnight. @@ -6755,7 +6746,7 @@ hint.sio.7.irq="12" The simple answer is that free memory is wasted - memory. Any memory that your programs do not actively + memory. Any memory that programs do not actively allocate is used within the &os; kernel as disk cache. The values shown by &man.top.1; labeled as Inact, Cache, and @@ -6778,9 +6769,9 @@ hint.sio.7.irq="12" Symlinks do not have permissions, and by default, &man.chmod.1; will follow symlinks to change the - permissions on the source file, if possible. So if you - have a file, foo, and a symlink to - that file, bar, then this command + permissions on the source file, if possible. For + the file, foo with a symlink named + bar, this command will always succeed. &prompt.user; chmod g-w bar @@ -6789,7 +6780,7 @@ hint.sio.7.irq="12" will not have changed. When changing modes of the file hierarchies rooted in - the files instead of the files themselves, you have to use + the files instead of the files themselves, use either or together with to make this work. See &man.chmod.1; and &man.symlink.7; for more @@ -6799,14 +6790,14 @@ hint.sio.7.irq="12" does a recursive &man.chmod.1;. Be careful about specifying directories or symlinks to - directories to &man.chmod.1;. If you want to change the + directories to &man.chmod.1;. To change the permissions of a directory referenced by a symlink, use &man.chmod.1; without any options and follow the symlink with a trailing slash (/). For example, if foo is a symlink to - directory bar, and you want to + directory bar, to change the permissions of foo - (actually bar), you would do + (actually bar), do something like: &prompt.user; chmod 555 foo/ @@ -6825,18 +6816,18 @@ hint.sio.7.irq="12" - Yes, you can use emulators/doscmd, - a DOS emulation program, available in the &os; Ports + Yes. A DOS emulation program, emulators/doscmd, + is available in the &os; Ports Collection. If doscmd will not suffice, - the add-on utility emulators/pcemu + emulators/pcemu emulates an 8088 and enough BIOS services to run many DOS - text mode applications. It requires the X Window + text-mode applications. It requires the X Window System. - You may also try emulators/dosbox - from the &os; Ports Collection. The main focus of this + The Ports Collection also has emulators/dosbox. + The main focus of this application is emulating old DOS games using the local file system for files. @@ -6886,7 +6877,7 @@ hint.sio.7.irq="12" - Other advice to help your mail reach its destination + Other advice to help mail reach its destination include: @@ -6904,7 +6895,7 @@ hint.sio.7.irq="12" If you still have trouble with email infrastructure at - FreeBSD.org + FreeBSD.org, send a note with the details to postmaster@freebsd.org; Include a date/time interval so that logs may be reviewed — @@ -6953,7 +6944,7 @@ hint.sio.7.irq="12" beastie is pronounced BSD. - You can learn more about the BSD daemon on his More about the BSD daemon is available on his home page. @@ -6966,15 +6957,15 @@ hint.sio.7.irq="12" Perhaps. The BSD daemon is copyrighted by Marshall - Kirk McKusick. You will want to check his Statement on the Use of the BSD Daemon Figure for detailed usage terms. - In summary, you are free to use the image in a + In summary, the image can be used in a tasteful manner, for personal use, so long as appropriate - credit is given. If you want to use him commercially, you - must contact &a.mckusick.email;. More details are + credit is given. Before using the logo commercially, + contact &a.mckusick.email; for permission. More details are available on the BSD Daemon's home page. @@ -6987,7 +6978,7 @@ hint.sio.7.irq="12" - You will find eps and Xfig drawings under + Xfig and eps drawings are available under /usr/share/examples/BSD_daemon/. @@ -7005,7 +6996,9 @@ hint.sio.7.irq="12" Glossary. - + + +