From owner-svn-doc-all@FreeBSD.ORG Mon May 12 15:15:45 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 16BD68A4; Mon, 12 May 2014 15:15:45 +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 0238B2004; Mon, 12 May 2014 15:15:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4CFFiuJ085144; Mon, 12 May 2014 15:15:44 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4CFFi6q085143; Mon, 12 May 2014 15:15:44 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405121515.s4CFFi6q085143@svn.freebsd.org> From: Dru Lavigne Date: Mon, 12 May 2014 15:15:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44816 - 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: Mon, 12 May 2014 15:15:45 -0000 Author: dru Date: Mon May 12 15:15:44 2014 New Revision: 44816 URL: http://svnweb.freebsd.org/changeset/doc/44816 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 Mon May 12 14:41:45 2014 (r44815) +++ head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 15:15:44 2014 (r44816) @@ -1090,7 +1090,8 @@ - Installation + + Installation NikClayton
nik@FreeBSD.org
@@ -1409,12 +1410,14 @@ Memory limits depend on the platform used. On a standard &i386; install, the limit is 4 GB but more - memory can be supported through &man.pae.4;. See instructions for using 4 GB or more memory on &i386;. + memory can be supported through &man.pae.4;. See instructions for using + 4 GB or more memory on &i386;. &os;/pc98 has a limit of 4 GB memory, and PAE can - not be used with it. Other architectures supported by &os; - have much higher theoretical limits on maximum memory (many - terabytes). + not be used with it. Other architectures supported by + &os; have much higher theoretical limits on maximum memory + (many terabytes). @@ -1424,44 +1427,47 @@ - For FFS file systems, the largest file system is practically - limited by the amount of memory required to &man.fsck.8; the file - system. &man.fsck.8; requires one bit per fragment, which with - the default fragment size of 4 KB equates to 32 MB - of memory per TB of disk. This does mean that on architectures - which limit userland processes to 2 GB (e.g., &i386;), - the maximum &man.fsck.8;'able filesystem is ~60 TB. - - If there was not a &man.fsck.8; memory limit the maximum - filesystem size would be 2 ^ 64 (blocks) * 32 KB - => 16 Exa * 32 KB => 512 ZettaBytes. + For FFS file systems, the largest file system is + practically limited by the amount of memory required to + &man.fsck.8; the file system. &man.fsck.8; requires one + bit per fragment, which with the default fragment size of + 4 KB equates to 32 MB of memory per TB of disk. + This does mean that on architectures which limit userland + processes to 2 GB (e.g., &i386;), the maximum + &man.fsck.8;'able filesystem is ~60 TB. + + If there was not a &man.fsck.8; memory limit the + maximum filesystem size would be 2 ^ 64 (blocks) + * 32 KB => 16 Exa * 32 KB => 512 + ZettaBytes. The maximum size of a single FFS file is approximately 2 PB with the default block size of 32 KB. Each 32 KB block can point to 4096 blocks. With triple indirect blocks, the calculation is 32 KB * 12 + 32 KB * 4096 + 32 KB * 4096^2 + 32 KB * - 4096^3. Increasing the block size to 64 KB will increase - the max file size by a factor of 16. + 4096^3. Increasing the block size to 64 KB will + increase the max file size by a factor of 16. - Why do I get an error message, - readin failed after compiling - and booting a new kernel? + Why do I get an error message, readin + failed after compiling and booting a new + kernel? - Because your world and kernel are out of sync. This is - not supported. Be sure you use make buildworld - and make buildkernel - to update your kernel. + Because your world and kernel are out of sync. This + is not supported. Be sure you use make + buildworld and make + buildkernel to update your kernel. You can boot by specifying the kernel directly at the - second stage, pressing any key when the | - shows up before loader is started. + second stage, pressing any key when the + | shows up before loader is + started. @@ -1491,8 +1497,8 @@ - I want to get a piece of hardware for my &os; system. - Which model/brand/type is best? + I want to get a piece of hardware for my &os; + system. Which model/brand/type is best? @@ -1500,36 +1506,41 @@ lists. Since hardware changes so quickly, however, we expect this. We still strongly recommend that you read through the Hardware Notes - for &os; &rel.current; or - &rel2.current; and - search the mailing list archives + for &os; &rel.current; + or &rel2.current; + and search the mailing list archives before asking about the latest and greatest hardware. Chances are a discussion about the type of hardware you are looking for took place just last week. - If you are looking for a laptop, check the &a.mobile; - archives. Otherwise, you probably want the archives for - the &a.questions;, or possibly a specific mailing list for - a particular hardware type. + If you are looking for a laptop, check the + &a.mobile; archives. Otherwise, you probably want the + archives for the &a.questions;, or possibly a specific + mailing list for a particular hardware type. - Does &os; support more than 4 GB of memory (RAM)? - More than 16 GB? More than 48 GB? + Does &os; support more than 4 GB of memory + (RAM)? More than 16 GB? More than + 48 GB? Yes. &os; as an operating system generally supports - as much physical memory (RAM) as the platform it is running - on does. Keep in mind that different platforms have - different limits for memory; for example &i386; without - PAE supports at most 4 GB of - memory (and usually less than that because of PCI address - space) and &i386; with PAE supports at most 64 GB - memory. AMD64 platforms currently deployed support up to - 1 TB of physical memory. + as much physical memory (RAM) as the platform it is + running on does. Keep in mind that different platforms + have different limits for memory; for example &i386; + without PAE supports at most + 4 GB of memory (and usually less than that because + of PCI address space) and &i386; with PAE supports at + most 64 GB memory. AMD64 platforms currently + deployed support up to 1 TB of physical + memory. @@ -1540,53 +1551,55 @@ - The total address space on &i386; machines is 32-bit, - meaning that at most 4 GB of memory is addressable (can - be accessed). Furthermore, some addresses in this range - are reserved by hardware for different purposes, for - example for using and controlling PCI devices, for - accessing video memory, and so on. Therefore, the total - amount of memory usable by the operating system for its - kernel and applications is limited to significantly less - than 4 GB. Usually, 3.2 GB to 3.7 GB is - the maximum usable physical memory in this - configuration. + The total address space on &i386; machines is + 32-bit, meaning that at most 4 GB of memory is + addressable (can be accessed). Furthermore, some + addresses in this range are reserved by hardware for + different purposes, for example for using and + controlling PCI devices, for accessing video memory, and + so on. Therefore, the total amount of memory usable by + the operating system for its kernel and applications is + limited to significantly less than 4 GB. Usually, + 3.2 GB to 3.7 GB is the maximum usable + physical memory in this configuration. To access more than 3.2 GB to 3.7 GB of - installed memory (meaning up to 4 GB but also more than - 4 GB), a special tweak called PAE - must be used. PAE stands for Physical Address Extension - and is a way for 32-bit x86 CPUs to address more than - 4 GB of memory. It remaps the memory that would - otherwise be overlaid by address reservations for - hardware devices above the 4 GB range and uses it as - additional physical memory (see &man.pae.4;). Using PAE - has some drawbacks; this mode of memory access is a little - bit slower than the normal (without PAE) mode and loadable - modules (see &man.kld.4;) are not supported. This means - all drivers must be compiled into the kernel. + installed memory (meaning up to 4 GB but also more + than 4 GB), a special tweak called + PAE must be used. PAE stands for + Physical Address Extension and is a way for 32-bit x86 + CPUs to address more than 4 GB of memory. It + remaps the memory that would otherwise be overlaid by + address reservations for hardware devices above the + 4 GB range and uses it as additional physical + memory (see &man.pae.4;). Using PAE has some drawbacks; + this mode of memory access is a little bit slower than + the normal (without PAE) mode and loadable modules (see + &man.kld.4;) are not supported. This means all drivers + must be compiled into the kernel. The most common way to enable PAE is to build a new - kernel with the special ready-provided kernel configuration - file called PAE, which is already - configured to build a safe kernel. Note that some entries - in this kernel configuration file are too conservative and - some drivers marked as unready to be used with PAE are - actually usable. A rule of thumb is that if the driver is - usable on 64-bit architectures (like AMD64), it is also - usable with PAE. If you wish to create your own kernel - configuration file, you can enable PAE by adding the - following line to your configuration: + kernel with the special ready-provided kernel + configuration file called PAE, + which is already configured to build a safe kernel. + Note that some entries in this kernel configuration file + are too conservative and some drivers marked as unready + to be used with PAE are actually usable. A rule of + thumb is that if the driver is usable on 64-bit + architectures (like AMD64), it is also usable with PAE. + If you wish to create your own kernel configuration + file, you can enable PAE by adding the following line to + your configuration: options PAE PAE is not much used nowadays because most new x86 hardware also supports running in 64-bit mode, known as AMD64 or &intel; 64. It has a much larger address - space and does not need such tweaks. &os; supports AMD64 - and it is recommended that this version of &os; be used - instead of the &i386; version if 4 GB or more memory - is required. + space and does not need such tweaks. &os; supports + AMD64 and it is recommended that this version of &os; be + used instead of the &i386; version if 4 GB or more + memory is required. @@ -1604,15 +1617,17 @@ Yes. &os; divides support into multiple tiers. - Tier 1 architectures, such as i386 or amd64; are - fully supported. Tiers 2 and 3 are supported on an + Tier 1 architectures, such as i386 or amd64; are fully + supported. Tiers 2 and 3 are supported on an if-possible basis. A full explanation of the tier - system is available in the - Committer's Guide. + system is available in the Committer's + Guide. A complete list of supported architectures can be - found on the - platforms page. + found on the platforms + page. @@ -1625,11 +1640,11 @@ &os; supports symmetric multi-processor (SMP) on all non-embedded platforms (e.g, &arch.i386;, &arch.amd64;, - etc.). SMP is also - supported in arm and MIPS kernels, although some CPUs - may not support this. &os;'s SMP implementation uses - fine-grained locking, and performance scales nearly - linearly with number of CPUs. + etc.). SMP is also supported in arm and MIPS kernels, + although some CPUs may not support this. &os;'s SMP + implementation uses fine-grained locking, and + performance scales nearly linearly with number of + CPUs. &man.smp.4; has more details. @@ -1644,10 +1659,12 @@ Microcode is a method of programmatically implementing hardware level instructions. This allows - for CPU bugs to be fixed without replacing the on board chip. + for CPU bugs to be fixed without replacing the on board + chip. Install sysutils/devcpu-data, then add: + microcode_update_enable="YES" to /etc/rc.conf @@ -1666,12 +1683,13 @@ - &os; supports EIDE, SATA, SCSI, and SAS drives (with a - compatible controller; see the next section), and all + &os; supports EIDE, SATA, SCSI, and SAS drives (with + a compatible controller; see the next section), and all drives using the original Western Digital - interface (MFM, RLL, ESDI, and of course IDE). A few ESDI - controllers that use proprietary interfaces may not work: - stick to WD1002/3/6/7 interfaces and clones. + interface (MFM, RLL, ESDI, and of course IDE). A few + ESDI controllers that use proprietary interfaces may not + work: stick to WD1002/3/6/7 interfaces and + clones. @@ -1682,8 +1700,10 @@ See the complete list in the Hardware Notes for &os; - &rel.current; - or &rel2.current;. + &rel.current; + or &rel2.current;. @@ -1693,7 +1713,8 @@ - &os; supports all standard SCSI tape interfaces. + &os; supports all standard SCSI tape + interfaces. @@ -1703,17 +1724,18 @@ - &os; supports SCSI changers using the &man.ch.4; device - and the &man.chio.1; command. The details of how you - actually control the changer can be found in the + &os; supports SCSI changers using the &man.ch.4; + device and the &man.chio.1; command. The details of how + you actually control the changer can be found in the &man.chio.1; manual page. - If you are not using AMANDA - or some other product that already understands changers, - remember that they only know how to move a tape from one - point to another, so you need to keep track of which slot a - tape is in, and which slot the tape currently in the drive - needs to go back to. + If you are not using + AMANDA or some other product + that already understands changers, remember that they + only know how to move a tape from one point to another, + so you need to keep track of which slot a tape is in, + and which slot the tape currently in the drive needs to + go back to. @@ -1723,8 +1745,8 @@ - Any SCSI drive connected to a supported controller is - supported. Most ATAPI compatible IDE CD-ROMs are + Any SCSI drive connected to a supported controller + is supported. Most ATAPI compatible IDE CD-ROMs are supported. @@ -1739,10 +1761,10 @@ drive. See &man.burncd.8; for details. &os; also supports any SCSI CD-R or CD-RW drives. - Install and use cdrecord - from the ports or packages system, and make sure that you - have the pass device compiled in - your kernel. + Install and use cdrecord from the + ports or packages system, and make sure that you have + the pass device compiled in your + kernel. @@ -1754,8 +1776,8 @@ - Is it possible to use a mouse in any way outside the X - Window system? + Is it possible to use a mouse in any way outside the + X Window system? @@ -1774,8 +1796,8 @@ automatically determine the protocol type of most mice, except old serial mice. Specify the auto protocol to invoke automatic - detection. If automatic detection does not work, see the - &man.moused.8; manual page for a list of supported + detection. If automatic detection does not work, see + the &man.moused.8; manual page for a list of supported protocol types. If you have a PS/2 mouse, just add @@ -1783,14 +1805,15 @@ /etc/rc.conf to start the mouse daemon at boot-time. Additionally, if you would like to use the mouse daemon on all virtual terminals instead of - just the console, add - allscreens_flags="-m on" to + just the console, add allscreens_flags="-m + on" to /etc/rc.conf. - When the mouse daemon is running, access to the mouse - must be coordinated between the mouse daemon and other - programs such as X Windows. Refer to the FAQ Why does my mouse not work with X? - for more details on this issue. + When the mouse daemon is running, access to the + mouse must be coordinated between the mouse daemon and + other programs such as X Windows. Refer to the FAQ + Why does my mouse not work + with X? for more details on this issue. @@ -1804,14 +1827,13 @@ It is not possible to remove data using the mouse. However, it is possible to copy and paste. - Once you get the mouse daemon running (see the - previous question) - hold down - button 1 (left button) and move the mouse to select a region - of text. Then, press button 2 (middle button) to paste - it at the text cursor. Pressing button 3 (right button) - will extend the selected region of - text. + Once you get the mouse daemon running (see the previous question) hold down + button 1 (left button) and move the mouse to select a + region of text. Then, press button 2 (middle button) to + paste it at the text cursor. Pressing button 3 (right + button) will extend the selected region + of text. If your mouse does not have a middle button, you may wish to emulate one or remap buttons using mouse daemon @@ -1835,7 +1857,8 @@ two, or three button mouse. For the possible usage of wheels in the X Window - environment, refer to that section. + environment, refer to that section. @@ -1847,20 +1870,22 @@ For the Bourne Shell, add - the following lines to your .shrc. See - &man.sh.1; and &man.editrc.5;. + the following lines to your .shrc. + See &man.sh.1; and &man.editrc.5;. bind ^? ed-delete-next-char # for console bind ^[[3~ ed-delete-next-char # for xterm For the C Shell, add the - following lines to your .cshrc. See - &man.csh.1;. + following lines to your .cshrc. + See &man.csh.1;. bindkey ^? delete-char # for console bindkey ^[[3~ delete-char # for xterm - For more information, see this page. + For more information, see this + page. @@ -1877,9 +1902,9 @@ bindkey ^[[3~ delete-char # for xterm

