From owner-svn-doc-head@FreeBSD.ORG Tue May 13 15:39:11 2014 Return-Path: Delivered-To: svn-doc-head@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 B576854C; Tue, 13 May 2014 15:39:11 +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 A112E2251; Tue, 13 May 2014 15:39:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4DFdBMn045776; Tue, 13 May 2014 15:39:11 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4DFdB84045775; Tue, 13 May 2014 15:39:11 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405131539.s4DFdB84045775@svn.freebsd.org> From: Dru Lavigne Date: Tue, 13 May 2014 15:39:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44819 - 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-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2014 15:39:11 -0000 Author: dru Date: Tue May 13 15:39:11 2014 New Revision: 44819 URL: http://svnweb.freebsd.org/changeset/doc/44819 Log: White space fix only. Translators can ignore. 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 Tue May 13 03:34:52 2014 (r44818) +++ head/en_US.ISO8859-1/books/faq/book.xml Tue May 13 15:39:11 2014 (r44819) @@ -6141,8 +6141,8 @@ Key F15 A A Menu Wo This command may be typed at the &man.ppp.8; command prompt or it may be entered in the /etc/ppp/ppp.conf configuration file - (the start of the default section is the - best place to put it). Make sure that + (the start of the default section is + the best place to put it). Make sure that /etc/syslog.conf (see &man.syslog.conf.5;) contains the lines below and the file /var/log/ppp.log exists: @@ -6500,11 +6500,11 @@ deny pred1 deflate deflate24 protocomp a set openmode active 3 - This tells &man.ppp.8; to be passive for 3 seconds, and - then to start sending LCP requests. If the peer starts - sending requests during this period, &man.ppp.8; will - immediately respond rather than waiting for the full 3 - second period. + This tells &man.ppp.8; to be passive for 3 seconds, + and then to start sending LCP requests. If the peer + starts sending requests during this period, &man.ppp.8; + will immediately respond rather than waiting for the full + 3 second period. @@ -6516,38 +6516,44 @@ deny pred1 deflate deflate24 protocomp a There is currently an implementation mis-feature in - &man.ppp.8; where it does not associate LCP, CCP & IPCP - responses with their original requests. As a result, if one - PPP implementation is more than 6 seconds slower than the - other side, the other side will send two additional LCP - configuration requests. This is fatal. - - Consider two implementations, A and - B. A starts sending LCP - requests immediately after connecting and B - takes 7 seconds to start. When B starts, - A has sent 3 LCP REQs. We are assuming the - line has ECHO switched off, otherwise we would see magic - number problems as described in the previous section. - B sends a REQ, then an ACK to the first of - A's REQs. This results in - A entering the OPENED - state and sending and ACK (the first) back to - B. In the meantime, B - sends back two more ACKs in response to the two additional - REQs sent by A before B - started up. B then receives the first ACK + &man.ppp.8; where it does not associate LCP, CCP & + IPCP responses with their original requests. As a result, + if one PPP implementation is more than 6 seconds slower + than the other side, the other side will send two + additional LCP configuration requests. This is + fatal. + + Consider two implementations, + A and B. + A starts sending LCP requests + immediately after connecting and + B takes 7 seconds to start. When + B starts, + A has sent 3 LCP REQs. We are + assuming the line has ECHO switched off, otherwise we + would see magic number problems as described in the + previous section. B sends a REQ, + then an ACK to the first of A's + REQs. This results in A entering + the OPENED state and sending and ACK + (the first) back to B. In the + meantime, B sends back two more + ACKs in response to the two additional REQs sent by + A before + B started up. + B then receives the first ACK from A and enters the - OPENED state. A - receives the second ACK from B and goes - back to the REQ-SENT state, sending - another (forth) REQ as per the RFC. It then receives the - third ACK and enters the OPENED state. - In the meantime, B receives the forth REQ - from A, resulting in it reverting to the - ACK-SENT state and sending another - (second) REQ and (forth) ACK as per the RFC. - A gets the REQ, goes into + OPENED state. + A receives the second ACK from + B and goes back to the + REQ-SENT state, sending another (forth) + REQ as per the RFC. It then receives the third ACK and + enters the OPENED state. In the + meantime, B receives the forth + REQ from A, resulting in it + reverting to the ACK-SENT state and + sending another (second) REQ and (forth) ACK as per the + RFC. A gets the REQ, goes into REQ-SENT and sends another REQ. It immediately receives the following ACK and enters OPENED. @@ -6556,15 +6562,16 @@ deny pred1 deflate deflate24 protocomp a getting nowhere and gives up. The best way to avoid this is to configure one side to - be passive — that is, make one side - wait for the other to start negotiating. This can be done - with the following command: + be passive — that is, make one + side wait for the other to start negotiating. This can be + done with the following command: set openmode passive - Care should be taken with this option. You should also - use this command to limit the amount of time that - &man.ppp.8; waits for the peer to begin negotiations: + Care should be taken with this option. You should + also use this command to limit the amount of time that + &man.ppp.8; waits for the peer to begin + negotiations: set stopped N @@ -6596,8 +6603,8 @@ deny pred1 deflate deflate24 protocomp a waiting for the command to complete. To execute commands like this, use - !bg instead. This will execute - the given command in the background, and &man.ppp.8; can + !bg instead. This will execute the + given command in the background, and &man.ppp.8; can continue to service the link. @@ -6639,14 +6646,15 @@ deny pred1 deflate deflate24 protocomp a This will log all traffic through the connection. The next time the line comes up unexpectedly, you will see the - reason logged with a convenient timestamp next to it. + reason logged with a convenient timestamp next to + it. You can now disable dialing under these circumstances. - Usually, this sort of problem arises due to DNS lookups. To - prevent DNS lookups from establishing a connection (this - will not prevent &man.ppp.8; from - passing the packets through an established connection), use - the following: + Usually, this sort of problem arises due to DNS lookups. + To prevent DNS lookups from establishing a connection + (this will not prevent &man.ppp.8; + from passing the packets through an established + connection), use the following: set dfilter 1 deny udp src eq 53 set dfilter 2 deny udp dst eq 53 @@ -6658,21 +6666,23 @@ set dfilter 3 permit 0/0 0/0 In the DNS case, you should try to determine what is - actually trying to resolve a host name. A lot of the time, - &man.sendmail.8; is the culprit. You should make sure that - you tell sendmail not to do any - DNS lookups in its configuration file. See the section on - using email with a dialup connection - in the &os; Handbook for details on how to create your own - configuration file and what should go into it. You may also - want to add the following line to + actually trying to resolve a host name. A lot of the + time, &man.sendmail.8; is the culprit. You should make + sure that you tell sendmail not + to do any DNS lookups in its configuration file. See the + section on using + email with a dialup connection in the &os; + Handbook for details on how to create your own + configuration file and what should go into it. You may + also want to add the following line to .mc: define(`confDELIVERY_MODE', `d')dnl - This will make sendmail queue - everything until the queue is run (usually, sendmail is - run with , telling it to run + This will make sendmail + queue everything until the queue is run (usually, sendmail + is run with , telling it to run the queue every 30 minutes) or until a sendmail -q is done (perhaps from your ppp.linkup). @@ -6703,7 +6713,8 @@ CCP: Received Terminate Ack (1) state = - Why does &man.ppp.8; not log my connection speed? + Why does &man.ppp.8; not log my connection + speed? @@ -6716,13 +6727,13 @@ CCP: Received Terminate Ack (1) state = This will make &man.ppp.8; log everything up until the last requested expect string. - If you wish to see your connect speed and are using PAP - or CHAP (and therefore do not have anything to + If you wish to see your connect speed and are using + PAP or CHAP (and therefore do not have anything to chat after the CONNECT in the dial script — no set login script), you must make sure that you instruct &man.ppp.8; to - expect the whole CONNECT line, something like - this: + expect the whole CONNECT line, something + like this: set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \ \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n" @@ -6742,18 +6753,18 @@ CCP: Received Terminate Ack (1) state = The ppp utility parses each line in your config files so that it can interpret strings - such as set phone "123 456 789" correctly - and realize that the number is actually only + such as set phone "123 456 789" + correctly and realize that the number is actually only one argument. To specify a " character, you must escape it using a backslash (\). When the chat interpreter parses each argument, it - re-interprets the argument to find any special - escape sequences such as \P or - \T (see the manual page). As a result of - this double-parsing, you must remember to use the correct - number of escapes. + re-interprets the argument to find any special escape + sequences such as \P or + \T (see the manual page). As a result + of this double-parsing, you must remember to use the + correct number of escapes. If you wish to actually send a \ character to (say) your modem, you would need something @@ -6789,17 +6800,18 @@ ATDT1234567 - The ppp utility (or any other - program for that matter) should never dump core. Because - &man.ppp.8; runs setuid (with an effective user ID of - 0), the operating system will not write - core image of &man.ppp.8; to disk before terminating it. - If, however &man.ppp.8; is actually terminating due to a - segmentation violation or some other signal that normally - causes core to be dumped, and you are - sure you are using the latest version (see the start of this - section), then you should install the system sources and do - the following: + The ppp utility (or any + other program for that matter) should never dump core. + Because &man.ppp.8; runs setuid (with an effective + user ID of 0), the operating + system will not write core image of &man.ppp.8; to disk + before terminating it. If, however &man.ppp.8; is + actually terminating due to a segmentation violation or + some other signal that normally causes core to be dumped, + and you are sure you are using the + latest version (see the start of this section), then you + should install the system sources and do the + following: &prompt.root; cd /usr/src/usr.sbin/ppp &prompt.root; echo STRIP= >> /etc/make.conf @@ -6807,10 +6819,11 @@ ATDT1234567 &prompt.root; make install clean You will now have a debuggable version of &man.ppp.8; - installed. You will have to be root to - run &man.ppp.8; as all of its privileges have been revoked. - When you start &man.ppp.8;, take a careful note of what your - current directory was at the time. + installed. You will have to be root to run &man.ppp.8; as + all of its privileges have been revoked. When you start + &man.ppp.8;, take a careful note of what your current + directory was at the time. Now, if and when &man.ppp.8; receives the segmentation violation, it will dump a core file called @@ -6829,12 +6842,13 @@ ATDT1234567 ..... All of this information should be given alongside your - question, making it possible to diagnose the problem. + question, making it possible to diagnose the + problem. If you are familiar with &man.gdb.1;, you may wish to find out some other bits and pieces such as what actually - caused the dump or the addresses and values of the relevant - variables. + caused the dump or the addresses and values of the + relevant variables. @@ -6847,61 +6861,64 @@ ATDT1234567 This was a known problem with &man.ppp.8; set up to negotiate a dynamic local IP number with the peer in - mode. It has been fixed a long time - ago — search the manual page for + mode. It has been fixed a long + time ago — search the manual page for iface. The problem was that when that initial program calls - &man.connect.2;, the IP number of the &man.tun.4; interface - is assigned to the socket endpoint. The kernel creates the - first outgoing packet and writes it to the &man.tun.4; - device. &man.ppp.8; then reads the packet and establishes a - connection. If, as a result of &man.ppp.8;'s dynamic IP - assignment, the interface address is changed, the original - socket endpoint will be invalid. Any subsequent packets - sent to the peer will usually be dropped. Even if they are - not, any responses will not route back to the originating - machine as the IP number is no longer owned by that - machine. + &man.connect.2;, the IP number of the &man.tun.4; + interface is assigned to the socket endpoint. The kernel + creates the first outgoing packet and writes it to the + &man.tun.4; device. &man.ppp.8; then reads the packet and + establishes a connection. If, as a result of + &man.ppp.8;'s dynamic IP assignment, the interface address + is changed, the original socket endpoint will be invalid. + Any subsequent packets sent to the peer will usually be + dropped. Even if they are not, any responses will not + route back to the originating machine as the IP number is + no longer owned by that machine. There are several theoretical ways to approach this - problem. It would be nicest if the peer would re-assign the - same IP number if possible. The current version of + problem. It would be nicest if the peer would re-assign + the same IP number if possible. The current version of &man.ppp.8; does this, but most other implementations do not. The easiest method from our side would be to never change the &man.tun.4; interface IP number, but instead to - change all outgoing packets so that the source IP number is - changed from the interface IP to the negotiated IP on the - fly. This is essentially what the - iface-alias option in the latest version - of &man.ppp.8; is doing (with the help of &man.libalias.3; - and &man.ppp.8;'s switch) — it - is maintaining all previous interface addresses and NATing - them to the last negotiated address. + change all outgoing packets so that the source IP number + is changed from the interface IP to the negotiated IP on + the fly. This is essentially what the + iface-alias option in the latest + version of &man.ppp.8; is doing (with the help of + &man.libalias.3; and &man.ppp.8;'s + switch) — it is maintaining all previous interface + addresses and NATing them to the last negotiated + address. Another alternative (and probably the most reliable) would be to implement a system call that changes all bound - sockets from one IP to another. &man.ppp.8; would use this - call to modify the sockets of all existing programs when a - new IP number is negotiated. The same system call could be - used by DHCP clients when they are forced - to call the bind() function for their - sockets. + sockets from one IP to another. &man.ppp.8; would use + this call to modify the sockets of all existing programs + when a new IP number is negotiated. The same system call + could be used by DHCP clients when they + are forced to call the bind() + function for their sockets. Yet another possibility is to allow an interface to be - brought up without an IP number. Outgoing packets would be - given an IP number of 255.255.255.255 up until the first - SIOCAIFADDR &man.ioctl.2; is done. This - would result in fully binding the socket. It would be up to - &man.ppp.8; to change the source IP number, but only if it - is set to 255.255.255.255, - and only the IP number and IP checksum would need to change. - This, however is a bit of a hack as the kernel would be - sending bad packets to an improperly configured interface, - on the assumption that some other mechanism is capable of - fixing things retrospectively. + brought up without an IP number. Outgoing packets would + be given an IP number of 255.255.255.255 up until + the first SIOCAIFADDR &man.ioctl.2; is + done. This would result in fully binding the socket. It + would be up to &man.ppp.8; to change the source IP number, + but only if it is set to 255.255.255.255, and only + the IP number and IP checksum would need to change. This, + however is a bit of a hack as the kernel would be sending + bad packets to an improperly configured interface, on the + assumption that some other mechanism is capable of fixing + things retrospectively. @@ -6913,26 +6930,27 @@ ATDT1234567 The reason games and the like do not work when - &man.libalias.3; is in use is that the machine on the outside - will try to open a connection or send (unsolicited) UDP - packets to the machine on the inside. The NAT software does - not know that it should send these packets to the interior - machine. + &man.libalias.3; is in use is that the machine on the + outside will try to open a connection or send + (unsolicited) UDP packets to the machine on the inside. + The NAT software does not know that it should send these + packets to the interior machine. To make things work, make sure that the only thing running is the software that you are having problems with, - then either run &man.tcpdump.1; on the &man.tun.4; interface - of the gateway or enable &man.ppp.8; TCP/IP logging - (set log +tcp/ip) on the gateway. + then either run &man.tcpdump.1; on the &man.tun.4; + interface of the gateway or enable &man.ppp.8; TCP/IP + logging (set log +tcp/ip) on the + gateway. When you start the offending software, you should see - packets passing through the gateway machine. When something - comes back from the outside, it will be dropped (that is the - problem). Note the port number of these packets then shut - down the offending software. Do this a few times to see if - the port numbers are consistent. If they are, then the - following line in the relevant section of - /etc/ppp/ppp.conf will make the + packets passing through the gateway machine. When + something comes back from the outside, it will be dropped + (that is the problem). Note the port number of these + packets then shut down the offending software. Do this a + few times to see if the port numbers are consistent. If + they are, then the following line in the relevant section + of /etc/ppp/ppp.conf will make the software functional: nat port proto internalmachine:port port @@ -6945,26 +6963,27 @@ ATDT1234567 number of the packets. You will not be able to use the software on other - machines without changing the above command, and running the - software on two internal machines at the same time is out of - the question — after all, the outside world is seeing - your entire internal network as being just a single - machine. + machines without changing the above command, and running + the software on two internal machines at the same time is + out of the question — after all, the outside world + is seeing your entire internal network as being just a + single machine. - If the port numbers are not consistent, there are three - more options: + If the port numbers are not consistent, there are + three more options: Submit support in &man.libalias.3;. Examples of special cases can be found in /usr/src/sys/netinet/libalias/alias_*.c - (alias_ftp.c is a good prototype). - This usually involves reading certain recognized - outgoing packets, identifying the instruction that tells - the outside machine to initiate a connection back to the - internal machine on a specific (random) port and setting - up a route in the alias table so that the + (alias_ftp.c is a good + prototype). This usually involves reading certain + recognized outgoing packets, identifying the + instruction that tells the outside machine to initiate + a connection back to the internal machine on a + specific (random) port and setting up a + route in the alias table so that the subsequent packets know where to go. This is the most difficult solution, but it is the @@ -6974,8 +6993,7 @@ ATDT1234567 Use a proxy. The application may support - socks5 for example, or - may have a + socks5 for example, or may have a passive option that avoids ever requesting that the peer open connections back to the local machine. @@ -6983,8 +7001,8 @@ ATDT1234567 Redirect everything to the internal machine using - nat addr. This is the sledge-hammer - approach. + nat addr. This is the + sledge-hammer approach. @@ -6996,12 +7014,12 @@ ATDT1234567 - FCS stands for Frame Check Sequence. Each - PPP packet has a checksum attached to ensure that the data - being received is the data being sent. If the FCS of an - incoming packet is incorrect, the packet is dropped and the - HDLC FCS count is increased. The HDLC error values can be - displayed using the show hdlc + FCS stands for Frame Check Sequence. Each PPP packet + has a checksum attached to ensure that the data being + received is the data being sent. If the FCS of an + incoming packet is incorrect, the packet is dropped and + the HDLC FCS count is increased. The HDLC error values + can be displayed using the show hdlc command. If your link is bad (or if your serial driver is @@ -7013,27 +7031,27 @@ ATDT1234567 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 tell - &man.ppp.8; to escape the ^Q 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 + tell &man.ppp.8; to escape the ^Q and ^S characters. Another reason for seeing 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 determine - if the incoming data is actually a login or shell prompt. - If you have 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 the - shell on the remote machine. + async logging at this point to + determine if the incoming data is actually a login or + shell prompt. If you have 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 + 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 + 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 terminated. @@ -7046,13 +7064,12 @@ ATDT1234567 - If all else fails, send as much information as you can, - including your config files, how you are starting + 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. + output of netstat -rn (before and after + connecting) to the &a.questions; and someone should point + you in the right direction. @@ -7062,7 +7079,8 @@ ATDT1234567 Serial Communications This section answers common questions about serial - communications with &os;. PPP is covered in the Networking section. + communications with &os;. PPP is covered in the Networking section. @@ -7072,8 +7090,9 @@ ATDT1234567 - There is a list of these in the Serial Communications - chapter of the handbook. + There is a list of these in the Serial + Communications chapter of the handbook. Most multi-port PCI cards that are based on 16550 or clones are supported with no extra effort. @@ -7093,7 +7112,9 @@ ATDT1234567 - See this section of the handbook. + See this + section of the handbook. @@ -7106,8 +7127,8 @@ 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 + You can either watch your system closely for the messages + it prints or run this command after your system is up and running: &prompt.user; dmesg | grep -E "^sio[0-9]" @@ -7121,20 +7142,23 @@ sio1: <16550A-compatible COM port> sio1: type 16550A This shows two serial ports. The first is on - IRQ 4, is using 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 - 0x2f8. Internal modem cards are 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 for - more details. + IRQ 4, is using 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 + 0x2f8. Internal modem cards are + 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 + for more details. @@ -7144,34 +7168,30 @@ sio1: type 16550A - The third serial port, sio2 - (see &man.sio.4;, known as COM3 in - DOS), is on /dev/cuad2 for dial-out + The third serial port, sio2 (see + &man.sio.4;, known as COM3 in DOS), + 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 opening - /dev/ttydX - in blocking mode, a process will wait for the corresponding + You use ttydX for dial-ins. 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 serial port is not already in use - by the - ttydX - device. If the port is available, it steals - it from the + cuadX device, it makes sure the + serial port is not already in use by 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 dial out with the same modem and the - system will take care of all the conflicts. + device. If the port is available, it + 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 + dial out with the same modem and the system will take care + of all the conflicts. @@ -7183,13 +7203,14 @@ sio1: type 16550A 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 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 consistency, use the - last serial port to specify the IRQ. Also, specify the - following option in the kernel configuration file: + information about configuring your kernel. For a + multiport 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 + consistency, use the last serial port to specify the IRQ. + Also, specify the following option in the kernel + configuration file: options COM_MULTIPORT @@ -7211,9 +7232,10 @@ hint.sio.7.port="0x2b8" hint.sio.7.flags="0x701" hint.sio.7.irq="12" - The flags indicate that the master port has minor number - 7 (0x700), and all the - ports share an IRQ (0x001). + The flags indicate that the master port has minor + number 7 (0x700), + and all the ports share an IRQ + (0x001). @@ -7224,8 +7246,10 @@ hint.sio.7.irq="12" - See the Serial Communications - section in the &os; Handbook. + See the Serial + Communications section in the &os; + Handbook. @@ -7235,18 +7259,21 @@ hint.sio.7.irq="12" - Please read the section about Dial-in Services - in the &os; Handbook. + Please read the section about Dial-in + Services in the &os; Handbook. - How can I connect a dumb terminal to my &os; box? + How can I connect a dumb terminal to my &os; + box? - You can find this information in the Terminals + You can find this information in the Terminals section of the &os; Handbook. @@ -7258,13 +7285,16 @@ hint.sio.7.irq="12" - On your system, the programs &man.tip.1; and &man.cu.1; - 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. + On your system, the programs &man.tip.1; and + &man.cu.1; 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. Alternatively, you can let everyone on your system run &man.tip.1; and &man.cu.1; by typing: @@ -7282,22 +7312,22 @@ hint.sio.7.irq="12" - &os; uses a lot of swap space even when the computer has - free memory left. Why? + &os; uses a lot of swap space even when the computer + has free memory left. Why? - &os; will proactively - move entirely idle, unused pages of main memory into swap in - order to make more main memory available for active use. - This heavy use of swap is balanced by using the extra free - memory for cacheing. + &os; will proactively move entirely idle, unused pages + of main memory into swap in order to make more main memory + available for active use. This heavy use of swap is + balanced by using the extra free memory for + cacheing. 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 idle - overnight. + 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 + idle overnight. @@ -7308,17 +7338,18 @@ hint.sio.7.irq="12" - The simple answer is that free memory is wasted memory. - Any memory that your 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 Buf are all - cached data at different aging levels. This cached data - means the system does not have to access a slow disk again - for data it has accessed recently, thus increasing overall - performance. In general, a low value shown for - Free memory in &man.top.1; is good, - provided it is not very low. + The simple answer is that free memory is wasted + memory. Any memory that your 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 + Buf are all cached data at different + aging levels. This cached data means the system does not + have to access a slow disk again for data it has accessed + recently, thus increasing overall performance. In + general, a low value shown for Free + memory in &man.top.1; is good, provided it is not + very low. @@ -7331,41 +7362,41 @@ 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 will always - succeed. + permissions on the source file, if possible. So if you + have a file, foo, and a symlink to + that file, bar, then this command + will always succeed. &prompt.user; chmod g-w bar However, the permissions on bar will not have changed. - When changing modes of the file hierarchies rooted in the - files instead of the files themselves, - you have to use either or - together with - to make this work. See &man.chmod.1; and - &man.symlink.7; for more information. + When changing modes of the file hierarchies rooted in + the files instead of the files themselves, you have to use + either or together + with to make this work. See + &man.chmod.1; and &man.symlink.7; for more + information. 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 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 change the - permissions of foo (actually - bar), you would do something - like: + recursive &man.chmod.1;. Be + careful about specifying directories or symlinks to + directories to &man.chmod.1;. If you want 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 + change the permissions of foo + (actually bar), you would do + something like: &prompt.user; chmod 555 foo/ - With the trailing slash, &man.chmod.1; will follow the - symlink, foo, to change the + With the trailing slash, &man.chmod.1; will follow + the symlink, foo, to change the permissions of the directory, bar. @@ -7378,19 +7409,20 @@ hint.sio.7.irq="12" - Yes, you can use emulators/doscmd, a DOS - emulation program, available in the &os; Ports + Yes, you can use emulators/doscmd, + a DOS emulation program, available in the &os; Ports Collection. If doscmd will not suffice, - the add-on utility emulators/pcemu emulates an 8088 - and enough BIOS services to run many DOS 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 application is - emulating old DOS games using the local file system for - files. + the add-on utility emulators/pcemu + emulates an 8088 and enough BIOS services to run many DOS + 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 + application is emulating old DOS games using the local + file system for files. @@ -7401,29 +7433,34 @@ hint.sio.7.irq="12" *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***