diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 2e56e38795..dd3ba4ac52 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -6,9 +6,9 @@ - Frequently Asked Questions for FreeBSD 6.<replaceable>X</replaceable> and 7.<replaceable>X</replaceable> + Frequently Asked Questions for &os; 6.<replaceable>X</replaceable> and 7.<replaceable>X</replaceable> - The FreeBSD Documentation Project + The &os; Documentation Project $FreeBSD$ @@ -27,7 +27,7 @@ 2006 2007 2008 - The FreeBSD Documentation Project + The &os; Documentation Project &bookinfo.legalnotice; @@ -57,17 +57,17 @@ - This is the FAQ for FreeBSD versions 6.X and 7.X. - All entries are assumed to be relevant to FreeBSD 6.X and + This is the FAQ for &os; versions 6.X and 7.X. + All entries are assumed to be relevant to &os; 6.X and later, unless otherwise noted. If you are interested in helping with this project, send email to the &a.doc;. The latest version of this document is always available from the FreeBSD + url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os; World Wide Web server. It may also be downloaded as one large HTML file with HTTP or as plain text, &postscript;, PDF, etc. from the FreeBSD FTP + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">&os; FTP server. You may also want to Search the FAQ. @@ -77,10 +77,10 @@ Introduction - Welcome to the FreeBSD 6.X-7.X FAQ! + Welcome to the &os; 6.X-7.X FAQ! As is usual with Usenet FAQs, this document aims to cover the - most frequently asked questions concerning the FreeBSD operating + most frequently asked questions concerning the &os; operating system (and of course answer them!). Although originally intended to reduce bandwidth and avoid the same old questions being asked over and over again, FAQs have become recognized as valuable @@ -93,11 +93,11 @@ - What is FreeBSD? + What is &os;? - Briefly, FreeBSD is a &unix; like operating system for + Briefly, &os; is a &unix; like operating system for AMD64 and &intel; EM64T, &i386; PC-98, IA-64, &arm;, &powerpc; and &ultrasparc; platforms based on U.C. Berkeley's 4.4BSD-Lite @@ -106,27 +106,27 @@ Jolitz's port of U.C. Berkeley's Net/2 to the &i386;, known as 386BSD, though very little of the 386BSD code remains. A fuller description of - what FreeBSD is and how it can work for you may be found on - the FreeBSD home + what &os; is and how it can work for you may be found on + the &os; home page. - FreeBSD is used by companies, Internet Service Providers, + &os; is used by companies, Internet Service Providers, researchers, computer professionals, students and home users all over the world in their work, education and recreation. - For more detailed information on FreeBSD, please see the - FreeBSD + For more detailed information on &os;, please see the + &os; Handbook. - What is the goal of the FreeBSD Project? + What is the goal of the &os; Project? - The goal of the FreeBSD Project is to provide software + The goal of the &os; Project is to provide software that may be used for any purpose and without strings attached. Many of us have a significant investment in the code (and project) and would certainly not mind a little financial @@ -150,18 +150,18 @@ to replace such software with submissions under the more relaxed - FreeBSD license whenever possible. + &os; license whenever possible. - Does the FreeBSD license have any restrictions? + Does the &os; license have any restrictions? Yes. Those restrictions do not control how you use - the code, merely how you treat the FreeBSD Project itself. + the code, merely how you treat the &os; Project itself. If you have serious license concerns, read the actual @@ -182,7 +182,7 @@ - Can FreeBSD replace my current operating system? + Can &os; replace my current operating system? @@ -191,7 +191,7 @@ Most people do not actually use an operating system. They use applications. The applications are what really - use the operating system. FreeBSD is designed to provide + use the operating system. &os; is designed to provide a robust and full-featured environment for applications. It supports a wide variety of web browsers, office suites, email readers, graphics programs, programming @@ -204,28 +204,28 @@ If you need to use an application that is only available on one operating system, you simply cannot replace that operating system. Chances are there is a very - similar application on FreeBSD, however. If you want a + similar application on &os;, however. If you want a solid office or Internet server, a reliable workstation, or just the ability to do your job without interruptions, - FreeBSD will almost certainly do everything you need. + &os; will almost certainly do everything you need. Many computer users across the world, including both - novices and experienced &unix; administrators, use FreeBSD + novices and experienced &unix; administrators, use &os; as their only desktop operating system. - If you are migrating to FreeBSD from some other &unix; + If you are migrating to &os; from some other &unix; environment, you already know most of what you need to. If your background is in graphic-driven operating systems such as &windows; and older versions of &macos;, expect to invest additional time learning the &unix; way of doing things. This FAQ and the FreeBSD Handbook are + url="&url.books.handbook;/index.html">&os; Handbook are excellent places to start. - Why is it called FreeBSD? + Why is it called &os;? @@ -253,7 +253,7 @@ free is being used in two ways here, one meaning at no cost, the other meaning you can do whatever you like. Apart from one or two things you - cannot do with the FreeBSD code, for + cannot do with the &os; code, for example pretending you wrote it, you can really do whatever you like with it. @@ -261,7 +261,7 @@ - What are the differences between FreeBSD and NetBSD, OpenBSD, + What are the differences between &os; and NetBSD, OpenBSD, and other open source BSD operating systems? @@ -278,7 +278,7 @@ - What is the latest version of FreeBSD? + What is the latest version of &os;? - At this point in FreeBSD's development, there are two + At this point in &os;'s development, there are two parallel development branches; releases are being made from both branches. The 6.X series of releases is being made from the 6-STABLE branch @@ -325,22 +325,22 @@ Releases are made every few months. While many people stay more up-to-date with - the FreeBSD sources (see the questions on &os.current; and &os.stable;) than that, doing so is more of a commitment, as the sources are a moving target. - More information on FreeBSD releases can be found on + More information on &os; releases can be found on the Release - Engineering page on the FreeBSD Web site. + Engineering page on the &os; Web site. - What is FreeBSD-CURRENT? + What is &os;-CURRENT? @@ -421,24 +421,24 @@ - What is the FreeBSD-STABLE concept? + What is the &os;-STABLE concept? - Back when FreeBSD 2.0.5 was released, FreeBSD + Back when &os; 2.0.5 was released, &os; development branched in two. One branch was named -STABLE, one -CURRENT. - FreeBSD-STABLE is intended for Internet Service Providers + &os;-STABLE is intended for Internet Service Providers and other commercial enterprises for whom sudden shifts or experimental features are quite undesirable. It receives only well-tested bug fixes and other small incremental - enhancements. FreeBSD-CURRENT, on the other hand, has + enhancements. &os;-CURRENT, on the other hand, has been one unbroken line since 2.0 was released, leading towards &rel.current;-RELEASE and beyond. For more detailed information on branches see FreeBSD Release Engineering: Creating the Release Branch, + url="&url.articles.releng;/release-proc.html#REL-BRANCH">&os; Release Engineering: Creating the Release Branch, the status of the branches and the upcoming release schedule can be found on the Release Engineering Information page. @@ -467,7 +467,7 @@ - When are FreeBSD releases made? + When are &os; releases made? @@ -480,14 +480,14 @@ that the addition of new features does not compromise the stability of the release. Many users regard this caution as one of the best things about - FreeBSD, even though waiting for all the latest goodies to reach + &os;, even though waiting for all the latest goodies to reach -STABLE can be a little frustrating. More information on the release engineering process (including a schedule of upcoming releases) can be found on the release - engineering pages on the FreeBSD Web site. + engineering pages on the &os; Web site. For people who need or want a little more excitement, binary snapshots are made daily as discussed above. @@ -496,18 +496,18 @@ - Who is responsible for FreeBSD? + Who is responsible for &os;? - The key decisions concerning the FreeBSD project, such + The key decisions concerning the &os; project, such as the overall direction of the project and who is allowed to add code to the source tree, are made by a core team of 9 people. There is a much larger team of more than 350 committers - who are authorized to make changes directly to the FreeBSD + who are authorized to make changes directly to the &os; source tree. However, most non-trivial changes are discussed in advance @@ -519,14 +519,14 @@ - Where can I get FreeBSD? + Where can I get &os;? - Every significant release of FreeBSD is available via + Every significant release of &os; is available via anonymous FTP from the - FreeBSD FTP site: + &os; FTP site: @@ -552,7 +552,7 @@ - Information about obtaining FreeBSD on CD, DVD, and other + Information about obtaining &os; on CD, DVD, and other media can be found in the Handbook. @@ -578,7 +578,7 @@ Before submitting a problem report, please read Writing - FreeBSD Problem Reports, an article on how to write + &os; Problem Reports, an article on how to write good problem reports. @@ -592,7 +592,7 @@ Please check the Documentation list on the main FreeBSD web + url="http://www.FreeBSD.org">&os; web site. @@ -605,7 +605,7 @@ - What good books are there about FreeBSD? + What good books are there about &os;? @@ -613,7 +613,7 @@ available online from this link: . The same documents are available as packages, that you can easily - install on your FreeBSD system. More details on + install on your &os; system. More details on documentation packages can be found in the next paragraphs. @@ -634,7 +634,7 @@ Yes. The documentation is available in a number of - different formats and compression schemes on the FreeBSD + different formats and compression schemes on the &os; FTP site, in the /pub/FreeBSD/doc/ directory. @@ -651,7 +651,7 @@ The document's language and encoding. These are based on the locale names you will find under - /usr/share/locale on your FreeBSD + /usr/share/locale on your &os; system. The current languages and encodings that we have for documentation are as follows: @@ -916,7 +916,7 @@ zip The Zip format. If you want to - uncompress this on FreeBSD you will need + uncompress this on &os; you will need to install the archivers/unzip port first. @@ -970,7 +970,7 @@ - Where do I find info on the FreeBSD mailing lists? + Where do I find info on the &os; mailing lists? @@ -982,7 +982,7 @@ - What FreeBSD news groups are available? + What &os; news groups are available? @@ -994,31 +994,31 @@ - Are there FreeBSD IRC (Internet Relay Chat) + Are there &os; IRC (Internet Relay Chat) channels? - Yes, most major IRC networks host a FreeBSD chat + Yes, most major IRC networks host a &os; chat channel: Channel #FreeBSD on EFNet - is a FreeBSD forum, but do not go there for tech + is a &os; forum, but do not go there for tech support or try to get folks there to help you avoid the pain of reading manual pages or doing your own research. It is a chat channel, first and foremost, and topics there are just as likely to involve sex, sports or nuclear - weapons as they are FreeBSD. You Have Been Warned! + weapons as they are &os;. You Have Been Warned! Available at server irc.chat.org. Channel #FreeBSDhelp on EFNet - is a channel dedicated to helping FreeBSD users. They + is a channel dedicated to helping &os; users. They are much more sympathetic to questions than #FreeBSD is. @@ -1028,7 +1028,7 @@ Freenode is a general help channel with about 300 users at any time. The conversations have been known to run off-topic for a while, - but priority is given to users with FreeBSD questions. We are + but priority is given to users with &os; questions. We are good about helping you understand the basics, referring to the Handbook whenever possible, and directing you where to learn more about the topic you need help with. We are a primarily @@ -1092,16 +1092,16 @@ - Where can I get commercial FreeBSD training and support? + Where can I get commercial &os; training and support? DaemonNews provides commercial training and support for - FreeBSD. More information can be found at their + &os;. More information can be found at their BSD Mall site. - The FreeBSD Mall provides commercial FreeBSD support. + The &os; Mall provides commercial &os; support. You can get more information at their web site. @@ -1129,7 +1129,7 @@ - Which file do I download to get FreeBSD? + Which file do I download to get &os;? @@ -1171,7 +1171,7 @@ Full instructions on this procedure and a little bit more about installation issues in general can be found in the Handbook entry on - installing FreeBSD. + installing &os;. @@ -1222,7 +1222,7 @@ fdimage or rawrite) described in the installation guide to - FreeBSD. + &os;. @@ -1230,18 +1230,18 @@ - Where are the instructions for installing FreeBSD? + Where are the instructions for installing &os;? Installation instructions can be found in the - Handbook entry on installing FreeBSD. + Handbook entry on installing &os;. - What do I need in order to run FreeBSD? + What do I need in order to run &os;? @@ -1288,13 +1288,13 @@ - Can &windows; co-exist with FreeBSD? + Can &windows; co-exist with &os;? - Install &windows; first, then FreeBSD. - FreeBSD's boot manager will then manage to boot &windows; and - FreeBSD. If you install &windows; second, it will boorishly + Install &windows; first, then &os;. + &os;'s boot manager will then manage to boot &windows; and + &os;. If you install &windows; second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next section. @@ -1307,13 +1307,13 @@ - You can reinstall the boot manager FreeBSD comes with in + You can reinstall the boot manager &os; comes with in one of three ways: Running DOS, go into the tools directory of your - FreeBSD distribution and look for + &os; distribution and look for bootinst.exe. You run it like so: @@ -1323,14 +1323,14 @@ - Boot the FreeBSD boot floppy again and go to the + Boot the &os; boot floppy again and go to the Custom menu item for custom installation. Choose Partition. Select the drive which used to contain your boot manager (likely the first one) and when you come to the partition editor for it, as the very first thing (e.g. do not make any changes) press W. This will ask for confirmation, select &gui.yes;, and when you get the Boot Manager selection prompt, be - sure to select the FreeBSD Boot Manager. This will + sure to select the &os; Boot Manager. This will re-write the boot manager to disk. Now quit out of the installation menu and reboot off the hard disk as normal. @@ -1359,14 +1359,14 @@ My A, T, or X series IBM Thinkpad locks up when I first - booted up my FreeBSD installation. How can I solve this? + booted up my &os; installation. How can I solve this? A bug in early revisions of IBM's BIOS on these machines - mistakenly identifies the FreeBSD partition as a potential FAT + mistakenly identifies the &os; partition as a potential FAT suspend-to-disk partition. When the BIOS tries to parse the - FreeBSD partition it hangs. + &os; partition it hangs. According to IBMIn an email from Keith Frechette @@ -1426,26 +1426,26 @@ url="http://docs.FreeBSD.org/cgi/mid.cgi?20010427133759.A71732">This message from Jacques Vidrine to the &a.mobile; describes a procedure which may work if your newer IBM - laptop does not boot FreeBSD properly, and you can upgrade + laptop does not boot &os; properly, and you can upgrade or downgrade the BIOS. If you have an earlier BIOS, and upgrading is not an option, a - workaround is to install FreeBSD, change the partition ID FreeBSD + workaround is to install &os;, change the partition ID &os; uses, and install new boot blocks that can handle the different partition ID. First, you will need to restore the machine to a state where it can get through its self-test screen. Doing this requires - powering up the machine without letting it find a FreeBSD + powering up the machine without letting it find a &os; partition on its primary disk. One way is to remove the hard disk and temporarily move it to an older ThinkPad (such as a ThinkPad 600) or a desktop PC with an appropriate conversion cable. Once - it is there, you can delete the FreeBSD partition and move the hard + it is there, you can delete the &os; partition and move the hard disk back. The ThinkPad should now be in a bootable state again. With the machine functional again, you can use the workaround - procedure described here to get a working FreeBSD + procedure described here to get a working &os; installation. @@ -1458,7 +1458,7 @@ - Install FreeBSD as normal on to the ThinkPad. + Install &os; as normal on to the ThinkPad. Do not use Dangerously Dedicated mode. Do not reboot when the install has finished. @@ -1472,7 +1472,7 @@ - Use &man.fdisk.8; to change the FreeBSD partition ID from + Use &man.fdisk.8; to change the &os; partition ID from 165 to 166 (this is the type used by OpenBSD). @@ -1485,23 +1485,23 @@ Use &man.disklabel.8; to write boot1 - and boot2 to your FreeBSD slice. + and boot2 to your &os; slice. &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn n is the number of the slice - where you installed FreeBSD. + where you installed &os;. Reboot. At the boot prompt you will be given the option of booting OpenBSD. This will actually - boot FreeBSD. + boot &os;. Getting this to work in the case where you want to dual boot - OpenBSD and FreeBSD on the same laptop is left as an exercise for + OpenBSD and &os; on the same laptop is left as an exercise for the reader. @@ -1622,20 +1622,20 @@ This causes a lot of confusion among new system administrators. First of all, the physical geometry of a SCSI drive is - totally irrelevant, as FreeBSD works in term of disk + totally irrelevant, as &os; works in term of disk blocks. In fact, there is no such thing as the physical geometry, as the sector density varies across the disk. What manufacturers claim is the physical geometry is usually the geometry that they have determined wastes the least - space. For IDE disks, FreeBSD does work in terms of C/H/S, + space. For IDE disks, &os; does work in terms of C/H/S, but all modern drives internally convert this into block references. All that matters is the logical geometry. This is the answer that the BIOS gets when it asks the drive what is your geometry? It - then uses this geometry to access the disk. As FreeBSD + then uses this geometry to access the disk. As &os; uses the BIOS when booting, it is very important to get this right. In particular, if you have more than one operating system on a disk, they must all agree on the @@ -1661,7 +1661,7 @@ have 261 cylinders, 63 sectors per track and 255 heads. - If you are not sure about this, or FreeBSD fails to + If you are not sure about this, or &os; fails to detect the geometry correctly during installation, the simplest way around this is usually to create a small DOS partition on the disk. The BIOS should then detect the @@ -1671,7 +1671,7 @@ programming network cards and the like, however. Alternatively, there is a freely available utility - distributed with FreeBSD called + distributed with &os; called pfdisk.exe. You can find it in the tools subdirectory on the &os; CD-ROM or on the various &os; FTP sites. This program @@ -1689,7 +1689,7 @@ Yes. You must make sure that your root partition is below 1024 cylinders so the BIOS can boot the kernel from it. (Note that - this is a limitation in the PC's BIOS, not FreeBSD). + this is a limitation in the PC's BIOS, not &os;). For a SCSI drive, this will normally imply that the root partition will be in the first 1024 MB (or in the first 4096 MB @@ -1725,15 +1725,15 @@ - When I boot FreeBSD for the first time after install I get Missing Operating + When I boot &os; for the first time after install I get Missing Operating System. What is happening? - This is classically a case of FreeBSD and DOS or some other + This is classically a case of &os; and DOS or some other OS conflicting over their ideas of disk geometry. You will have to reinstall - FreeBSD, but obeying the instructions given above will almost + &os;, but obeying the instructions given above will almost always get you going. @@ -1746,11 +1746,11 @@ This is another symptom of the problem described in the - preceding question. Your BIOS geometry and FreeBSD geometry + preceding question. Your BIOS geometry and &os; geometry settings do not agree! If your controller or BIOS supports cylinder translation (often marked as >1GB drive support), try toggling its setting and reinstalling - FreeBSD. + &os;. @@ -1778,7 +1778,7 @@ Having the sources on-line and knowing how to build a system with them will make it much easier for you to upgrade - to future releases of FreeBSD. + to future releases of &os;. To actually select a subset of the sources, use the Custom menu item when you are in the Distributions menu of the @@ -1793,7 +1793,7 @@ Building a new kernel was originally pretty much a required - step in a FreeBSD installation, but more recent releases have + step in a &os; installation, but more recent releases have benefited from the introduction of much friendlier kernel configuration methods. It is very easy to configure the kernel's configuration by much more flexible @@ -1814,7 +1814,7 @@ - The default password format on FreeBSD is to use + The default password format on &os; is to use MD5-based passwords. These are believed to be more secure than the traditional &unix; password format, which used a scheme based on the @@ -1859,7 +1859,7 @@ block's and the kernel's understanding of the disk devices. The error usually manifests on two-disk IDE systems, with the hard disks arranged as the master or - single device on separate IDE controllers, with FreeBSD + single device on separate IDE controllers, with &os; installed on the secondary IDE controller. The boot blocks think the system is installed on ad0 (the second BIOS disk) while the kernel assigns the first disk on the @@ -1882,7 +1882,7 @@ set root_disk_unit="disk_number" . disk_number - will be 0 if FreeBSD is installed + will be 0 if &os; is installed on the master drive on the first IDE controller, 1 if it is installed on the slave on the first IDE controller, 2 if @@ -1896,14 +1896,14 @@ To make this change permanent (i.e, so you do not have to do this every time you reboot or turn on - your FreeBSD machine), put the line + your &os; machine), put the line root_disk_unit="disk_number" in /boot/loader.conf.local . - Move the FreeBSD disk onto the primary IDE + Move the &os; disk onto the primary IDE controller, so the hard disks are consecutive. @@ -2076,12 +2076,12 @@ - I want to get a piece of hardware for my FreeBSD + I want to get a piece of hardware for my &os; system. Which model/brand/type is best? - This is discussed continually on the FreeBSD mailing + This is discussed continually on the &os; mailing lists. Since hardware changes so quickly, however, we expect this. We still strongly recommend that you read through the Hardware Notes for &os; @@ -2186,12 +2186,12 @@ - Does FreeBSD support architectures other than the x86? + Does &os; support architectures other than the x86? - Yes. FreeBSD currently runs on the Intel x86 and the AMD64 + Yes. &os; currently runs on the Intel x86 and the AMD64 architectures. The Intel EM64T, IA-64, &arm;, &powerpc;, sun4v and &sparc64; architectures are also supported. Upcoming platforms are &mips; and &s390;, join the &a.mips; for more information about @@ -2207,7 +2207,7 @@ - Does FreeBSD support Symmetric Multiprocessing + Does &os; support Symmetric Multiprocessing (SMP)? @@ -2244,11 +2244,11 @@ - What kind of hard drives does FreeBSD support? + What kind of hard drives does &os; support? - FreeBSD supports EIDE, SATA, SCSI, and SAS drives (with a + &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 @@ -2276,21 +2276,21 @@ - FreeBSD supports SCSI and QIC-36 (with a QIC-02 interface). + &os; supports SCSI and QIC-36 (with a QIC-02 interface). This includes 8-mm (aka Exabyte) and DAT drives. Some of the early 8-mm drives are not quite compatible - with SCSI-2, and may not work well with FreeBSD. + with SCSI-2, and may not work well with &os;. - Does FreeBSD support tape changers? + Does &os; support tape changers? - FreeBSD supports SCSI changers using the &man.ch.4; + &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. @@ -2350,14 +2350,14 @@ - Which CD-RW drives are supported by FreeBSD? + Which CD-RW drives are supported by &os;? - FreeBSD supports any ATAPI-compatible IDE CD-R or CD-RW + &os; supports any ATAPI-compatible IDE CD-R or CD-RW drive. See &man.burncd.8; for details. - FreeBSD also supports any SCSI CD-R or CD-RW drives. + &os; also supports any SCSI CD-R or CD-RW drives. Install and use the cdrecord command from the ports or packages system, and make sure that you have the pass device compiled in your @@ -2367,11 +2367,11 @@ - Does FreeBSD support &iomegazip; drives? + Does &os; support &iomegazip; drives? - FreeBSD supports SCSI and ATAPI (IDE) &iomegazip; drives out + &os; supports SCSI and ATAPI (IDE) &iomegazip; drives out of the box. SCSI ZIP drives can only be set to run at SCSI target IDs 5 or 6, but if your SCSI host adapter's BIOS supports it you can even boot from it. It @@ -2380,7 +2380,7 @@ your adapter's documentation if you would like to use this feature. - FreeBSD also supports Parallel Port Zip Drives. Check + &os; also supports Parallel Port Zip Drives. Check that your kernel contains the scbus0, da0, @@ -2404,13 +2404,13 @@ - Does FreeBSD support &jaz;, EZ and other removable + Does &os; support &jaz;, EZ and other removable drives? They work. Most of these are SCSI devices, so they - look like SCSI disks to FreeBSD. The IDE EZ looks like an + look like SCSI disks to &os;. The IDE EZ looks like an IDE drive. Make sure that any external units are powered on when @@ -2436,11 +2436,11 @@ - Does FreeBSD support my USB keyboard? + Does &os; support my USB keyboard? - FreeBSD supports USB keyboards + &os; supports USB keyboards out-of-the-box. Once you have USB keyboard support enabled on your system, the AT keyboard becomes /dev/kbd0 and the USB keyboard @@ -2506,7 +2506,7 @@ - FreeBSD supports the bus mouse and the InPort bus + &os; supports the bus mouse and the InPort bus mouse from such manufacturers as Microsoft, Logitech and ATI. The GENERIC kernel does not include the device driver. To build a custom kernel with the bus mouse @@ -2615,7 +2615,7 @@ My mouse has a fancy wheel and buttons. Can I use them in - FreeBSD? + &os;? @@ -2679,28 +2679,28 @@ bindkey ^[[3~ delete-char # for xterm - Which network cards does FreeBSD support? + Which network cards does &os; support? See the Hardware Notes supplied with each release of - FreeBSD for a more + &os; for a more complete list. - Does FreeBSD support software modems, such as Winmodems? + Does &os; support software modems, such as Winmodems? - FreeBSD supports many software modems via add-on + &os; supports many software modems via add-on software. For example, the comms/ltmdm port adds support for modems based on the very popular Lucent LT chipsets. - You cannot install FreeBSD via a software modem; this + You cannot install &os; via a software modem; this software must be installed after the OS is installed. @@ -2728,7 +2728,7 @@ bindkey ^[[3~ delete-char # for xterm Which multi-port serial cards are supported by - FreeBSD? + &os;? @@ -2767,7 +2767,7 @@ bindkey ^[[3~ delete-char # for xterm - Which sound cards are supported by FreeBSD? + Which sound cards are supported by &os;? @@ -2852,7 +2852,7 @@ bindkey ^[[3~ delete-char # for xterm Certain Micron motherboards have a non-conforming PCI BIOS - implementation that causes grief when FreeBSD boots because PCI + implementation that causes grief when &os; boots because PCI devices do not get configured at their reported addresses. Disable the Plug and Play Operating System @@ -2967,7 +2967,7 @@ ARRE (Auto Read Reallocation Enbld): 1 - Why does FreeBSD not detect my HP Netserver's SCSI + Why does &os; not detect my HP Netserver's SCSI controller? @@ -2976,7 +2976,7 @@ ARRE (Auto Read Reallocation Enbld): 1 controller in the HP Netserver machines occupies EISA slot number 11, so all the true EISA slots are in front of it. Alas, the address space for EISA slots >= 10 - collides with the address space assigned to PCI, and FreeBSD's + collides with the address space assigned to PCI, and &os;'s auto-configuration currently cannot handle this situation very well. @@ -3088,7 +3088,7 @@ quit - If it is a problem with part of the base FreeBSD system, + 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 @@ -3097,7 +3097,7 @@ quit In particular, a dead giveaway that this is - not a FreeBSD bug is if you see the + 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. @@ -3182,7 +3182,7 @@ quit 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 FreeBSD, and you should follow the + 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 FreeBSD developers are very interested in these + 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 - Why does FreeBSD only use 64 MB of RAM when my system has + Why does &os; only use 64 MB of RAM when my system has 128 MB of RAM installed? - Due to the manner in which FreeBSD gets the memory size + Due to the manner in which &os; gets the memory size from the BIOS, it can only detect 16 bits worth of Kbytes in size (65535 Kbytes = 64 MB) (or less... some BIOSes peg the - memory size to 16 MB). If you have more than 64 MB, FreeBSD will + memory size to 16 MB). If you have more than 64 MB, &os; will attempt to detect it; however, the attempt may fail. To work around this problem, you need to use the kernel @@ -3299,7 +3299,7 @@ quit - Normally, FreeBSD determines a number of kernel parameters, + Normally, &os; determines a number of kernel parameters, such as as the maximum number of files that can be open concurrently, from the amount of memory installed in the system. On systems with one gigabyte of RAM or more, this @@ -3321,7 +3321,7 @@ quit - My system does not have 1 GB of RAM, and FreeBSD still + My system does not have 1 GB of RAM, and &os; still panics with kmem_map too small! @@ -3343,7 +3343,7 @@ quit - The FreeBSD kernel will only allow a certain number of + 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 @@ -3467,7 +3467,7 @@ quit The remote machine may be setting your terminal type to something other than the cons25 terminal - type required by the FreeBSD console. + type required by the &os; console. There are a number of possible work-arounds for this problem: @@ -3481,7 +3481,7 @@ quit Use a VT100 emulator like - screen at the FreeBSD console. + screen at the &os; console. screen offers you the ability to run multiple concurrent sessions from one terminal, and is a neat program in its own right. Each @@ -3499,7 +3499,7 @@ quit - Fire up an X server at the FreeBSD end and login to + 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 @@ -3520,7 +3520,7 @@ quit The reasons for this behavior are explained by the following email, posted to the &a.questions; by &a.peter;, in answer to a question about an internal modem that was - no longer found after an upgrade to FreeBSD 4.X (the comments + no longer found after an upgrade to &os; 4.X (the comments in [] have been added to clarify the context). @@ -3686,7 +3686,7 @@ chip1@pci0:31:5: class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02 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 FreeBSD, do this in order to, among + servers that come with &os;, do this in order to, among other things, store the hostname in a log file for future reference by the administrator. @@ -3815,12 +3815,12 @@ calcru: runtime went backwards from 408 usec to 204 usec for pid 0 (swapper) - Your computer has two or more clocks, and FreeBSD has chosen to + Your computer has two or more clocks, and &os; has chosen to use the wrong one. Run &man.dmesg.8;, and check for lines that contain Timecounter. The one with the highest - quality value that FreeBSD chose. + quality value that &os; chose. &prompt.root; dmesg | grep Timecounter Timecounter "i8254" frequency 1193182 Hz quality 0 @@ -3843,7 +3843,7 @@ kern.timecounter.hardware: ACPI-fast 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 FreeBSD is unaware of these adjustments, + 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 @@ -3891,15 +3891,15 @@ kern.timecounter.hardware: TSC -> i8254 - Why does FreeBSD's boot loader display + Why does &os;'s boot loader display Read error and stop after the BIOS screen? - FreeBSD's boot loader is incorrectly recognizing the hard + &os;'s boot loader is incorrectly recognizing the hard drive's geometry. This must be manually set within &man.fdisk.8; when - creating or modifying FreeBSD's slice. + creating or modifying &os;'s slice. The correct drive geometry values can be found within the @@ -4000,7 +4000,7 @@ kern.timecounter.hardware: TSC -> i8254 - An answer for this question can be found in the FreeBSD + An answer for this question can be found in the &os; Glosssary, see LOR. @@ -4021,7 +4021,7 @@ kern.timecounter.hardware: TSC -> i8254 supposed to only be held to maintain short periods of synchronization. This programming contract allows device drivers to use mutexes to synchronize with the rest of the kernel - during interrupts. Interrupts (under FreeBSD) may not sleep. + during interrupts. Interrupts (under &os;) may not sleep. Hence it is imperative that no subsystem in the kernel block for an extended period while holding a mutex. @@ -4060,10 +4060,10 @@ kern.timecounter.hardware: TSC -> i8254 This section is still very sparse, though we are hoping, of - course, that companies will add to it! :) The FreeBSD group has + course, that companies will add to it! :) The &os; group has no financial interest in any of the companies listed here but simply lists them as a public service (and feels that commercial - interest in FreeBSD can have very positive effects on FreeBSD's + interest in &os; can have very positive effects on &os;'s long-term viability). We encourage commercial software vendors to send their entries here for inclusion. See the @@ -4073,26 +4073,26 @@ kern.timecounter.hardware: TSC -> i8254 - Where can I get an Office Suite for FreeBSD? + Where can I get an Office Suite for &os;? The open-source OpenOffice.org office - suite works natively on FreeBSD. The &linux; version of + suite works natively on &os;. The &linux; version of StarOffice, the value-added closed-source version of OpenOffice.org, also - works on FreeBSD. + works on &os;. - FreeBSD also includes a variety of text editors, + &os; also includes a variety of text editors, spreadsheets, and drawing programs in the Ports Collection. - Where can I get &motif; for FreeBSD? + Where can I get &motif; for &os;? @@ -4113,7 +4113,7 @@ kern.timecounter.hardware: TSC -> i8254 software available. These, however, are not for free, but their license allows them to be used in closed-source software. Contact Apps2go for the - least expensive ELF &motif; 2.1.20 distribution for FreeBSD + least expensive ELF &motif; 2.1.20 distribution for &os; (&i386;). There are two distributions, the development @@ -4139,7 +4139,7 @@ kern.timecounter.hardware: TSC -> i8254 - Be sure to specify that you want the FreeBSD version of + Be sure to specify that you want the &os; version of &motif; when ordering (do not forget to mention the architecture you want too)! Versions for NetBSD and OpenBSD are also sold by Apps2go. This is currently a FTP only @@ -4177,12 +4177,12 @@ kern.timecounter.hardware: TSC -> i8254 - Where can I get CDE for FreeBSD? + Where can I get CDE for &os;? Xi Graphics used to sell CDE - for FreeBSD, but no longer do. + for &os;, but no longer do. KDE is an open source X11 desktop which is similar to CDE in many respects. @@ -4195,13 +4195,13 @@ kern.timecounter.hardware: TSC -> i8254 - Are there any Database systems for FreeBSD? + Are there any Database systems for &os;? Yes! See the - Commercial Vendors section of FreeBSD's Web site. + Commercial Vendors section of &os;'s Web site. Also see the @@ -4211,12 +4211,12 @@ kern.timecounter.hardware: TSC -> i8254 - Can I run &oracle; on FreeBSD? + Can I run &oracle; on &os;? Yes. The following pages tell you exactly how to set up - &linux; &oracle; on FreeBSD: + &linux; &oracle; on &os;: @@ -4249,7 +4249,7 @@ kern.timecounter.hardware: TSC -> i8254 Please take a look at the ports page - for info on software packages ported to FreeBSD. The list + 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; @@ -4258,7 +4258,7 @@ kern.timecounter.hardware: TSC -> i8254 Most ports should work on the 6.X, 7.X and 8.X branches. - Each time a FreeBSD release is made, a snapshot of the + 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. @@ -4279,7 +4279,7 @@ kern.timecounter.hardware: TSC -> i8254 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 FreeBSD at the + over the net for various versions of &os; at the following locations: @@ -4339,7 +4339,7 @@ kern.timecounter.hardware: TSC -> i8254 - Does FreeBSD support &java;? + Does &os; support &java;? @@ -4355,7 +4355,7 @@ kern.timecounter.hardware: TSC -> i8254 - If you are running a FreeBSD version that lags + If you are running a &os; version that lags significantly behind -CURRENT or -STABLE, you may need to update your Ports Collection; see the @@ -4423,29 +4423,29 @@ kern.timecounter.hardware: TSC -> i8254 - Why is CVSup not integrated in the main FreeBSD tree? + Why is CVSup not integrated in the main &os; tree? - The FreeBSD base system is designed as self-hosting — it + The &os; base system is designed as self-hosting — it should be possible to build the whole operating system starting with a very limited set of tools. Thus, the actual build tools - needed to compile the FreeBSD sources are bundled with the + needed to compile the &os; sources are bundled with the sources themselves. This includes a C compiler (&man.gcc.1;), &man.make.1;, &man.awk.1;, and similar tools. - Since CVSup is written in Modula-3, adding it to the FreeBSD + Since CVSup is written in Modula-3, adding it to the &os; base system would also require adding and maintaining a Modula-3 compiler. This would lead to both an increase in the disk space - consumed by the FreeBSD sources and additional maintenance work. + consumed by the &os; sources and additional maintenance work. Thus, it is much easier for both the developers and users to keep CVSup as a separate port, which can be easily installed as - a package bundled on the FreeBSD installation CDs. + a package bundled on the &os; installation CDs. However, &os; users are not without an integrated CVSup compatible client anymore - since FreeBSD 6.2-RELEASE. Thanks to &a.mux;, + since &os; 6.2-RELEASE. Thanks to &a.mux;, CVSup was rewritten in C as &man.csup.1; and it is the part of the base system by now. Although it does not implement all the features of @@ -4463,20 +4463,20 @@ kern.timecounter.hardware: TSC -> i8254 - FreeBSD does not include a port upgrading tool, but it + &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 FreeBSD Handbook. + section in the &os; Handbook. Why is /bin/sh so minimal? Why does - FreeBSD not use bash or another shell? + &os; not use bash or another shell? @@ -4560,7 +4560,7 @@ kern.timecounter.hardware: TSC -> i8254 The WAV files can then be converted to other formats or burned onto audio CDs, as described in the FreeBSD Handbook. + url="&url.books.handbook;/creating-cds.html">&os; Handbook. @@ -4669,7 +4669,7 @@ kern.timecounter.hardware: TSC -> i8254 How do I fix this? The problem here is that - FreeBSD has code built-in to keep the kernel from getting + &os; has code built-in to keep the kernel from getting trashed due to hardware or software conflicts. The way to fix this is to leave out the IRQ settings on all but one port. Here is an example: @@ -4717,11 +4717,11 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr Even if you are trying to build FreeBSD-STABLE, it is possible that + linkend="stable">&os;-STABLE, it is possible that you fetched the source tree at a time when it was either being modified, or broken for other reasons; only releases are absolutely guaranteed to be buildable, although FreeBSD-STABLE builds fine the + linkend="stable">&os;-STABLE builds fine the majority of the time. If you have not already done so, try re-fetching the source tree and see if the problem goes away. Try using a different server in case the one you are @@ -4784,13 +4784,13 @@ kern.sched.name: 4BSD - How can I add my new hard disk to my FreeBSD system? + How can I add my new hard disk to my &os; system? See the Adding Disks - section in the FreeBSD Handbook. + section in the &os; Handbook. @@ -4914,11 +4914,11 @@ kern.sched.name: 4BSD you to chose two different methods in partitioning your hard disk(s). The default way makes it compatible with other operating systems on the same machine, by using &man.fdisk.8; table - entries (called slices in FreeBSD), with a - FreeBSD slice that employs partitions of its own. Optionally, + entries (called slices in &os;), with a + &os; slice that employs partitions of its own. Optionally, one can chose to install a boot-selector to switch between the possible operating systems on the disk(s). The alternative uses - the entire disk for FreeBSD, and makes no attempt to be + the entire disk for &os;, and makes no attempt to be compatible with other operating systems. So why it is called dangerous? A disk @@ -4935,20 +4935,20 @@ kern.sched.name: 4BSD 53C8xx range of SCSI controllers). This is not a complete list, there are more. Symptoms of this confusion include the read error message printed by - the FreeBSD bootstrap when it cannot find itself, as well + the &os; bootstrap when it cannot find itself, as well as system lockups when booting. Why have this mode at all then? It only saves a few kbytes of disk space, and it can cause real problems for a new installation. Dangerously dedicated mode's origins lie in a desire to avoid one of the most common - problems plaguing new FreeBSD installers — matching the BIOS + problems plaguing new &os; installers — matching the BIOS geometry numbers for a disk to the disk itself. Geometry is an outdated concept, but one still at the heart of the PC's BIOS and its interaction with - disks. When the FreeBSD installer creates slices, it has to + disks. When the &os; installer creates slices, it has to record the location of these slices on the disk in a fashion that corresponds with the way the BIOS expects to find them. If it gets it wrong, you will not be able to boot. @@ -4968,7 +4968,7 @@ kern.sched.name: 4BSD installer starts, the kernel will print a list of BIOS geometries. Do not panic — wait for the installer to start and then use scrollback to read the numbers. Typically the BIOS - disk units will be in the same order that FreeBSD lists your + disk units will be in the same order that &os; lists your disks, first IDE, then SCSI. When you are slicing up your disk, check that the disk @@ -4977,10 +4977,10 @@ kern.sched.name: 4BSD G key to fix it. You may have to do this if there is absolutely nothing on the disk, or if the disk has been moved from another system. Note that this is only an issue with - the disk that you are going to boot from; FreeBSD will sort + the disk that you are going to boot from; &os; will sort itself out just fine with any other disks you may have. - Once you have got the BIOS and FreeBSD agreeing about the + Once you have got the BIOS and &os; agreeing about the geometry of the disk, your problems are almost guaranteed to be over, and with no need for DD mode at all. If, however, you are still greeted with the dreaded read @@ -5147,7 +5147,7 @@ use "disklabel -r" to install initial label ext2/ext3 - FreeBSD supports ext2fs and ext3fs + &os; supports ext2fs and ext3fs partitions. See &man.mount.ext2fs.8; for more information. @@ -5157,7 +5157,7 @@ use "disklabel -r" to install initial label NTFS - FreeBSD includes a read-only NTFS driver. For + &os; includes a read-only NTFS driver. For more information, see &man.mount.ntfs.8;. A port of ntfs-3g supports write operations on NTFS (see FAT - FreeBSD includes a read-write FAT driver. For + &os; includes a read-write FAT driver. For more information, see &man.mount.msdosfs.8;. @@ -5178,7 +5178,7 @@ use "disklabel -r" to install initial label ReiserFS - FreeBSD includes a read-only ReiserFS driver. For + &os; includes a read-only ReiserFS driver. For more information, see &man.mount.reiserfs.8;. @@ -5187,7 +5187,7 @@ use "disklabel -r" to install initial label ZFS - As of this writing, FreeBSD includes a + As of this writing, &os; includes a port of &sun;'s ZFS driver. The current recommendation is to use it only on &arch.amd64; platforms with sufficient memory. For more information, see &man.zfs.8;. @@ -5234,18 +5234,18 @@ use "disklabel -r" to install initial label Yes. You can use either &man.gbde.8; or &man.geli.8;, see the Encrypting Disk Partitions - section of the FreeBSD Handbook. + section of the &os; Handbook. - How can I use the &windowsnt; loader to boot FreeBSD? + How can I use the &windowsnt; loader to boot &os;? The general idea is that you copy the first sector of your - native root FreeBSD partition into a file in the DOS/&windowsnt; + native root &os; partition into a file in the DOS/&windowsnt; partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the @@ -5257,17 +5257,17 @@ timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" -C:\BOOTSECT.BSD="FreeBSD" +C:\BOOTSECT.BSD="&os;" C:\="DOS" - If FreeBSD is installed on the same disk as the &windowsnt; boot + If &os; is installed on the same disk as the &windowsnt; boot partition simply copy /boot/boot1 to - C:\BOOTSECT.BSD. However, if FreeBSD is + C:\BOOTSECT.BSD. However, if &os; is installed on a different disk /boot/boot1 will not work, /boot/boot0 is needed. /boot/boot0 needs to be installed - using &man.sysinstall.8; by selecting the FreeBSD boot manager on + using &man.sysinstall.8; by selecting the &os; boot manager on the screen which asks if you wish to use a boot manager. This is because /boot/boot0 has the partition table area filled with NULL characters @@ -5281,7 +5281,7 @@ C:\="DOS" un-bootable! - When the FreeBSD boot manager runs it records the last + When the &os; boot manager runs it records the last OS booted by setting the active flag on the partition table entry for that OS and then writes the whole 512-bytes of itself back to the MBR so if you just copy @@ -5294,11 +5294,11 @@ C:\="DOS" - How do I boot FreeBSD and &linux; from LILO? + How do I boot &os; and &linux; from LILO? - If you have FreeBSD and &linux; on the same disk, just follow + If you have &os; and &linux; on the same disk, just follow LILO's installation instructions for booting a non-&linux; operating system. Very briefly, these are: @@ -5307,26 +5307,26 @@ C:\="DOS" other=/dev/hda2 table=/dev/hda - label=FreeBSD + label=&os; - (the above assumes that your FreeBSD slice is known to + (the above assumes that your &os; slice is known to &linux; as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. - If FreeBSD resides on another disk, you need to add + If &os; resides on another disk, you need to add loader=/boot/chain.b to the LILO entry. For example: other=/dev/dab4 table=/dev/dab loader=/boot/chain.b - label=FreeBSD + label=&os; In some cases you may need to specify the BIOS drive number - to the FreeBSD boot loader to successfully boot off the second - disk. For example, if your FreeBSD SCSI disk is probed by BIOS - as BIOS disk 1, at the FreeBSD boot loader prompt you need to + to the &os; boot loader to successfully boot off the second + disk. For example, if your &os; SCSI disk is probed by BIOS + as BIOS disk 1, at the &os; boot loader prompt you need to specify: Boot: 1:da(0,a)/boot/kernel/kernel @@ -5337,8 +5337,8 @@ C:\="DOS" The - &linux;+FreeBSD mini-HOWTO is a good reference for - FreeBSD and &linux; interoperability issues. + &linux;+&os; mini-HOWTO is a good reference for + &os; and &linux; interoperability issues. @@ -5354,7 +5354,7 @@ C:\="DOS" /boot/grub/grub.conf in some systems, e.g. Red Hat Linux and its derivatives). - title FreeBSD 6.1 + title &os; 6.1 root (hd0,a) kernel /boot/loader @@ -5369,7 +5369,7 @@ C:\="DOS" - How do I boot FreeBSD and &linux; using BootEasy? + How do I boot &os; and &linux; using BootEasy? @@ -5507,7 +5507,7 @@ C:\="DOS" Why do all non-English characters in filenames show up as - ? on my CDs when mounted in FreeBSD? + ? on my CDs when mounted in &os;? @@ -5523,7 +5523,7 @@ C:\="DOS" - I burned a CD under FreeBSD and now I can not read it + I burned a CD under &os; and now I can not read it under any other operating system. Why? @@ -5726,7 +5726,7 @@ perm /dev/acd0 0660 change to be visible! This situation is common on web servers. Many people - set up a FreeBSD web server and forget to rotate the log + set up a &os; web server and forget to rotate the log files. The access log fills up /var. The new administrator deletes the file, but the system still complains that the partition is full. Stopping and @@ -5881,7 +5881,7 @@ perm /dev/acd0 0660 The actual reason for the error is that the system crontab has an extra field, specifying which user to run the command as. In the default system crontab provided with - FreeBSD, this is root for all entries. + &os;, this is root for all entries. When this crontab is used as the root user's crontab (which is not the same as the system crontab), &man.cron.8; assumes the string @@ -6072,7 +6072,7 @@ perm /dev/acd0 0660 - Does FreeBSD support System V IPC primitives? + Does &os; support System V IPC primitives? @@ -6097,7 +6097,7 @@ options SYSVMSG # enable for messaging The sendmail server is - the default mail-server software for FreeBSD, but you can + the default mail-server software for &os;, but you can easily replace it with one of the other MTA (for instance, an MTA installed from the ports). @@ -6362,12 +6362,12 @@ options SYSVMSG # enable for messaging Short answer: it is just a name. RC stands for Release Candidate. It signifies that a - release is imminent. In FreeBSD, -PRERELEASE is typically + release is imminent. In &os;, -PRERELEASE is typically synonymous with the code freeze before a release. (For some releases, the -BETA label was used in the same way as -PRERELEASE.) - Long answer: FreeBSD derives its releases from one of + Long answer: &os; derives its releases from one of two places. Major, dot-zero, releases, such as 6.0-RELEASE and 7.0-RELEASE, are branched from the head of the development stream, commonly referred to as greater than 0. Reboot directly to Single User mode to install the kernel. - Long answer: FreeBSD disallows changing system flags + Long answer: &os; disallows changing system flags at security levels greater than 0. You can check your security level with the command: @@ -6441,7 +6441,7 @@ options SYSVMSG # enable for messaging greater than 1. Reboot directly to Single User mode to change the date. - Long answer: FreeBSD disallows changing the time by + Long answer: &os; disallows changing the time by more that one second at security levels greater than 1. You can check your security level with the command: @@ -6726,7 +6726,7 @@ options SYSVMSG # enable for messaging For further information, read the X11 section of the - FreeBSD Handbook. + &os; Handbook. @@ -6788,7 +6788,7 @@ options SYSVMSG # enable for messaging For further information, read the X11 section of the - FreeBSD Handbook. + &os; Handbook. @@ -6948,7 +6948,7 @@ EndSection session, do AltF1. - The default FreeBSD installation has eight virtual + The default &os; installation has eight virtual consoles enabled. AltF1, - Diskless booting means that the FreeBSD + Diskless booting means that the &os; box is booted over a network, and reads the necessary files from a server instead of its hard disk. For full details, please read the @@ -7474,7 +7474,7 @@ Key F15 A A Menu Workplace Nop - Can a FreeBSD box be used as a dedicated network + Can a &os; box be used as a dedicated network router? @@ -7490,15 +7490,15 @@ Key F15 A A Menu Workplace Nop Can I connect my &windows; box to the Internet via - FreeBSD? + &os;? Typically, people who ask this question have two PCs - at home, one with FreeBSD and one with some version of - &windows; the idea is to use the FreeBSD box to connect to + at home, one with &os; and one with some version of + &windows; the idea is to use the &os; box to connect to the Internet and then be able to access the Internet from - the &windows; box through the FreeBSD box. This is really + the &windows; box through the &os; box. This is really just a special case of the previous question and works perfectly well. @@ -7524,7 +7524,7 @@ Key F15 A A Menu Workplace Nop - Does FreeBSD support SLIP and PPP? + Does &os; support SLIP and PPP? @@ -7550,7 +7550,7 @@ Key F15 A A Menu Workplace Nop - Does FreeBSD support NAT or Masquerading? + Does &os; support NAT or Masquerading? @@ -7566,7 +7566,7 @@ Key F15 A A Menu Workplace Nop - How do I connect two FreeBSD systems over a parallel line + How do I connect two &os; systems over a parallel line using PLIP? @@ -7618,7 +7618,7 @@ Key F15 A A Menu Workplace Nop - Why am I having trouble with NFS and FreeBSD? + Why am I having trouble with NFS and &os;? @@ -7662,7 +7662,7 @@ Key F15 A A Menu Workplace Nop Why does mountd keep telling me it can't change attributes and that I have a - bad exports list on my FreeBSD NFS + bad exports list on my &os; NFS server? @@ -7858,7 +7858,7 @@ Key F15 A A Menu Workplace Nop firewall_type="open" in /etc/rc.conf. - For further information on configuring a FreeBSD + For further information on configuring a &os; firewall, see the Handbook chapter. @@ -8032,12 +8032,12 @@ Key F15 A A Menu Workplace Nop This means that some device on your local Ethernet is - using a MAC address in a format that FreeBSD does not + using a MAC address in a format that &os; does not recognize. This is probably caused by someone experimenting with an Ethernet card somewhere else on the network. You will see this most commonly on cable modem networks. It is harmless, and should not affect the - performance of your FreeBSD machine. + performance of your &os; machine. @@ -8677,7 +8677,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj - Prior to FreeBSD version 2.2.5, once the link was + Prior to &os; version 2.2.5, once the link was established, &man.ppp.8; would wait for the peer to initiate the Line Control Protocol (LCP). Many ISPs will not initiate negotiations and expect the client to do so. @@ -8919,7 +8919,7 @@ set dfilter 3 permit 0/0 0/0 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 FreeBSD Handbook for + 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 your .mc @@ -9468,18 +9468,18 @@ ATDT1234567 Serial Communications This section answers common questions about serial - communications with FreeBSD. PPP and SLIP are covered in the + communications with &os;. PPP and SLIP are covered in the Networking section. - How do I tell if FreeBSD found my serial ports? + How do I tell if &os; found my serial ports? - As the FreeBSD kernel boots, it will probe for the serial + 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 @@ -9515,7 +9515,7 @@ sio1: type 16550A - How do I tell if FreeBSD found my modem cards? + How do I tell if &os; found my modem cards? @@ -9526,7 +9526,7 @@ sio1: type 16550A - How do I access the serial ports on FreeBSD? + How do I access the serial ports on &os;? @@ -9607,7 +9607,7 @@ hint.sio.7.irq="12" - Can FreeBSD handle multiport serial cards sharing + Can &os; handle multiport serial cards sharing IRQs? @@ -9645,7 +9645,7 @@ hint.sio.7.irq="12" - How can I connect a dumb terminal to my FreeBSD + How can I connect a dumb terminal to my &os; box? @@ -9826,20 +9826,20 @@ hint.sio.7.irq="12" - FreeBSD uses far more swap space than &linux;. Why? + &os; uses far more swap space than &linux;. Why? - FreeBSD only appears to use more swap than &linux;. In - actual fact, it does not. The main difference between FreeBSD - and &linux; in this regard is that FreeBSD will proactively move + &os; only appears to use more swap than &linux;. In + actual fact, it does not. The main difference between &os; + and &linux; in this regard is that &os; will proactively move entirely idle, unused pages of main memory into swap in order to make more main memory available for active use. &linux; tends to only move pages to swap as a last resort. The perceived heavier use of swap is balanced by the more efficient use of main memory. - Note that while FreeBSD is proactive in this regard, it + 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 @@ -9856,7 +9856,7 @@ 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 FreeBSD kernel as disk + 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 @@ -9920,7 +9920,7 @@ hint.sio.7.irq="12" - Can I run DOS binaries under FreeBSD? + Can I run DOS binaries under &os;? @@ -9944,13 +9944,13 @@ hint.sio.7.irq="12" - What do I need to do to translate a FreeBSD document into + What do I need to do to translate a &os; document into my native language? See the - Translation FAQ in the FreeBSD Documentation Project + Translation FAQ in the &os; Documentation Project Primer. @@ -9971,7 +9971,7 @@ hint.sio.7.irq="12" The email is being sent from a known spam domain or IP block. - The FreeBSD mail servers reject email from known + The &os; mail servers reject email from known spam sources. If you have service through a company or domain who generates or relays spam, please switch to a service provider who does not. @@ -10024,11 +10024,11 @@ hint.sio.7.irq="12" - Where can I find a free FreeBSD account? + Where can I find a free &os; account? - While FreeBSD does not provide open access to any of their + While &os; does not provide open access to any of their servers, others do provide open access &unix; systems. The charge varies and limited services may be available. @@ -10216,24 +10216,24 @@ hint.sio.7.irq="12" - The FreeBSD Funnies + The &os; Funnies - How cool is FreeBSD? + How cool is &os;? Q. Has anyone done any temperature testing while - running FreeBSD? I know &linux; runs cooler than DOS, but have - never seen a mention of FreeBSD. It seems to run really + running &os;? I know &linux; runs cooler than DOS, but have + never seen a mention of &os;. It seems to run really hot. A. No, but we have done numerous taste tests on blindfolded volunteers who have also had 250 micrograms of LSD-25 administered beforehand. 35% of the volunteers said that - FreeBSD tasted sort of orange, whereas &linux; tasted like purple + &os; tasted sort of orange, whereas &linux; tasted like purple haze. Neither group mentioned any significant variances in temperature. We eventually had to throw the results of this survey out entirely anyway when we found that @@ -10242,11 +10242,11 @@ hint.sio.7.irq="12" are at Apple now, working on their new scratch and sniff GUI. It is a funny old business we are in! - Seriously, both FreeBSD and &linux; use the + Seriously, both &os; and &linux; use the HLT (halt) instruction when the system is idle thus lowering its energy consumption and therefore the heat it generates. Also if you have APM (advanced power - management) configured, then FreeBSD can also put the CPU into + management) configured, then &os; can also put the CPU into a low power mode. @@ -10257,7 +10257,7 @@ hint.sio.7.irq="12" - Q. Is there anything odd that FreeBSD + Q. Is there anything odd that &os; does when compiling the kernel which would cause the memory to make a scratchy sound? When compiling (and for a brief moment after recognizing the floppy drive upon startup, as well), a @@ -10288,7 +10288,7 @@ hint.sio.7.irq="12" - How many FreeBSD hackers does it take to change a + How many &os; hackers does it take to change a lightbulb? @@ -10347,7 +10347,7 @@ hint.sio.7.irq="12" shines dimmer than the old one; Two to back it out with a furious flame of a commit - message, arguing that FreeBSD is better off in the dark than + message, arguing that &os; is better off in the dark than with a dim lightbulb; Forty-six to argue vociferously about the backing out @@ -10355,7 +10355,7 @@ hint.sio.7.irq="12" -core; Eleven to request a smaller lightbulb so it will fit - their Tamagotchi if we ever decide to port FreeBSD to that + their Tamagotchi if we ever decide to port &os; to that platform; Seventy-three to complain about the SNR on -hackers and @@ -10371,7 +10371,7 @@ hint.sio.7.irq="12" Thirty-one to point out that the new lightbulb would shine 0.364% brighter if compiled with TenDRA (although it will have - to be reshaped into a cube), and that FreeBSD should therefore + to be reshaped into a cube), and that &os; should therefore switch to TenDRA instead of GCC; One to complain that the new lightbulb lacks @@ -10461,18 +10461,18 @@ hint.sio.7.irq="12" - How can I learn more about FreeBSD's internals? + How can I learn more about &os;'s internals? - At this time, there is only one book on FreeBSD-specific OS + At this time, there is only one book on &os;-specific OS internals, namely The Design and Implementation of the - FreeBSD Operating System by Marshall Kirk McKusick and + &os; Operating System by Marshall Kirk McKusick and George V. Neville-Neil, ISBN 0-201-70245-2, which focuses on version 5.X of &os;. Additionally, much general &unix; knowledge is directly - applicable to FreeBSD. + applicable to &os;. For a list of relevant books, please check the Handbook's Operating @@ -10482,13 +10482,13 @@ hint.sio.7.irq="12" - How can I contribute to FreeBSD? + How can I contribute to &os;? Please see the article on Contributing - to FreeBSD for specific advice on how to do this. + to &os; for specific advice on how to do this. Assistance is more than welcome! @@ -10500,7 +10500,7 @@ hint.sio.7.irq="12" There are currently three active/semi-active branches - in the FreeBSD CVS Repository. (Earlier branches are only changed very rarely, which is why there are only three active @@ -10632,7 +10632,7 @@ hint.sio.7.irq="12" Please take a look at the article on Contributing - to FreeBSD to learn how to submit code. + to &os; to learn how to submit code. And thanks for the thought!