- Some sound cards set their output volume to 0 at every - boot. Run the following command every time the machine - boots: + Some sound cards set their output volume to 0 at + every boot. Run the following command every time the + machine boots: &prompt.root; mixer pcm 100 vol 100 cd 100 @@ -1892,9 +1917,9 @@ bindkey ^[[3~ delete-char # for xterm

- &os; supports the ACPI - features found in modern hardware. Further - information can be found in &man.acpi.4;. + &os; supports the ACPI features + found in modern hardware. Further information can be + found in &man.acpi.4;. @@ -1907,44 +1932,47 @@ bindkey ^[[3~ delete-char # for xterm

- Why is &os; finding the wrong amount of memory on &i386; - hardware? + Why is &os; finding the wrong amount of memory on + &i386; hardware? The most likely reason is the difference between physical memory addresses and virtual addresses. - The convention for most PC hardware is to use the memory - area between 3.5 GB and 4 GB for a special purpose - (usually for PCI). This address space is used to access PCI - hardware. As a result real, physical memory can not be - accessed by that address space. + The convention for most PC hardware is to use the + memory area between 3.5 GB and 4 GB for a + special purpose (usually for PCI). This address space is + used to access PCI hardware. As a result real, physical + memory can not be accessed by that address space. What happens to the memory that should appear in that - location is dependent on your hardware. Unfortunately, some - hardware does nothing and the ability to use that last - 500 MB of RAM is entirely lost. + location is dependent on your hardware. Unfortunately, + some hardware does nothing and the ability to use that + last 500 MB of RAM is entirely lost. Luckily, most hardware remaps the memory to a higher location so that it can still be used. However, this can - cause some confusion if you watch the boot messages. + cause some confusion if you watch the boot + messages. - On a 32-bit version of &os;, the memory appears - lost, since it will be remapped above 4 GB, which a - 32-bit kernel is unable to access. In this case, the - solution is to build a PAE enabled kernel. See the entry on memory limits - and about different - memory limits on different platforms for more + On a 32-bit version of &os;, the memory appears lost, + since it will be remapped above 4 GB, which a 32-bit + kernel is unable to access. In this case, the solution is + to build a PAE enabled kernel. See the entry on memory + limits and about different memory + limits on different platforms for more information. On a 64-bit version of &os;, or when running a - PAE-enabled kernel, &os; will correctly detect and remap the - memory so it is usable. During boot, however, it may seem - as if &os; is detecting more memory than the system really - has, due to the described remapping. This is normal and the - available memory will be corrected as the boot process - completes. + PAE-enabled kernel, &os; will correctly detect and remap + the memory so it is usable. During boot, however, it may + seem as if &os; is detecting more memory than the system + really has, due to the described remapping. This is + normal and the available memory will be corrected as the + boot process completes. @@ -1956,10 +1984,10 @@ bindkey ^[[3~ delete-char # for xterm

Signal 11 errors are caused when your process has - attempted to access memory which the operating system has not - granted it access to. If something like this is happening - at seemingly random intervals then you need to start - investigating things very carefully. + attempted to access memory which the operating system has + not granted it access to. If something like this is + happening at seemingly random intervals then you need to + start investigating things very carefully. These problems can usually be attributed to either: @@ -1973,34 +2001,34 @@ bindkey ^[[3~ delete-char # for xterm

If it is a problem with part of the base &os; - system, it may also be buggy code, but more often than not - these problems are found and fixed long before us - general FAQ readers get to use these bits of code (that - is what -CURRENT is for). + system, it may also be buggy code, but more often than + not these problems are found and fixed long before us + general FAQ readers get to use these bits of code + (that is what -CURRENT is for). In particular, a dead giveaway that this is not a &os; bug is if you see the problem when you are compiling a program, but the activity - that the compiler is carrying out changes each time. + that the compiler is carrying out changes each + time. - For example, suppose you are running - make buildworld, - and the compile fails while trying to compile - ls.c into ls.o. - If you then run - make buildworld - again, and the compile fails in the same place then this is - a broken build — try updating your sources and try - again. If the compile fails elsewhere then this is almost - certainly hardware. + For example, suppose you are running make + buildworld, and the compile fails while trying + to compile ls.c into + ls.o. If you then run make + buildworld again, and the compile fails in the + same place then this is a broken build — try + updating your sources and try again. If the compile fails + elsewhere then this is almost certainly hardware. What you should do: In the first case you can use a debugger e.g., &man.gdb.1; to find the point in the program which is - attempting to access a bogus address and then fix it. + attempting to access a bogus address and then fix + it. In the second case you need to verify that it is not your hardware at fault. @@ -2009,76 +2037,81 @@ bindkey ^[[3~ delete-char # for xterm

- Your hard disks might be overheating: Check the fans - in your case are still working, as your disk (and perhaps - other hardware might be overheating). + Your hard disks might be overheating: Check the + fans in your case are still working, as your disk (and + perhaps other hardware might be overheating). - The processor running is overheating: This might be - because the processor has been overclocked, or the fan - on the processor might have died. In either case you - need to ensure that you have hardware running at what it - is specified to run at, at least while trying to solve - this problem (in other words, clock it back to the default - settings.) + The processor running is overheating: This might + be because the processor has been overclocked, or the + fan on the processor might have died. In either case + you need to ensure that you have hardware running at + what it is specified to run at, at least while trying + to solve this problem (in other words, clock it back + to the default settings.) If you are overclocking then note that it is far cheaper to have a slow system than a fried system that - needs replacing! Also the wider community is not often - sympathetic to problems on overclocked systems, whether - you believe it is safe or not. + needs replacing! Also the wider community is not + often sympathetic to problems on overclocked systems, + whether you believe it is safe or not. Dodgy memory: If you have multiple memory SIMMS/DIMMS installed then pull them all out and try - running the machine with each SIMM or DIMM individually - and narrow the problem down to either the problematic - DIMM/SIMM or perhaps even a combination. + running the machine with each SIMM or DIMM + individually and narrow the problem down to either the + problematic DIMM/SIMM or perhaps even a + combination. Over-optimistic Motherboard settings: In your BIOS - settings, and some motherboard jumpers you have options - to set various timings, mostly the defaults will be - sufficient, but sometimes, setting the wait states on - RAM too low, or setting the RAM Speed: - Turbo option, or similar in the BIOS will cause - strange behavior. A possible idea is to set to BIOS - defaults, but it might be worth noting down your - settings first! + settings, and some motherboard jumpers you have + options to set various timings, mostly the defaults + will be sufficient, but sometimes, setting the wait + states on RAM too low, or setting the RAM + Speed: Turbo option, or similar in the BIOS + will cause strange behavior. A possible idea is to + set to BIOS defaults, but it might be worth noting + down your settings first! Unclean or insufficient power to the motherboard. - If you have any unused I/O boards, hard disks, or CD-ROMs - in your system, try temporarily removing them or - disconnecting the power cable from them, to see if your - power supply can manage a smaller load. Or try another - power supply, preferably one with a little more power - (for instance, if your current power supply is rated at - 250 Watts try one rated at 300 Watts). + If you have any unused I/O boards, hard disks, or + CD-ROMs in your system, try temporarily removing them + or disconnecting the power cable from them, to see if + your power supply can manage a smaller load. Or try + another power supply, preferably one with a little + more power (for instance, if your current power supply + is rated at 250 Watts try one rated at + 300 Watts). - You should also read the SIG11 FAQ (listed below) which - has excellent explanations of all these problems, albeit from - a &linux; viewpoint. It also discusses how memory testing - software or hardware can still pass faulty memory. - - Finally, if none of this has helped it is possible that - you have just found a bug in &os;, and you should follow the - instructions to send a problem report. - - There is an extensive FAQ on this at the SIG11 problem FAQ. + You should also read the SIG11 FAQ (listed below) + which has excellent explanations of all these problems, + albeit from a &linux; viewpoint. It also discusses how + memory testing software or hardware can still pass faulty + memory. + + Finally, if none of this has helped it is possible + that you have just found a bug in &os;, and you should + follow the instructions to send a problem report. + + There is an extensive FAQ on this at the SIG11 + problem FAQ. - My system crashes with either Fatal trap 12: - page fault in kernel mode, or + My system crashes with either Fatal trap + 12: page fault in kernel mode, or panic:, and spits out a bunch of information. What should I do? @@ -2087,10 +2120,12 @@ bindkey ^[[3~ delete-char # for xterm

The &os; developers are very interested in these errors, but need some more information than just the error you see. Copy your full crash message. Then consult the - FAQ section on kernel panics, - build a debugging kernel, and get a backtrace. This might - sound difficult, but you do not need any programming skills; - you just have to follow the instructions. + FAQ section on kernel + panics, build a debugging kernel, and get a + backtrace. This might sound difficult, but you do not + need any programming skills; you just have to follow the + instructions. @@ -2103,19 +2138,21 @@ bindkey ^[[3~ delete-char # for xterm

The &os; kernel will only allow a certain number of - processes to exist at one time. The number is based on the - kern.maxusers &man.sysctl.8; variable. - kern.maxusers also affects various other - in-kernel limits, such as network buffers. - If your machine is heavily loaded, you probably - want to increase kern.maxusers. This - will increase these other system limits in addition to the + processes to exist at one time. The number is based on + the kern.maxusers &man.sysctl.8; + variable. kern.maxusers also affects + various other in-kernel limits, such as network buffers. + If your machine is heavily loaded, you probably want to + increase kern.maxusers. This will + increase these other system limits in addition to the maximum number of processes. To adjust your kern.maxusers value, - see the File/Process Limits - section of the Handbook. (While that section refers to open - files, the same limits apply to processes.) + see the File/Process + Limits section of the Handbook. (While that + section refers to open files, the same limits apply to + processes.) If your machine is lightly loaded, and you are simply running a very large number of processes, you can adjust @@ -2124,25 +2161,25 @@ bindkey ^[[3~ delete-char # for xterm

/boot/loader.conf. The tunable will not get adjusted until the system is rebooted. For more information about tuning tunables, see - &man.loader.conf.5;. - If these processes are being run by a single user, you will - also need to adjust kern.maxprocperuid to - be one less than your new kern.maxproc - value. (It must be at least one less because one system - program, &man.init.8;, must always be running.) + &man.loader.conf.5;. If these processes are being run by + a single user, you will also need to adjust + kern.maxprocperuid to be one less than + your new kern.maxproc value. (It must + be at least one less because one system program, + &man.init.8;, must always be running.) - Why does sendmail give me an - error reading mail loops back to + Why does sendmail give me + an error reading mail loops back to myself? This is answered in the Sendmail + xlink:href="http://www.sendmail.org/faq/">Sendmail FAQ as follows. This FAQ is recommended reading when tweaking the mail setup. @@ -2170,9 +2207,9 @@ to /etc/mail/sendmail.cf. - The remote machine may be setting your terminal type to - something other than the cons25 terminal - type required by the &os; console. + The remote machine may be setting your terminal type + to something other than the cons25 + terminal type required by the &os; console. There are a number of possible work-arounds for this problem: @@ -2207,11 +2244,12 @@ to /etc/mail/sendmail.cf. - Fire up an X server at the &os; end and login to the - remote machine using an X based terminal emulator such - as xterm or rxvt. - The TERM variable at the remote host - should be set to xterm or + Fire up an X server at the &os; end and login to + the remote machine using an X based terminal emulator + such as xterm or + rxvt. The TERM + variable at the remote host should be set to + xterm or vt100. @@ -2221,46 +2259,48 @@ to /etc/mail/sendmail.cf. Why does it take so long to connect to my computer via - ssh or telnet? + ssh or + telnet? - The symptom: there is a long delay between the time the - TCP connection is established and the time when the client - software asks for a password (or, in &man.telnet.1;'s case, - when a login prompt appears). + The symptom: there is a long delay between the time + the TCP connection is established and the time when the + client software asks for a password (or, in + &man.telnet.1;'s case, when a login prompt + appears). The problem: more likely than not, the delay is caused by the server software trying to resolve the client's IP address into a hostname. Many servers, including the Telnet and - SSH servers that come with &os;, - do this to store the hostname - in a log file for future reference by the - administrator. + SSH servers that come with + &os;, do this to store the hostname in a log file for + future reference by the administrator. The remedy: if the problem occurs whenever you connect - from your computer (the client) to any server, the problem is - with the client; likewise, if the problem only occurs when - someone connects to your computer (the server) the problem - is with the server. - - If the problem is with the client, the only remedy is to - fix the DNS so the server can resolve it. If this is on a - local network, consider it a server problem and keep - reading; conversely, if this is on the global Internet, you - will most likely need to contact your ISP and ask them to - fix it for you. + from your computer (the client) to any server, the problem + is with the client; likewise, if the problem only occurs + when someone connects to your computer (the server) the + problem is with the server. + + If the problem is with the client, the only remedy is + to fix the DNS so the server can resolve it. If this is + on a local network, consider it a server problem and keep + reading; conversely, if this is on the global Internet, + you will most likely need to contact your ISP and ask them + to fix it for you. If the problem is with the server, and this is on a - local network, you need to configure the server to be able to - resolve address-to-hostname queries for your local address - range. See the &man.hosts.5; and &man.named.8; manual pages - for more information. If this is on the global Internet, - the problem may be that your server's resolver is not - functioning correctly. To check, try to look up another - host — say, www.yahoo.com. If it - does not work, that is your problem. + local network, you need to configure the server to be able + to resolve address-to-hostname queries for your local + address range. See the &man.hosts.5; and &man.named.8; + manual pages for more information. If this is on the + global Internet, the problem may be that your server's + resolver is not functioning correctly. To check, try to + look up another host — say, + www.yahoo.com. If it does not + work, that is your problem. Following a fresh install of &os;, it is also possible that domain and name server information is missing from @@ -2268,10 +2308,10 @@ to /etc/mail/sendmail.cf.