diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index d7df846293..ad3cf7a3dd 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -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. + 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. + 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. + 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. + 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. + 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. + 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 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. cause a delay in SSH, as the option UseDNS is set to yes by default in - /etc/ssh/sshd_config. - If this is causing the - problem, you will either need to fill in the missing - information in /etc/resolv.conf or set + /etc/ssh/sshd_config. If this is + causing the problem, you will either need to fill in the + missing information in + /etc/resolv.conf or set UseDNS to no in sshd_config as a temporary workaround. @@ -2280,23 +2320,26 @@ to /etc/mail/sendmail.cf. - Why does file: table is full show - up repeatedly in &man.dmesg.8;? + Why does file: table is full + show up repeatedly in &man.dmesg.8;? This error message indicates you have exhausted the - number of available file descriptors on your system. Please - see the kern.maxfiles - section of the Tuning Kernel Limits - section of the Handbook for a discussion and - solution. + number of available file descriptors on your system. + Please see the kern.maxfiles + section of the Tuning + Kernel Limits section of the Handbook for a + discussion and solution. - Why does the clock on my computer keep incorrect time? + Why does the clock on my computer keep incorrect + time? @@ -2320,20 +2363,21 @@ Timecounters tick every 1.000 msec &prompt.root; sysctl kern.timecounter.hardware kern.timecounter.hardware: ACPI-fast - It may be a broken ACPI timer. The simplest solution is - to disable the ACPI timer in + It may be a broken ACPI timer. The simplest solution + is to disable the ACPI timer in /boot/loader.conf: debug.acpi.disabled="timer" Or the BIOS may modify the TSC clock—perhaps to - change the speed of the processor when running from batteries, - or going into a power saving mode, but &os; is unaware of - these adjustments, and appears to gain or lose time. + change the speed of the processor when running from + batteries, or going into a power saving mode, but &os; is + unaware of these adjustments, and appears to gain or lose + time. In this example, the i8254 clock is - also available, and can be selected by writing its name to the - kern.timecounter.hardware + also available, and can be selected by writing its name to + the kern.timecounter.hardware &man.sysctl.3;. &prompt.root; sysctl kern.timecounter.hardware=i8254 @@ -2342,8 +2386,8 @@ kern.timecounter.hardware: TSC -> i8254 Your computer should now start keeping more accurate time. - To have this change automatically run at boot time, add - the following line to + To have this change automatically run at boot time, + add the following line to /etc/sysctl.conf: kern.timecounter.hardware=i8254 @@ -2360,12 +2404,12 @@ kern.timecounter.hardware: TSC -> i8254 This means that a process is trying to page memory to disk, and the page attempt has hung trying to access the disk for more than 20 seconds. It might be caused by bad - blocks on the disk drive, disk wiring, cables, or any other - disk I/O-related hardware. If the drive itself is actually - bad, you will also see disk errors in - /var/log/messages and in the output of - dmesg. Otherwise, check your cables and - connections. + blocks on the disk drive, disk wiring, cables, or any + other disk I/O-related hardware. If the drive itself is + actually bad, you will also see disk errors in + /var/log/messages and in the output + of dmesg. Otherwise, check your cables + and connections. @@ -2379,34 +2423,35 @@ kern.timecounter.hardware: TSC -> i8254 The &os; kernel uses a number of resource locks to arbitrate contention for certain resources. When multiple kernel threads try to obtain multiple resource locks, - there's always the potential for a deadlock, - where two threads have each obtained one of the locks and - blocks forever waiting for the other thread to release one - of the other locks. This sort of locking problem can be - avoided if all threads obtain the locks in the same - order. + there's always the potential for a deadlock, where two + threads have each obtained one of the locks and blocks + forever waiting for the other thread to release one of the + other locks. This sort of locking problem can be avoided + if all threads obtain the locks in the same order. - A run-time lock diagnostic system called &man.witness.4;, - enabled in &os.current; and disabled by default for stable - branches and releases, detects the potential for deadlocks due to - locking errors, including errors caused by obtaining multiple - resource locks with a different order from different parts of the - kernel. The &man.witness.4; framework tries to detect this - problem as it happens, and reports it by printing a message to the - system console about a lock order reversal - (often referred to also as LOR). + A run-time lock diagnostic system called + &man.witness.4;, enabled in &os.current; and disabled by + default for stable branches and releases, detects the + potential for deadlocks due to locking errors, including + errors caused by obtaining multiple resource locks with a + different order from different parts of the kernel. The + &man.witness.4; framework tries to detect this problem as + it happens, and reports it by printing a message to the + system console about a lock order + reversal (often referred to also as + LOR). - It is possible to get false positives, as &man.witness.4; - is conservative. A true positive report does - not mean that a system is dead-locked; instead - it should be understood as a warning of the form if - you were unlucky, a deadlock would have happened - here. + It is possible to get false positives, as + &man.witness.4; is conservative. A true positive report + does not mean that a system is + dead-locked; instead it should be understood as a warning + of the form if you were unlucky, a deadlock would + have happened here. - Problematic LORs tend to get fixed - quickly, so check &a.current.url; before posting to the - mailing lists. + Problematic LORs tend to get + fixed quickly, so check &a.current.url; before posting + to the mailing lists. @@ -2439,8 +2484,8 @@ kern.timecounter.hardware: TSC -> i8254 In summary, such warnings are non-fatal, however with unfortunate timing they could cause undesirable effects - ranging from a minor blip in the system's responsiveness to - a complete system lockup. + ranging from a minor blip in the system's responsiveness + to a complete system lockup. For additional information about locking in &os; see &man.locking.9;. @@ -2456,12 +2501,13 @@ kern.timecounter.hardware: TSC -> i8254 - This error does not mean that the &man.touch.1; utility - is missing. The error is instead probably due to the dates - of the files being set sometime in the future. If your - CMOS-clock is set to local time you need to run the command - adjkerntz -i to adjust the kernel - clock when booting into single user mode. + This error does not mean that the &man.touch.1; + utility is missing. The error is instead probably due to + the dates of the files being set sometime in the future. + If your CMOS-clock is set to local time you need to run + the command adjkerntz -i to adjust + the kernel clock when booting into single user + mode. @@ -2477,34 +2523,35 @@ kern.timecounter.hardware: TSC -> i8254 - Please take a look at the ports page - for info on software packages ported to &os;. The list - currently tops &os.numports; and is growing daily, so come - back to check often or subscribe to the &a.announce; for - periodic updates on new entries. + Please take a look at the ports + page for info on software packages ported to + &os;. The list currently tops &os.numports; and is + growing daily, so come back to check often or subscribe to + the &a.announce; for periodic updates on new + entries. - Most ports should work on the - &rel3.relx;, &rel2.relx;, and &rel.relx; branches. - Each time a &os; - release is made, a snapshot of the ports tree at the time of - release in also included in the ports/ - directory. + Most ports should work on the &rel3.relx;, + &rel2.relx;, and &rel.relx; branches. Each time a &os; + release is made, a snapshot of the ports tree at the time + of release in also included in the + ports/ directory. - We also support the concept of a package, - essentially no more than a compressed binary distribution - with a little extra intelligence embedded in it for doing - whatever custom installation work is required. A package - can be installed and uninstalled again easily without having - to know the gory details of which files it includes. + We also support the concept of a + package, essentially no more than a + compressed binary distribution with a little extra + intelligence embedded in it for doing whatever custom + installation work is required. A package can be installed + and uninstalled again easily without having to know the + gory details of which files it includes. - Use - &man.pkg.7; on the specific package files - you are interested in installing. Package files can usually - be identified by their .txz suffix and + Use &man.pkg.7; on the specific package files you are + interested in installing. Package files can usually be + identified by their .txz suffix and CD-ROM distribution people will have a packages/All directory on their CD - which contains such files. They can also be downloaded over - the net for various versions of &os;. + which contains such files. They can also be downloaded + over the net for various versions of &os;. @@ -2522,18 +2569,17 @@ kern.timecounter.hardware: TSC -> i8254 Use portsnap for most use cases. - Use SVN directly if you need custom patches - to the ports tree. + Use SVN directly if you need custom patches to the + ports tree. - Use CTM if you prefer getting patches - by email (this is a rarer use case). + Use CTM if you prefer getting patches by email + (this is a rarer use case). - Any other method should be considered a - legacy method. If you do not already use them, - do not start. + Any other method should be considered a legacy method. + If you do not already use them, do not start. @@ -2543,7 +2589,8 @@ kern.timecounter.hardware: TSC -> i8254 - Yes. Please see http://www.FreeBSD.org/java/. + Yes. Please see http://www.FreeBSD.org/java/. @@ -2558,15 +2605,16 @@ kern.timecounter.hardware: TSC -> i8254 If you are running a &os; version that lags significantly behind -CURRENT or -STABLE, you may need to update your - Ports Collection; see the Keeping Up - section of the Porter's Handbook for further information on - how to do this. If you are up to date, then someone might - have committed a change to the port which works for - -CURRENT but which broke the port for - -STABLE. Please submit a bug report on - this with the &man.send-pr.1; command, since the Ports - Collection is supposed to work for both the - -CURRENT and + Ports Collection; see the Keeping + Up section of the Porter's Handbook for further + information on how to do this. If you are up to date, + then someone might have committed a change to the port + which works for -CURRENT but which + broke the port for -STABLE. Please + submit a bug report on this with the &man.send-pr.1; + command, since the Ports Collection is supposed to work + for both the -CURRENT and -STABLE branches. @@ -2574,8 +2622,7 @@ kern.timecounter.hardware: TSC -> i8254 I just tried to build INDEX using - make index, and - it failed. Why? + make index, and it failed. Why? @@ -2591,38 +2638,39 @@ kern.timecounter.hardware: TSC -> i8254 WITHOUT_* variables being set in make.conf. If you suspect that this is the case, please try to make - INDEX with those make variables turned - off before reporting it to &a.ports;. + INDEX with those make variables + turned off before reporting it to &a.ports;. - I updated the sources, now how do I update my installed - ports? + I updated the sources, now how do I update my + installed ports? - &os; does not include a port upgrading tool, but it does - have some tools to make the upgrade process somewhat easier. - You can also install additional tools to simplify port - handling, see the Upgrading Ports - section in the &os; Handbook. + &os; does not include a port upgrading tool, but it + does have some tools to make the upgrade process somewhat + easier. You can also install additional tools to simplify + port handling, see the Upgrading + Ports section in the &os; Handbook. - Do I need to recompile every port each time I perform a - major version update? + Do I need to recompile every port each time I perform + a major version update? By all means! While a recent system will run with - software compiled under an older release, you will end up with - things randomly crashing and failing to work once you start - installing other ports or updating a portion of what you - already have. + software compiled under an older release, you will end up + with things randomly crashing and failing to work once you + start installing other ports or updating a portion of what + you already have. When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be @@ -2630,21 +2678,22 @@ kern.timecounter.hardware: TSC -> i8254 the older versions may fail to start or, in other cases, fail to function properly. - For more information, see the section on upgrades - in the &os; Handbook. + For more information, see the + section on upgrades in the &os; Handbook. - Do I need to recompile every port each time I perform a - minor version update? + Do I need to recompile every port each time I perform + a minor version update? In general, no. &os; developers do their utmost to - guarantee binary compatibility across all releases with the - same major version number. Any exceptions will be + guarantee binary compatibility across all releases with + the same major version number. Any exceptions will be documented in the Release Notes, and advice given there should be followed. @@ -2673,17 +2722,15 @@ kern.timecounter.hardware: TSC -> i8254 The existing implementation is our best effort at meeting as many of these requirements simultaneously as we - can. To keep /bin/sh small, - we have not provided many of the convenience features that - other shells have. That is why other more - featureful shells like - bash, scsh, + can. To keep /bin/sh small, we have + not provided many of the convenience features that other + shells have. That is why other more featureful shells + like bash, scsh, &man.tcsh.1;, and zsh are available. - (You can - compare for yourself the memory utilization of all these - shells by looking at the VSZ and - RSS columns in a ps - -u listing.) + (You can compare for yourself the memory utilization of + all these shells by looking at the VSZ and + RSS columns in a ps -u + listing.) @@ -2694,17 +2741,20 @@ kern.timecounter.hardware: TSC -> i8254 To create audio CDs from MIDI files, first install - audio/timidity++ from - ports then install manually the GUS patches set by Eric A. - Welsh, available at http://alleg.sourceforge.net/digmid.html. - After TiMidity++ has been installed - properly, MIDI files may be converted to WAV files with the - following command line: + audio/timidity++ from ports then + install manually the GUS patches set by Eric A. Welsh, + available at http://alleg.sourceforge.net/digmid.html. + After TiMidity++ has been + installed properly, MIDI files may be converted to WAV + files with the following command line: &prompt.user; timidity -Ow -s 44100 -o /tmp/juke/01.wav 01.mid - The WAV files can then be converted to other formats or - burned onto audio CDs, as described in the &os; Handbook. + The WAV files can then be converted to other formats + or burned onto audio CDs, as described in the &os; + Handbook. @@ -2714,9 +2764,10 @@ kern.timecounter.hardware: TSC -> i8254 - The open-source Apache OpenOffice - and LibreOffice - office suites work natively on &os;. + The open-source Apache + OpenOffice and + LibreOffice office suites work + natively on &os;. &os; also includes a variety of text editors, spreadsheets, and drawing programs in the Ports @@ -2738,8 +2789,7 @@ kern.timecounter.hardware: TSC -> i8254 requires lots of manual editing of internal package database files. However, if you have just run pkg2ng then you may remove - /var/db/pkg/local.sqlite - and extract + /var/db/pkg/local.sqlite and extract /var/backups/pkgdb.bak.tbz. @@ -2757,16 +2807,19 @@ kern.timecounter.hardware: TSC -> i8254 - Not at all! Check out the kernel config section of the Handbook. + Not at all! Check out the kernel + config section of the Handbook. - The new kernel will be installed - to the /boot/kernel directory along - with its modules, while the old kernel and its modules - will be moved to the /boot/kernel.old - directory, so if you make a mistake the next time you play - with your configuration you can boot the previous version - of your kernel. + The new kernel will be + installed to the /boot/kernel + directory along with its modules, while the old kernel + and its modules will be moved to the + /boot/kernel.old directory, so if + you make a mistake the next time you play with your + configuration you can boot the previous version of your + kernel. @@ -2779,16 +2832,16 @@ kern.timecounter.hardware: TSC -> i8254 GENERIC kernels shipped with &os; and later are compiled in debug mode. - Kernels built in debug mode - contain many symbols in separate files that are used for - debugging, thus greatly increasing the size of - /boot/kernel/. - Note that there will be little or no performance loss - from running a debug kernel, and it is useful to keep one + Kernels built in debug mode contain many symbols in + separate files that are used for debugging, thus greatly + increasing the size of /boot/kernel/. + Note that there will be little or no performance loss from + running a debug kernel, and it is useful to keep one around in case of a system panic. However, if you are running low on disk space, there - are different options to reduce the size of /boot/kernel/. + are different options to reduce the size of + /boot/kernel/. If you do not want the symbol files to be installed, make sure you have the following line present in @@ -2798,13 +2851,13 @@ kern.timecounter.hardware: TSC -> i8254 For more information see &man.src.conf.5;. - If you do not want to build a debug kernel, make - sure that both of the following are true: + If you do not want to build a debug kernel, make sure + that both of the following are true: - You do not have a line in your kernel configuration - file that reads: + You do not have a line in your kernel + configuration file that reads: makeoptions DEBUG=-g @@ -2816,29 +2869,31 @@ kern.timecounter.hardware: TSC -> i8254 Either of the above settings will cause your kernel to - be built in debug mode. As long as you make sure you follow - the steps above, you can build your kernel normally. + be built in debug mode. As long as you make sure you + follow the steps above, you can build your kernel + normally. - If you want only the modules you use to be built - and installed, make sure you have a line like below in + If you want only the modules you use to be built and + installed, make sure you have a line like below in /etc/make.conf: MODULES_OVERRIDE= accf_http ipfw - Replace accf_httpd ipfw with - a list of modules you need. Only these modules will be + Replace accf_httpd ipfw with a + list of modules you need. Only these modules will be built. This does not only reduce the size of the kernel directory but also decreases the amount of time needed to build your kernel. For more information see /usr/share/examples/etc/make.conf. You can also remove unneeded devices from your kernel - to further reduce the size. See - for more information. + to further reduce the size. See for more information. To put any of these options into effect you will have - to build and install - your new kernel. + to build + and install your new kernel. Most kernels (/boot/kernel/kernel) tend to be around 12 MB to 16 MB.