diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index c0e9e496de..28ff57749d 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -46,10 +46,32 @@ The FreeBSD Documentation Project - &bookinfo.trademarks; - &bookinfo.legalnotice; + + &tm-attrib.freebsd; + &tm-attrib.3com; + &tm-attrib.adobe; + &tm-attrib.creative; + &tm-attrib.cvsup; + &tm-attrib.ibm; + &tm-attrib.ieee; + &tm-attrib.intel; + &tm-attrib.iomega; + &tm-attrib.linux; + &tm-attrib.microsoft; + &tm-attrib.mips; + &tm-attrib.netscape; + &tm-attrib.opengroup; + &tm-attrib.oracle; + &tm-attrib.sgi; + &tm-attrib.sparc; + &tm-attrib.sun; + &tm-attrib.usrobotics; + &tm-attrib.xfree86; + &tm-attrib.general; + + This is the FAQ for FreeBSD versions 2.X, 3.X, 4.X and 5.X. All entries are assumed to be relevant to FreeBSD 2.0.5 and @@ -60,7 +82,7 @@ URL="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">FreeBSD 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 server. You may also want to Search the @@ -91,13 +113,13 @@ - Briefly, FreeBSD is a UN*X-like operating system for - the i386, IA-64, PC-98, Alpha/AXP, and UltraSPARC platforms + Briefly, FreeBSD is a &unix; like operating system for + the &i386;, IA-64, PC-98, Alpha/AXP, and &ultrasparc; platforms based on U.C. Berkeley's 4.4BSD-Lite release, with some 4.4BSD-Lite2 enhancements. It is also based indirectly on William Jolitz's port of U.C. Berkeley's Net/2 to - the i386, known as 386BSD, though very + 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 @@ -211,7 +233,7 @@ If you are migrating to FreeBSD 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 Mac OS, expect to + 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 @@ -699,7 +721,7 @@ Is the documentation available in other formats, such as plain - text (ASCII), or PostScript? + text (ASCII), or &postscript;? @@ -840,7 +862,7 @@ ps - PostScript + &postscript; @@ -927,7 +949,7 @@ - So the PostScript version of the Handbook, + So the &postscript; version of the Handbook, compressed using BZip2 will be stored in a file called book.ps.bz2 in the handbook/ directory. @@ -1332,13 +1354,13 @@ File: +DESC (ignored) - Can Windows 95/98 co-exist with FreeBSD? + Can &windows; 95/98 co-exist with FreeBSD? - Install Windows 95/98 first, after that FreeBSD. + Install &windows; 95/98 first, after that FreeBSD. FreeBSD's boot manager will then manage to boot Win95/98 and - FreeBSD. If you install Windows 95/98 second, it will boorishly + FreeBSD. If you install &windows; 95/98 second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next section. @@ -1346,7 +1368,7 @@ File: +DESC (ignored) - Windows 95/98 killed my boot manager! + &windows; 95/98 killed my boot manager! How do I get it back? @@ -1668,7 +1690,7 @@ sectors/track: 63 - If you are using Windows95 or Win98 did you run + If you are using &windows; 95 or 98 did you run fdimage or rawrite in pure DOS mode? These operating systems can interfere with programs that @@ -1678,7 +1700,7 @@ sectors/track: 63 - There have also been reports of Netscape causing problems + There have also been reports of &netscape; causing problems when downloading the boot floppy, so it is probably best to use a different FTP client if you can. @@ -1695,7 +1717,7 @@ sectors/track: 63 drive. Many PCs now ship with the CDROM as the slave device on the secondary IDE controller, with no master device on that controller. This is illegal according to the ATAPI specification, - but Windows plays fast and loose with the specification, and the + but &windows; plays fast and loose with the specification, and the BIOS ignores it when booting. This is why the BIOS was able to see the CDROM to boot from it, but why FreeBSD cannot see it to complete the install. @@ -1775,7 +1797,7 @@ sectors/track: 63 If it is turned on (it is often supplied this way to get around certain limitations in - MSDOS) and the disk capacity is more than 1GB, use M + &ms-dos;) and the disk capacity is more than 1GB, use M cylinders, 63 sectors per track (not 64), and 255 heads, where 'M' is the disk capacity in MB divided by 7.844238 (!). So our example 2GB drive would @@ -1938,7 +1960,7 @@ sectors/track: 63 The default password format on FreeBSD is to use MD5-based passwords. These are - believed to be more secure than the traditional Unix + believed to be more secure than the traditional &unix; password format, which used a scheme based on the DES algorithm. DES passwords are still available if you need to share your password file @@ -1967,7 +1989,7 @@ sectors/track: 63 - If you have a IDE Zip or Jaz drive installed, remove it + If you have a IDE &iomegazip; or &jaz; drive installed, remove it and try again. The boot floppy can get confused by the drives. After the system is installed you can reconnect the drive. Hopefully this will be fixed in a later release. @@ -2244,9 +2266,9 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2Yes. FreeBSD currently runs on the Intel x86 and DEC (now Compaq) Alpha architectures. As of FreeBSD 5.0, the - IA-64, AMD-64 and SPARC-64 architectures are also supported. + IA-64, AMD-64 and &sparc64; architectures are also supported. Upcoming platforms are - MIPS and PowerPC; join the &a.ppc; or the + &mips; and &powerpc;, join the &a.ppc; or the &a.mips; respectively for more information about ongoing work on these platforms. For general discussion on new architectures, join the &a.platforms;. @@ -2379,11 +2401,11 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2 - Does FreeBSD support ZIP drives? + Does FreeBSD support &iomegazip; drives? - FreeBSD supports SCSI and ATAPI (IDE) ZIP drives out + FreeBSD supports SCSI and ATAPI (IDE) &iomegazip; drives out of the box, of course. 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 @@ -2416,7 +2438,7 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2 - Does FreeBSD support JAZ, EZ and other removable drives? + Does FreeBSD support &jaz;, EZ and other removable drives? @@ -2755,14 +2777,14 @@ usbd_flags="" In order to use the USB mouse in the X session, edit - XF86Config. If you are using XFree86 + XF86Config. If you are using &xfree86; 3.3.2 or later, be sure to have the following lines in the Pointer section: Device "/dev/sysmouse" Protocol "Auto" - If you are using earlier versions of XFree86, be sure to + If you are using earlier versions of &xfree86;, be sure to have the following lines in the Pointer section: @@ -2854,17 +2876,17 @@ Protocol "SysMouse" - FreeBSD supports the SoundBlaster, SoundBlaster Pro, - SoundBlaster 16, Pro Audio Spectrum 16, AdLib and Gravis + FreeBSD supports the &soundblaster;, &soundblaster; Pro, + &soundblaster; 16, Pro Audio Spectrum 16, AdLib and Gravis UltraSound sound cards. There is also limited support for MPU-401 and compatible MIDI cards. Cards conforming to the - Microsoft Sound System specification are also supported through + µsoft; Sound System specification are also supported through the pcm driver. This is only for sound! This driver does not support CDROMs, SCSI or joysticks on these cards, except for the - SoundBlaster. The SoundBlaster SCSI interface and some + &soundblaster;. The &soundblaster; SCSI interface and some non-SCSI CDROMs are supported, but you cannot boot off this device. @@ -3047,7 +3069,7 @@ Protocol "SysMouse" - Why does my 3Com PCI network card not work with my Micron + Why does my &tm.3com; PCI network card not work with my Micron computer? @@ -3241,7 +3263,7 @@ ARRE (Auto Read Reallocation Enbld): 1 FreeBSD 2.1 only supports Firmware revisions 2.21 onward. If you have a Firmware revision older than this your card will not be recognized as a Buslogic card. It may be recognized as - an Adaptec 1540, however. The early Buslogic firmware contains + an &adaptec; 1540, however. The early Buslogic firmware contains an AHA1540 emulation mode. This is not a good thing for an EISA card, however. @@ -3327,7 +3349,7 @@ quit - Why did my 3COM 3C509 card stop working for no + Why did my &tm.3com; 3C509 card stop working for no apparent reason? @@ -3466,7 +3488,7 @@ quit 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 + &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 @@ -3549,8 +3571,8 @@ quit Even after applying these workarounds, you may still find that the X Window System does not work properly. If this is the - case, make sure that the XFree86 version you are using is at - least XFree86 3.3.3 or higher. This version and upwards has + case, make sure that the &xfree86; version you are using is at + least &xfree86; 3.3.3 or higher. This version and upwards has built-in support for the Mach64 cards and even a dedicated X server for those cards. @@ -4382,10 +4404,10 @@ kern.timecounter.hardware: TSC -> i8254 - The Linux version of The &linux; version of StarOffice works flawlessly on FreeBSD. The easiest way to - install the Linux version of StarOffice is through the + install the &linux; version of StarOffice is through the FreeBSD Ports collection. Future versions of the open-source - Where can I get Motif for FreeBSD? + Where can I get &motif; for FreeBSD? - The Open Group has released the source code to Motif 2.1.30. + The Open Group has released the source code to &motif; 2.1.30. You can install the open-motif package, or compile it from ports. Refer to the ports section of the Handbook for more information on how to do this. - The Open Motif distribution only allows redistribution + The Open &motif; distribution only allows redistribution if it is running on an open source operating system. - In addition, there are commercial distributions of the Motif + In addition, there are commercial distributions of the &motif; 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 - (either i386 or Alpha). + least expensive ELF &motif; 2.1.20 distribution for FreeBSD + (either &i386; or Alpha). There are two distributions, the development edition and the runtime edition (for @@ -4427,7 +4449,7 @@ kern.timecounter.hardware: TSC -> i8254 - OSF/Motif manager, xmbind, panner, wsm. + OSF/&motif; manager, xmbind, panner, wsm. @@ -4446,7 +4468,7 @@ kern.timecounter.hardware: TSC -> i8254 Be sure to specify that you want the FreeBSD version of - Motif when ordering (do not forget to mention the architecture + &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 download. @@ -4479,13 +4501,13 @@ kern.timecounter.hardware: TSC -> i8254 Contact Metro Link - for an either ELF or a.out Motif 2.1 distribution for + for an either ELF or a.out &motif; 2.1 distribution for FreeBSD. This distribution includes: - OSF/Motif manager, xmbind, panner, wsm. + OSF/&motif; manager, xmbind, panner, wsm. @@ -4510,17 +4532,17 @@ kern.timecounter.hardware: TSC -> i8254 Be sure to specify that you want the FreeBSD version - of Motif when ordering! Versions for Linux are also sold by + of &motif; when ordering! Versions for &linux; are also sold by Metro Link. This is available on either a CDROM or for FTP download. Contact Xi Graphics for an - a.out Motif 2.0 distribution for FreeBSD. + a.out &motif; 2.0 distribution for FreeBSD. This distribution includes: - OSF/Motif manager, xmbind, panner, wsm. + OSF/&motif; manager, xmbind, panner, wsm. @@ -4543,7 +4565,7 @@ kern.timecounter.hardware: TSC -> i8254 Be sure to specify that you want the FreeBSD version - of Motif when ordering! Versions for BSDI and Linux are also + of &motif; when ordering! Versions for BSDI and &linux; are also sold by Xi Graphics. This is currently a 4 diskette set... in the future this will change to a unified CD distribution like their CDE. @@ -4586,7 +4608,7 @@ kern.timecounter.hardware: TSC -> i8254 Not to mention the Metro Link offering is available at the very reasonable price of $39. - Metro Link also sells both ELF and a.out Motif for + Metro Link also sells both ELF and a.out &motif; for FreeBSD (see above). @@ -4618,14 +4640,14 @@ kern.timecounter.hardware: TSC -> i8254 The Xi Graphics offering is a high performance X Server that offers easy configuration, support for multiple concurrent video boards and is distributed in binary form only, in a - unified diskette distribution for FreeBSD and Linux. Xi + unified diskette distribution for FreeBSD and &linux;. Xi Graphics also offers a high performance X Server tailored for laptop support. There is a free compatibility demo of version 5.0 available. - Xi Graphics also sells Motif and CDE for FreeBSD (see + Xi Graphics also sells &motif; and CDE for FreeBSD (see above). @@ -4674,12 +4696,12 @@ kern.timecounter.hardware: TSC -> i8254 - Can I run Oracle on FreeBSD? + Can I run &oracle; on FreeBSD? Yes. The following pages tell you exactly how to set up - Linux-Oracle on FreeBSD: + &linux;-&oracle; on FreeBSD: @@ -4816,7 +4838,7 @@ kern.timecounter.hardware: TSC -> i8254 - What version of Microsoft FrontPage should I get? + What version of µsoft; FrontPage should I get? @@ -4828,7 +4850,7 @@ kern.timecounter.hardware: TSC -> i8254 - Does FreeBSD support Java? + Does FreeBSD support &java;? @@ -4913,7 +4935,7 @@ kern.timecounter.hardware: TSC -> i8254 - a.out applications like Netscape Navigator require + a.out applications like &netscape.navigator; require a.out libraries. A version of FreeBSD built with ELF libraries does not install them by default. You will get complaints about not having @@ -4999,11 +5021,11 @@ kern.timecounter.hardware: TSC -> i8254 - Because POSIX says that there shall be such a shell. + Because &posix; says that there shall be such a shell. The more complicated answer: many people need to write shell scripts which will be portable across many systems. That is why - POSIX specifies the shell and utility commands in great detail. + &posix; specifies the shell and utility commands in great detail. Most scripts are written in Bourne shell, and because several important programming interfaces (&man.make.1;, &man.system.3;, &man.popen.3;, and analogues in higher-level scripting @@ -5027,13 +5049,13 @@ kern.timecounter.hardware: TSC -> i8254 - Why do Netscape and Opera take so long to + Why do &netscape; and Opera take so long to start? The usual answer is that DNS on your system is - misconfigured. Both Netscape and Opera perform DNS checks + misconfigured. Both &netscape; and Opera perform DNS checks when starting up. The browser will not appear on your desktop until the program either gets a response or determines that the system has no network @@ -5653,7 +5675,7 @@ use "disklabel -r" to install initial label - Linux + &linux; FreeBSD supports ext2fs @@ -5663,7 +5685,7 @@ use "disklabel -r" to install initial label - NT + &windowsnt; FreeBSD includes a read-only NTFS driver. For @@ -5717,12 +5739,12 @@ use "disklabel -r" to install initial label - How can I use the NT loader to boot FreeBSD? + How can I use the &windowsnt; loader to boot FreeBSD? The general idea is that you copy the first sector of your - native root FreeBSD partition into a file in the DOS/NT + native root FreeBSD 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 @@ -5737,7 +5759,7 @@ multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.BSD="FreeBSD" C:\="DOS" - If FreeBSD is installed on the same disk as the NT boot + If FreeBSD is installed on the same disk as the &windowsnt; boot partition simply copy /boot/boot1 to C:\BOOTSECT.BSD. However, if FreeBSD is installed on a different disk /boot/boot1 @@ -5771,15 +5793,15 @@ C:\="DOS" - How do I boot FreeBSD and Linux from LILO? + How do I boot FreeBSD and &linux; from LILO? - If you have FreeBSD and Linux on the same disk, just follow - LILO's installation instructions for booting a non-Linux + If you have FreeBSD and &linux; on the same disk, just follow + LILO's installation instructions for booting a non-&linux; operating system. Very briefly, these are: - Boot Linux, and add the following lines to + Boot &linux;, and add the following lines to /etc/lilo.conf: other=/dev/hda2 @@ -5787,7 +5809,7 @@ C:\="DOS" label=FreeBSD (the above assumes that your FreeBSD slice is known to - Linux as /dev/hda2; tailor to + &linux; as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. @@ -5814,24 +5836,24 @@ C:\="DOS" The - Linux+FreeBSD mini-HOWTO is a good reference for - FreeBSD and Linux interoperability issues. + &linux;+FreeBSD mini-HOWTO is a good reference for + FreeBSD and &linux; interoperability issues. - How do I boot FreeBSD and Linux using BootEasy? + How do I boot FreeBSD and &linux; using BootEasy? - Install LILO at the start of your Linux boot partition + Install LILO at the start of your &linux; boot partition instead of in the Master Boot Record. You can then boot LILO from BootEasy. - If you are running Windows 95 and Linux this is recommended - anyway, to make it simpler to get Linux booting again if you - should need to reinstall Windows 95 (which is a Jealous + If you are running &windows; 95 and &linux; this is recommended + anyway, to make it simpler to get &linux; booting again if you + should need to reinstall &windows; 95 (which is a Jealous Operating System, and will bear no other Operating Systems in the Master Boot Record). @@ -5858,7 +5880,7 @@ C:\="DOS" - Whether it is a removable drive like a ZIP or an EZ drive + Whether it is a removable drive like a &iomegazip; or an EZ drive (or even a floppy, if you want to use it that way), or a new hard disk, once it is installed and recognized by the system, and you have your cartridge/floppy/whatever slotted in, things @@ -6101,7 +6123,7 @@ C:\="DOS" Enabling vfs.usermount, however, has negative security implications. A better way to - access MSDOS formatted media is to use the mtools package in the ports collection. @@ -6369,8 +6391,8 @@ C:\="DOS" Some printers require a host-based driver to do any kind of printing. These so-called WinPrinters are not natively supported by - FreeBSD. If your printer does not work in DOS or Windows - NT 4.0, it is probably a WinPrinter. Your only hope of + FreeBSD. If your printer does not work in DOS or &windowsnt; + 4.0, it is probably a WinPrinter. Your only hope of getting one of these to work is to check if the print/pnm2ppa port supports it. @@ -6560,7 +6582,7 @@ options SYSVMSG # enable for messaging - How do I reformat DOS text files to Unix ones? + How do I reformat DOS text files to &unix; ones? @@ -7062,7 +7084,7 @@ options SYSVMSG # enable for messaging The X Window System is the most widely available windowing system - capable of running on UNIX or UNIX-like systems, including + capable of running on &unix; or &unix; like systems, including &os;. X.org administers the X protocol standards. The current release of the specification @@ -7087,7 +7109,7 @@ options SYSVMSG # enable for messaging In the past, if you wanted to run X on &os;, you were basically restricted to running an X implementation called - XFree86™ which is maintained by + &xfree86; which is maintained by The XFree86 Project, Inc. This software was installed by default on &os; versions up until 4.10 and 5.2. Although X.org @@ -7099,13 +7121,13 @@ options SYSVMSG # enable for messaging However, early in 2004, the XFree86 Project split over issues including the pace of code changes, future directions, and a licensing change. X.org updated its - source tree to the last XFree86 release before the + source tree to the last &xfree86; release before the licensing change (XFree86 version 4.3.99.903), incorporated many changes that had previously been maintained separately, and has released that software as X11R6.7.0. A separate but related project, freedesktop.org (or fd.o for short), - is working on rearchitecting the original XFree86 code to + is working on rearchitecting the original &xfree86; code to reflect modern graphics card technology (with the goal of greatly increased performance) and modern software practices (with the goal of incresed maintainability, and thus faster @@ -7113,10 +7135,10 @@ options SYSVMSG # enable for messaging incorporate the freedesktop.org changes in its future releases. The current technology roadmap for &os; includes - replacing XFree86 with freedesktop.org as the default server sometime + replacing &xfree86; with freedesktop.org as the default server sometime later in 2004 under the assumption that the pace of its development will more closely match that of &os; itself. - The XFree86 ports + The &xfree86; ports (x11/XFree86-4 and subports) will remain in the ports collection and be supported as developer interest permits. @@ -7129,7 +7151,7 @@ options SYSVMSG # enable for messaging The following paragraphs refer to the existing - XFree86 implementation, but most should also be applicable + &xfree86; implementation, but most should also be applicable to the freedesktop.org implementation as well. While the default configuration filename for the freedesktop.org implementation is xorg.conf, it will search for @@ -7150,7 +7172,7 @@ options SYSVMSG # enable for messaging Then read and follow the documentation on the xf86config tool, which assists you in - configuring XFree86 for your particular graphics + configuring &xfree86; for your particular graphics card/mouse/etc. You may also wish to investigate the Xaccel server. @@ -7209,7 +7231,7 @@ Protocol "SysMouse" Device "/dev/sysmouse" ..... - The above example is for XFree86 3.3.2 or later. For + The above example is for &xfree86; 3.3.2 or later. For earlier versions, the Protocol should be MouseSystems. @@ -7282,7 +7304,7 @@ Device "/dev/sysmouse" <quote>Pointer</quote> Section for Wheeled - Mouse in XFree86 3.3.x series XF86Config with moused + Mouse in &xfree86; 3.3.x series XF86Config with moused Translation Section "Pointer" @@ -7294,7 +7316,7 @@ EndSection <quote>InputDevice</quote> Section for Wheeled - Mouse in XFree86 4.x series XF86Config with X Server + Mouse in &xfree86; 4.x series XF86Config with X Server Translation Section "InputDevice" @@ -7328,8 +7350,8 @@ EndSection /etc/XF86Config file. First, you need to choose the proper protocol for your mouse. Most wheeled mice use the - IntelliMouse protocol. However, - XFree86 does support other protocols, such as + &intellimouse; protocol. However, + &xfree86; does support other protocols, such as MouseManPlusPS/2 for the Logitech MouseMan+ mice. Once you have chosen the protocol you will use, you need to add a @@ -7342,7 +7364,7 @@ EndSection ZAxisMapping option. For example, if you are not using - &man.moused.8;, and you have an IntelliMouse + &man.moused.8;, and you have an &intellimouse; attached to the PS/2 mouse port you would use the following in /etc/XF86Config. @@ -7361,7 +7383,7 @@ EndSection <quote>InputDevice</quote> Section for Wheeled - Mouse in XFree86 4.x series XF86Config with X Server + Mouse in &xfree86; 4.x series XF86Config with X Server Translation Section "InputDevice" @@ -7464,7 +7486,7 @@ EndSection .xsession file. You can safely ignore any warnings imwheel displays about PID files. Those warnings only apply - to the Linux version of + to the &linux; version of imwheel. @@ -7749,19 +7771,19 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure - Before, I was able to run XFree86 as a regular user. Why does + Before, I was able to run &xfree86; as a regular user. Why does it now say that I must be root? All X servers need to be run as root in order to get direct access to - your video hardware. Older versions of XFree86 (<= + your video hardware. Older versions of &xfree86; (<= 3.3.6) installed all bundled servers to be automatically run as root (setuid to root). This is obviously a security hazard because X servers are large, complicated programs. - Newer versions of XFree86 do not install the servers + Newer versions of &xfree86; do not install the servers setuid to root for just this reason. @@ -7779,7 +7801,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure essentially the graphical counterpart of &man.getty.8; and &man.login.1;. For more information on xdm see - the XFree86 + the &xfree86; documentation, and the the FAQ entry on it. @@ -7878,12 +7900,12 @@ UserConfig> quit - An X app I am building depends on XFree86 3.3.X, but I - have XFree86 4.X installed. What should I do? + An X app I am building depends on &xfree86; 3.3.X, but I + have &xfree86; 4.X installed. What should I do? - To tell the port build to link to the XFree86 4.X libraries, + To tell the port build to link to the &xfree86; 4.X libraries, add the following to /etc/make.conf, (if you do not have this file, create it): @@ -7935,7 +7957,7 @@ UserConfig> quit FreeBSD 3.1 The first step is to find a bitmap version of your - splash screen. Release 3.1 only supports Windows bitmap + splash screen. Release 3.1 only supports &windows; bitmap splash screens. Once you have found your splash screen of choice copy it to /boot/splash.bmp. Next, you need to have a @@ -7995,7 +8017,7 @@ bitmap_name="/boot/splash.pcx" - Can I use the Windows + Can I use the &windows; keys on my keyboard in X? @@ -8003,20 +8025,17 @@ bitmap_name="/boot/splash.pcx" Yes. All you need to do is use &man.xmodmap.1; to define what function you wish them to perform. - Assuming all Windows keyboards + Assuming all &windows; keyboards are standard then the keycodes for the 3 keys are - 115 - Windows key, between + 115 - &windows; key, between the left-hand Ctrl and Alt keys - 116 - Windows key, to the + 116 - &windows; key, to the right of the AltGr key @@ -8026,8 +8045,7 @@ bitmap_name="/boot/splash.pcx" - To have the left Windows key print a comma, + To have the left &windows; key print a comma, try this. &prompt.root; xmodmap -e "keycode 115 = comma" @@ -8035,7 +8053,7 @@ bitmap_name="/boot/splash.pcx" You will probably have to re-start your window manager to see the result. - To have the Windows + To have the &windows; key-mappings enabled automatically every time you start X either put the xmodmap commands in your ~/.xinitrc file or, preferably, create a file @@ -8085,25 +8103,25 @@ Key F15 A A Menu Workplace Nop How can I get 3D hardware acceleration for - OpenGL? + &opengl;? The availability of 3D acceleration depends on the - version of XFree86 you are using and the type of video chip + version of &xfree86; you are using and the type of video chip you have. If you have an NVIDIA chip, you can use the binary drivers provided for FreeBSD 4.7 on the Drivers section of their website. For other cards - with XFree86-4, including the Matrox G200/G400, ATI Rage + with &xfree86;-4, including the Matrox G200/G400, ATI Rage 128/Radeon, and 3dfx Voodoo 3, 4, 5, and Banshee, information on hardware acceleration is available on the XFree86-4 Direct Rendering on FreeBSD page. Users of - XFree86 version 3.3 can use the Utah-GLX port found in + &xfree86; version 3.3 can use the Utah-GLX port found in graphics/utah-glx to - get limited accelerated OpenGL on the Matrox Gx00, ATI + get limited accelerated &opengl; on the Matrox Gx00, ATI Rage Pro, SiS 6326, i810, Savage, and older NVIDIA chips. @@ -8147,16 +8165,16 @@ Key F15 A A Menu Workplace Nop - Can I connect my Windows box to the Internet via + Can I connect my &windows; box to the Internet via FreeBSD? Typically, people who ask this question have two PC's at home, one with FreeBSD and one with some version of - Windows; the idea is to use the FreeBSD box to connect to + &windows; the idea is to use the FreeBSD 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 FreeBSD box. This is really just a special case of the previous question and works perfectly well. @@ -8167,7 +8185,7 @@ Key F15 A A Menu Workplace Nop gateway_enable to YES in /etc/rc.conf, and configure your - Windows machine correctly, this should work fine. For more + &windows; machine correctly, this should work fine. For more information, please see the &man.ppp.8; manual page or the Handbook entry on user PPP. @@ -8250,7 +8268,7 @@ Key F15 A A Menu Workplace Nop then you should pick up a book describing network administration on another BSD-related operating system; with few significant exceptions, administering networking - on FreeBSD is basically the same as on SunOS 4.0 or + on FreeBSD is basically the same as on &sunos; 4.0 or Ultrix. @@ -8310,11 +8328,11 @@ Key F15 A A Menu Workplace Nop - Why can I not NFS-mount from a Linux box? + Why can I not NFS-mount from a &linux; box? - Some versions of the Linux NFS code only accept mount + Some versions of the &linux; NFS code only accept mount requests from a privileged port; try &prompt.root; mount -o -P linuxbox:/blah /mnt @@ -8327,7 +8345,7 @@ Key F15 A A Menu Workplace Nop - Sun workstations running SunOS 4.X only accept mount + &sun; workstations running &sunos; 4.X only accept mount requests from a privileged port; try &prompt.root; mount -o -P sunbox:/blah /mnt @@ -8681,8 +8699,8 @@ Key F15 A A Menu Workplace Nop - How do I mount a disk from a Windows machine that is on my - network, like smbmount in Linux? + How do I mount a disk from a &windows; machine that is on my + network, like smbmount in &linux;? @@ -8784,10 +8802,10 @@ Key F15 A A Menu Workplace Nop Errors like these are caused by installing the net/cvsup port on a machine which does not have the - XFree86 suite. If you want to + &xfree86; suite. If you want to use the GUI included with CVSup you will need to install - XFree86 now. Alternatively if + &xfree86; now. Alternatively if you just wish to use CVSup from a command line you should delete the package previously installed. Then install the - Unix implements two core sandboxes. One is at the + &unix; implements two core sandboxes. One is at the process level, and one is at the userid level. - Every Unix process is completely firewalled off from every - other Unix process. One process cannot modify the address - space of another. This is unlike Windows where a process + Every &unix; process is completely firewalled off from every + other &unix; process. One process cannot modify the address + space of another. This is unlike &windows; where a process can easily overwrite the address space of any other, leading to a crash. - A Unix process is owned by a particular userid. If + A &unix; process is owned by a particular userid. If the userid is not the root user, it serves to firewall the process off from processes owned by other users. The userid is also used to firewall off @@ -9282,7 +9300,7 @@ add 0 0 HISADDR There is a setting on most modems for determining how tolerant it should be to temporary losses of carrier. On a - USR Sportster for example, this is measured by the S10 + USR &sportster; for example, this is measured by the S10 register in tenths of a second. To make your modem more forgiving, you could add the following send-expect sequence to your dial string: @@ -10136,7 +10154,7 @@ ATDT1234567 - Why do MacOS and Windows 98 connections freeze when + Why do &macos; and &windows; 98 connections freeze when running PPPoE on the gateway? @@ -10147,7 +10165,7 @@ ATDT1234567 solution: This is due to what is called a Black Hole - router. MacOS and Windows 98 (and maybe other Microsoft OSs) + router. &macos; and &windows; 98 (and maybe other Microsoft OSs) send TCP packets with a requested segment size too big to fit into a PPPoE frame (MTU is 1500 by default for Ethernet) and have the do not @@ -10172,30 +10190,30 @@ ATDT1234567 be unable to deal with packets larger than this. This registry key has been changed to Tcpip\Parameters\Interfaces\ID for - adapter\MTU in Windows 2000 and + adapter\MTU in &windows; 2000 and becomes a DWORD. Refer to the Microsoft Knowledge Base documents Q158474 - Windows TCPIP Registry Entries and Q120642 - - TCPIP & NBT Configuration Parameters for Windows - NT for more information on changing Windows MTU to + - TCPIP & NBT Configuration Parameters for &windowsnt; + for more information on changing &windows; MTU to work with a NAT router. - Another regedit possibility under Windows 2000 is to + Another regedit possibility under &windows; 2000 is to set the Tcpip\Parameters\Interfaces\ID for adapter\EnablePMTUBHDetect DWORD to 1 as mentioned in the Microsoft document 120642 mentioned above. - Unfortunately, MacOS does not provide an interface for + Unfortunately, &macos; does not provide an interface for changing TCP/IP settings. However, there is commercial software available, such as OTAdvancedTuner (OT for OpenTransport, the - MacOS TCP/IP stack) by Sustainable Softworks, - that will allow users to customize TCP/IP settings. MacOS NAT + that will allow users to customize TCP/IP settings. &macos; NAT users should select ip_interface_MTU from the drop-down menu, enter 1450 instead of 1500 in the box, click the box next to @@ -10457,7 +10475,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrSee the section on sending AT commands below for information on how to make these - settings without resorting to an MS-DOS terminal program. + settings without resorting to an &ms-dos; terminal program. Next, make an entry in /etc/ttys (see &man.ttys.5;) for the modem. This file lists all the @@ -10843,7 +10861,7 @@ raisechar=^^ - If you are talking to another Unix system, you can + If you are talking to another &unix; system, you can send and receive files with ~p (put) and ~t (take). These commands run &man.cat.1; and &man.echo.1; on the remote system to @@ -10891,15 +10909,15 @@ raisechar=^^ - FreeBSD uses far more swap space than Linux. Why? + FreeBSD uses far more swap space than &linux;. Why? - FreeBSD only appears to use more swap than Linux. In + 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 + and &linux; in this regard is that FreeBSD 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 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. @@ -11088,12 +11106,12 @@ raisechar=^^ While FreeBSD does not provide open access to any of their - servers, others do provide open access Unix systems. The + servers, others do provide open access &unix; systems. The charge varies and limited services may be available. Arbornet, Inc, also known as M-Net, has been providing open - access to Unix systems since 1983. Starting on an Altos + access to &unix; systems since 1983. Starting on an Altos running System III, the site switched to BSD/OS in 1991. In June of 2000, the site switched again to FreeBSD. M-Net can be accessed via telnet and SSH and provides basic access to the @@ -11104,8 +11122,8 @@ raisechar=^^ Grex provides a site very similar to M-Net including the same bulletin board - and interactive chat software. However, the machine is a Sun - 4M and is running SunOS + and interactive chat software. However, the machine is a &sun; + 4M and is running &sunos;. @@ -11202,12 +11220,12 @@ raisechar=^^ to tell you that BSD's translation is something between, Formula-1 Racing Team, Penguins are tasty snacks, and We have a better sense of - humor than Linux. :-) + humor than &linux;. :-) Seriously, BSD is an acronym for Berkeley Software Distribution, which is the name the Berkeley CSRG (Computer Systems Research - Group) chose for their Unix distribution way back when. + Group) chose for their &unix; distribution way back when. @@ -11345,14 +11363,14 @@ raisechar=^^ Q. Has anyone done any temperature testing while - running FreeBSD? I know Linux runs cooler than DOS, but have + running FreeBSD? I know &linux; runs cooler than DOS, but have never seen a mention of FreeBSD. 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 + FreeBSD 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 @@ -11361,7 +11379,7 @@ raisechar=^^ 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 FreeBSD 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 @@ -11398,7 +11416,7 @@ raisechar=^^ satanic voice of Bill Gates coming from the built-in speaker, take off running and do not ever look back! Freed from the counterbalancing influence of the BSD daemons, the twin demons - of DOS and Windows are often able to re-assert total control + of DOS and &windows; are often able to re-assert total control over your machine to the eternal damnation of your soul. Now that you know, given a choice you would probably prefer to get used to the scratchy noises, no?