diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 9d1ab876bc..b4abacd3e4 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -13,7 +13,7 @@ - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.50 2000/04/10 13:32:27 brian Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.51 2000/04/30 22:04:04 nik Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries @@ -96,7 +96,7 @@ use and provides the widest possible benefit. This is, we believe, one of the most fundamental goals of Free Software and one that we enthusiastically support. - + That code in our source tree which falls under the GNU General Public License (GPL) or GNU Library General Public License (LGPL) comes with slightly more strings attached, @@ -237,22 +237,22 @@ testers. - + No claims are made that any snapshot can be considered ``production quality'' for any purpose. For stability and tested mettle, you will have to stick to full releases. - + Snapshot releases are directly available from - ftp://current.FreeBSD.org/pub/FreeBSD/ - for 5.0-CURRENT and + ftp://current.FreeBSD.org/pub/FreeBSD/ + for 5.0-CURRENT and - releng4.FreeBSD.org for 4-STABLE snapshots. - 3-STABLE snapshots can be found at + releng4.FreeBSD.org for 4-STABLE snapshots. + 3-STABLE snapshots can be found at - releng3.FreeBSD.org. - Snapshots are generated, on the average, once a day for + releng3.FreeBSD.org. + Snapshots are generated, on the average, once a day for all actively developed branches. @@ -275,7 +275,7 @@ which essentially has been one unbroken line leading towards 5.0-RELEASE (and beyond) since 2.0 was released. If a little ASCII art would help, this is how it looks: - + 2.0 | | @@ -331,9 +331,9 @@ things about FreeBSD, although it can be a little frustrating when waiting for all the latest goodies to become available... - + Releases are made about every 4 months on average. - + For people needing (or wanting) a little more excitement, there are SNAPs released more frequently, particularly during the month or so leading up to a release. @@ -409,7 +409,7 @@ found in the 4.0-RELEASE directory. - + 3.X Snapshot @@ -417,13 +417,13 @@ (post 3.0-RELEASE) as it continues on its way towards 3.5-RELEASE. - + 4.X snapshots are made once a day as well. - + 5.0 Snapshot @@ -433,7 +433,7 @@ developers. - + FreeBSD is also available via CDROM, from the following place(s): @@ -449,9 +449,9 @@ email: WC Orders address WWW: WC Home page - + In Australia, you may find it at: - +
Advanced Multimedia Distributors Factory 1/1 Ovata Drive @@ -577,7 +577,7 @@ actual questions about FreeBSD, there is the questions mailing list: <freebsd-questions@FreeBSD.org>. - + A FreeBSD ``handbook'' is available, and can be found as: the FreeBSD Handbook. Note that this is a work in progress, and @@ -657,7 +657,7 @@ McKusick, Marshall Kirk, Keith Bostic, Michael J Karels, and John Quarterman. - + The Design and Implementation of the 4.4BSD Operating System. Reading, Mass. : Addison-Wesley, 1996. @@ -666,7 +666,7 @@ 0-201-54979-4 A good book on system administration is: - + Evi Nemeth, Garth Snyder, Scott Seebass & Trent R. Hein, ``Unix System Administration Handbook'', Prentice-Hall, @@ -725,7 +725,7 @@ URL="http://www.FreeBSD.org/FAQ/FAQ.ps">http://www.FreeBSD.org/FAQ/FAQ.ps - + As ASCII text (about 220KB): @@ -733,7 +733,7 @@ http://www.FreeBSD.org/FAQ/FAQ.ascii - + As ISO 8859-1 text (about 220KB): @@ -821,7 +821,7 @@ $ col -b < inputfile > outputfile your cvsup file: -www release=current hostname=/home base=/usr/local/etc/cvsup +www release=current hostname=/home base=/usr/local/etc/cvsup prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix @@ -863,7 +863,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix The following newsgroups contain pertinent discussion for FreeBSD users: - + @@ -885,7 +885,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix Web resources: - + @@ -915,7 +915,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix - + The FreeBSD handbook also has a fairly complete bibliography section which is worth reading if you're looking for actual @@ -946,7 +946,7 @@ copied onto floppies by tools like fdimage or If you need to download the distributions yourself (for a DOS filesystem install, for instance), below are some recommendations for distributions to grab: - + @@ -972,56 +972,56 @@ for distributions to grab: - + 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. - + Help! The boot floppy image will not fit on a single floppy! -A 3.5 inch (1.44MB) floppy can accomodate 1474560 bytes of data. +A 3.5 inch (1.44MB) floppy can accomodate 1474560 bytes of data. The boot image is exactly 1474560 bytes in size. - + Common mistakes when preparing the boot floppy are: Not downloading the floppy image in binary mode when -using FTP. +using FTP. Some FTP clients default their transfer mode to ascii -and attempt to change any end-of-line characters received to match +and attempt to change any end-of-line characters received to match the conventions used by the client's system. This will almost invariably corrupt the boot image. Check the -size of the downloaded boot image: if it is not exactly +size of the downloaded boot image: if it is not exactly that on the server, then the download process is suspect. -To workaround: type binary at the FTP command prompt -after getting connected to the server and before starting the +To workaround: type binary at the FTP command prompt +after getting connected to the server and before starting the download of the image. -Using the DOS copy command (or equivalent GUI tool) to +Using the DOS copy command (or equivalent GUI tool) to transfer the boot image to floppy. -Programs like copy will not work as the boot +Programs like copy will not work as the boot image has been created to be booted into directly. The image has the complete content of the floppy, track for track, and is not meant to be placed on the floppy as a regular file. -You have to transfer it to the floppy ``raw'', using the -low-level tools (e.g. fdimage or rawrite) +You have to transfer it to the floppy ``raw'', using the +low-level tools (e.g. fdimage or rawrite) described in the installation guide to FreeBSD. - + @@ -1029,7 +1029,7 @@ described in the installation guide to Fre Installation instructions can be found in the Handbook entry on installing FreeBSD. - + @@ -1038,9 +1038,9 @@ described in the installation guide to Fre You'll need a 386 or better PC, with 5 MB or more of RAM and at least 60 MB of hard disk space. It can run with a low end MDA graphics card but to run X11R6, a VGA or better video card is needed. - + See also the section on - + @@ -1049,34 +1049,34 @@ graphics card but to run X11R6, a VGA or better video card is needed. FreeBSD 2.1.7 was the last version of FreeBSD that could be installed on a 4MB system. Newer versions of FreeBSD, like 2.2, need at least 5MB to install on a new system. - + All versions of FreeBSD, including 3.0, will RUN in 4MB of ram, they just can't run the installation program in 4MB. You can add extra memory for the install process, if you like, and then after the system is up and running, go back to 4MB. Or you could always just swap your disk into a system which has >4MB, install onto it and then swap it back. - + There are also situations in which FreeBSD 2.1.7 will not install in 4 MB. To be exact: it does not install with 640 kB base + 3 MB extended memory. If your motherboard can remap some of the ``lost'' memory out of the 640kB to 1MB region, then you may still be able to get FreeBSD 2.1.7 up. - + Try to go into your BIOS setup and look for a ``remap'' option. Enable it. You may also have to disable ROM shadowing. - + It may be easier to get 4 more MB just for the install. Build a custom kernel with only the options you need and then get the 4 MB out again. - + You may also install 2.0.5 and then upgrade your system to 2.1.7 with the ``upgrade'' option of the 2.1.7 installation program. - + After the installation, if you build a custom kernel, it will run in 4 MB. Someone has even succeeded in booting with 2 MB (the system was almost unusable though :-)) - + @@ -1088,16 +1088,16 @@ You have to cut a whole new release, which will include your install floppy. There's some code in /usr/src/release/floppies/Makefile that's supposed to let you *just* make those floppies, but it's not really gelled yet. - + To make a custom release, follow the instructions here. - + Can I have more than one operating system on my PC? Have a look at The multi-OS page. - + @@ -1108,7 +1108,7 @@ manager will then manage to boot Win95 and FreeBSD. If you install Windows 95 second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next section. - + @@ -1117,7 +1117,7 @@ the next section. You can reinstall the boot manager FreeBSD comes with in one of two ways: - + @@ -1150,7 +1150,7 @@ installation menu and reboot off the hard disk as normal. - + @@ -1162,9 +1162,9 @@ it must unfortunately be said that if you've got an IDE or ESDI drive with lots of bad blocks, then FreeBSD is probably not for you! That said, it does work on thousands of IDE based systems, so you'd do well to try it first before simply giving up. - + If you have a SCSI drive with bad blocks, see this answer. - + @@ -1173,7 +1173,7 @@ you'd do well to try it first before simply giving up. If you're seeing things like the machine grinding to a halt or spontaneously rebooting when you try to boot the install floppy, here are three questions to ask yourself:- - + @@ -1203,11 +1203,11 @@ shell in the GUI can cause this problem. - + There have also been reports of Netscape causing problems when downloading the boot floppy, so it's probably best to use a different FTP client if you can. - + @@ -1219,7 +1219,7 @@ blocksize is 20 (10240 bytes), and tapes created using this default size cannot be used to install 2.1.7R; with these tapes, you will get an error that complains about the record size being too big. - + @@ -1228,7 +1228,7 @@ too big. Get a laplink cable. Make sure both computer have a kernel with lpt driver support. - + $ dmesg | grep lp lpt0 at 0x378-0x37f irq 7 on isa @@ -1236,56 +1236,56 @@ with lpt driver support. lp0: TCP/IP capable interface - + Plug in the laplink cable into the parallel interface. - + Configure the network interface parameters for lp0 on both sites as root. For example, if you want connect the host max with moritz - + max <-----> moritz IP Address 10.0.0.1 10.0.0.2 - + on max start # ifconfig lp0 10.0.0.1 10.0.0.2 - + on moritz start - + # ifconfig lp0 10.0.0.2 10.0.0.1 - -Thats all! Please read also the manpages + +Thats all! Please read also the manpages lp(4) and lpt(4) . - + You should also add the hosts to /etc/hosts. - + - 127.0.0.1 localhost.my.domain localhost + 127.0.0.1 localhost.my.domain localhost 10.0.0.1 max.my.domain max 10.0.0.2 moritz.my.domain moritz - + To check if it works do: - + on max: - + $ ifconfig lp0 lp0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.0.0.1 --> 10.0.0.2 netmask 0xff000000 - + $ netstat -r Routing tables @@ -1294,7 +1294,7 @@ Internet: Destination Gateway Flags Refs Use Netif Expire moritz max UH 4 127592 lp0 - + $ ping -c 4 moritz PING moritz (10.0.0.2): 56 data bytes @@ -1307,7 +1307,7 @@ PING moritz (10.0.0.2): 56 data bytes 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms - + @@ -1316,7 +1316,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms Connect the two computers using a Laplink parallel cable to use this feature: - + +----------------------------------------+ |A-name A-End B-End Descr. Port/Bit | @@ -1340,9 +1340,9 @@ this feature: +----------------------------------------+ - + See also this note on the Mobile Computing page. - + heads and sectors/track on a disk - I'll refer to this as C/H/S for convenience. This is how the PC's BIOS works out which area on a disk to read/write from). - + This seems to cause a lot of confusion for some reason. First of all, the physical geometry of a SCSI drive is totally irrelevant, as FreeBSD works in term of disk blocks. In fact, there @@ -1364,14 +1364,14 @@ physical geometry is usually the geometry that they've worked out results in the least wasted space. For IDE disks, FreeBSD does work in terms of C/H/S, but all modern drives will convert this into block references internally as well. - + All that matters is the logical geometry - the answer that the BIOS gets when it asks "what is your geometry?" and then uses to access the disk. As FreeBSD uses the BIOS when booting, it's 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 geometry, otherwise you will have serious problems booting! - + For SCSI disks, the geometry to use depends on whether extended translation support is turned on in your controller (this is often referred to as "support for DOS disks >1GB" or something @@ -1379,28 +1379,28 @@ similar). If it's turned off, then use N cylinders, 64 heads and 32 sectors/track, where 'N' is the capacity of the disk in MB. For example, a 2GB disk should pretend to have 2048 cylinders, 64 heads and 32 sectors/track. - + If it is turned on (it's often supplied this way to get around certain limitations in MSDOS) 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 have 261 cylinders, 63 sectors per track and 255 heads. - + If you are not sure about this, or FreeBSD 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 correct geometry should then be detected (and you can always remove the DOS partition in the partition editor if you don't want to keep it, or leave it around for programming network cards and the like). - + Alternatively, there is a freely available utility distributed with FreeBSD called ``pfdisk.exe'' (located in the tools subdirectory on the FreeBSD CDROM or on the various FreeBSD ftp sites) which can be used to work out what geometry the other operating systems on the disk are using. You can then enter this geometry in the partition editor. - + @@ -1409,12 +1409,12 @@ geometry in the partition editor. 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). - + For a SCSI drive, this will normally imply that the root partition will be in the first 1024MB (or in the first 4096MB if extended translation is turned on - see previous question). For IDE, the corresponding figure is 504MB. - + @@ -1423,32 +1423,32 @@ corresponding figure is 504MB. FreeBSD recognizes the Ontrack Disk Manager and makes allowances for it. Other disk managers are not supported. - + If you just want to use the disk with FreeBSD you don't need a disk manager. Just configure the disk for as much space as the BIOS can deal with (usually 504 megabytes), and FreeBSD should figure out how much space you really have. If you're using an old disk with an MFM controller, you may need to explicitly tell FreeBSD how many cylinders to use. - + If you want to use the disk with FreeBSD and another operating system, you may be able to do without a disk manager: just make sure the the FreeBSD boot partition and the slice for the other operating system are in the first 1024 cylinders. If you're reasonably careful, a 20 megabyte boot partition should be plenty. - + When I boot FreeBSD I get ``Missing Operating System'' - + This is classically a case of FreeBSD 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 always get you going. - + @@ -1459,7 +1459,7 @@ question. Your BIOS geometry and FreeBSD 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. - + - + Also look at the section on >64M machines if you have that much memory, or if you're using a Compaq or other BIOS that lies about the available memory. - + @@ -1488,7 +1488,7 @@ includes several of the files mentioned here, and the ``sys'' (kernel) source kit, which includes sources for the kernel. There is nothing in the system which requires the presence of the sources to operate, however, except for the -kernel-configuration program +kernel-configuration program config . With the exception of the kernel sources, our build structure is set up so that you @@ -1498,17 +1498,17 @@ restriction, we recommend that you not mount this on /usr/src directly, but rather in some other location with appropriate symbolic links to duplicate the top-level structure of the source tree.) - + 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 actually select a subset of the sources, use the Custom menu item when you are in the Distributions menu of the system installation tool. The src/install.sh script will also install partial pieces of the source distribution, depending on the arguments you pass it. - + @@ -1521,12 +1521,12 @@ configuration tool. When at the FreeBSD boot prompt (boot:), use the "-c" flag and you will be dropped into a visual configuration screen which allows you to configure the kernel's settings for most common ISA cards. - + It's still recommended that you eventually build a new kernel containing just the drivers that you need, just to save a bit of RAM, but it's no longer a strict requirement for most systems. - + @@ -1540,26 +1540,26 @@ more CPU-intensive to crack with an automated password cracker than DES, and allows longer passwords as well. The only reason for not using the MD5-based crypt today would be to use the the same password entries on FreeBSD and non-FreeBSD systems. - + Since the DES encryption algorithm cannot legally be exported from the US, non-US users should not download this software (as part of the secrdist from US FTP sites. - + There is however a replacement libcrypt available, based on sources written in Australia by David Burren. This code is now available on some non-US FreeBSD mirror sites. Sources for the unencumbered libcrypt, and binaries of the programs which use it, can be obtained from the following FTP sites: - + South Africa ftp://ftp.internat.FreeBSD.org/pub/FreeBSD ftp://storm.sea.uct.ac.za/pub/FreeBSD - + - + @@ -1567,9 +1567,9 @@ can be obtained from the following FTP sites: ftp://ftp.iqm.unicamp.br/pub/FreeBSD - + - + @@ -1577,34 +1577,34 @@ can be obtained from the following FTP sites: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt - + - + The non-US securedist can be used as a direct replacement for the encumbered US securedist. This securedist package is installed the same way as the US package (see installation notes for details). If you are going to install DES encryption, you should do so as soon as possible, before installing other software. - + Non-US users should please not download any encryption software from the USA. This can get the maintainers of the sites from which the software is downloaded into severe legal difficulties. - + A non-US distribution of Kerberos is also being developed, and current versions can generally be obtained by anonymous FTP from braae.ru.ac.za. - + There is also a mailing list for the discussion of non-US encryption software. For more information, send an email message with a single line saying ``help'' in the body of your message to - + majordomo@braae.ru.ac.za. - + @@ -1615,24 +1615,24 @@ of your message to 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. - + I get a ``panic: cant mount root'' error when rebooting the system after installation. -This error comes from confusion between the boot block's and the -kernel's understanding of the disk devices. The error usually +This error comes from confusion between the boot 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 installed on the secondary IDE controller. The boot blocks think the system is installed on wd1 (the second BIOS disk) while the kernel assigns the first disk on the secondary controller device wd2. After -the device probing, the kernel tries to mount what the boot blocks +the device probing, the kernel tries to mount what the boot blocks think is the boot disk, wd1, while it is really wd2, and fails. - + To fix the problem, do one of the following: - + @@ -1660,14 +1660,14 @@ everytime you reboot or turn on your FreeBSD machine), put the line If using FreeBSD 3.2 or earlier, at the Boot: prompt, enter 1:wd(2,a)kernel and press Enter. If the system starts, then -run the command +run the command echo "1:wd(2,a)kernel" > /boot.config to make it the default boot string. -Move the FreeBSD disk onto the primary IDE controller, so the +Move the FreeBSD disk onto the primary IDE controller, so the hard disks are consecutive. @@ -1685,7 +1685,7 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2 Install the new kernel. -If you moved your disks and wish to restore the previous +If you moved your disks and wish to restore the previous configuration, replace the disks in the desired configuration and reboot. Your system should boot successfully. @@ -1693,18 +1693,18 @@ Your system should boot successfully. - + What are the limits for memory? For memory, the limit is 4 gigabytes. This configuration has -been tested, see wcarchive's -configuration for more details. If you plan to install this -much memory into a machine, you need to be careful. You'll probably -want to use ECC memory and to reduce capacitive loading use 9 chip +configuration for more details. If you plan to install this +much memory into a machine, you need to be careful. You'll probably +want to use ECC memory and to reduce capacitive loading use 9 chip memory modules vice 18 chip memory modules. @@ -1716,10 +1716,10 @@ memory modules vice 18 chip memory modules. (2G blocks), or 16TB for the default block size of 8K. In practice, there is a soft limit of 1 terabyte, but with modifications filesystems with 4 terabytes are possible (and exist). - -The maximum size of a single ffs file is approximately 1G blocks + +The maximum size of a single ffs file is approximately 1G blocks (4TB) if the block size is 4K. - + maxfilesize ---------------------------------- @@ -1733,7 +1733,7 @@ fs block size -STABLE -CURRENT works should-work 64K 2048+G 64T-1 2048+G 128T-1 - + When the fs block size is 4K, triple indirect blocks work and everything should be limited by the maximum fs block number that can be represented using triple indirect blocks (approx. 1K^3 + 1K^2 + @@ -1741,7 +1741,7 @@ be represented using triple indirect blocks (approx. 1K^3 + 1K^2 + numbers. The limit on fs block numbers should be 2G-1. There are some bugs for fs block numbers near 2G-1, but such block numbers are unreachable when the fs block size is 4K. - + For block sizes of 8K and larger, everything should be limited by the 2G-1 limit on fs block numbers, but is actually limited by the 1G-1 limit on fs block numbers, except under -STABLE triple indirect @@ -1750,7 +1750,7 @@ that can be represented using double indirect blocks (approx. (blocksize/4)^2 + (blocksize/4)), and under -CURRENT exceeding this limit may cause problems. Using the correct limit of 2G-1 blocks does cause problems. - + @@ -1760,12 +1760,12 @@ exceeding this limit may cause problems. Using the correct limit of file size is not closely related to the maximum disk size. The maximum disk size is 1TB. It is a feature that the file size can be larger than the disk size. - + The following example creates a file of size 8T-1 using a whole 32K of disk space (3 indirect blocks and 1 data block) on a small root partition. The dd command requires a dd that works with large files. - + ttyv0:bde@alphplex:/tmp/q> cat foo df . @@ -1785,9 +1785,9 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0a 64479 27734 31587 47% / ttyv0:bde@alphplex:/tmp/q> exit - + Bruce Evans, September 1998 - + @@ -1798,7 +1798,7 @@ stage, pressing any key when the | shows up before loader is started. More specifically, you have upgraded the source for your kernel, and installed a new kernel builtin from them without making world. This is not supported. Make world. - + @@ -1814,7 +1814,7 @@ Handbook for more information. Upgrading via source is never recommended for new users, and upgading from 3.X -> 4.X is even less so; make sure you have read the instructions carefully before attempting to upgrade via -source this! +source this! @@ -1833,24 +1833,24 @@ original "Western Digital" interface (MFM, RLL, ESDI, and of course IDE). A few ESDI controllers that use proprietary interfaces may not work: stick to WD1002/3/6/7 interfaces and clones. - + Which SCSI controllers are supported? -See the complete list in the +See the complete list in the Handbook. - + Which CD-ROM drives are supported by FreeBSD? Any SCSI drive connected to a supported controller is supported. - + The following proprietary CD-ROM interfaces are also supported: - + @@ -1876,13 +1876,13 @@ and clones. - + All non-SCSI cards are known to be extremely slow compared to SCSI drives, and some ATAPI CDROMs may not work. - + As of 2.2 the FreeBSD CDROM from Walnut Creek supports booting directly from the CD. - + @@ -1894,20 +1894,20 @@ your SCSI host adapter's BIOS supports it you can even boot from it. I don't know which host adapters let you boot from targets other than 0 or 1... look at your docs (and let me know if it works out for you). - + ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and later releases. - + FreeBSD has contained support for Parallel Port Zip Drives since version 3.0. If you are using a sufficiently up to date version, then -you should check that your kernel contains the scbus0, da0, ppbus0, and vp0 drivers (the GENERIC kernel -contains everything except vp0). With all these drivers present, the -Parallel Port drive should be available as /dev/da0s4. Disks can +you should check that your kernel contains the scbus0, da0, ppbus0, and vp0 drivers (the GENERIC kernel +contains everything except vp0). With all these drivers present, the +Parallel Port drive should be available as /dev/da0s4. Disks can be mounted using mount /dev/da0s4 /mnt OR (for dos disks) mount_msdos /dev/da0s4 /mnt as appropriate. - + Also check out this note on removable drives, and this note on 'formatting'. - + @@ -1917,14 +1917,14 @@ and this note on 'formatting'. Apart from the IDE version of the EZ drive, these are all SCSI devices, so the should all look like SCSI disks to FreeBSD, and the IDE EZ should look like an IDE drive. - + I'm not sure how well FreeBSD supports changing the media out while running. You will of course need to dismount the drive before swapping media, and make sure that any external units are powered on when you boot the system so FreeBSD can see them. - + See this note on 'formatting'. - + @@ -1932,13 +1932,13 @@ powered on when you boot the system so FreeBSD can see them. There is a list of these in the Miscellaneous devices section of the handbook. - + Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible. - + Check the sio man page to get more information on configuring such cards. - + @@ -2028,17 +2028,17 @@ id="busmouse"> FreeBSD supports the bus mouse and the InPort bus mouse from such manufactures as Microsoft, Logitech and ATI. The bus device driver is compiled in the GENERIC kernel by default in FreeBSD versions 2.X, but -not included in version 3.0 or later. If you are building -a custom kernel with the bus mouse driver, make sure to add the +not included in version 3.0 or later. If you are building +a custom kernel with the bus mouse driver, make sure to add the following line to the kernel config file - + In FreeBSD 3.0 or before, add: device mse0 at isa? port 0x23c tty irq5 vector mseintr - + In FreeBSD 3.1 or later, the line should be: @@ -2050,7 +2050,7 @@ following line to the kernel config file It may allow you to set the port address and the IRQ number other than shown above. Refer to the manual of your mouse and the &man.mse.4; man page for more information. - + How do I use my PS/2 (``mouse port'' or ``keyboard'') mouse? If you're running a post-2.2.5 version of FreeBSD, the necessary -driver, psm, is included and enabled in the kernel. The kernel +driver, psm, is included and enabled in the kernel. The kernel should detect your PS/2 mouse at boot time. - -If you're running a previous but relatively recent version of + +If you're running a previous but relatively recent version of FreeBSD (2.1.x or better) then you can simply enable it in the kernel configuration menu at installation time, otherwise later with at the boot: prompt. It is disabled by default, so you will need to enable it explicitly. - + If you're running an older version of FreeBSD then you'll have to add the following lines to your kernel configuration file and compile a new kernel. @@ -2094,18 +2094,18 @@ a new kernel. See the Handbook entry on configuring the kernel if you've no experience with building kernels. - + Once you have a kernel detecting psm0 correctly at boot time, make sure that an entry for psm0 exists in /dev. You can do this by typing: - + cd /dev; sh MAKEDEV psm0 - + when logged in as root. - + use a mouse pointer in text consoles to cut & paste text. Run the mouse daemon, moused, and turn on the mouse pointer in the virtual console: - + - moused -p /dev/xxxx -t yyyy + moused -p /dev/xxxx -t yyyy vidcontrol -m on - -Where xxxx is the mouse device name and yyyy -is a protocol type for the mouse. See the + +Where xxxx is the mouse device name and yyyy +is a protocol type for the mouse. See the &man.moused.8; man page for supported protocol types. - -You may wish to run the mouse daemon automatically when the + +You may wish to run the mouse daemon automatically when the system starts. In version 2.2.1, set the following variables in /etc/sysconfig. - + mousedtype="yyyy" mousedport="xxxx" mousedflags="" - + In versions 2.2.2 or later, set the following variables in /etc/rc.conf. - + moused_type="yyyy" moused_port="xxxx" moused_flags="" - + In addition, if you would like to be able to use the mouse daemon on all virtual terminals instead of just console at boot-time, add the following to /etc/rc.conf. - + allscreens_flags="-m on" -Staring from FreeBSD 2.2.6, the mouse daemon is capable of -determining the correct protocol type automatically unless the mouse +Staring from FreeBSD 2.2.6, the mouse daemon is capable of +determining the correct protocol type automatically unless the mouse is a relatively old serial mouse model. Specify ``auto'' as the protocol to invoke automatic detection. - + When the mouse daemon is running, access to the mouse needs to be coordinated between the mouse daemon and other programs such as the -X Window. Refer to another section +X Window. Refer to another section on this issue. - + How do I cut and paste text with mouse in the text console? -Once you get the mouse daemon running (see previous section), hold down the button 1 (left button) +Once you get the mouse daemon running (see previous section), hold down the button 1 (left button) and move the mouse to select a region of text. Then, press the button 2 (middle button) or the button 3 (right button) to paste it at the text cursor. - -In versions 2.2.6 and later, pressing the button 2 will paste + +In versions 2.2.6 and later, pressing the button 2 will paste the text. Pressing the button 3 will ``extend'' the selected region of text. If your mouse does not have the middle button, you may wish -to emulate it or remap buttons using moused options. See the +to emulate it or remap buttons using moused options. See the moused(8) man page for details. - + I have a USB mouse. Does FreeBSD support the USB mouse? - + USB device support was added to FreeBSD 3.1. However, it is still in a preliminary state and may not always work as of version @@ -2272,11 +2272,11 @@ Protocol "SysMouse" The answer is, unfortunately, “It depends”. These mice with additional features require specialized driver in most cases. -Unless the mouse device driver or the user program has specific -support for the mouse, it will act just like a standard two, or +Unless the mouse device driver or the user program has specific +support for the mouse, it will act just like a standard two, or three button mouse. - -For the possible usage of wheels in the X Window environment, + +For the possible usage of wheels in the X Window environment, refer to that section. @@ -2287,7 +2287,7 @@ refer to that section. on the screen. The mouse has a wheel and is connected to the PS/2 mouse port. - + The PS/2 mouse driver psm in FreeBSD versions 3.2 or earlier has difficulty with some wheel mice, including Logitech model M-S48 and @@ -2306,10 +2306,10 @@ diff -u -r1.60.2.1 -r1.60.2.2 +++ psm.c 1999/07/12 13:40:52 1.60.2.2 @@ -959,14 +959,28 @@ sc->mode.packetsize = vendortype[i].packetsize; - + /* set mouse parameters */ +#if 0 -+ /* ++ /* + * A version of Logitech FirstMouse+ won't report wheel movement, + * if SET_DEFAULTS is sent... Don't use this command. + * This fix was found by Takashi Nishida. @@ -2320,7 +2320,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 +#endif if (sc->config & PSM_CONFIG_RESOLUTION) { sc->mode.resolution - = set_mouse_resolution(sc->kbdc, + = set_mouse_resolution(sc->kbdc, - (sc->config & PSM_CONFIG_RESOLUTION) - 1); + (sc->config & PSM_CONFIG_RESOLUTION) - 1); + } else if (sc->mode.resolution >= 0) { @@ -2331,7 +2331,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 + sc->mode.rate = set_mouse_sampling_rate(sc->kbdc, sc->dflt_mode.rate); } + set_mouse_scaling(sc->kbdc, 1); - + /* request a data packet and extract sync. bits */ if (get_mouse_status(sc->kbdc, stat, 1, 3) < 3) { @@ -2345,7 +2345,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 Please refer to the answer to the previous question. And check out this note on the Mobile Computing page. - + @@ -2354,10 +2354,10 @@ Computing page. FreeBSD supports SCSI, QIC-36 (with a QIC-02 interface) and QIC-40/80 (Floppy based) tape drives. This includes 8-mm (aka Exabyte) and DAT drives. The QIC-40/80 drives are known to be slow. - + Some of the early 8-mm drives are not quite compatible with SCSI-2, and may not work well with FreeBSD. - + @@ -2370,13 +2370,13 @@ command. The details of how you actually control the changer can be found in the chio(1) man page. - + If you're not using AMANDA or some other product that already understands changers, remember that they're only know how to move a tape from one point to another, so you need to keep track of which slot a tape is in, and which slot the tape currently in the drive needs to go back to. - + @@ -2385,23 +2385,23 @@ tape currently in the drive needs to go back to. 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 +Cards conforming to the Microsoft Sound System specification are also supported through the pcm driver. - + NOTE This is only for sound! This driver does not support CD-ROMs, SCSI or joysticks on these cards, except for the SoundBlaster. The SoundBlaster SCSI interface and some non-SCSI CDROMS are supported, but you can't boot off this device. - + Workarounds for no sound from es1370 with pcm driver? You can run the following command everytime the machine booted up: - + mixer pcm 100 vol 100 cd 100 - + @@ -2409,7 +2409,7 @@ CDROMS are supported, but you can't boot off this device. See the Ethernet cards section of the handbook for a more complete list. - + @@ -2417,25 +2417,25 @@ complete list. Note This will only affect 386/486SX/486SLC owners - other machines will have one built into the CPU. - + In general this will not cause any problems, but there are circumstances where you will take a hit, either in performance or accuracy of the math emulation code (see the section on FP emulation). In particular, drawing arcs in X will be VERY slow. It is highly recommended that you buy a math co-processor; it's well worth it. - + NOTE Some math co-processors are better than others. It pains us to say it, but nobody ever got fired for buying Intel. Unless you're sure it works with FreeBSD, beware of clones. - + What other devices does 2.X support? -See the Handbook +See the Handbook for the list of other devices supported. - + @@ -2443,7 +2443,7 @@ for the list of other devices supported. FreeBSD supports APM on certain machines. Please look in the LINT kernel config file, searching for the APM keyword. - + @@ -2452,11 +2452,11 @@ for the list of other devices supported. Certain Micron motherboards have a non-conforming PCI BIOS implementation that causes grief when FreeBSD boots because PCI devices don't get configured at their reported addresses. - + Disable the "Plug and Play Operating System" flag in the BIOS to work around this problem. More information can be found at http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron - + @@ -2468,7 +2468,7 @@ framework which made it's debut in 3.0. Patches against 2.2-STABLE are in ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/. A CAM-enhanced boot floppy is available at http://people.FreeBSD.org/~abial/cam-boot/. In both cases read the README before beginning. - + @@ -2476,20 +2476,20 @@ beginning. You will need to add the modem's PnP ID to the PnP ID list in the serial driver. -To enable Plug & Play support, compile a new kernel with controller pnp0 in +To enable Plug & Play support, compile a new kernel with controller pnp0 in the configuration file, then reboot the system. The kernel will print the PnP IDs -of all the devices it finds. Copy the PnP ID from the modem to the table in -/sys/i386/isa/sio.c, at about line 2777. Look for the string "SUP1310" -in the structure "siopnp_ids[]" to +of all the devices it finds. Copy the PnP ID from the modem to the table in +/sys/i386/isa/sio.c, at about line 2777. Look for the string "SUP1310" +in the structure "siopnp_ids[]" to find the table. Build the kernel again, install, reboot, and your modem should be found. - -You may have to manually configure the PnP devices using the `pnp' command in the + +You may have to manually configure the PnP devices using the `pnp' command in the boot-time configuration with a command like pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8 to make the modem show. - + @@ -2513,9 +2513,9 @@ to make the modem show. - + See /usr/src/sys/i386/boot/biosboot/README.serial for information. - + @@ -2524,13 +2524,13 @@ to make the modem show. Certain Micron motherboards have a non-conforming PCI BIOS implementation that does not configure PCI devices at the addresses reported. This causes grief when FreeBSD boots. - -To work around this problem, disable the "Plug and Play Operating + +To work around this problem, disable the "Plug and Play Operating System" flag in the BIOS. - + More information on this problem is available at URL: http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron - + @@ -2538,7 +2538,7 @@ System" flag in the BIOS. SMP is supported in 3.0-STABLE and later releases only. - + @@ -2567,90 +2567,90 @@ id="awre"> With SCSI drives, the drive should be capable of re-mapping these automatically. However, many drives are shipped with this feature disabled, for some mysterious reason... - + To enable this, you'll need to edit the first device page mode, which can be done on FreeBSD by giving the command (as root) - + scsi -f /dev/rsd0c -m 1 -e -P 3 - + and changing the values of AWRE and ARRE from 0 to 1:- - + AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 - -The following paragraphs were submitted by + +The following paragraphs were submitted by Ted Mittelstaedt: - + For IDE drives, any bad block is usually a sign of potential trouble. -All modern IDE drives come with internal bad-block remapping turned -on. All IDE hard drive manufacturers today offer extensive +All modern IDE drives come with internal bad-block remapping turned +on. All IDE hard drive manufacturers today offer extensive warranties and will replace drives with bad blocks on them. - + If you still want to attempt to rescue an IDE drive with bad blocks, -you can attempt to download the IDE drive manufacturer's IDE diagnostic -program, and run this against the drive. Sometimes these programs can -be set to force the drive electronics to rescan the drive for bad blocks +you can attempt to download the IDE drive manufacturer's IDE diagnostic +program, and run this against the drive. Sometimes these programs can +be set to force the drive electronics to rescan the drive for bad blocks and lock them out. - -For ESDI, RLL and MFM drives, bad blocks are a normal part of the -drive and are no sign of trouble, generally. With a PC, the disk drive -controller card and BIOS handle the task of locking out bad sectors. -This is fine for operating systems like DOS that use BIOS code to -access the disk. However, FreeBSD's disk driver does not go through -BIOS, therefore a mechanism, bad144, exists that replaces this + +For ESDI, RLL and MFM drives, bad blocks are a normal part of the +drive and are no sign of trouble, generally. With a PC, the disk drive +controller card and BIOS handle the task of locking out bad sectors. +This is fine for operating systems like DOS that use BIOS code to +access the disk. However, FreeBSD's disk driver does not go through +BIOS, therefore a mechanism, bad144, exists that replaces this functionality. bad144 only works with the wd driver, it is NOT able to be used with SCSI. bad144 works by entering all bad sectors found into a special file. - -One caveat with bad144 - the bad block special file is placed on the + +One caveat with bad144 - the bad block special file is placed on the last track of the disk. As this file may possibly contain a listing for -a bad sector that would occur near the beginning of the disk, where the -/kernel file might be located, it therefore must be accessible to the -bootstrap program that uses BIOS calls to read the kernel file. This -means that the disk with bad144 used on it must not exceed 1024 -cylinders, 16 heads, and 63 sectors. This places an effective limit +a bad sector that would occur near the beginning of the disk, where the +/kernel file might be located, it therefore must be accessible to the +bootstrap program that uses BIOS calls to read the kernel file. This +means that the disk with bad144 used on it must not exceed 1024 +cylinders, 16 heads, and 63 sectors. This places an effective limit of 500MB on a disk that is mapped with bad144. - -To use bad144, simply set the "Bad Block" scanning to ON in the -FreeBSD fdisk screen during the initial install. This works up through -FreeBSD 2.2.7. The disk must have less than 1024 cylinders. It is -generally recommended that the disk drive has been in operation for at -least 4 hours prior to this to allow for thermal expansion and track + +To use bad144, simply set the "Bad Block" scanning to ON in the +FreeBSD fdisk screen during the initial install. This works up through +FreeBSD 2.2.7. The disk must have less than 1024 cylinders. It is +generally recommended that the disk drive has been in operation for at +least 4 hours prior to this to allow for thermal expansion and track wandering. - + If the disk has more than 1024 cylinders (such as a large ESDI drive) -the ESDI controller uses a special translation mode to make it work -under DOS. The wd driver understands about these translation modes, -IF you enter the "translated" geometry with the "set geometry" command -in fdisk. You must also NOT use the "dangerously dedicated" mode of -creating the FreeBSD partition, as this ignores the geometry. Also, -even though fdisk will use your overridden geometry, it still knows the -true size of the disk, and will attempt to create a too large FreeBSD -partition. If the disk geometry is changed to the translated geometry, +the ESDI controller uses a special translation mode to make it work +under DOS. The wd driver understands about these translation modes, +IF you enter the "translated" geometry with the "set geometry" command +in fdisk. You must also NOT use the "dangerously dedicated" mode of +creating the FreeBSD partition, as this ignores the geometry. Also, +even though fdisk will use your overridden geometry, it still knows the +true size of the disk, and will attempt to create a too large FreeBSD +partition. If the disk geometry is changed to the translated geometry, the partition MUST be manually created with the number of blocks. - -A quick trick to use is to set up the large ESDI disk with the ESDI + +A quick trick to use is to set up the large ESDI disk with the ESDI controller, boot it with a DOS disk and format it with a DOS partition. -Then, boot the FreeBSD install and in the fdisk screen, read off and -write down the blocksize and block numbers for the DOS partition. Then, -reset the geometry to the same that DOS uses, delete the DOS partition, -and create a "cooperative" FreeBSD partition using the blocksize you -recorded earlier. Then, set the partition bootable and turn on bad -block scanning. During the actual install, bad144 will run first, -before any filesystems are created. (you can view this with an Alt-F2) -If it has any trouble creating the badsector file, you have set too -large a disk geometry - reboot the system and start all over again +Then, boot the FreeBSD install and in the fdisk screen, read off and +write down the blocksize and block numbers for the DOS partition. Then, +reset the geometry to the same that DOS uses, delete the DOS partition, +and create a "cooperative" FreeBSD partition using the blocksize you +recorded earlier. Then, set the partition bootable and turn on bad +block scanning. During the actual install, bad144 will run first, +before any filesystems are created. (you can view this with an Alt-F2) +If it has any trouble creating the badsector file, you have set too +large a disk geometry - reboot the system and start all over again (including repartitioning and reformatting with DOS). - -If remapping is enabled and you are seeing bad blocks, consider + +If remapping is enabled and you are seeing bad blocks, consider replacing the drive. The bad blocks will only get worse as time goes on. - + @@ -2658,7 +2658,7 @@ replacing the drive. The bad blocks will only get worse as time goes on. This info is specific to the 742a but may also cover other Buslogic cards. (Bustek = Buslogic) - + There are 2 general ``versions'' of the 742a card. They are hardware revisions A-G, and revisions H - onwards. The revision letter is located after the Assembly number on the edge of the @@ -2669,33 +2669,33 @@ of firmware chip. Buslogic will send upgrade ROMS out if you call their tech support dept. The BIOS and Firmware chips are shipped as a matched pair. You must have the most current Firmware ROM in your adapter card for your hardware revision. - + The REV A-G cards can only accept BIOS/Firmware sets up to 2.41/2.21. The REV H- up cards can accept the most current BIOS/Firmware sets of 4.70/3.37. The difference between the firmware sets is that the 3.37 firmware supports ``round robin'' - + The Buslogic cards also have a serial number on them. If you have a old hardware revision card you can call the Buslogic RMA department and give them the serial number and attempt to exchange the card for a newer hardware revision. If the card is young enough they will do so. - + 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 AHA1540 ``emulation'' mode. This is not a good thing for an EISA card, however. - + If you have an old hardware revision card and you obtain the 2.21 firmware for it, you will need to check the position of jumper W1 to B-C, the default is A-B. - + The 742a EISA cards never had the ``>16MB'' problem mentioned in the section on >16 MB machines. This is a problem that occurs with the Vesa-Local Buslogic SCSI cards. - + @@ -2708,34 +2708,34 @@ 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 auto-configuration currently cannot handle this situation very well. - + So now, the best you can do is to pretend there is no address range clash :), by bumping the kernel option EISA_SLOTS to a value of 12. Configure and compile a kernel, as described in the Handbook entry on configuring the kernel. - + Of course, this does present you with a chicken-and-egg problem when installing on such a machine. In order to work around this problem, a special hack is available inside UserConfig. Do not use the ``visual'' interface, but the plain command-line interface there. Simply type - + eisa 12 quit - + at the prompt, and install your system as usual. While it's recommended you compile and install a custom kernel anyway, - + Hopefully, future versions will have a proper fix for this problem. - + NOTE: You can not use a dangerously dedicated disk with an HP Netserver. See this note for more info. - + @@ -2743,16 +2743,16 @@ more info. It's broken. It cannot handle commands on both channels simultaneously. - + There's a workaround available now and it is enabled automatically if your system uses this chip. For the details refer to the manual page of the disk driver (man 4 wd). - + If you're already running FreeBSD 2.2.1 or 2.2.2 with a CMD640 IDE controller and you want to use the second channel, build a new kernel with options "CMD640" enabled. This is the default for 2.2.5 and later. - + @@ -2764,24 +2764,24 @@ of this, and the network driver would still function in the presence of IRQ conflicts. However, with 2.0.5R and later, IRQ conflicts are no longer tolerated. Boot with the -c option and change the ed0/de0/... entry to match your board. - + If you're using the BNC connector on your network card, you may also see device timeouts because of bad termination. To check this, attach a terminator directly to the NIC (with no cable) and see if the error messages go away. - -Some NE2000 compatible cards will give this error if there is + +Some NE2000 compatible cards will give this error if there is no link on the UTP port or if the cable is disconnected. - + When I mount a CDROM, I get ``Incorrect super block''. -You have to tell +You have to tell mount -the type of the device that you want to mount. By default, +the type of the device that you want to mount. By default, mount(8) will assume the filesystem is of type ``ufs''. You want to mount @@ -2792,26 +2792,26 @@ URL="http://www.FreeBSD.org/cgi/man.cgi?mount(8)">mount(8) CDROM contains an ISO 9660 filesystem, which is what most CDROMs have. As of 1.1R, FreeBSD automatically understands the Rock Ridge (long filename) extensions as well. - + As an example, if you want to mount the CDROM device, ``/dev/cd0c'', under /mnt, you would execute: - + mount -t cd9660 /dev/cd0c /mnt - + Note that your device name (``/dev/cd0c'' in this example) could be different, depending on the CDROM interface. Note that the ``'' option just causes the ``mount_cd9660'' command to be executed, and so the above example could be shortened to: - + mount_cd9660 /dev/cd0c /mnt - + @@ -2822,17 +2822,17 @@ or the drive is not visible on the bus. Feed the drive something, and/or check its master/slave status if it is IDE (ATAPI). It can take a couple of seconds for a CDROM drive to notice that it's been fed, so be patient. - + Sometimes a SCSI CD-ROM may be missed because it hadn't enough time to answer the bus reset. If you have a SCSI CD-ROM please try to add the following symbol into your kernel configuration file and recompile. - + options "SCSI_DELAY=15" - + @@ -2840,16 +2840,16 @@ and recompile. If it's parallel, and the only problem is that it's terribly slow, try setting your printer port into ``polled'' mode: - + lptcontrol -p - + Some newer HP printers are claimed not to work correctly in interrupt mode, apparently due to some (not yet exactly understood) timing problem. - + @@ -2863,18 +2863,18 @@ to pass all memory tests, yet fail under operating conditions (such as during bus mastering DMA from a SCSI controller like the Adaptec 1542, when you're beating on memory by compiling a kernel, or just when the system's running particularly hot). - + The SIG11 FAQ (listed below) points up slow memory as being the most common problem. Increase the number of wait states in your BIOS setup, or get faster memory. - + For me the guilty party has been bad cache RAM or a bad on-board cache controller. Try disabling the on-board (secondary) cache in the BIOS setup and see if that solves the problem. - + There's an extensive FAQ on this at the SIG11 problem FAQ - + @@ -2888,9 +2888,9 @@ URL="http://www.FreeBSD.org/cgi/man.cgi?sio(4)">sio(4) driver it will touch this port even if you don't have the fourth serial port, and even if you disable sio3 (the fourth port) which normally uses this address. - + Until the bug has been fixed, you can use this workaround: - + @@ -2913,14 +2913,14 @@ into configuration mode). - + If you want to be able to use your serial ports, you'll have to build a new kernel with the following modification: in /usr/src/sys/i386/isa/sio.c find the one occurrence of the string 0x2e8 and remove that string and the preceding comma (keep the trailing comma). Now follow the normal procedure of building a new kernel. - + 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 @@ -2931,7 +2931,7 @@ Mach64 cards and even a dedicated X server for those cards. I have 128 MB of RAM but the system only uses 64 MB. - + Due to the manner in which FreeBSD gets the memory size from the @@ -2939,7 +2939,7 @@ BIOS, it can only detect 16 bits worth of Kbytes in size (65535 Kbytes = 64MB) (or less... some BIOSes peg the memory size to 16M). If you have more than 64MB, FreeBSD will attempt to detect it; however, the attempt may fail. - + To work around this problem, you need to use the kernel option specified below. There is a way to get complete memory information from the BIOS, but we don't have room in the @@ -2947,33 +2947,33 @@ bootblocks to do it. Someday when lack of room in the bootblocks is fixed, we'll use the extended BIOS functions to get the full memory information...but for now we're stuck with the kernel option. - + options "MAXMEM=<n>" - + Where n is your memory in Kilobytes. For a 128 MB machine, you'd want to use 131072. - + FreeBSD 2.0 panics with ``kmem_map too small!'' Note The message may also be ``mb_map too small!'' - + The panic indicates that the system ran out of virtual memory for network buffers (specifically, mbuf clusters). You can increase the amount of VM available for mbuf clusters by adding: - + options "NMBCLUSTERS=<n>" - + to your kernel config file, where <n> is a number in the range 512-4096, depending on the number of concurrent TCP connections you need to support. I'd recommend trying 2048 - this should get rid of the panic completely. You can monitor the number of mbuf clusters allocated/in use on the system with -netstat -m. The default value for NMBCLUSTERS is +netstat -m. The default value for NMBCLUSTERS is 512 + MAXUSERS * 16. - + @@ -2982,33 +2982,33 @@ number of mbuf clusters allocated/in use on the system with The logic that attempts to detect an out of date /var/db/kvm_*.db files sometimes fails and using a mismatched file can sometimes lead to panics. - + If this happens, reboot single-user and do: - + rm /var/db/kvm_*.db - + ahc0: brkadrint, Illegal Host Access at seqaddr 0x0 This is a conflict with an Ultrastor SCSI Host Adapter. - + During the boot process enter the kernel configuration menu and disable uha0, which is causing the problem. - + Sendmail says ``mail loops back to myself'' This is answered in the sendmail FAQ as follows:- - + * I'm getting "Local configuration error" messages, such as: @@ -3025,7 +3025,7 @@ which is causing the problem. to /etc/sendmail.cf. - + The current version of the sendmail FAQ is no longer maintained with the sendmail release. It is however regularly posted to comp.mail.sendmail, @@ -3037,7 +3037,7 @@ You can also receive a copy via email by sending a message to mail-server@rtfm.mit.edu with the command "send usenet/news.answers/mail/sendmail-faq" as the body of the message. - + @@ -3045,24 +3045,24 @@ message. The remote machine may be setting your terminal type -to something other than the cons25 terminal type +to something other than the cons25 terminal type required by the FreeBSD console. - + There are a number of possible work-arounds for this problem: -After logging on to the remote machine, set your TERM shell -variable to ansi or +After logging on to the remote machine, set your TERM shell +variable to ansi or sco if the remote machine knows about these terminal types. -Use a VT100 emulator like screen -at the FreeBSD console. -screen offers you the ability to run multiple -concurrent sessions from one terminal, and is a neat program in its own right. +Use a VT100 emulator like screen +at the FreeBSD console. +screen offers you the ability to run multiple +concurrent sessions from one terminal, and is a neat program in its own right. Each screen window behaves like a VT100 terminal, so the TERM variable at the remote end should be set to vt100. @@ -3070,52 +3070,52 @@ vt100. -Install the cons25 terminal database entry on +Install the cons25 terminal database entry on the remote machine. The way to do this depends on the operating system on the remote machine. The system administration manuals for the remote system should be able to help you here. -Fire up an X server at the FreeBSD end and login to the remote machine -using an X based terminal emulator such as xterm or -rxvt. The TERM variable at the remote host +Fire up an X server at the FreeBSD end and login to the remote machine +using an X based terminal emulator such as xterm or +rxvt. The TERM variable at the remote host should be set to xterm or vt100 . - + My machine prints "calcru: negative time..." -This can be caused by various hardware and/or software ailments -relating to interrupts. It may be due to bugs but can also happen -by nature of certain devices. Running TCP/IP over the parallel -port using a large MTU is one good way to provoke this problem. -Graphics accelerators can also get you here, in which case you +This can be caused by various hardware and/or software ailments +relating to interrupts. It may be due to bugs but can also happen +by nature of certain devices. Running TCP/IP over the parallel +port using a large MTU is one good way to provoke this problem. +Graphics accelerators can also get you here, in which case you should check the interrupt setting of the card first. - -A side effect of this problem are dying processes with the + +A side effect of this problem are dying processes with the message "SIGXCPU exceeded cpu time limit". - -For FreeBSD 3.0 and later from Nov 29, 1998 forward: If the -problem cannot be fixed otherwise the solution is to set + +For FreeBSD 3.0 and later from Nov 29, 1998 forward: If the +problem cannot be fixed otherwise the solution is to set this sysctl variable: sysctl -w kern.timecounter.method=1 - - This means a performance impact, but considering the cause of -this problem, you probably will not notice. If the problem -persists, keep the sysctl set to one and set the "NTIMECOUNTER" -option in your kernel to increasingly large values. If by the -time you have reached "NTIMECOUNTER=20" the problem isn't -solved, interrupts are too hosed on your machine for reliable + + This means a performance impact, but considering the cause of +this problem, you probably will not notice. If the problem +persists, keep the sysctl set to one and set the "NTIMECOUNTER" +option in your kernel to increasingly large values. If by the +time you have reached "NTIMECOUNTER=20" the problem isn't +solved, interrupts are too hosed on your machine for reliable timekeeping. - + @@ -3129,10 +3129,10 @@ 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 long-term viability). We encourage commercial software vendors to send their -entries here for inclusion. See +entries here for inclusion. See the Vendors page for a longer list. - + Where can I get Motif for FreeBSD? @@ -3140,7 +3140,7 @@ for a longer list. Contact Apps2go for the least expensive ELF Motif 2.1.20 distribution for FreeBSD (either i386 or Alpha). - + There are two distributions, the "developement edition" and the "runtime edition" (for much less). These distributions includes: @@ -3168,20 +3168,20 @@ and above). - + Be sure to specify that you want the FreeBSD version of Motif when ordering (don't 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. - + More info Apps2go WWW page - + - + @@ -3190,9 +3190,9 @@ This is currently a FTP only download. Sales or Support email addresses. - + - + @@ -3200,15 +3200,15 @@ This is currently a FTP only download. phone (817) 431 8775 or +1 817 431-8775 - + - + Contact Metro Link for an either ELF or a.out Motif 2.1 distribution for FreeBSD. - + This distribution includes: @@ -3240,15 +3240,15 @@ files. - + Be sure to specify that you want the FreeBSD version 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. - + This distribution includes: @@ -3280,12 +3280,12 @@ eariler). - + Be sure to specify that you want the FreeBSD version 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. - + @@ -3293,42 +3293,42 @@ future this will change to a unified CD distribution like their CDE. Xi Graphics used to sell CDE for FreeBSD, but no longer do. - + KDE is an open source X11 desktop which is similar to CDE in many respects. You might also like the look and feel of xfce. KDE and xfce are both in the ports system. - + Are there any commercial high-performance X servers? -Yes, Xi Graphics and +Yes, Xi Graphics and Metro Link sells Accelerated-X product for FreeBSD and other Intel based systems. - + The Metro Link offering is a high performance X Server that offers easy configuration using the FreeBSD Package suite of tools, support for multiple concurrent video boards and is distributed in binary form only, in a convienent FTP download. 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 FreeBSD (see above). - + More info Metro Link WWW page - + - + @@ -3337,9 +3337,9 @@ Link offering is available at the very reasonable price of $39. Sales or Support email addresses. - + - + @@ -3347,31 +3347,31 @@ Link offering is available at the very reasonable price of $39. phone (954) 938-0283 or +1 954 938-0283 - + - + 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 Graphics also offers a high performance X Server taylored for laptop support. - + There is a free "compatibility demo" of version 5.0 available. - + Xi Graphics also sells Motif and CDE for FreeBSD (see above). - + More info Xi Graphics WWW page - + - + @@ -3380,9 +3380,9 @@ laptop support. Sales or Support email addresses. - + - + @@ -3390,21 +3390,21 @@ laptop support. phone (800) 946 7433 or +1 303 298-7478. - + - + Are there any Database systems for FreeBSD? Yes! See the Commercial Vendors section of FreeBSD's Web site. - + Also see the Databases section of the Ports collection. - + @@ -3412,7 +3412,7 @@ laptop support. Yes. The following pages tell you exactly how to setup Linux-Oracle on FreeBSD: - + @@ -3427,7 +3427,7 @@ on FreeBSD: - + @@ -3444,20 +3444,20 @@ FreeBSD. The list currently tops 1800 and is growing daily, so come back to check often or subscribe to the freebsd-announce mailing list for periodic updates on new entries. - + Most ports should be available for the 2.2, 3.x and 4.0 branches, and many of them should work on 2.1.x systems as well. Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release in also included in the ports/ directory. - + We also support the concept of a ``package'', essentially no more than a gzipped binary distribution with a little extra intelligence embedded in it for doing whatever custom installation work is required. A package can be installed and uninstalled again easily without having to know the gory details of which files it includes. - + Use the package installation menu in /stand/sysinstall (under the post-configuration menu item) or invoke the pkg_add(1) command on the specific package files you're @@ -3466,15 +3466,15 @@ their .tgz suffix and CDROM 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 following locations: - + for 2.2.8-RELEASE/2.2.8-STABLE ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/ - + - + @@ -3482,9 +3482,9 @@ of FreeBSD at the following locations: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/ - + - + @@ -3492,7 +3492,7 @@ of FreeBSD at the following locations: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/ - + @@ -3506,14 +3506,14 @@ of FreeBSD at the following locations: - + or your nearest local mirror site. - + Note that all ports may not be available as packages since new ones are constantly being added. It is always a good idea to check back periodically to see which packages are available at the ftp.FreeBSD.org master site. - + @@ -3554,7 +3554,7 @@ at the ftp.FreeBSD.org m You are trying to run a package built on 2.2 and later on a 2.1.x system. Please take a look at the previous section and get the correct port/package for your system. - + I get a message "Error: can't find @@ -3562,7 +3562,7 @@ libc.so.4.0" You accidently downloaded packages meant for 4.X and 5.X -systems and attempted to install them on your 2.X or 3.X FreeBSD system. +systems and attempted to install them on your 2.X or 3.X FreeBSD system. Please download the correct version of the packages. @@ -3576,15 +3576,15 @@ id="emul"> You will need to add the alternative math emulator to your kernel; you do this by adding the following to your kernel config file and it will be compiled in. - + options GPL_MATH_EMULATE - + NOTE You will need to remove the MATH_EMULATE option when you do this. - + @@ -3594,18 +3594,18 @@ option when you do this. You first need to edit the /etc/sysconfig (or /etc/rc.conf) file in the last section to change the following variable to YES: - + # Set to YES if you want ibcs2 (SCO) emulation loaded at startup ibcs2=NO - + It will load the ibcs2 kernel module at startup. - + You'll then need to set up /compat/ibcs2/dev to look like: - + lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 X0R@ -> /dev/null lrwxr-xr-x 1 root wheel 7 Oct 15 22:20 nfsd@ -> socksys @@ -3614,13 +3614,13 @@ lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -> /dev/null crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx - + You just need socksys to go to /dev/null to fake the open & close. The code in -CURRENT will handle the rest. This is much cleaner than the way it was done before. If you want the spx driver for a local socket X connection, define SPX_HACK when you compile the system. - + @@ -3629,7 +3629,7 @@ want the spx driver for a local socket X connectio After installing the inn package or port, an excellent place to start is Dave Barr's INN Page where you'll find the INN FAQ. - + @@ -3637,14 +3637,14 @@ start is Dave Barr's I Use the Port, Luke! A pre-patched version of Apache is available in the ports tree. - + Does FreeBSD support Java? Yes. Please see http://www.FreeBSD.org/java/. - + @@ -3658,7 +3658,7 @@ someone might have committed a change to the port which works for report on this with the send-pr(1) command, since the ports collection is supposed to work for both the -CURRENT and -STABLE branches. - + @@ -3671,7 +3671,7 @@ They are included in the compat22 distribution. Use /stand/sysinstall or install.sh in the compat22 subdirectory and install it. Also read ERRATAs for 3.1-R and 3.2-R. - + @@ -3683,11 +3683,11 @@ id="kernelconfig"> I'd like to customize my kernel. Is it difficult? - + Not at all! Check out the kernel config section of the Handbook. - + NOTE: I recommend making a dated snapshot of your kernel in kernel.YYMMDD after you get it all working, that way if you do something dire the next time you play with your configuration @@ -3695,7 +3695,7 @@ you can boot that kernel instead of having to go all the way back to kernel.GENERIC. This is particularly important if you're now booting off a controller that isn't supported in the GENERIC kernel (yes, personal experience). - + @@ -3707,7 +3707,7 @@ kernel configuration file because you don't have a math co-processor, right? Wrong! :-) The npx0 is MANDATORY. Even if you don't have a mathematic co-processor, you must include the npx0 device. - + @@ -3716,12 +3716,12 @@ device. Q. When I compile a kernel with multi-port serial code, it tells me that only the first port is probed and the rest skipped due to interrupt conflicts. How do I fix this? - + A. The problem here is that FreeBSD 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 a example: - + # # Multiport high-speed serial line - 16550 UARTS @@ -3732,7 +3732,7 @@ on all but one port. Here is a example: device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr - + @@ -3741,7 +3741,7 @@ on all but one port. Here is a example: You need to uncomment the following line in the generic config file (or add it to your config file), add a ``flags 0x1'' on the fdc line and recompile. - + controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 flags 0x1 vector fdintr disk fd0 at fdc0 drive 0 ^^^^^^^^^ @@ -3750,28 +3750,28 @@ disk fd1 at fdc0 drive 1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - + Next, you create a device called /dev/ft0 by going into /dev and run the following command: - + sh ./MAKEDEV ft0 - + for the first device. ft1 for a second one and so on. - + You will have a device called /dev/ft0, which you can write to through a special program to manage it called ``ft'' - see the man page on ft for further details. - + Versions previous to also had some trouble dealing with bad tape media; if you have trouble where ft seems to go back and forth over the same spot, try grabbing the latest version of ft from /usr/src/sbin/ft in and try that. - + @@ -3787,56 +3787,56 @@ id="admin"> /etc/sysconfig. All the options are to be specified in this file and other files such as /etc/rc and /etc/netstart just include it. - + Look in the /etc/sysconfig file and change the value to match your system. This file is filled with comments to show what to put in there. - + In post-2.2.1 and 3.0, /etc/sysconfig was renamed to a more self-describing rc.conf file and the syntax cleaned up a bit in the process. /etc/netstart was also renamed to /etc/rc.network so that all files could be copied with a cp /usr/src/etc/rc* /etc command. - + /etc/rc.local is here as always and may be used to start up additional local services like INN or set custom options. - + The /etc/rc.serial is for serial port initialization (e.g. locking the port characteristics, and so on.). - + The /etc/rc.i386 is for Intel-specifics settings, such as iBCS2 emulation or the PC system console configuration. - + Starting with 2.1.0R, you can also have "local" startup files in a directory specified in /etc/sysconfig (or /etc/rc.conf): - + # Location of local startup files. local_startup=/usr/local/etc/rc.local.d - + Each file ending in .sh will be executed in alphabetical order. - + If you want to ensure a certain execution order without changing all the file names, you can use a scheme similar to the following with digits prepended to each file name to insure the ordering: - + 10news.sh 15httpd.sh 20ssh.sh - + It can be seen as ugly (or SysV :-)) but it provides a simple and regular scheme for locally-added packages without resorting to magical editing of /etc/rc.local. Many of the ports/packages assume that /usr/local/etc/rc.d is a local startup directory. - + @@ -3844,17 +3844,17 @@ assume that /usr/local/etc/rc.d is a local startup director Use the adduser command. For more complicated usage, the pw command. - + To remove the user again, use the rmuser command. - + How can I add my new hard disk to my FreeBSD system? -See the Disk Formatting Tutorial at +See the Disk Formatting Tutorial at www.FreeBSD.org. - + @@ -3865,32 +3865,32 @@ even a floppy, if you want to use it that way), or a new hard disk, once it's installed and recognized by the system, and you have your cartridge/floppy/whatever slotted in, things are pretty much the same for all devices. - + (this section is based on Mark Mayo's ZIP FAQ) - + If it's a ZIP drive or a floppy , you've already got a DOS filesystem on it, you can use a command like this: - + mount -t msdos /dev/fd0c /floppy - + if it's a floppy, or this: - + mount -t msdos /dev/da2s4 /zip - + for a ZIP disk with the factory configuration. - + For other disks, see how they're laid out using fdisk or /stand/sysinstall. - + The rest of the examples will be for a ZIP drive on da2, the third SCSI disk. - + Unless it's a floppy, or a removable you plan on sharing with other people, it's probably a better idea to stick a BSD file system on it. You'll get long filename support, at least a 2X @@ -3900,42 +3900,42 @@ use fdisk or - + dd if=/dev/zero of=/dev/rda2 count=2 disklabel -Brw da2 auto - + You can use disklabel or /stand/sysinstall to create multiple BSD partitions. You'll certainly want to do this if you're adding swap space on a fixed disk, but it's probably irrelevant on a removable drive like a ZIP. - + Finally, create a new file system, this one's on our ZIP drive using the whole disk: - + newfs /dev/rda2c - + and mount it: - + mount /dev/da2c /zip - + and it's probably a good idea to add a line like this to /etc/fstab so you can just type "mount /zip" in the future: - + /dev/da2c /zip ffs rw,noauto 0 0 - + @@ -3945,14 +3945,14 @@ future: partitions. For example, if you have an "E" partition as the second DOS partition on the second SCSI drive, you need to create the special files for "slice 5" in /dev, then mount /dev/da1s5: - + # cd /dev # ./MAKEDEV da1s5 # mount -t msdos /dev/da1s5 /dos/e - + @@ -3962,16 +3962,16 @@ the special files for "slice 5" in /dev, then mount /dev/da1s5: Mounting disk partitions from Digital UNIX and other systems that support UFS may be more complex, depending on the details of the disk partitioning for the operating system in question. - + Linux: 2.2 and later have support for ext2fs partitions. See mount_ext2fs for more information. - - NT: A read-only NTFS driver exists for FreeBSD. For more + + NT: A read-only NTFS driver exists for FreeBSD. For more information, see this tutorial by Mark Ovens at http://ukug.uk.freebsd.org/~mark/ntfs_install.html. - + Any other information on this subject would be appreciated. - + @@ -3986,7 +3986,7 @@ partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: - + [boot loader] timeout=30 @@ -3997,74 +3997,74 @@ something like this: C:\="DOS" - + For 2.2.x systems this procedure assumes that DOS, NT, FreeBSD, or whatever have been installed into their respective fdisk partitions on the same disk. In my case DOS & NT are in the first fdisk partition and FreeBSD is in the second. I also installed FreeBSD to boot from its native partition, not the disk MBR. - + Mount a DOS-formatted floppy (if you've converted to NTFS) or the FAT partition, under, say, /mnt. - + dd if=/dev/rda0a of=/mnt/bootsect.bsd bs=512 count=1 - + Reboot into DOS or NT. NTFS users copy the bootsect.bsd and/or the bootsect.lnx file from the floppy to C:\. Modify the attributes (permissions) on boot.ini with: - + attrib -s -r c:\boot.ini - + Edit to add the appropriate entries from the example boot.ini above, and restore the attributes: - + attrib +s +r c:\boot.ini - + If FreeBSD is booting from the MBR, restore it with the DOS ``fdisk'' command after you reconfigure them to boot from their native partitions. For FreeBSD 3.x systems the procedure is somewhat simpler. -If FreeBSD is installed on the same disk as the NT boot partition -copy /boot/boot1 to c:\bootsect.bsd +If FreeBSD is installed on the same disk as the NT boot partition +copy /boot/boot1 to c:\bootsect.bsd or if FreeBSD is installed on a different disk copy /boot/boot0 to c:\bootsect.bsd. Then edit c:\bootsect.ini as described earlier. - + 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 operating +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 table=/dev/hda label=FreeBSD -(the above assumes that your FreeBSD slice is known to Linux as -/dev/hda2; tailor to suit your setup). Then, +(the above assumes that your FreeBSD 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 -``loader=/boot/chain.b'' to the LILO entry. + +If FreeBSD resides on another disk, you need to add +``loader=/boot/chain.b'' to the LILO entry. For example: other=/dev/dab4 table=/dev/dab @@ -4072,35 +4072,35 @@ For example: label=FreeBSD - -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 + +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 specify: Boot: 1:da(0,a)/kernel - + On FreeBSD 2.2.5 and later, you can configure boot(8) to automatically do this for you at boot time. - + The Linux+FreeBSD mini-HOWTO is a good reference for FreeBSD and Linux interoperability issues. - + How do I boot FreeBSD and Linux using BootEasy? -Install LILO at the start of your Linux boot partition instead of +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're running Windows-95 and Linux this is recommended anyway, to make it simpler to get Linux booting again if you should need to reinstall Windows95 (which is a Jealous Operating System, and will bear no other Operating Systems in the Master Boot Record). - + @@ -4116,7 +4116,7 @@ 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 compatible with other operating systems. - + So why it is called ``dangerous''? A disk in this mode doesn't contain what normal PC utilities would consider a valid fdisk table. Depending on how well they have been @@ -4126,78 +4126,78 @@ damage the BSD bootstrap without even asking or notifying you. In addition, the ``dangerously dedicated'' disk's layout is known to confuse many BIOSsen, including those from AWARD (eg. as found in HP Netserver and Micronics systems as well as -many others) and Symbios/NCR (for the popular 53C8xx range of +many others) and Symbios/NCR (for the popular 53C8xx range of SCSI controllers). This isn't a complete list, there are more. Symptoms of this confusion include the "read error" message printed by the FreeBSD bootstrap when it can't 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 +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 ``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 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 won't be able to boot. - + ``Dangerously dedicated'' mode tries to work around this by making the problem simpler. In some cases, it gets it right. But it's meant to be used as a last-ditch alternative - there are better ways to solve the problem 99 times out of 100. - + So, how do you avoid the need for ``DD'' mode when you're installing? Start by making a note of the geometry that your BIOS claims to be using for your disks. You can arrange to have -the kernel print this as it boots by specifying ``-v'' at the -``boot:'' prompt, or using ``boot -v'' in the loader. Just -before the installer starts, the kernel will print a list of +the kernel print this as it boots by specifying ``-v'' at the +``boot:'' prompt, or using ``boot -v'' in the loader. Just +before the installer starts, the kernel will print a list of BIOS geometries. Don't 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 FreeBSD lists your disks, first IDE, then SCSI. - -When you're slicing up your disk, check that the disk geometry -displayed in the FDISK screen is correct (ie. it matches the BIOS -numbers); if it's wrong, use the ``g'' key to fix it. You may have + +When you're slicing up your disk, check that the disk geometry +displayed in the FDISK screen is correct (ie. it matches the BIOS +numbers); if it's wrong, use the ``g'' key to fix it. You may have to do this if there's absolutely nothing on the disk, or if the -disk has been moved from another system. Note that this is only +disk has been moved from another system. Note that this is only an issue with the disk that you're going to boot from; FreeBSD will sort itself out just fine with any other disks you may have. - -Once you've got the BIOS and FreeBSD agreeing about the -geometry of the disk, your problems are almost guaranteed to be + +Once you've got the BIOS and FreeBSD 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 error'' message -when you try to boot, it's time to cross your fingers and +when you try to boot, it's time to cross your fingers and go for it - there's nothing left to lose. - + To return a ``dangerously dedicated'' disk for normal PC use, there are basically two options. The first is, you write enough NULL bytes over the MBR to make any subsequent installation believe this to be a blank disk. You can do this for example with - + dd if=/dev/zero of=/dev/rda0 count=15 - + Alternatively, the undocumented DOS ``feature'' - + fdisk /mbr - + will to install a new master boot record as well, thus clobbering the BSD bootstrap. - + @@ -4210,47 +4210,47 @@ main memory. However, if you have a very small amount of main memory you may want to configure swap beyond that. It is also a good idea to configure sufficient swap relative to anticipated future memory upgrades so you do not have to futz with your swap configuration later. - + Adding swap onto a separate disk makes things faster than simply adding swap onto the same disk. As an example, if you are compiling source located on one disk, and the swap is on another disk, this is much faster than both swap and compile on the same disk. This is true for SCSI disks specifically. - + When you have several disks, configuring a swap partition on each one is usually beneficial, even if you wind up putting swap on a work disk. Typically, each fast disk in your system should have some -swap configured. FreeBSD supports up to 4 interleaved swap devices by +swap configured. FreeBSD supports up to 4 interleaved swap devices by default. When configuring multiple swap partitions you generally -want to make them all about the same size, but people sometimes make +want to make them all about the same size, but people sometimes make their primary swap parition larger in order to accomodate a kernel core dump. Your primary swap partition must be at least as large as main memory in order to be able to accomodate a kernel core. - + IDE drives are not able to allow access to both drives on the same channel at the same time (FreeBSD doesn't support mode 4, so all IDE disk I/O is ``programmed''). I would still suggest putting your swap on a separate drive however. The drives are so cheap, it is not worth worrying about. - + Swapping over NFS is only recommended if you do not have a local disk to swap to. Swapping over NFS is slow and inefficient in FreeBSD -releases prior to 4.x, but reasonably fast in releases greater or +releases prior to 4.x, but reasonably fast in releases greater or equal to 4.0. Even so, it will be limited to the network bandwidth available and puts an additional burden on the NFS server. - + Here is an example for 64Mb vn-swap (/usr/swap0, though of course you can use any name that you want). - + Make sure your kernel was built with the line - + pseudo-device vn 1 #Vnode driver (turns a file into a device) - + in your config-file. The GENERIC kernel already contains this. - + @@ -4297,14 +4297,14 @@ of course you can use any name that you want). - + To enable the swap file immediately, type - + vnconfig -ce /dev/vn0c /usr/swap0 swap - + @@ -4313,7 +4313,7 @@ of course you can use any name that you want). Please have a look at the Handbook entry on printing. It should cover most of your problem. See the Handbook entry on printing. - + @@ -4322,24 +4322,24 @@ should cover most of your problem. See the The kbdcontrol program has an option to load a keyboard map file. Under /usr/share/syscons/keymaps are a number of map files. Choose the one relevant to your system and load it. - + kbdcontrol -l uk.iso - + Both the /usr/share/syscons/keymaps and the .kbd -extension are assumed by +extension are assumed by kbdcontrol. - + This can be configured in /etc/sysconfig (or rc.conf). See the appropriate comments in this file. - + In 2.0.5R and later, everything related to text fonts, keyboard mapping is in /usr/share/examples/syscons. - + The following mappings are currently supported: - + @@ -4449,7 +4449,7 @@ mapping is in /usr/share/examples/syscons. - + @@ -4477,35 +4477,35 @@ to be enforced on. ie: - + What's inappropriate about my ccd? The symptom of this is: - + # ccdconfig -C ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format # - + This usually happens when you are trying to concatenate the `c' partitions, which default to type `unused'. The ccd driver requires the underlying partition type to be FS_BSDFFS. Edit the disklabel of the disks you are trying to concatenate and change the types of partitions to `4.2BSD'. - + Why can't I edit the disklabel on my ccd? The symptom of this is: - + # disklabel ccd0 (it prints something sensible here, so let's try to edit it) @@ -4516,11 +4516,11 @@ to concatenate and change the types of partitions to # - + This is because the disklabel returned by ccd is actually a `fake' one that is not really on the disk. You can solve this problem by writing it back explicitly, as in: - + # disklabel ccd0 > /tmp/disklabel.tmp # disklabel -Rr ccd0 /tmp/disklabel.tmp @@ -4528,7 +4528,7 @@ this problem by writing it back explicitly, as in: (this will work now) - + @@ -4537,7 +4537,7 @@ this problem by writing it back explicitly, as in: Yes, FreeBSD supports System V-style IPC. This includes shared memory, messages and semaphores. You need to add the following lines to your kernel config to enable them. - + options SYSVSHM options "SHMMAXPGS=64" # 256Kb of sharable memory @@ -4545,13 +4545,13 @@ lines to your kernel config to enable them. options SYSVMSG # enable for messaging - + Recompile and install. - + NOTE: You may need to increase SHMMAXPGS to some ridiculous number like 4096 (16M!) if you want to run GIMP. 256Kb is plenty for X11R6 shared memory. - + suited for sites that connect directly to the Internet. Sites that wish to exchange their mail via UUCP must install another sendmail configuration file. - + Tweaking /etc/sendmail.cf manually is considered something for purists. Sendmail version 8 comes with a -new approach of generating config files via some +new approach of generating config files via some m4 preprocessing, where the actual hand-crafted configuration is on a higher abstraction level. You should use the configuration files under - + /usr/src/usr.sbin/sendmail/cf - + If you didn't install your system with full sources, the sendmail config stuff has been broken out into a separate source distribution tarball just for you. Assuming you've got your CD-ROM mounted, do: @@ -4584,31 +4584,31 @@ tarball just for you. Assuming you've got your CD-ROM mounted, do: Don't panic, this is only a few hundred kilobytes in size. The file README in the cf directory can serve as a basic introduction to m4 configuration. - + For UUCP delivery, you are best advised to use the mailertable feature. This constitutes a database that sendmail can use to base its routing decision upon. - + First, you have to create your .mc file. The directory /usr/src/usr.sbin/sendmail/cf/cf is the home of these files. Look around, there are already a few examples. Assuming you have named your file foo.mc, all you need to do in order to convert it into a valid sendmail.cf is: - + &prompt.root; cd /usr/src/usr.sbin/sendmail/cf/cf &prompt.root; make foo.cf &prompt.root; cp foo.cf /etc/sendmail.cf - + A typical .mc file might look like: - + include(`../m4/cf.m4') VERSIONID(`Your version number') OSTYPE(bsd4.4) - + FEATURE(nodns) FEATURE(nocanonify) FEATURE(mailertable) @@ -4629,11 +4629,11 @@ prevent any usage of the DNS during mail delivery. The don't ask. Simply put an Internet hostname there that is able to handle .UUCP pseudo-domain addresses; most likely, you will enter the mail relay of your ISP there. - + Once you've got this, you need this file called /etc/mailertable. A typical example of this gender again: - + # # makemap hash /etc/mailertable.db < /etc/mailertable # @@ -4645,7 +4645,7 @@ horus.UUCP uucp-dom:horus if-bus.UUCP uucp-dom:if-bus . uucp-dom: - + As you can see, this is part of a real-life file. The first three lines handle special cases where domain-addressed mail should not be sent out to the default route, but instead to @@ -4660,13 +4660,13 @@ serves as your universal mail gateway to the world. All of the node names behind the uucp-dom: keyword must be valid UUCP neighbors, as you can verify using the command uuname. - + As a reminder that this file needs to be converted into a DBM database file before being usable, the command line to accomplish this is best placed as a comment at the top of the mailertable. You always have to execute this command each time you change your mailertable. - + Final hint: if you are uncertain whether some particular mail routing would work, remember the option to sendmail. It starts sendmail in address test mode; @@ -4675,7 +4675,7 @@ test for the mail routing. The last line tells you the used internal mail agent, the destination host this agent will be called with, and the (possibly translated) address. Leave this mode by typing Control-D. - + &prompt.user; sendmail -bt ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) Enter <ruleset> <address> @@ -4686,69 +4686,69 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \ < @ interface-business . de > > ^D - + How do I set up mail with a dialup connection to the 'net? - + If you've got a statically assigned IP number, you should not need to adjust anything from the default. Set your host name up as your assigned internet name and sendmail will do the rest. - + If you've got a dynamically assigned IP number and use a dialup ppp connection to the internet, you will probably be given a mailbox on your ISPs mail server. Lets assume your ISPs domain is myISP.com, and that your user name is user. Lets also assume you've called your machine bsd.home and that your ISP has told you that you may use relay.myISP.com as a mail relay. - + In order to retrieve mail from your mailbox, you'll need to install a retrieval agent. Fetchmail is a good choice as it supports many different protocols. Usually, POP3 will be provided by your ISP. If you've chosen to use user-ppp, you can automatically fetch your mail when a connection to the 'net is established with the following entry in /etc/ppp/ppp.linkup: - + MYADDR: !bg su user -c fetchmail - + If you are using sendmail (as shown below) to deliver mail to non-local accounts, put the command - + !bg su user -c "sendmail -q" - + after the above shown entry. This forces sendmail to process your mailqueue as soon as the connection to the 'net is established. - + I'm assuming that you have an account for user on bsd.home. In the home directory of user on bsd.home, create a .fetchmailrc file: - + poll myISP.com protocol pop3 fetchall pass MySecret; - + Needless to say, this file should not be readable by anyone except user as it contains the password MySecret. - + In order to send mail with the correct from: header, you must tell sendmail to use user@myISP.com rather than user@bsd.home. You may also wish to tell sendmail to send all mail via relay.myISP.com, allowing quicker mail transmission. - + The following .mc file should suffice: - + VERSIONID(`bsd.home.mc version 1.0') OSTYPE(bsd4.4)dnl @@ -4768,25 +4768,25 @@ mail via relay.myISP.com, allowing quicker mail transmissio define(`confDELIVERY_MODE',`deferred')dnl - + Refer to the previous section for details of how to turn this .mc file into a sendmail.cf file. Also, don't forget to restart sendmail after updating sendmail.cf. - + Eek! I forgot the root password! -Don't Panic! Simply restart the system, type boot -s +Don't Panic! Simply restart the system, type boot -s at the Boot: prompt (just -s for FreeBSD releases before 3.2) to enter Single User mode. At the question about the shell to use, hit ENTER. You'll be dropped to a &prompt.root; prompt. Enter mount -u / to -remount your root filesystem read/write, then run mount -a to -remount all the filesystems. Run passwd root to +remount your root filesystem read/write, then run mount -a to +remount all the filesystems. Run passwd root to change the root password then run exit to continue booting. - + @@ -4807,68 +4807,68 @@ use the following kernel configuration line instead: options PCVT_CTRL_ALT_DEL For older versions of FreeBSD, -edit the keymap you are using for the console and replace the -boot keywords with nop. The default keymap is +edit the keymap you are using for the console and replace the +boot keywords with nop. The default keymap is /usr/share/syscons/keymaps/us.iso.kbd. You may have to instruct /etc/rc.conf to load this keymap explicitly for the change to take effect. Of course if you are using an alternate keymap for your country, you should edit that one instead. - + How do I reformat DOS text files to UNIX ones? Simply use this perl command: - + perl -i.bak -npe 's/\r\n/\n/g' file ... - + file is the file(s) to process. The modification is done in-place, with the original file stored with a .bak extension. - + Alternatively you can use the tr command: - + tr -d '\r' < dos-text-file > unix-file - + dos-text-file is the file containing DOS text while -unix-file will contain the converted output. This can +unix-file will contain the converted output. This can be quite a bit faster than using perl. - + How do I kill processes by name? Use killall. - + Why is su bugging me about not being in root's ACL? -The error comes from the Kerberos distributed authentication system. +The error comes from the Kerberos distributed authentication system. The problem isn't fatal but annoying. You can either run su with the -K option, or uninstall Kerberos as described in the next question. - + How do I uninstall Kerberos? To remove Kerberos from the system, reinstall the bin distribution -for the release you are running. If you have the CDROM, you can +for the release you are running. If you have the CDROM, you can mount the cd (we'll assume on /cdrom) and run - + cd /cdrom/bin ./install.sh - + @@ -4876,7 +4876,7 @@ mount the cd (we'll assume on /cdrom) and run If you have lots of telnet, ssh, X, or screen users, you'll probably run out of pseudoterminals. Here's how to add more: - + @@ -4919,7 +4919,7 @@ terminals. They should match the form of the existing entries, i.e. they look li -The order of the letter designations is tty[pqrsPQRS][0-9a-v], +The order of the letter designations is tty[pqrsPQRS][0-9a-v], using a regular expression. @@ -4931,7 +4931,7 @@ using a regular expression. - + @@ -4954,7 +4954,7 @@ using a regular expression. a reboot? Go into single user mode and than back to multi user mode. - + On the console do: # shutdown now (Note: without -r or -h) @@ -4962,14 +4962,14 @@ using a regular expression. # return # exit - + What is a sandbox? "Sandbox" is a security term. It can mean two things: - + @@ -5037,20 +5037,20 @@ that he is sitting in it. - + UNIX implements two core sanboxes. 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 can not 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 patricular 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 on-disk data. - + @@ -5058,11 +5058,11 @@ used to firewall off on-disk data. How do I let ordinary users mount floppies and other removable media? - + Ordinary users can be permitted to mount devices. Here is how: - + As root assign the appropriate @@ -5071,7 +5071,7 @@ used to firewall off on-disk data. For example, to allow users to mount the first floppy drive, use: - + &prompt.root; chmod 777 /dev/fd0 @@ -5079,23 +5079,23 @@ used to firewall off on-disk data. As root set the sysctl variable vfs.usermount to 1. - + &prompt.root; sysctl -w vfs.usermount=1 - + Users can now mount /dev/fd0 onto a directory that they own: - + &prompt.user; mkdir ~/my-mount-point &prompt.user; mount -t msdos /dev/fd0 ~/my-mount-point Unmounting the device is simple: - + &prompt.user; umount ~/my-mount-point - + Enabling vfs.usermount, however, has - negative security implications. A better way to access MSDOS + negative security implications. A better way to access MSDOS formatted media is to use the mtools package in the ports collection. @@ -5115,14 +5115,14 @@ id="x"> The easiest way is to simply specify that you want to run X during the installation process. - + Then read and follow the documentation on the xf86config tool, which assists you in configuring XFree86(tm) for your particular graphics card/mouse/etc. - + You may also wish to investigate the Xaccel server. See the section on Xi Graphics or Metro Link for more details. - + and use X, see and set up moused. - + Then edit /etc/XF86Config and make sure you have the following lines. @@ -5148,27 +5148,27 @@ Device "/dev/sysmouse" ..... The above example is for XFree86 3.3.2 or later. For earlier -versions, the Protocol should be +versions, the Protocol should be MouseSystems. Some people prefer to use ``/dev/mouse'' under X. To make this work, ``/dev/mouse'' should be linked to /dev/sysmouse: - + # cd /dev # rm -f mouse # ln -s sysmouse mouse - + My mouse has a fancy wheel. Can I use it in X? - + Yes. But you need to customize X client programs. See Colas Nahaboo's web page (http://www.inria.fr/koala/colas/mouse-wheel-scroll/). @@ -5377,18 +5377,18 @@ EndSection X Window menus and dialog boxes don't work right! Try turning off the Num Lock key. - + If your Num Lock key is on by default at boot-time, you may add the following line in the ``Keyboard'' section of the XF86Config file. - + # Let the server do the NumLock processing. This should only be # required when using pre-R6 clients ServerNumLock - + @@ -5397,12 +5397,12 @@ the following line in the ``Keyboard'' section of Virtual consoles, put simply, enable you to have several simultaneous sessions on the same machine without doing anything complicated like setting up a network or running X. - + When the system starts, it will display a login prompt on the monitor after displaying all the boot messages. You can then type in your login name and password and start working (or playing!) on the first virtual console. - + At some point, you will probably wish to start another session, perhaps to look at documentation for a program you are running or to read your mail while waiting for an @@ -5410,15 +5410,15 @@ FTP transfer to finish. Just do Alt-F2 (hold down the Alt key and press the F2 key), and you will find a login prompt waiting for you on the second ``virtual console''! When you want to go back to the original session, do Alt-F1. - + The default FreeBSD installation has three virtual consoles enabled (8 starting with 3.3-RELEASE), and Alt-F1, Alt-F2, and Alt-F3 will switch between these virtual consoles. - + To enable more of them, edit /etc/ttys and add entries for ``ttyv4'' to ``ttyvc'' after the comment on ``Virtual terminals'': - + # Edit the existing entry for ttyv3 in /etc/ttys and change # "off" to "on". @@ -5433,72 +5433,72 @@ comment on ``Virtual terminals'': ttyvb "/usr/libexec/getty Pc" cons25 on secure - + Use as many or as few as you want. The more virtual terminals you have, the more resources that are used; this can be important if you have 8MB RAM or less. You may also want to change the ``secure'' to ``insecure''. - + IMPORTANT NOTE if you want to run an X server you MUST leave at least one virtual terminal unused (or turned off) for it to use. That is to say that if you want to have a login prompt pop up for all twelve of your Alt-function keys, you're out of luck - you can only do this for eleven of them if you also want to run an X server on the same machine. - + The easiest way to disable a console is by turning it off. For example, if you had the full 12 terminal allocation mentioned above and you wanted to run X, you would change settings for virtual terminal 12 from: - + ttyvb "/usr/libexec/getty Pc" cons25 on secure - + to: - + ttyvb "/usr/libexec/getty Pc" cons25 off secure - + If your keyboard has only ten function keys, you would end up with: - + ttyv9 "/usr/libexec/getty Pc" cons25 off secure ttyva "/usr/libexec/getty Pc" cons25 off secure ttyvb "/usr/libexec/getty Pc" cons25 off secure - + (You could also just delete these lines.) - + Once you have edited /etc/ttys, the next step is to make sure that you have enough virtual terminal devices. The easiest way to do this is: - + # cd /dev # ./MAKEDEV vty12 # For 12 devices - + Next, the easiest (and cleanest) way to activate the virtual consoles is to reboot. However, if you really don't want to reboot, you can just shut down the X Window system and execute (as root): - + kill -HUP 1 - + It's imperative that you completely shut down X Window if it is running, before running this command. If you don't, your system will probably appear to hang/lock up after executing the kill command. - + @@ -5512,7 +5512,7 @@ virtual terminal or back to X Window. You do not need to also press the Ctrl key. If you use the control key to switch back to X on some older releases, you can find your text console stuck in ``control-lock'' mode. Tap the control key to wake it up again. - + @@ -5520,23 +5520,23 @@ mode. Tap the control key to wake it up again. There are two schools of thought on how to start xdm. One school starts xdm from /etc/ttys using the supplied example, while the other -simply runs xdm from rc.local or +simply runs xdm from rc.local or from a X.sh script in /usr/local/etc/rc.d. -Both are equally valid, and one may work in +Both are equally valid, and one may work in situations where the other doesn't. In both cases the result is the same: X will popup a graphical login: prompt. - + The ttys method has the advantage of documenting which vty X will start on and passing the responsibility of restarting the X server on logout to init. The rc.local method makes it easy to kill xdm if there is a problem starting the X server. - -If loaded from rc.local, xdm should be started without any -arguments (i.e., as a daemon). xdm must start AFTER getty runs, or -else getty and xdm will conflict, locking out the console. The best + +If loaded from rc.local, xdm should be started without any +arguments (i.e., as a daemon). xdm must start AFTER getty runs, or +else getty and xdm will conflict, locking out the console. The best way around this is to have the script sleep 10 seconds or so then launch xdm. - + If you are to start xdm from /etc/ttys, there still is a chance of conflict between xdm and getty. One way to @@ -5544,12 +5544,12 @@ launch xdm. /usr/X11R6/lib/X11/xdm/Xservers file. :0 local /usr/X11R6/bin/X vt4 - + The above example will direct the X server to run in /dev/ttyv3. Note the number is offset by one. The X server counts the vty from one, whereas the FreeBSD kernel numbers the vty from zero. - + @@ -5557,24 +5557,24 @@ launch xdm. If you start X with startx, the permissions on /dev/console will not get changed, resulting in things like xterm -C and xconsole not working. - + This is because of the way console permissions are set by default. On a multi-user system, one doesn't necessarily want just any user to be able to write on the system console. For users who are logging -directly onto a machine with a VTY, the +directly onto a machine with a VTY, the fbtab file exists to solve such problems. - + In a nutshell, make sure an uncommented line of the form - + /dev/ttyv0 0600 /dev/console - + is in /etc/fbtab and it will ensure that whomever logs in on /dev/ttyv0 will own the console. - + @@ -5582,61 +5582,61 @@ file exists to solve such problems. Your mouse and the mouse driver may have somewhat become out of synchronization. - -In versions 2.2.5 and earlier, switching away from X to a -virtual terminal and getting back to X again may make them -re-synchronized. If the problem occurs often, you may add the + +In versions 2.2.5 and earlier, switching away from X to a +virtual terminal and getting back to X again may make them +re-synchronized. If the problem occurs often, you may add the following option in your kernel configuration file and recompile it. - + options PSM_CHECKSYNC - + See the section on building a kernel if you've no experience with building kernels. - + With this option, there should be less chance of synchronization problem between the mouse and the driver. If, however, you still see the problem, click any mouse button while holding the mouse still to re-synchronize the mouse and the driver. - + Note that unfortunately this option may not work with all the systems and voids the ``tap'' feature of the ALPS GlidePoint device attached to the PS/2 mouse port. - + In versions 2.2.6 and later, synchronization check is done in a slightly better way and is standard in the PS/2 mouse driver. It should even work with GlidePoint. (As the check code has become a standard feature, PSM_CHECKSYNC option is not available in these versions.) However, in rare case the driver may erroneously report synchronization problem and you may see the kernel message: - + psmintr: out of sync (xxxx != yyyy) - + and find your mouse doesn't seem to work properly. - + If this happens, disable the synchronization check code by setting the driver flags for the PS/2 mouse driver to 0x100. -Enter UserConfig by giving the ``'' option +Enter UserConfig by giving the ``'' option at the boot prompt: - + boot: -c - + Then, in the UserConfig command line, type: - + UserConfig> flags psm0 0x100 UserConfig> quit - + @@ -5644,15 +5644,15 @@ at the boot prompt: There have been some reports that certain model of PS/2 mouse from MouseSystems works only if it is put into the ``high resolution'' -mode. Otherwise, the mouse cursor may jump to the upper-left +mode. Otherwise, the mouse cursor may jump to the upper-left corner of the screen every so often. - -Unfortunately there is no workaround for versions 2.0.X and -2.1.X. In versions 2.2 through 2.2.5, apply the following patch -to /sys/i386/isa/psm.c and rebuild the kernel. See the + +Unfortunately there is no workaround for versions 2.0.X and +2.1.X. In versions 2.2 through 2.2.5, apply the following patch +to /sys/i386/isa/psm.c and rebuild the kernel. See the section on building a kernel if you've no experience with building kernels. - + diff -u psm.c.orig psm.c @@ -766,6 +766,8 @@ @@ -5666,39 +5666,39 @@ if you've no experience with building kernels. set_mouse_mode(sc->kbdc); /* stream mode */ - + In versions 2.2.6 or later, specify the flags 0x04 to the PS/2 mouse driver to put the mouse into the high resolution mode. -Enter UserConfig by giving the ``'' option +Enter UserConfig by giving the ``'' option at the boot prompt: - + boot: -c - + Then, in the UserConfig command line, type: - + UserConfig> flags psm0 0x04 UserConfig> quit - + See the previous section for another possible cause of mouse problems. - + When building an X app, imake can't find Imake.tmpl. Where is it? -Imake.tmpl is part of the Imake package, a standard X application building tool. -Imake.tmpl, as well as several header files that are required to build X apps, +Imake.tmpl is part of the Imake package, a standard X application building tool. +Imake.tmpl, as well as several header files that are required to build X apps, is contained in the X prog distribution. You can install this from sysinstall or manually from the X distribution files. - + @@ -5706,7 +5706,7 @@ manually from the X distribution files. Run the command xmodmap -e "pointer = 3 2 1" from your .xinitrc or .xsession. - + @@ -5725,12 +5725,12 @@ the VM86 kernel option to be compiled into the kernel. The actual VESA support can either be compiled directly into the kernel with the VESA kernel config option or by loading the VESA kld module during bootup. - + To use a splash screen, you need to modify the startup files that control the boot process for FreeBSD. The files for this changed prior to the release of FreeBSD 3.2, so there are now two ways of loading a splash screen: - + @@ -5805,10 +5805,10 @@ create a /boot/loader.conf that contains: - + Now all you need is a splash screen. For that you can surf on over to the gallery at http://www.cslab.vt.edu/~jobaldwi/splash/. - + @@ -5828,18 +5828,18 @@ on over to the gallery at 115 - Windows(tm) key, between the left-hand Ctrl and Alt keys - + 116 - Windows(tm) key, to the right of the Alt-Gr key - + 117 - Menu key, to the left of the right-hand Ctrl key - + To have the left Windows(tm) key print a comma, try this. @@ -5899,7 +5899,7 @@ id="networking"> network, and reads the necessary files from a server instead of its hard disk. For full details, please read the Handbook entry on diskless booting - + @@ -5910,27 +5910,27 @@ its hard disk. For full details, please read providing packet forwarding by default in FreeBSD. You can however enable this feature by changing the following variable to YES in rc.conf: - + gateway_enable=YES # Set to YES if this host will be a gateway - + This option will put the sysctl variable net.inet.ip.forwarding to 1. - + In most cases, you will also need to run a routing process to tell other systems on your network about your router; FreeBSD -comes with the standard BSD routing daemon +comes with the standard BSD routing daemon routed, or for more complex situations you may want to try GaTeD (available from http://www.gated.org/ ) which supports FreeBSD as of 3_5Alpha7. - + It is our duty to warn you that, even when FreeBSD is configured in this way, it does not completely comply with the Internet standard requirements for routers; however, it comes close enough for ordinary usage. - + @@ -5941,10 +5941,10 @@ with FreeBSD and one with Win95; the idea is to use the FreeBSD box to connect to the Internet and then be able to access the Internet from the Windows95 box through the FreeBSD box. This is really just a special case of the previous question. - + There's a useful document available which explains how to set FreeBSD up as a PPP Dialup Router - + NOTE: This requires having at least two fixed IP addresses available, and possibly three or more, depending on how much work you want to go through to set up the Windows box. As an @@ -5953,9 +5953,9 @@ the private IP subnets and install proxies such as SQUID and the TIS firewall toolkit on your FreeBSD box. - + See also the section on natd. - + @@ -5965,23 +5965,23 @@ on your FreeBSD box. There is a conflict between the ``cdefs.h'' file in the distribution and the one shipped with FreeBSD. Just remove compat/include/sys/cdefs.h. - + Does FreeBSD support SLIP and PPP? -Yes. See the man pages for +Yes. See the man pages for slattach, sliplogin, -pppd and +pppd and ppp. pppd and ppp provide support for both incoming and outgoing connections. Sliplogin deals exclusively with incoming connections and slattach deals exclusively with outgoing connections. - + These programs are described in the following sections of the handbook: - + @@ -6006,12 +6006,12 @@ connections. Sliplogi - + If you only have access to the Internet through a "shell account", you may want to have a look at the slirp package. It can provide you with (limited) access to services such as ftp and http direct from your local machine. - + natd program. Natd allows you to connect an entire subnet to the internet using only a single IP number. - + The ppp program has similar functionality built in via the switch. The alias library is used in both cases. - + @@ -6045,7 +6045,7 @@ 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 Ultrix. - + @@ -6053,24 +6053,24 @@ Ultrix. Add ``netmask 0xffffffff'' to your ifconfig command-line like the following: - + ifconfig ed0 alias 204.141.95.2 netmask 0xffffffff - + How do I get my 3C503 to use the other network port? If you want to use the other ports, you'll have to specify an -additional parameter on the +additional parameter on the ifconfig command line. The default port is ``link0''. To use the AUI port instead of the BNC one, use ``link2''. These flags should be specified using the ifconfig_* variables in /etc/rc.conf. - + @@ -6079,10 +6079,10 @@ using the ifconfig_* variables in the Handbook entry on NFS for more information on this topic. - + @@ -6090,12 +6090,12 @@ for more information on this topic. Some versions of the Linux NFS code only accept mount requests from a privileged port; try - + mount -o -P linuxbox:/blah /mnt - + @@ -6103,12 +6103,12 @@ from a privileged port; try Sun workstations running SunOS 4.X only accept mount requests from a privileged port; try - + mount -o -P sunbox:/blah /mnt - + @@ -6116,41 +6116,41 @@ from a privileged port; try Try disabling the TCP extensions in /etc/rc.conf by changing the following variable to NO: - + tcp_extensions=NO - + Xylogic's Annex boxes are also broken in this regard and you must use the above change to connect thru them. - + How do I enable IP multicast support? Multicast host operations are fully supported in FreeBSD 2.0 and -later by default. If you want your box to run as a multicast router, +later by default. If you want your box to run as a multicast router, you will need to recompile your kernel with the MROUTING option and run mrouted. FreeBSD 2.2 and later will start -mrouted at boot time if the flag mrouted_enable is set +mrouted at boot time if the flag mrouted_enable is set to "YES" in /etc/rc.conf. - -MBONE tools are available in their own ports category, mbone. If -you are looking for the conference tools vic and vat, + +MBONE tools are available in their own ports category, mbone. If +you are looking for the conference tools vic and vat, look there! - -For more information, see the + +For more information, see the Mbone Information Web. - + Which network cards are based on the DEC PCI chipset? Here is a list compiled by Glen Foster, with some more modern additions: - + Vendor Model ---------------------------------------------- @@ -6173,7 +6173,7 @@ look there! ZX444, ZX474, ZX478, ZX212, ZX214 (10mbps/hd) - + @@ -6184,7 +6184,7 @@ domain; for example, if you are in foo.bar.edu and you wish to reach a host called ``mumble'' in the bar.edu domain, you will have to refer to it by the fully-qualified domain name, ``mumble.bar.edu'', instead of just ``mumble''. - + Traditionally, this was allowed by BSD BIND resolvers. However the current version of bind that ships with FreeBSD no longer provides default abbreviations for non-fully @@ -6192,30 +6192,30 @@ qualified domain names other than the domain you are in. So an unqualified host mumble must either be found as mumble.foo.bar.edu, or it will be searched for in the root domain. - + This is different from the previous behavior, where the search continued across mumble.bar.edu, and mumble.edu. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole. - + As a good workaround, you can place the line - + search foo.bar.edu bar.edu - + instead of the previous - + domain foo.bar.edu - + into your /etc/resolv.conf file. However, make sure that the search order does not go beyond the ``boundary between local and public administration'', as RFC 1535 calls it. - + @@ -6225,21 +6225,21 @@ administration'', as RFC 1535 calls it. option, you need to be aware that the default policy as of 2.1.7R (this actually changed during 2.1-STABLE development) is to deny all packets that are not explicitly allowed. - + If you had unintentionally misconfigured your system for firewalling, you can restore network operability by typing the following while logged in as root: - + ipfw add 65534 allow all from any to any - + You can also set "firewall_type='open'" in /etc/rc.conf. - + For further information on configuring a FreeBSD firewall, see the Handbook section. - + @@ -6249,57 +6249,57 @@ see the Handbook section. speed. For most applications dealing with ethernet and small rule sets, the answer is, negligible. For those of you that need actual measurements to satisfy your curiosity, read on. - + The following measurements were made using 2.2.5-STABLE on a 486-66. IPFW was modified to measure the time spent within the ip_fw_chk routine, displaying the results to the console every 1000 packets. - + Two rule sets, each with 1000 rules were tested. The first set was designed to demonstrate a worst case scenario by repeating the rule: - + ipfw add deny tcp from any to any 55555 - + This demonstrates worst case by causing most of IPFW's packet check routine to be executed before finally deciding that the packet does not match the rule (by virtue of the port number). Following the 999th iteration of this rule was an allow ip from any to any. - + The second set of rules were designed to abort the rule check quickly: - + ipfw add deny ip from 1.2.3.4 to 1.2.3.4 - + The nonmatching source IP address for the above rule causes these rules to be skipped very quickly. As before, the 1000th rule was an allow ip from any to any. - + The per-packet processing overhead in the former case was approximately 2.703ms/packet, or roughly 2.7 microseconds per rule. Thus the theoretical packet processing limit with these rules is around 370 packets per second. Assuming 10Mbps ethernet and a ~1500 byte packet size, we would only be able to achieve a 55.5% bandwidth utilization. - + For the latter case each packet was processed in approximately 1.172ms, or roughly 1.2 microseconds per rule. The theoretical packet processing limit here would be about 853 packets per second, which could consume 10Mbps ethernet bandwidth. - + The excessive number of rules tested and the nature of those rules do not provide a real-world scenario -- they were used only to generate the timing information presented here. Here are a few things to keep in mind when building an efficient rule set: - + @@ -6321,7 +6321,7 @@ statistics with ipfw -a l. - + @@ -6329,54 +6329,54 @@ statistics with ipfw -a l. You can redirect FTP (and other service) request with the 'socket' -package, available in the ports tree in category 'sysutils'. +package, available in the ports tree in category 'sysutils'. Simply replace the service's commandline to call socket instead, like so: - + ftp stream tcp nowait nobody /usr/local/bin/socket socket ftp.foo.com ftp - + where 'ftp.foo.com' and 'ftp' are the host and port to redirect to, respectively. - + Where can I get a bandwidth management tool? -There are two bandwidth management tools available for FreeBSD. +There are two bandwidth management tools available for FreeBSD. ALTQ is available for free; Bandwidth Manager from Emerging Technologies is a commercial product. - + Why do I get “/dev/bpf0: device not configured”? The Berkeley Packet Filter (bpf) driver -needs to be enabled before running programs that utilize it. +needs to be enabled before running programs that utilize it. Add this to your kernel config file and build a new kernel: - + pseudo-device bpfilter # Berkeley Packet Filter - + Secondly, after rebooting you will have to create the device node. This can be accomplished by a change to the /dev directory, followed by the execution of: - + # sh MAKEDEV bpf0 - + Please see the handbook's entry on device nodes for more information on creating devices. - + @@ -6402,34 +6402,34 @@ id="userppp"> You should first read the ppp man page and the ppp section of the handbook. Enable logging with the command - + set log Phase Chat Connect Carrier lcp ipcp ccp command - + This command may be typed at the ppp command prompt or it may be entered in the /etc/ppp/ppp.conf configuration file (the start of the default section is the best place to put it). Make sure that /etc/syslog.conf contains the lines - + !ppp *.* /var/log/ppp.log - + and that the file /var/log/ppp.log exists. You can now find out a lot about what's going on from the log file. Don't worry if it doesn't all make sense. If you need to get help from someone, it may make sense to them. - + If your version of ppp doesn't understand the "set log" command, you should download the latest version. It will build on FreeBSD version 2.1.5 and higher. - + Ppp just hangs when I run it @@ -6440,18 +6440,18 @@ consoluted by your resolver first by editing /etc/host.conf and putting the hosts line first. Then, simply put an entry in /etc/hosts for your local machine. If you have no local network, change your localhost line: - + 127.0.0.1 foo.bar.com foo localhost - + Otherwise, simply add another entry for your host. Consult the relevant man pages for more details. - + You should be able to successfully ping -c1 `hostname` when you're done. - + @@ -6459,76 +6459,76 @@ when you're done. First, check that you've got a default route. By running http://www.FreeBSD.org/cgi/man.cgi?netstat name="netstat -rn">, you should see two entries like this: - + Destination Gateway Flags Refs Use Netif Expire default 10.0.0.2 UGSc 0 0 tun0 10.0.0.2 10.0.0.1 UH 0 0 tun0 - + This is assuming that you've used the addresses from the handbook, the man page or from the ppp.conf.sample file. If you haven't got a default route, it may be because you're running an old version of ppp that doesn't understand the word HISADDR in the ppp.conf file. If your version of ppp is from before FreeBSD 2.2.5, change the - + add 0 0 HISADDR - + line to one saying - + add 0 0 10.0.0.2 - + Another reason for the default route line being missing is that you have mistakenly set up a default router in your /etc/rc.conf file (this file was called /etc/sysconfig prior to release 2.2.2), and you have omitted the line saying - + delete ALL - + from ppp.conf. If this is the case, go back to the Final system configuration section of the handbook. - + What does "No route to host" mean This error is usually due to a missing - + MYADDR: delete ALL add 0 0 HISADDR - + section in your /etc/ppp/ppp.linkup file. This is only necessary if you have a dynamic IP address or don't know the address of your gateway. If you're using interactive mode, you can type the following after entering packet mode (packet mode is indicated by the capitalized PPP in the prompt): - + delete ALL add 0 0 HISADDR - + Refer to the PPP and Dynamic IP addresses section of the handbook for further details. - + @@ -6536,12 +6536,12 @@ for further details. The default ppp timeout is 3 minutes. This can be adjusted with the line - + set timeout NNN - + where NNN is the number of seconds of inactivity before the connection is closed. If NNN is zero, the connection is never closed due to a timeout. It is possible to put this command in @@ -6552,7 +6552,7 @@ the line is active by connecting to ppps server so or pppctl. Refer to the ppp man page for further details. - + @@ -6564,12 +6564,12 @@ machine and the peer. Ppp deduces that the line must therefore be bad, and disconnects. Prior to FreeBSD version 2.2.5, LQR was enabled by default. It is now disabled by default. LQR can be disabled with the line - + disable lqr - + @@ -6578,20 +6578,20 @@ LQR can be disabled with the line Sometimes, on a noisy phone line or even on a line with call waiting enabled, your modem may hang up because it thinks (incorrectly) that it lost carrier. - + There's 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 register in tenths of a second. To make your modem more forgiving, you could add the following send-expect sequence to your dial string: - + set dial "...... ATS10=10 OK ......" - + Refer to your modem manual for details. - + @@ -6600,7 +6600,7 @@ add the following send-expect sequence to your dial string: Many people experience hung connections with no apparent explaination. The first thing to establish is which side of the link is hung. - + If you are using an external modem, you can simply try using ping to see if the TD light is flashing when you transmit data. If it flashes (and the RD light doesn't), the @@ -6616,11 +6616,11 @@ local async and use ping from another w use of the link. The async logging will show you the data being transmitted and received on the link. If data is going out and not coming back, the problem is remote. - + Having established whether the problem is local or remote, you now have two possibilities: - + The remote end isn't responding @@ -6631,35 +6631,35 @@ refuse to help if you're not running a Microsoft OS. You can detect the remote failure and hang up, but this detection is relatively slow and therefore not that useful. You may want to avoid telling your ISP that you're running user-ppp.... - + First, try disabling all local compression by adding the following to your configuration: - + disable pred1 deflate deflate24 protocomp acfcomp shortseq vj deny pred1 deflate deflate24 protocomp acfcomp shortseq vj - + Then reconnect to ensure that this makes no difference. If things improve or if the problem is solved completely, determine which setting makes the difference through trial and error. This will provide good amunition when you contact your ISP (although it may make it apparent that you're not running a Microsoft product). - + Before contacting your ISP, enable async logging locally and wait until the connection hangs again. This may use up quite a bit of disk space. The last data read from the port may be of interest. It is usually ascii data, and may even describe the problem (``Memory fault, core dumped'' ?). - + If your ISP is helpful, they should be able to enable logging on their end, then when the next link drop occurs, they may be able to tell you why their side is having a problem. Feel free to send the details to brian@Awfulhak.org, or even to ask your ISP to contact me directly. - + @@ -6671,9 +6671,9 @@ and STRIP= to the end of the Makefile, then doing a ppp hangs, find the ppp process id with ps ajxww | fgrep ppp and run gdb ppp PID. From the gdb prompt, you can then use bt to get a stack trace. - + Send the results to brian@Awfulhak.org. - + @@ -6684,16 +6684,16 @@ and run gdb ppp PID. From the gdb prompt, you can Protocol (LCP). Many ISPs will not initiate negotiations and expect the client to do so. To force ppp to initiate the LCP, use the following line: - + set openmode active - + Note: It usually does no harm if both sides initiate negotiation, so openmode is now active by default. However, the next section explains when it does do some harm. - + @@ -6706,7 +6706,7 @@ exits. Most ppp implementations cannot survive this problem, and even if the link seems to come up, you'll see repeated configure requests and configure acknowledgements in the log file until ppp eventually gives up and closes the connection. - + This normally happens on server machines with slow disks that are spawning a getty on the port, and executing ppp from a login script or program after login. I've also heard reports @@ -6715,7 +6715,7 @@ that in the time taken between getty exiting and ppp starting, the client-side ppp starts sending Line Control Protocol (LCP) packets. Because ECHO is still switched on for the port on the server, the client ppp sees these packets "reflect" back. - + One part of the LCP negotiation is to establish a magic number for each side of the link so that "reflections" can be detected. The protocol says that when the peer tries to negotiate @@ -6731,29 +6731,29 @@ it's flooded with magic number changes and almost immediately decides it's tried enough to negotiate LCP and gives up. Meanwhile, the client, who no longer sees the reflections, becomes happy just in time to see a hangup from the server. - + This can be avoided by allowing the peer to start negotiating with the following line in your ppp.conf file: - + set openmode passive - + This tells ppp to wait for the server to initiate LCP negotiations. Some servers however may never initiate negotiations. If this is the case, you can do something like: - + set openmode active 3 - + This tells ppp to be passive for 3 seconds, and then to start sending LCP requests. If the peer starts sending requests during this period, ppp will immediately respond rather than waiting for the full 3 second period. - + @@ -6766,7 +6766,7 @@ their original requests. As a result, if one ppp implementation is more than 6 seconds slower than the other side, the other side will send two additional LCP configuration requests. This is fatal. - + Consider two implementations, A and B. A starts sending LCP requests immediately after connecting and B takes 7 seconds to start. When B starts, A has sent 3 LCP @@ -6786,39 +6786,39 @@ to the ACK-SENT state and sending another (second) (forth) ACK as per the RFC. A gets the REQ, goes into REQ-SENT and sends another REQ. It immediately receives the following ACK and enters OPENED. - + This goes on 'till one side figures out that they're getting nowhere and gives up. - + The best way to avoid this is to configure one side to be passive - that is, make one side wait for the other to start negotiating. This can be done with the - + set openmode passive - + command. Care should be taken with this option. You should also use the - + set stopped N - + command to limit the amount of time that ppp waits for the peer to begin negotiations. Alternatively, the - + set openmode active N - + command (where N is the number of seconds to wait before starting negotiations) can be used. Check the manual page for details. - + @@ -6831,12 +6831,12 @@ only happen if both sides tried to negotiate different Compression Control Protocols (CCP). This problem is now corrected, but if you're still running an old version of ppp, the problem can be circumvented with the line - + disable pred1 - + @@ -6849,11 +6849,11 @@ to complete before continuing. If you attempt to use the ppp link while running the command, the link will appear to have frozen. This is because ppp is waiting for the command to complete. - + If you wish to execute commands like this, use the !bg command instead. This will execute the given command in the background, and ppp can continue to service the link. - + @@ -6864,14 +6864,14 @@ a direct connection has been dropped. This is due to the lines that are used in a null-modem serial cable. When using this sort of connection, LQR should always be enabled with the line - + enable lqr - + LQR is accepted by default if negotiated by the peer. - + @@ -6879,78 +6879,78 @@ the line If ppp is dialing unexpectedly, you must determine the cause, and set up Dial filters (dfilters) to prevent such dialing. - + To determine the cause, use the following line: - + set log +tcp/ip - + This will log all traffic through the connection. The next time the line comes up unexpectedly, you will see the reason logged with a convenient timestamp next to it. - + You can now disable dialing under these circumstances. Usually, this sort of problem arises due to DNS lookups. To prevent DNS lookups from establishing a connection (this will not prevent ppp from passing the packets through an established connection), use the following: - + set dfilter 1 deny udp src eq 53 set dfilter 2 deny udp dst eq 53 set dfilter 3 permit 0/0 0/0 - + This is not always suitable, as it will effectively break your demand-dial capabilities - most programs will need a DNS lookup before doing any other network related things. - + In the DNS case, you should try to determine what is actually -trying to resolve a host name. A lot of the time, +trying to resolve a host name. A lot of the time, sendmail is the culprit. You should make sure that you tell sendmail not to do any DNS lookups in its configuration file. See the section on Mail Configuration 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 file: - + define(`confDELIVERY_MODE', `d')dnl - + This will make sendmail queue everything until the queue is run (usually, sendmail is invoked with ``-bd -q30m'', telling it to run the queue every 30 minutes) or until a ``sendmail -q'' is done (perhaps from your ppp.linkup file). - + What do these CCP errors mean I keep seeing the following errors in my log file: - + CCP: CcpSendConfigReq CCP: Received Terminate Ack (1) state = Req-Sent (6) - + This is because ppp is trying to negotiate Predictor1 compression, and the peer does not want to negotiate any compression at all. The messages are harmless, but if you wish to remove them, you can disable Predictor1 compression locally too: - + disable pred1 - + @@ -6960,17 +6960,17 @@ locally too: driver that prevents incoming packets of a size larger than the tun interface's MTU size. Receipt of a packet greater than the MTU size results in an IO error being logged via syslogd. - + The ppp specification says that an MRU of 1500 should always be accepted as a minimum, despite any LCP negotiations, therefore it is possible that should you decrease the MTU to less than 1500, your ISP will transmit packets of 1500 regardless, and you will tickle this non-feature - locking up your link. - + The problem can be circumvented by never setting an MTU of less than 1500 under FreeBSD 2.2.2 or before. - + @@ -6978,30 +6978,30 @@ less than 1500 under FreeBSD 2.2.2 or before. In order to log all lines of your modem ``conversation'', you must enable the following: - + set log +connect - -This will make + +This will make ppp log everything up until the last requested "expect" string. - + If you wish to see your connect speed and are using PAP or CHAP (and therefore don't have anything to "chat" after the CONNECT in the dial script - no "set login" script), you must make sure that you instruct ppp to "expect" the whole CONNECT line, something like this: - + set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n" - + Here, we get our CONNECT, send nothing, then expect a line-feed, forcing ppp to read the whole CONNECT response. - + @@ -7012,23 +7012,23 @@ interpret strings such as set phone "123 456 789" (and realize that the number is actually only one argument. In order to specify a “"” character, you must escape it using a backslash (“\”). - + When the chat interpreter parses each argument, it re-interprets the argument in order to find any special escape sequences such as “\P” or “\T” (see the man page). As a result of this double-parsing, you must remember to use the correct number of escapes. - + If you wish to actually send a “\” character to (say) your modem, you'd need something like: - + set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK" - + resulting in the following sequence: - + ATZ OK @@ -7036,24 +7036,24 @@ modem, you'd need something like: OK - + or - + set phone 1234567 set dial "\"\" ATZ OK ATDT\\T" - + resulting in the following sequence: - + ATZ OK ATDT1234567 - + @@ -7067,7 +7067,7 @@ termating due to a segmentation violation or some other signal that normally causes core to be dumped, and you're sure you're using the latest version (see the start of this section), then you should do the following: - + $ tar xfz ppp-*.src.tar.gz $ cd ppp*/ppp @@ -7079,16 +7079,16 @@ section), then you should do the following: # chmod 555 /usr/sbin/ppp - + You will now have a debuggable version of ppp installed. You will have to be root to run ppp as all of its privileges have been revoked. When you start ppp, take a careful note of what your current directory was at the time. - + Now, if and when ppp receives the segmentation violation, it will dump a core file called ppp.core. You should then do the following: - + $ su # gdb /usr/sbin/ppp ppp.core @@ -7102,14 +7102,14 @@ following: ..... - + All of this information should be given alongside your question, making it possible to diagnose the problem. - + If you're familiar with gdb, you may wish to find out some other bits and pieces such as what actually caused the dump and the addresses & values of the relevant variables. - + @@ -7119,7 +7119,7 @@ the addresses & values of the relevant variables. This was a known problem with ppp set up to negotiate a dynamic local IP number with the peer in auto mode. It is fixed in the latest version - search the man page for iface. - + The problem was that when that initial program calls connect(2), the IP number of the tun interface is assigned to the socket endpoint. The kernel creates the first @@ -7130,12 +7130,12 @@ the original socket endpoint will be invalid. Any subsequent packets sent to the peer will usually be dropped. Even if they aren't, any responses will not route back to the originating machine as the IP number is no longer owned by that machine. - + There are several theoretical ways to approach this problem. It would be nicest if the peer would re-assign the same IP number if possible :-) The current version of ppp does this, but most other implementations don't. - + The easiest method from our side would be to never change the tun interface IP number, but instead to change all outgoing packets so that the source IP number is changed from the interface IP to @@ -7144,14 +7144,14 @@ the negotiated IP on the fly. This is essentially what the doing (with the help of libalias(3) and ppp's switch) - it's maintaining all previous interface addresses and NATing them to the last negotiated address. - + Another alternative (and probably the most reliable) would be to implement a system call that changes all bound sockets from one IP to another. Ppp would use this call to modify the sockets of all existing programs when a new IP number is negotiated. The same system call could be used by dhcp clients when they are forced to re-bind() their sockets. - + Yet another possibility is to allow an interface to be brought up without an IP number. Outgoing packets would be given an IP number of 255.255.255.255 up until the first SIOCAIFADDR @@ -7162,7 +7162,7 @@ would need to change. This, however is a bit of a hack as the kernel would be sending bad packets to an improperly configured interface, on the assumption that some other mechanism is capable of fixing things retrospectively. - + @@ -7173,12 +7173,12 @@ in use is that the machine on the outside will try to open a connection or send (unsolicited) UDP packets to the machine on the inside. The NAT software doesn't know that it should send these packets to the interior machine. - + To make things work, make sure that the only thing running is the software that you're having problems with, then either run tcpdump on the tun interface of the gateway or enable ppp tcp/ip logging (``set log +tcp/ip'') on the gateway. - + When you start the offending software, you should see packets passing through the gateway machine. When something comes back from the outside, it'll be dropped (that's the problem). Note @@ -7186,26 +7186,26 @@ the port number of these packets then shut down the offending software. Do this a few times to see if the port numbers are consistent. If they are, then the following line in the relevant section of /etc/ppp/ppp.conf will make the software functional: - + nat port proto internalmachine:port port - + where ``proto'' is either ``tcp'' or ``udp'', ``internalmachine'' is the machine that you want the packets to be sent to and ``port'' is the destination port number of the packets. - + You won't be able to use the software on other machines without changing the above command, and running the software on two internal machines at the same time is out of the question - after all, the outside world is seeing your entire internal network as being just a single machine. - + If the port numbers aren't consistent, there are three more options: - + 1) Submit support in libalias. Examples of ``special cases'' can be found in /usr/src/lib/libalias/alias_*.c (alias_ftp.c is a good prototype). This usually involves reading certain @@ -7214,19 +7214,19 @@ tells the outside machine to initiate a connection back to the internal machine on a specific (random) port and setting up a ``route'' in the alias table so that the subsequent packets know where to go. - + This is the most difficult solution, but it is the best and will make the software work with multiple machines. - + 2) Use a proxy. The application may support socks5 for example, or (as in the ``cvsup'' case) may have a ``passive'' option that avoids ever requesting that the peer open connections back to the local machine. - + 3) Redirect everything to the internal machine using ``nat addr''. This is the sledge-hammer approach. - + Has anybody made a list of useful port numbers ? @@ -7234,7 +7234,7 @@ back to the local machine. Not yet, but this is intended to grow into such a list (if any interest is shown). In each example, internal should be replaced with the IP number of the machine playing the game. - + @@ -7250,7 +7250,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7263,7 +7263,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7278,7 +7278,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7291,7 +7291,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7306,7 +7306,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7318,14 +7318,14 @@ being received is the data being sent. If the FCS of an incoming packet is incorrect, the packet is dropped and the HDLC FCS count is increased. The HDLC error values can be displayed using the show hdlc command. - + If your link is bad (or if your serial driver is dropping packets), you will see the occasional FCS error. This is not usually worth worrying about although it does slow down the compression protocols substantially. If you have an external modem, make sure your cable is properly shielded from interference - this may eradicate the problem. - + If your link freezes as soon as you've connected and you see a large number of FCS errors, this may be because your link is not 8 bit clean. Make sure your modem is not using software @@ -7333,7 +7333,7 @@ flow control (XON/XOFF). If your datalink must us software flow control, use the command set accmap 0x000a0000 to tell ppp to escape the ^Q and ^S characters. - + Another reason for seeing too many FCS errors may be that the remote end has stopped talking PPP. You may want to enable async logging at this point to determine if the @@ -7342,11 +7342,11 @@ have a shell prompt at the remote end, it's possible to terminate ppp without dropping the line by using the close lcp command (a following term command will reconnect you to the shell on the remote machine. - + If nothing in your log file indicates why the link might have been terminated, you should ask the remote administrator (your ISP?) why the session was terminated. - + @@ -7412,7 +7412,7 @@ the relevant parts of your log file and the output of the freebsd-questions@FreeBSD.org mailing list or the comp.unix.bsd.freebsd.misc news group, and someone should point you in the right direction. - + @@ -7423,7 +7423,7 @@ id="serial"> This section answers common questions about serial communications with FreeBSD. PPP and SLIP are covered in the section. - + How do I tell if FreeBSD found my serial ports? @@ -7432,16 +7432,16 @@ with FreeBSD. PPP and SLIP are covered in the - + dmesg | grep sio - + after your system's up and running. - + Here's some example output from the above command: - + sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -7449,14 +7449,14 @@ run the command sio1: type 16550A - + This shows two serial ports. The first is on irq 4, is using port address 0x3f8, and has a 16550A-type UART chip. The second uses the same kind of chip but is on irq 3 and is at port address 0x2f8. Internal modem cards are treated just like serial ports---except that they always have a modem ``attached'' to the port. - + The GENERIC kernel includes support for two serial ports using the same irq and port address settings in the above example. If these settings aren't right for your system, or if @@ -7464,14 +7464,14 @@ you've added modem cards or have more serial ports than your kernel is configured for, just reconfigure your kernel. See section about building a kernel for more details. - + How do I tell if FreeBSD found my modem cards? Refer to the answer to the previous question. - + @@ -7479,7 +7479,7 @@ more details. Don't worry, they have been merged with the ttydX devices. You'll have to change any old configuration files you have, though. - + @@ -7489,7 +7489,7 @@ You'll have to change any old configuration files you have, though. COM3 in DOS), is on /dev/cuaa2 for dial-out devices, and on /dev/ttyd2 for dial-in devices. What's the difference between these two classes of devices? - + You use ttydX for dial-ins. When opening /dev/ttydX in blocking mode, a process will wait for the corresponding cuaaX device to become inactive, and then wait @@ -7501,7 +7501,7 @@ device doesn't care about carrier detect. With this scheme and an auto-answer modem, you can have remote users log in and you can still dialout with the same modem and the system will take care of all the conflicts. - + @@ -7515,9 +7515,9 @@ specifiers on only one of the entries. All of the ports on the card should share one irq. For consistency, use the last serial port to specify the irq. Also, specify the COM_MULTIPORT option. - + The following example is for an AST 4-port serial card on irq 7: - + options "COM_MULTIPORT" device sio4 at isa? port 0x2a0 tty flags 0x781 @@ -7526,18 +7526,18 @@ option. device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - + The flags indicate that the master port has minor number 7 (0x700), diagnostics enabled during probe (0x080), and all the ports share an irq (0x001). - + Can FreeBSD handle multiport serial cards sharing irqs? Not yet. You'll have to use a different irq for each card. - + @@ -7547,45 +7547,45 @@ all the ports share an irq (0x001). you'll want to open for your applications. When a process opens the device, it'll have a default set of terminal I/O settings. You can see these settings with the command - + stty -a -f /dev/ttyd1 - + When you change the settings to this device, the settings are in effect until the device is closed. When it's reopened, it goes back to the default set. To make changes to the default set, you can open and adjust the settings of the ``initial state'' device. For example, to turn on CLOCAL mode, 8 bits, and XON/XOFF flow control by default for ttyd5, do: - + stty -f /dev/ttyid5 clocal cs8 ixon ixoff - + A good place to do this is in /etc/rc.serial. Now, an application will have these settings by default when it opens ttyd5. It can still change these settings to its liking, though. - + You can also prevent certain settings from being changed by an application by making adjustments to the ``lock state'' device. For example, to lock the speed of ttyd5 to 57600 bps, do - + stty -f /dev/ttyld5 57600 - + Now, an application that opens ttyd5 and tries to change the speed of the port will be stuck with 57600 bps. - + Naturally, you should make the initial state and lock state devices writable only by root. The MAKEDEV script does NOT do this when it creates the device entries. - + @@ -7601,27 +7601,27 @@ flow control or no local flow control at all. Finally, it must use a constant speed between the computer and itself, but (to be nice to your callers) it should negotiate a speed between itself and the remote modem. - + For many Hayes command-set--compatible modems, this command will make these settings and store them in nonvolatile memory: - + AT &C1 &D3 &K3 &Q6 S0=1 &W - + See the section on sending AT commands below for information on how to make these settings without resorting to an MS-DOS terminal program. - + Next, make an entry in /etc/ttys for the modem. This file lists all the ports on which the operating system will await logins. Add a line that looks something like this: - + ttyd1 "/usr/libexec/getty std.57600" dialup on insecure - + This line indicates that the second serial port (/dev/ttyd1) has a modem connected running at 57600 bps and no parity (std.57600, which comes from the file @@ -7629,7 +7629,7 @@ and no parity (std.57600, which comes from the fil ``dialup.'' The port is ``on'' and is ``insecure''---meaning root logins on the port aren't allowed. For dialin ports like this one, use the ttydX entry. - + It's common practice to use ``dialup'' as the terminal type. Many users set up in their .profile or .login files a prompt for the actual terminal type if the starting type is dialup. The @@ -7637,31 +7637,31 @@ example shows the port as insecure. To become root on this port, you have to login as a regular user, then ``su'' to root. If you use ``secure'' then root can login in directly. - + After making modifications to /etc/ttys, you need to send a hangup or HUP signal to the init process: - + kill -HUP 1 - + This forces the init process to reread /etc/ttys. The init process will then start getty processes on all ``on'' ports. You can find out if logins are available for your port by typing - + ps -ax | grep '[t]tyd1' - + You should see something like: - + 747 ?? I 0:00.04 /usr/libexec/getty std.57600 ttyd1 - + @@ -7671,19 +7671,19 @@ You can find out if logins are available for your port by typing system, get a null modem cable to go between the two serial ports. If you're using an actual terminal, see its accompanying instructions. - + Then, modify /etc/ttys, like above. For example, if you're hooking up a WYSE-50 terminal to the fifth serial port, use an entry like this: - + ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure - + This example shows that the port on /dev/ttyd4 has a wyse50 terminal connected at 38400 bps with no parity (std.38400 from /etc/gettytab) and root logins are allowed (secure). - + @@ -7693,16 +7693,16 @@ wyse50 terminal connected at 38400 bps with no parity executable only by uucp and group dialer. You can use the group dialer to control who has access to your modem or remote systems. Just add yourself to group dialer. - + Alternatively, you can let everyone on your system run tip and cu by typing: - + # chmod 4511 /usr/bin/cu # chmod 4511 /usr/bin/tip - + @@ -7711,26 +7711,26 @@ and cu by typing: Actually, the man page for tip is out of date. There is a generic Hayes dialer already built in. Just use ``at=hayes'' in your /etc/remote file. - + The Hayes driver isn't smart enough to recognize some of the advanced features of newer modems---messages like BUSY, NO DIALTONE, or CONNECT 115200 will just confuse it. You should turn those messages off when you use tip (using ATX0&W). - + Also, the dial timeout for tip is 60 seconds. Your modem should use something less, or else tip will think there's a communication problem. Try ATS7=45&W. - + Actually, as shipped tip doesn't yet support it fully. The solution is to edit the file tipconf.h in the directory /usr/src/usr.bin/tip/tip. Obviously you need the source distribution to do this. - + Edit the line ``#define HAYES 0'' to ``#define HAYES 1''. Then ``make'' and ``make install''. Everything works nicely after that. - + /etc/remote file. For example, if your modem's hooked up to the first serial port, /dev/cuaa0, then put in the following line: - + cuaa0:dv=/dev/cuaa0:br#19200:pa=none - + Use the highest bps rate your modem supports in the br capability. Then, type tip cuaa0 and you'll be connected to your modem. - + If there is no /dev/cuaa0 on your system, do this: - + # cd /dev # ./MAKEDEV cuaa0 - + Or use cu as root with the following command: - + # cu -l``line'' -s``speed'' - + with line being the serial port (e.g./dev/cuaa0) and speed being the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit. - + @@ -7780,12 +7780,12 @@ entering the AT commands hit ~. to exit. /etc/phones for a phone number. But the <@> sign is also a special character in capability files like /etc/remote. Escape it with a backslash: - + pn=\@ - + @@ -7793,7 +7793,7 @@ also a special character in capability files like Put what's called a ``generic'' entry in your /etc/remote file. For example: - + tip115200|Dial any phone number at 115200 bps:\ :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: @@ -7801,19 +7801,19 @@ also a special character in capability files like :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: - + Then you can do something like ``tip -115200 5551234''. If you prefer cu over tip, use a generic cu entry: - + cu115200|Use cu to dial any number at 115200bps:\ :dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du: - + and type ``cu 5551234 -s 115200''. - + @@ -7823,7 +7823,7 @@ generic cu entry: use whatever bps rate is appropriate with the br capability. tip thinks a good default is 1200 bps which is why it looks for a ``tip1200'' entry. You don't have to use 1200 bps, though. - + @@ -7833,7 +7833,7 @@ You don't have to use 1200 bps, though. ``CONNECT <host>'' each time, use tip's cm capability. For example, these entries in /etc/remote: - + pain|pain.deep13.com|Forrester's machine:\ :cm=CONNECT pain\n:tc=deep13: @@ -7843,11 +7843,11 @@ capability. For example, these entries in :dv=/dev/cua02:br#38400:at=hayes:du:pa=none:pn=5551234: - + will let you type ``tip pain'' or ``tip muffin'' to connect to the hosts pain or muffin; and ``tip deep13'' to get to the terminal server. - + @@ -7855,10 +7855,10 @@ get to the terminal server. This is often a problem where a university has several modem lines and several thousand students trying to use them... - + Make an entry for your university in /etc/remote and use <\@> for the pn capability: - + big-university:\ :pn=\@:tc=dialout @@ -7866,10 +7866,10 @@ and use <\@> for the pn - + Then, list the phone numbers for the university in /etc/phones: - + big-university 5551111 big-university 5551112 @@ -7877,37 +7877,37 @@ and use <\@> for the pn - + tip will try each one in the listed order, then give up. If you want to keep retrying, run tip in a while loop. - + Why do I have to hit CTRL+P twice to send CTRL+P once? -CTRL+P is the default ``force'' character, used to tell +CTRL+P is the default ``force'' character, used to tell tip that the next character is literal data. You can set the force character to any other character with the ~s escape, which means ``set a variable.'' - + Type ``~sforce=<single-char>'' followed by a newline. <single-char> is any single character. If you leave out <single-char>, then the force character is the nul character, which you can get by typing CTRL+2 or CTRL+SPACE. A pretty good value for <single-char> is SHIFT+CTRL+6, which I've seen only used on some terminal servers. - + You can have the force character be whatever you want by specifying the following in your $HOME/.tiprc file: - + force=<single-char> - + @@ -7918,18 +7918,18 @@ character,'' specially designed for people with broken caps-lock keys. Use ~s as above and set the variable ``raisechar'' to something reasonable. In fact, you can set it to the same as the force character, if you never expect to use either of these features. - + Here's a sample .tiprc file perfect for Emacs users who need to type CTRL+2 and CTRL+A a lot: - + force=^^ raisechar=^^ - + The ^^ is SHIFT+CTRL+6. - + @@ -7939,16 +7939,16 @@ type CTRL+2 and CTRL+A a lot: receive files with ~p (put) and ~t (take). These commands run cat and echo on the remote system to accept and send files. The syntax is: - + ~p <local-file> [<remote-file>] ~t <remote-file> [<local-file>] - + There's no error checking, so you probably should use another protocol, like zmodem. - + @@ -7958,16 +7958,16 @@ protocol, like zmodem. collection (such as one of the two from the comms category, lrzsz and rzsz). - + To receive files, start the sending program on the remote end. Then, press enter and type ``~C rz'' (or ``~C lrz'' if you installed lrzsz) to begin receiving them locally. - + To send files, start the receiving program on the remote end. Then, press enter and type ``~C sz <files>'' (or ``~C lsz <files>'') to send them to the remote system. - + @@ -7975,9 +7975,9 @@ remote system. settings are correct. Motherboards and cards with Acer UARTs do not probe properly under -the FreeBSD sio probe. Obtain a patch from +the FreeBSD sio probe. Obtain a patch from www.lemis.com to fix your problem. - + @@ -7993,16 +7993,16 @@ id="misc"> 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 entirely idle, unused pages -of main memory into swap in order to make more main memory available +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 does not + +Note that while FreeBSD is proactive in this regard, it does not arbitrarily decide to swap pages when the system is truely idle. Thus you will not find your system all paged out when you get up in the morning after leaving it idle overnight. - + @@ -8012,7 +8012,7 @@ morning after leaving it idle overnight. To understand why FreeBSD uses the a.out format, you must first know a little about the 3 currently "dominant" executable formats for UNIX: - + @@ -8057,13 +8057,13 @@ Solaris, SCO) does it hold true. FreeBSD tries to work around this problem somewhat by providing a utility for branding a known ELF executable with information about the ABI it's compliant with. -See the man page for +See the man page for brandelf for more information. - + FreeBSD comes from the "classic" camp and has traditionally used the a.out format, a technology tried and proven through many generations of BSD releases. Though it has also been possible @@ -8079,11 +8079,11 @@ tools available offered a solution to the shared library problem and were generally seen as "the way forward" anyway, the migration cost was accepted as necessary and the transition made. - + In FreeBSD's case, our shared library mechanism is based more closely on Sun's SunOS-style shared library mechanism and, as such, is very -easy to use. +easy to use. However, starting with 3.0, FreeBSD officially supports ELF binaries as the default format. Even though the a.out executable format has served us well, the GNU people, who author the @@ -8093,7 +8093,7 @@ the compler and linker, and has kept us from reaping the benefits of the latest GNU development efforts. Also the demands of ISO-C++, notably contstructors and destructors, has also led to native ELF support in future FreeBSD releases. - + @@ -8107,7 +8107,7 @@ simple system (a PDP-11). As people ported unix from this simple system, they retained the a.out format because it was sufficient for the early ports of unix to architectures like the Motorola 68k, VAXen, etc. - + Then some bright hardware engineer decided that if he could force software to do some sleazy tricks, then he'd be able to shave a few gates off the design and allow his CPU core to run @@ -8118,7 +8118,7 @@ better performance from this hardware than the limited, simple a.out format could offer. Things like COFF, ECOFF, and a few obscure others were invented and their limitations explored before things seemed to settle on ELF. - + In addition, program sizes were getting huge and disks (and physical memory) were still relatively small so the concept of a shared library was born. The VM system also became more @@ -8137,7 +8137,7 @@ While ELF solved many of these problems, it would be painful to switch from the system that basically worked. So ELF had to wait until it was more painful to remain with a.out than it was to migrate to ELF. - + However, as time passed, the build tools that FreeBSD derived their build tools from (the assembler and loader especially) evolved in two parallel trees. The FreeBSD tree added shared @@ -8155,7 +8155,7 @@ binaries, why bother having a.out any more? It is a tired old horse that has proven useful for a long time, but it is time to turn him out to pasture for his long, faithful years of service. - + ELF is more expressive than a.out and will allow more extensibility in the base system. The ELF tools are better maintained, and offer cross compilation support, which is @@ -8167,14 +8167,14 @@ important, but they are differences. In time support for a.out will be moved out of the GENERIC kernel, and eventually removed from the kernel once the need to run legacy a.out programs is past. - + Why won't chmod change the permissions on symlinks? Symlinks do not have permissions, and by default, - &man.chmod.1; will not follow symlinks to change the permissions + &man.chmod.1; will not follow symlinks to change the permissions on the target file. So if you have a file, foo, and a symlink to that file, bar, then this command will always @@ -8184,12 +8184,12 @@ eventually removed from the kernel once the need to run legacy However, the permissions on foo will not have changed. - + You have to use either ``'' or ``'' together with -the ``'' option to make this work. See the chmod and +the ``'' option to make this work. See the chmod and symlink man pages for more info. - + WARNING the ``'' option does a RECURSIVE chmod. Be careful about specifying directories or symlinks to directories to chmod. If you want to change the @@ -8199,16 +8199,16 @@ without any options and follow the symlink with a trailing slash (``/''). For example, if ``foo'' is a symlink to directory ``bar'', and you want to change the permissions of ``foo'' (actually ``bar''), you would do something like: - + chmod 555 foo/ - + With the trailing slash, chmod will follow the symlink, ``foo'', to change the permissions of the directory, ``bar''. - + @@ -8224,13 +8224,13 @@ this get you log files which are trashed (due to variable-length records getting written when fixed records were expected), but it can break Sun's NIS clients and potentially cause other problems in interacting with other UNIX systems. - + In FreeBSD 3.0 and later, the maximum name length has been increased to 16 characters and those various utilities with hard-coded name sizes have been found and fixed. The fact that this touched so many areas of the system is why, in fact, the change was not made until 3.0. - + If you're absolutely confident in your ability to find and fix these sorts of problems for yourself when and if they pop up, you can increase the login name length in earlier releases by editing @@ -8239,7 +8239,7 @@ also update MAXLOGNAME in /usr/include/sys/param.h to match the UT_NAMESIZE change. Finally, if you build from sources, don't forget that /usr/include is updated each time! Change the appropriate files in /usr/src/.. instead. - + @@ -8249,13 +8249,13 @@ files in /usr/src/.. instead. DOS emulation which has been integrated and enhanced. Send mail to The FreeBSD emulation discussion list if you're interested in joining this ongoing effort! - -For pre-3.0 systems, there is a neat utility called + +For pre-3.0 systems, there is a neat utility called pcemu in the ports collection which emulates an 8088 and enough BIOS services to run DOS text mode applications. It requires the X Window System (provided as XFree86). - + @@ -8266,11 +8266,11 @@ System (provided as XFree86). stands for Software Update Protocol, and was developed by CMU for keeping their development trees in sync. We used it to keep remote sites in sync with our central development sources. - + SUP is not bandwidth friendly, and has been retired. The current recommended method to keep your sources up to date is Handbook entry on CVSup - + @@ -8279,7 +8279,7 @@ recommended method to keep your sources up to date is 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 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 @@ -8291,13 +8291,13 @@ volunteers were wandering out of the room during the tests, thus skewing the results. I think most of the volunteers are at Apple now, working on their new ``scratch and sniff'' GUI. It's a funny old business we're in! - + 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 (automatic power management) configured, then FreeBSD can also put the CPU into a low power mode. - + @@ -8308,14 +8308,14 @@ 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 strange scratchy sound emanates from what appears to be the memory banks. - + A. Yes! You'll see frequent references to ``daemons'' in the BSD documentation, and what most people don't know is that this refers to genuine, non-corporeal entities that now possess your computer. The scratchy sound coming from your memory is actually high-pitched whispering exchanged among the daemons as they best decide how to deal with various system administration tasks. - + If the noise gets to you, a good ``fdisk /mbr'' from DOS will get rid of them, but don't be surprised if they react adversely and try to stop you. In fact, if at any point during @@ -8326,7 +8326,7 @@ twin demons of DOS and Windows are often able to re-assert total control over your machine to the eternal damnation of your soul. Given a choice, I think I'd prefer to get used to the scratchy noises, myself! - + @@ -8335,7 +8335,7 @@ noises, myself! MFC is an acronym for 'Merged From -CURRENT.' It's used in the CVS logs to denote when a change was migrated from the CURRENT to the STABLE branches. - + @@ -8346,110 +8346,110 @@ members can know. It doesn't translate literally but its ok 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.' :-) - + 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. - + How many FreeBSD hackers does it take to change a lightbulb? One thousand, one hundred and seventy-two: - + Twenty-three to complain to -CURRENT about the lights being out; - + Four to claim that it is a configuration problem, and that such matters really belong on -questions; - + Three to submit PRs about it, one of which is misfiled under doc and consists only of "it's dark"; - + One to commit an untested lightbulb which breaks buildworld, then back it out five minutes later; - + Eight to flame the PR originators for not including patches in their PRs; - + Five to complain about buildworld being broken; - + Thirty-one to answer that it works for them, and they must have cvsupped at a bad time; - + One to post a patch for a new lightbulb to -hackers; - + One to complain that he had patches for this three years ago, but when he sent them to -CURRENT they were just ignored, and he has had bad experiences with the PR system; besides, the proposed new lightbulb is non-reflexive; - + Thirty-seven to scream that lightbulbs do not belong in the base system, that committers have no right to do things like this without consulting the Community, and WHAT IS -CORE DOING ABOUT IT!? - + Two hundred to complain about the color of the bicycle shed; - + Three to point out that the patch breaks style(9); - + Seventeen to complain that the proposed new lightbulb is under GPL; - + Five hundred and eighty-six to engage in a flame war about the comparative advantages of the GPL, the BSD license, the MIT license, the NPL, and the personal hygiene of unnamed FSF founders; - + Seven to move various portions of the thread to -chat and -advocacy; - + One to commit the suggested lightbulb, even though it 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 with a dim lightbulb; - + Forty-six to argue vociferously about the backing out of the dim lightbulb and demanding a statement from -core; - + Eleven to request a smaller lightbulb so it will fit their Tamagotchi if we ever decide to port FreeBSD to that platform; - + Seventy-three to complain about the SNR on -hackers and -chat and unsubscribe in protest; - + Thirteen to post "unsubscribe", "How do I unsubscribe?", or "Please remove me from the list", followed by the usual footer; - + One to commit a working lightbulb while everybody is too busy flaming everybody else to notice; - + 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 switch to TenDRA instead of EGCS; - + One to complain that the new lightbulb lacks fairings; - + Nine (including the PR originators) to ask "what is MFC?"; - + Fifty-seven to complain about the lights being out two weeks after the bulb has been changed. - + Nik Clayton adds: - + I was laughing quite hard at this. - + And then I thought, "Hang on, shouldn't there be '1 to document it.' in that list somewhere?" - + And then I was enlightened :-) - + This entry is Copyright (c) 1999 Dag-Erling Coïdan Smørgrav. Please do not reproduce without attribution. @@ -8466,7 +8466,7 @@ id="hackers"> There are currently three active/semi-active branches in the FreeBSD CVS Repository: - + @@ -8488,19 +8488,19 @@ id="hackers"> - + HEAD is not an actual branch tag, like the other two, it's simply a symbolic constant for "the current, non-branched development stream" which we simply refer to as . - + Right now, is the 5.0 development stream and the 4-STABLE branch, RELENG_4, forked off from in Mar 2000. - + The 2.2-STABLE branch, RELENG_2_2, departed -CURRENT in November 1996, and has pretty much been retired. - + To make a release you need to do three things: First, you need to be running a kernel with the vn driver configured in. Add this to your kernel config file and build a new kernel: - + pseudo-device vn #Vnode driver (turns a file into a device) - + Second, you have to have the whole CVS repository at hand. To get this you can use CVSUP but in your supfile set the release name to cvs and remove any tag or date fields: - + *default prefix=/home/ncvs *default base=/a @@ -8540,21 +8540,21 @@ date fields: doc-all - + Then run cvsup -g supfile to suck all the good bits onto your box... - + Finally, you need a chunk of empty space to build into. Let's say it's in /some/big/filesystem, and from the example above you've got the CVS repository in /home/ncvs: - + setenv CVSROOT /home/ncvs # or export CVSROOT=/home/ncvs cd /usr/src/release make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release - + An entire release will be built in /some/big/filesystem/release and you will have a full FTP-type installation in /some/big/filesystem/release/R/ftp when you're @@ -8562,7 +8562,7 @@ done. If you want to build your SNAP along some other branch than -CURRENT, you can also add RELEASETAG=SOMETAG to the make release command line above, e.g. RELEASETAG=RELENG_2_2 would build an up-to-the- minute 2.2-STABLE snapshot. - + @@ -8574,7 +8574,7 @@ binary archives is automated by various targets in be enough to get you started. However, it should be said that this involves doing a ``make world'' and will therefore take up a lot of time and disk space. - + @@ -8584,7 +8584,7 @@ time and disk space. ``make world'' rebuilds every system binary from scratch, so you can be certain of having a clean and consistent environment at the end (which is why it takes so long). - + If the environment variable DESTDIR is defined while running ``make world'' or ``make install'', the newly-created binaries will be deposited in a directory tree identical to the @@ -8592,7 +8592,7 @@ installed one, rooted at ${DESTDIR}. Some random combination of shared libraries modifications and program rebuilds can cause this to fail in ``make world'', however. - + @@ -8608,7 +8608,7 @@ configuration option in order to have this take place. Using it on those systems where it works may make your disks run faster, but on those systems where it doesn't, your data could be corrupted. - + Yes, you can do this without downloading the whole source tree by using the CTM facility. - + @@ -8626,9 +8626,9 @@ by using the CTM facility.

Newer BSD based systems have a ``'' option to split that allows them to split files on arbitrary byte boundaries. - + Here is an example from /usr/src/Makefile. - + bin-tarball: (cd ${DISTDIR}; \ @@ -8638,23 +8638,23 @@ allows them to split files on arbitrary byte boundaries. ${RELEASEDIR}/tarballs/bindist/bin_tgz.) - + I've written a kernel extension, who do I send it to? Please take a look at The Handbook entry on how to submit code. - + And thanks for the thought! - + How are Plug N Play ISA cards detected and initialized? By: Frank Durda IV - + In a nutshell, there a few I/O ports that all of the PnP boards respond to when the host asks if anyone is out there. So when the PnP probe routine starts, he asks if there are any PnP boards @@ -8673,30 +8673,30 @@ repeating this semi-binary search of IDs-in-range enough times, the probing code will eventually identify all PnP boards present in a given machine with a number of iterations that is much lower than what 2^64 would take. - + The IDs are two 32-bit fields (hence 2ˆ64) + 8 bit checksum. The first 32 bits are a vendor identifier. They never come out and say it, but it appears to be assumed that different types of boards from the same vendor could have different 32-bit vendor ids. The idea of needing 32 bits just for unique manufacturers is a bit excessive. - + The lower 32 bits are a serial #, ethernet address, something that makes this one board unique. The vendor must never produce a second board that has the same lower 32 bits unless the upper 32 bits are also different. So you can have multiple boards of the same type in the machine and the full 64 bits will still be unique. - + The 32 bit groups can never be all zero. This allows the wired-OR to show non-zero bits during the initial binary search. - + Once the system has identified all the board IDs present, it will reactivate each board, one at a time (via the same I/O ports), and find out what resources the given board needs, what interrupt choices are available, etc. A scan is made over all the boards to collect this information. - + This info is then combined with info from any ECU files on the hard disk or wired into the MLB BIOS. The ECU and BIOS PnP support for hardware on the MLB is usually synthetic, and the @@ -8704,16 +8704,16 @@ peripherals don't really do genuine PnP. However by examining the BIOS info plus the ECU info, the probe routines can cause the devices that are PnP to avoid those devices the probe code cannot relocate. - + Then the PnP devices are visited once more and given their I/O, DMA, IRQ and Memory-map address assignments. The devices will then appear at those locations and remain there until the next reboot, although there is nothing that says you can't move them around whenever you want. - + There is a lot of oversimplification above, but you should get the general idea. - + Microsoft took over some of the primary printer status ports to do PnP, on the logic that no boards decoded those addresses for the opposing I/O cycles. I found a genuine IBM printer board @@ -8722,7 +8722,7 @@ proposal review period, but MS said ``tough''. So they do a write to the printer status port for setting addresses, plus that use that address + 0x800, and a third I/O port for reading that can be located anywhere between 0x200 and 0x3ff. - + @@ -8741,13 +8741,13 @@ number of working ports and packages. FreeBSD/AXP should be considered BETA quality software at this time. For status information, please join the freebsd-alpha@FreeBSD.orgmailing list. - + Interest has also been expressed in a port of FreeBSD to the SPARC architecture, join the freebsd-sparc@FreeBSD.orgmailing list if you are interested in joining that project. For general discussion on new architectures, join the freebsd-platforms@FreeBSD.org mailing list. - + @@ -8763,7 +8763,7 @@ character major number 32 and block major number 8 have been reserved specifically for this purpose; please use them. In any case, we'd appreciate hearing about your driver on freebsd-hackers@FreeBSD.org. - + @@ -8773,34 +8773,34 @@ appreciate hearing about your driver on directories, the scheme that is currently in use is unchanged from what I wrote in 1983. I wrote that policy for the original fast filesystem, and never revisited it. It works well at keeping -cylinder groups from filling up. As several of you have noted, -it works poorly for find. Most filesystems are created from -archives that were created by a depth first search (aka ftw). +cylinder groups from filling up. As several of you have noted, +it works poorly for find. Most filesystems are created from +archives that were created by a depth first search (aka ftw). These directories end up being striped across the cylinder groups -thus creating a worst possible senario for future depth first -searches. If one knew the total number of directories to be -created, the solution would be to create (total / fs_ncg) per -cylinder group before moving on. Obviously, one would have to -create some heuristic to guess at this number. Even using a +thus creating a worst possible senario for future depth first +searches. If one knew the total number of directories to be +created, the solution would be to create (total / fs_ncg) per +cylinder group before moving on. Obviously, one would have to +create some heuristic to guess at this number. Even using a small fixed number like say 10 would make an order of magnitude -improvement. To differentiate restores from normal operation -(when the current algorithm is probably more sensible), you -could use the clustering of up to 10 if they were all done -within a ten second window. Anyway, my conclusion is that this +improvement. To differentiate restores from normal operation +(when the current algorithm is probably more sensible), you +could use the clustering of up to 10 if they were all done +within a ten second window. Anyway, my conclusion is that this is an area ripe for experimentation. - + Kirk McKusick, September 1998 - + Making the most of a kernel panic - + [This section was extracted from a mail written by Bill Paul on the freebsd-current mailing list by Dag-Erling Coïdan Smørgrav, who fixed a few typos and added the bracketed comments] - + From: Bill Paul <wpaul@skynet.ctr.columbia.edu> Subject: Re: the fs fun never stops @@ -8809,7 +8809,7 @@ Date: Sun, 20 Sep 1998 15:22:50 -0400 (EDT) Cc: current@FreeBSD.org - + [<ben@rosengart.com> posted the following panic message] > Fatal trap 12: page fault while in kernel mode @@ -8828,7 +8828,7 @@ message] > panic: page fault - + [When] you see a message like this, it's not enough to just reproduce it and send it in. The instruction pointer value that I highlighted up there is important; unfortunately, it's also @@ -8838,9 +8838,9 @@ using a GENERIC kernel image from one of the snapshots, then it's possible for somebody else to track down the offending function, but if you're running a custom kernel then only you can tell us where the fault occured. - + What you should do is this: - + @@ -8854,7 +8854,7 @@ it's the 0xf0xxxxxx part that we want. When the system reboots, do the following: % nm /kernel.that.caused.the.panic | grep f0xxxxxx - + where f0xxxxxx is the instruction pointer value. The odds are you will not get an exact match since the symbols in the kernel symbol table are for the entry points of @@ -8874,11 +8874,11 @@ failure, but it's better than nothing. - + I see people constantly show panic messages like this but rarely do I see someone take the time to match up the instruction pointer with a function in the kernel symbol table. - + The best way to track down the cause of a panic is by capturing a crash dump, then using gdb(1) to to a stack trace on the crash dump. Of course, this depends on gdb(1) @@ -8887,9 +8887,9 @@ somebody saying that the new ELF-ized gdb(1) didn't handle kernel crash dumps correctly: somebody should check this before 3.0 goes out of beta or there'll be a lot of red faces after the CDs ship). - + In any case, the method I normally use is this: - + @@ -8929,7 +8929,7 @@ some kind.) was installed as /kernel, while kernel.debug can be used as the source of debugging symbols for gdb(1). - + To make sure you capture a crash dump, you need edit /etc/rc.conf and set dumpdev to point to your swap partition. This will cause the rc(8) scripts to use the @@ -8939,7 +8939,7 @@ recovered using savecore(8); if dumpdev/etc/rc.conf, the rc(8) scripts will run savecore(8) automatically and put the crash dump in /var/crash. - + NOTE: FreeBSD crash dumps are usually the same size as the physical RAM size of your machine. That is, if you have 64MB of RAM, you will get a 64MB crash dump. Therefore you must make sure @@ -8952,16 +8952,16 @@ will use to something a little more sensible. For example, if you have 128MB of RAM, you can limit the kernel's memory usage to 16MB so that your crash dump size will be 16MB instead of 128MB. - + Once you have recovered the crash dump, you can get a stack trace with gdb(1) as follows: - + % gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0 (gdb) where - + Note that there may be several screens worth of information; ideally you should use script(1) to capture all of them. Using the unstripped kernel image with all the debug symbols @@ -8971,7 +8971,7 @@ bottom up in order to trace the exact sequence of events that lead to the crash. You can also use gdb(1) to print out the contents of various variables or structures in order to examine the system state at the time of the crash. - + Now, if you're really insane and have a second computer, you can also configure gdb(1) to do remote debugging such that you can use gdb(1) on one system to debug the kernel on @@ -8980,30 +8980,30 @@ through the kernel code, just like you can do with a normal user-mode program. I haven't played with this yet as I don't often have the chance to set up two machines side by side for debugging purposes. - + [Bill adds: "I forgot to mention one thing: if you have DDB enabled and the kernel drops into the debugger, you can force a panic (and a crash dump) just by typing 'panic' at the ddb prompt. It may stop in the debugger again during the panic phase. If it does, type 'continue' and it will finish the crash dump." -ed] - + dlsym() stopped working for ELF executables! -The ELF toolchain does not, by default, make the symbols -defined in an executable visible to the dynamic linker. -Consequently dlsym() searches on handles obtained +The ELF toolchain does not, by default, make the symbols +defined in an executable visible to the dynamic linker. +Consequently dlsym() searches on handles obtained from calls to dlopen(NULL, flags) will fail to find such symbols. - -If you want to search, using dlsym(), for symbols -present in the main executable of a process, you need to link + +If you want to search, using dlsym(), for symbols +present in the main executable of a process, you need to link the executable using the option to the ELF linker. - + @@ -9013,18 +9013,18 @@ the executable using the option to the and 1 GB on FreeBSD 4.x. If you run a network-intensive server (e.g. a large FTP or HTTP server), you might find that 256 MB is not enough. - + So how do you increase the address space? There are two aspects to this. First, you need to tell the kernel to reserve a larger portion of the address space for itself. Second, since the kernel is loaded at the top of the address space, you need to lower the load address so it doesn't bump its head against the ceiling. - + The first goal is achieved by increasing the value of NKPDE in src/sys/i386/include/pmap.h. Here's what it looks like for a 1 GB address space: - + #ifndef NKPDE #ifdef SMP @@ -9035,11 +9035,11 @@ it looks like for a 1 GB address space: #endif - + To find the correct value of NKPDE, divide the desired address space size (in megabytes) by four, then subtract one for UP and two for SMP. - + To achieve the second goal, you need to compute the correct load address: simply subtract the address space size (in bytes) from 0x100100000; the result is 0xc0100000 for a 1 GB address space. @@ -9047,7 +9047,7 @@ Set LOAD_ADDRESS in src/sys/i386/conf/Makefile.i386src/sys/i386/conf/kernel.script to the same value, as follows: - + OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386") OUTPUT_ARCH(i386) @@ -9060,22 +9060,22 @@ SECTIONS .interp : { *(.interp) } - + Then reconfig and rebuild your kernel. You will probably have problems with ps(1), top(1) and the like; make world should take care of it (or a manual rebuild of libkvm, ps and top after copying the patched pmap.h to /usr/include/vm/. - + NOTE: the size of the kernel address space must be a multiple of four megabytes. - + [David Greenman adds: I think the kernel address space needs to be a power of two, but I'm not certain about that. The old(er) boot code used to monkey with the high order address bits and I think expected at least 256MB granularity.] - + @@ -9092,15 +9092,15 @@ id="acknowledgments"> FreeBSD Core Team - + Jordan Hubbard Occasional fits of FAQ-reshuffling and updating. - + - + @@ -9108,9 +9108,9 @@ id="acknowledgments"> Services above and beyond the call of duty on freebsd-questions - + - + @@ -9118,9 +9118,9 @@ id="acknowledgments"> Services above and beyond the call of duty on Usenet - + - + @@ -9128,9 +9128,9 @@ id="acknowledgments"> Networking and formatting - + - + @@ -9138,9 +9138,9 @@ id="acknowledgments"> Multicast information - + - + @@ -9148,9 +9148,9 @@ id="acknowledgments"> FreeBSD FAQ typing machine slavey - + - + @@ -9158,13 +9158,13 @@ id="acknowledgments"> Kvetching, moaning, submitting data - + - + And to any others we've forgotten, apologies and heartfelt thanks! - + diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 9d1ab876bc..b4abacd3e4 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -13,7 +13,7 @@ - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.50 2000/04/10 13:32:27 brian Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.51 2000/04/30 22:04:04 nik Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries @@ -96,7 +96,7 @@ use and provides the widest possible benefit. This is, we believe, one of the most fundamental goals of Free Software and one that we enthusiastically support. - + That code in our source tree which falls under the GNU General Public License (GPL) or GNU Library General Public License (LGPL) comes with slightly more strings attached, @@ -237,22 +237,22 @@ testers. - + No claims are made that any snapshot can be considered ``production quality'' for any purpose. For stability and tested mettle, you will have to stick to full releases. - + Snapshot releases are directly available from - ftp://current.FreeBSD.org/pub/FreeBSD/ - for 5.0-CURRENT and + ftp://current.FreeBSD.org/pub/FreeBSD/ + for 5.0-CURRENT and - releng4.FreeBSD.org for 4-STABLE snapshots. - 3-STABLE snapshots can be found at + releng4.FreeBSD.org for 4-STABLE snapshots. + 3-STABLE snapshots can be found at - releng3.FreeBSD.org. - Snapshots are generated, on the average, once a day for + releng3.FreeBSD.org. + Snapshots are generated, on the average, once a day for all actively developed branches. @@ -275,7 +275,7 @@ which essentially has been one unbroken line leading towards 5.0-RELEASE (and beyond) since 2.0 was released. If a little ASCII art would help, this is how it looks: - + 2.0 | | @@ -331,9 +331,9 @@ things about FreeBSD, although it can be a little frustrating when waiting for all the latest goodies to become available... - + Releases are made about every 4 months on average. - + For people needing (or wanting) a little more excitement, there are SNAPs released more frequently, particularly during the month or so leading up to a release. @@ -409,7 +409,7 @@ found in the 4.0-RELEASE directory. - + 3.X Snapshot @@ -417,13 +417,13 @@ (post 3.0-RELEASE) as it continues on its way towards 3.5-RELEASE. - + 4.X snapshots are made once a day as well. - + 5.0 Snapshot @@ -433,7 +433,7 @@ developers. - + FreeBSD is also available via CDROM, from the following place(s): @@ -449,9 +449,9 @@ email: WC Orders address WWW: WC Home page
- + In Australia, you may find it at: - +
Advanced Multimedia Distributors Factory 1/1 Ovata Drive @@ -577,7 +577,7 @@ actual questions about FreeBSD, there is the questions mailing list: <freebsd-questions@FreeBSD.org>. - + A FreeBSD ``handbook'' is available, and can be found as: the FreeBSD Handbook. Note that this is a work in progress, and @@ -657,7 +657,7 @@ McKusick, Marshall Kirk, Keith Bostic, Michael J Karels, and John Quarterman. - + The Design and Implementation of the 4.4BSD Operating System. Reading, Mass. : Addison-Wesley, 1996. @@ -666,7 +666,7 @@ 0-201-54979-4 A good book on system administration is: - + Evi Nemeth, Garth Snyder, Scott Seebass & Trent R. Hein, ``Unix System Administration Handbook'', Prentice-Hall, @@ -725,7 +725,7 @@ URL="http://www.FreeBSD.org/FAQ/FAQ.ps">http://www.FreeBSD.org/FAQ/FAQ.ps - + As ASCII text (about 220KB): @@ -733,7 +733,7 @@ http://www.FreeBSD.org/FAQ/FAQ.ascii - + As ISO 8859-1 text (about 220KB): @@ -821,7 +821,7 @@ $ col -b < inputfile > outputfile your cvsup file: -www release=current hostname=/home base=/usr/local/etc/cvsup +www release=current hostname=/home base=/usr/local/etc/cvsup prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix @@ -863,7 +863,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix The following newsgroups contain pertinent discussion for FreeBSD users: - + @@ -885,7 +885,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix Web resources: - + @@ -915,7 +915,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix - + The FreeBSD handbook also has a fairly complete bibliography section which is worth reading if you're looking for actual @@ -946,7 +946,7 @@ copied onto floppies by tools like fdimage or If you need to download the distributions yourself (for a DOS filesystem install, for instance), below are some recommendations for distributions to grab: - + @@ -972,56 +972,56 @@ for distributions to grab: - + 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. - + Help! The boot floppy image will not fit on a single floppy! -A 3.5 inch (1.44MB) floppy can accomodate 1474560 bytes of data. +A 3.5 inch (1.44MB) floppy can accomodate 1474560 bytes of data. The boot image is exactly 1474560 bytes in size. - + Common mistakes when preparing the boot floppy are: Not downloading the floppy image in binary mode when -using FTP. +using FTP. Some FTP clients default their transfer mode to ascii -and attempt to change any end-of-line characters received to match +and attempt to change any end-of-line characters received to match the conventions used by the client's system. This will almost invariably corrupt the boot image. Check the -size of the downloaded boot image: if it is not exactly +size of the downloaded boot image: if it is not exactly that on the server, then the download process is suspect. -To workaround: type binary at the FTP command prompt -after getting connected to the server and before starting the +To workaround: type binary at the FTP command prompt +after getting connected to the server and before starting the download of the image. -Using the DOS copy command (or equivalent GUI tool) to +Using the DOS copy command (or equivalent GUI tool) to transfer the boot image to floppy. -Programs like copy will not work as the boot +Programs like copy will not work as the boot image has been created to be booted into directly. The image has the complete content of the floppy, track for track, and is not meant to be placed on the floppy as a regular file. -You have to transfer it to the floppy ``raw'', using the -low-level tools (e.g. fdimage or rawrite) +You have to transfer it to the floppy ``raw'', using the +low-level tools (e.g. fdimage or rawrite) described in the installation guide to FreeBSD. - + @@ -1029,7 +1029,7 @@ described in the installation guide to Fre Installation instructions can be found in the Handbook entry on installing FreeBSD. - + @@ -1038,9 +1038,9 @@ described in the installation guide to Fre You'll need a 386 or better PC, with 5 MB or more of RAM and at least 60 MB of hard disk space. It can run with a low end MDA graphics card but to run X11R6, a VGA or better video card is needed. - + See also the section on - + @@ -1049,34 +1049,34 @@ graphics card but to run X11R6, a VGA or better video card is needed. FreeBSD 2.1.7 was the last version of FreeBSD that could be installed on a 4MB system. Newer versions of FreeBSD, like 2.2, need at least 5MB to install on a new system. - + All versions of FreeBSD, including 3.0, will RUN in 4MB of ram, they just can't run the installation program in 4MB. You can add extra memory for the install process, if you like, and then after the system is up and running, go back to 4MB. Or you could always just swap your disk into a system which has >4MB, install onto it and then swap it back. - + There are also situations in which FreeBSD 2.1.7 will not install in 4 MB. To be exact: it does not install with 640 kB base + 3 MB extended memory. If your motherboard can remap some of the ``lost'' memory out of the 640kB to 1MB region, then you may still be able to get FreeBSD 2.1.7 up. - + Try to go into your BIOS setup and look for a ``remap'' option. Enable it. You may also have to disable ROM shadowing. - + It may be easier to get 4 more MB just for the install. Build a custom kernel with only the options you need and then get the 4 MB out again. - + You may also install 2.0.5 and then upgrade your system to 2.1.7 with the ``upgrade'' option of the 2.1.7 installation program. - + After the installation, if you build a custom kernel, it will run in 4 MB. Someone has even succeeded in booting with 2 MB (the system was almost unusable though :-)) - + @@ -1088,16 +1088,16 @@ You have to cut a whole new release, which will include your install floppy. There's some code in /usr/src/release/floppies/Makefile that's supposed to let you *just* make those floppies, but it's not really gelled yet. - + To make a custom release, follow the instructions here. - + Can I have more than one operating system on my PC? Have a look at The multi-OS page. - + @@ -1108,7 +1108,7 @@ manager will then manage to boot Win95 and FreeBSD. If you install Windows 95 second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next section. - + @@ -1117,7 +1117,7 @@ the next section. You can reinstall the boot manager FreeBSD comes with in one of two ways: - + @@ -1150,7 +1150,7 @@ installation menu and reboot off the hard disk as normal. - + @@ -1162,9 +1162,9 @@ it must unfortunately be said that if you've got an IDE or ESDI drive with lots of bad blocks, then FreeBSD is probably not for you! That said, it does work on thousands of IDE based systems, so you'd do well to try it first before simply giving up. - + If you have a SCSI drive with bad blocks, see this answer. - + @@ -1173,7 +1173,7 @@ you'd do well to try it first before simply giving up. If you're seeing things like the machine grinding to a halt or spontaneously rebooting when you try to boot the install floppy, here are three questions to ask yourself:- - + @@ -1203,11 +1203,11 @@ shell in the GUI can cause this problem. - + There have also been reports of Netscape causing problems when downloading the boot floppy, so it's probably best to use a different FTP client if you can. - + @@ -1219,7 +1219,7 @@ blocksize is 20 (10240 bytes), and tapes created using this default size cannot be used to install 2.1.7R; with these tapes, you will get an error that complains about the record size being too big. - + @@ -1228,7 +1228,7 @@ too big. Get a laplink cable. Make sure both computer have a kernel with lpt driver support. - + $ dmesg | grep lp lpt0 at 0x378-0x37f irq 7 on isa @@ -1236,56 +1236,56 @@ with lpt driver support. lp0: TCP/IP capable interface - + Plug in the laplink cable into the parallel interface. - + Configure the network interface parameters for lp0 on both sites as root. For example, if you want connect the host max with moritz - + max <-----> moritz IP Address 10.0.0.1 10.0.0.2 - + on max start # ifconfig lp0 10.0.0.1 10.0.0.2 - + on moritz start - + # ifconfig lp0 10.0.0.2 10.0.0.1 - -Thats all! Please read also the manpages + +Thats all! Please read also the manpages lp(4) and lpt(4) . - + You should also add the hosts to /etc/hosts. - + - 127.0.0.1 localhost.my.domain localhost + 127.0.0.1 localhost.my.domain localhost 10.0.0.1 max.my.domain max 10.0.0.2 moritz.my.domain moritz - + To check if it works do: - + on max: - + $ ifconfig lp0 lp0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.0.0.1 --> 10.0.0.2 netmask 0xff000000 - + $ netstat -r Routing tables @@ -1294,7 +1294,7 @@ Internet: Destination Gateway Flags Refs Use Netif Expire moritz max UH 4 127592 lp0 - + $ ping -c 4 moritz PING moritz (10.0.0.2): 56 data bytes @@ -1307,7 +1307,7 @@ PING moritz (10.0.0.2): 56 data bytes 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms - + @@ -1316,7 +1316,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms Connect the two computers using a Laplink parallel cable to use this feature: - + +----------------------------------------+ |A-name A-End B-End Descr. Port/Bit | @@ -1340,9 +1340,9 @@ this feature: +----------------------------------------+ - + See also this note on the Mobile Computing page. - + heads and sectors/track on a disk - I'll refer to this as C/H/S for convenience. This is how the PC's BIOS works out which area on a disk to read/write from). - + This seems to cause a lot of confusion for some reason. First of all, the physical geometry of a SCSI drive is totally irrelevant, as FreeBSD works in term of disk blocks. In fact, there @@ -1364,14 +1364,14 @@ physical geometry is usually the geometry that they've worked out results in the least wasted space. For IDE disks, FreeBSD does work in terms of C/H/S, but all modern drives will convert this into block references internally as well. - + All that matters is the logical geometry - the answer that the BIOS gets when it asks "what is your geometry?" and then uses to access the disk. As FreeBSD uses the BIOS when booting, it's 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 geometry, otherwise you will have serious problems booting! - + For SCSI disks, the geometry to use depends on whether extended translation support is turned on in your controller (this is often referred to as "support for DOS disks >1GB" or something @@ -1379,28 +1379,28 @@ similar). If it's turned off, then use N cylinders, 64 heads and 32 sectors/track, where 'N' is the capacity of the disk in MB. For example, a 2GB disk should pretend to have 2048 cylinders, 64 heads and 32 sectors/track. - + If it is turned on (it's often supplied this way to get around certain limitations in MSDOS) 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 have 261 cylinders, 63 sectors per track and 255 heads. - + If you are not sure about this, or FreeBSD 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 correct geometry should then be detected (and you can always remove the DOS partition in the partition editor if you don't want to keep it, or leave it around for programming network cards and the like). - + Alternatively, there is a freely available utility distributed with FreeBSD called ``pfdisk.exe'' (located in the tools subdirectory on the FreeBSD CDROM or on the various FreeBSD ftp sites) which can be used to work out what geometry the other operating systems on the disk are using. You can then enter this geometry in the partition editor. - + @@ -1409,12 +1409,12 @@ geometry in the partition editor. 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). - + For a SCSI drive, this will normally imply that the root partition will be in the first 1024MB (or in the first 4096MB if extended translation is turned on - see previous question). For IDE, the corresponding figure is 504MB. - + @@ -1423,32 +1423,32 @@ corresponding figure is 504MB. FreeBSD recognizes the Ontrack Disk Manager and makes allowances for it. Other disk managers are not supported. - + If you just want to use the disk with FreeBSD you don't need a disk manager. Just configure the disk for as much space as the BIOS can deal with (usually 504 megabytes), and FreeBSD should figure out how much space you really have. If you're using an old disk with an MFM controller, you may need to explicitly tell FreeBSD how many cylinders to use. - + If you want to use the disk with FreeBSD and another operating system, you may be able to do without a disk manager: just make sure the the FreeBSD boot partition and the slice for the other operating system are in the first 1024 cylinders. If you're reasonably careful, a 20 megabyte boot partition should be plenty. - + When I boot FreeBSD I get ``Missing Operating System'' - + This is classically a case of FreeBSD 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 always get you going. - + @@ -1459,7 +1459,7 @@ question. Your BIOS geometry and FreeBSD 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. - + - + Also look at the section on >64M machines if you have that much memory, or if you're using a Compaq or other BIOS that lies about the available memory. - + @@ -1488,7 +1488,7 @@ includes several of the files mentioned here, and the ``sys'' (kernel) source kit, which includes sources for the kernel. There is nothing in the system which requires the presence of the sources to operate, however, except for the -kernel-configuration program +kernel-configuration program config . With the exception of the kernel sources, our build structure is set up so that you @@ -1498,17 +1498,17 @@ restriction, we recommend that you not mount this on /usr/src directly, but rather in some other location with appropriate symbolic links to duplicate the top-level structure of the source tree.) - + 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 actually select a subset of the sources, use the Custom menu item when you are in the Distributions menu of the system installation tool. The src/install.sh script will also install partial pieces of the source distribution, depending on the arguments you pass it. - + @@ -1521,12 +1521,12 @@ configuration tool. When at the FreeBSD boot prompt (boot:), use the "-c" flag and you will be dropped into a visual configuration screen which allows you to configure the kernel's settings for most common ISA cards. - + It's still recommended that you eventually build a new kernel containing just the drivers that you need, just to save a bit of RAM, but it's no longer a strict requirement for most systems. - + @@ -1540,26 +1540,26 @@ more CPU-intensive to crack with an automated password cracker than DES, and allows longer passwords as well. The only reason for not using the MD5-based crypt today would be to use the the same password entries on FreeBSD and non-FreeBSD systems. - + Since the DES encryption algorithm cannot legally be exported from the US, non-US users should not download this software (as part of the secrdist from US FTP sites. - + There is however a replacement libcrypt available, based on sources written in Australia by David Burren. This code is now available on some non-US FreeBSD mirror sites. Sources for the unencumbered libcrypt, and binaries of the programs which use it, can be obtained from the following FTP sites: - + South Africa ftp://ftp.internat.FreeBSD.org/pub/FreeBSD ftp://storm.sea.uct.ac.za/pub/FreeBSD - + - + @@ -1567,9 +1567,9 @@ can be obtained from the following FTP sites: ftp://ftp.iqm.unicamp.br/pub/FreeBSD - + - + @@ -1577,34 +1577,34 @@ can be obtained from the following FTP sites: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt - + - + The non-US securedist can be used as a direct replacement for the encumbered US securedist. This securedist package is installed the same way as the US package (see installation notes for details). If you are going to install DES encryption, you should do so as soon as possible, before installing other software. - + Non-US users should please not download any encryption software from the USA. This can get the maintainers of the sites from which the software is downloaded into severe legal difficulties. - + A non-US distribution of Kerberos is also being developed, and current versions can generally be obtained by anonymous FTP from braae.ru.ac.za. - + There is also a mailing list for the discussion of non-US encryption software. For more information, send an email message with a single line saying ``help'' in the body of your message to - + majordomo@braae.ru.ac.za. - + @@ -1615,24 +1615,24 @@ of your message to 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. - + I get a ``panic: cant mount root'' error when rebooting the system after installation. -This error comes from confusion between the boot block's and the -kernel's understanding of the disk devices. The error usually +This error comes from confusion between the boot 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 installed on the secondary IDE controller. The boot blocks think the system is installed on wd1 (the second BIOS disk) while the kernel assigns the first disk on the secondary controller device wd2. After -the device probing, the kernel tries to mount what the boot blocks +the device probing, the kernel tries to mount what the boot blocks think is the boot disk, wd1, while it is really wd2, and fails. - + To fix the problem, do one of the following: - + @@ -1660,14 +1660,14 @@ everytime you reboot or turn on your FreeBSD machine), put the line If using FreeBSD 3.2 or earlier, at the Boot: prompt, enter 1:wd(2,a)kernel and press Enter. If the system starts, then -run the command +run the command echo "1:wd(2,a)kernel" > /boot.config to make it the default boot string. -Move the FreeBSD disk onto the primary IDE controller, so the +Move the FreeBSD disk onto the primary IDE controller, so the hard disks are consecutive. @@ -1685,7 +1685,7 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2 Install the new kernel. -If you moved your disks and wish to restore the previous +If you moved your disks and wish to restore the previous configuration, replace the disks in the desired configuration and reboot. Your system should boot successfully. @@ -1693,18 +1693,18 @@ Your system should boot successfully. - + What are the limits for memory? For memory, the limit is 4 gigabytes. This configuration has -been tested, see wcarchive's -configuration for more details. If you plan to install this -much memory into a machine, you need to be careful. You'll probably -want to use ECC memory and to reduce capacitive loading use 9 chip +configuration for more details. If you plan to install this +much memory into a machine, you need to be careful. You'll probably +want to use ECC memory and to reduce capacitive loading use 9 chip memory modules vice 18 chip memory modules. @@ -1716,10 +1716,10 @@ memory modules vice 18 chip memory modules. (2G blocks), or 16TB for the default block size of 8K. In practice, there is a soft limit of 1 terabyte, but with modifications filesystems with 4 terabytes are possible (and exist). - -The maximum size of a single ffs file is approximately 1G blocks + +The maximum size of a single ffs file is approximately 1G blocks (4TB) if the block size is 4K. - + maxfilesize ---------------------------------- @@ -1733,7 +1733,7 @@ fs block size -STABLE -CURRENT works should-work 64K 2048+G 64T-1 2048+G 128T-1 - + When the fs block size is 4K, triple indirect blocks work and everything should be limited by the maximum fs block number that can be represented using triple indirect blocks (approx. 1K^3 + 1K^2 + @@ -1741,7 +1741,7 @@ be represented using triple indirect blocks (approx. 1K^3 + 1K^2 + numbers. The limit on fs block numbers should be 2G-1. There are some bugs for fs block numbers near 2G-1, but such block numbers are unreachable when the fs block size is 4K. - + For block sizes of 8K and larger, everything should be limited by the 2G-1 limit on fs block numbers, but is actually limited by the 1G-1 limit on fs block numbers, except under -STABLE triple indirect @@ -1750,7 +1750,7 @@ that can be represented using double indirect blocks (approx. (blocksize/4)^2 + (blocksize/4)), and under -CURRENT exceeding this limit may cause problems. Using the correct limit of 2G-1 blocks does cause problems. - + @@ -1760,12 +1760,12 @@ exceeding this limit may cause problems. Using the correct limit of file size is not closely related to the maximum disk size. The maximum disk size is 1TB. It is a feature that the file size can be larger than the disk size. - + The following example creates a file of size 8T-1 using a whole 32K of disk space (3 indirect blocks and 1 data block) on a small root partition. The dd command requires a dd that works with large files. - + ttyv0:bde@alphplex:/tmp/q> cat foo df . @@ -1785,9 +1785,9 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0a 64479 27734 31587 47% / ttyv0:bde@alphplex:/tmp/q> exit - + Bruce Evans, September 1998 - + @@ -1798,7 +1798,7 @@ stage, pressing any key when the | shows up before loader is started. More specifically, you have upgraded the source for your kernel, and installed a new kernel builtin from them without making world. This is not supported. Make world. - + @@ -1814,7 +1814,7 @@ Handbook for more information. Upgrading via source is never recommended for new users, and upgading from 3.X -> 4.X is even less so; make sure you have read the instructions carefully before attempting to upgrade via -source this! +source this! @@ -1833,24 +1833,24 @@ original "Western Digital" interface (MFM, RLL, ESDI, and of course IDE). A few ESDI controllers that use proprietary interfaces may not work: stick to WD1002/3/6/7 interfaces and clones. - + Which SCSI controllers are supported? -See the complete list in the +See the complete list in the Handbook. - + Which CD-ROM drives are supported by FreeBSD? Any SCSI drive connected to a supported controller is supported. - + The following proprietary CD-ROM interfaces are also supported: - + @@ -1876,13 +1876,13 @@ and clones. - + All non-SCSI cards are known to be extremely slow compared to SCSI drives, and some ATAPI CDROMs may not work. - + As of 2.2 the FreeBSD CDROM from Walnut Creek supports booting directly from the CD. - + @@ -1894,20 +1894,20 @@ your SCSI host adapter's BIOS supports it you can even boot from it. I don't know which host adapters let you boot from targets other than 0 or 1... look at your docs (and let me know if it works out for you). - + ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and later releases. - + FreeBSD has contained support for Parallel Port Zip Drives since version 3.0. If you are using a sufficiently up to date version, then -you should check that your kernel contains the scbus0, da0, ppbus0, and vp0 drivers (the GENERIC kernel -contains everything except vp0). With all these drivers present, the -Parallel Port drive should be available as /dev/da0s4. Disks can +you should check that your kernel contains the scbus0, da0, ppbus0, and vp0 drivers (the GENERIC kernel +contains everything except vp0). With all these drivers present, the +Parallel Port drive should be available as /dev/da0s4. Disks can be mounted using mount /dev/da0s4 /mnt OR (for dos disks) mount_msdos /dev/da0s4 /mnt as appropriate. - + Also check out this note on removable drives, and this note on 'formatting'. - + @@ -1917,14 +1917,14 @@ and this note on 'formatting'. Apart from the IDE version of the EZ drive, these are all SCSI devices, so the should all look like SCSI disks to FreeBSD, and the IDE EZ should look like an IDE drive. - + I'm not sure how well FreeBSD supports changing the media out while running. You will of course need to dismount the drive before swapping media, and make sure that any external units are powered on when you boot the system so FreeBSD can see them. - + See this note on 'formatting'. - + @@ -1932,13 +1932,13 @@ powered on when you boot the system so FreeBSD can see them. There is a list of these in the Miscellaneous devices section of the handbook. - + Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible. - + Check the sio man page to get more information on configuring such cards. - + @@ -2028,17 +2028,17 @@ id="busmouse"> FreeBSD supports the bus mouse and the InPort bus mouse from such manufactures as Microsoft, Logitech and ATI. The bus device driver is compiled in the GENERIC kernel by default in FreeBSD versions 2.X, but -not included in version 3.0 or later. If you are building -a custom kernel with the bus mouse driver, make sure to add the +not included in version 3.0 or later. If you are building +a custom kernel with the bus mouse driver, make sure to add the following line to the kernel config file - + In FreeBSD 3.0 or before, add: device mse0 at isa? port 0x23c tty irq5 vector mseintr - + In FreeBSD 3.1 or later, the line should be: @@ -2050,7 +2050,7 @@ following line to the kernel config file It may allow you to set the port address and the IRQ number other than shown above. Refer to the manual of your mouse and the &man.mse.4; man page for more information. - + How do I use my PS/2 (``mouse port'' or ``keyboard'') mouse? If you're running a post-2.2.5 version of FreeBSD, the necessary -driver, psm, is included and enabled in the kernel. The kernel +driver, psm, is included and enabled in the kernel. The kernel should detect your PS/2 mouse at boot time. - -If you're running a previous but relatively recent version of + +If you're running a previous but relatively recent version of FreeBSD (2.1.x or better) then you can simply enable it in the kernel configuration menu at installation time, otherwise later with at the boot: prompt. It is disabled by default, so you will need to enable it explicitly. - + If you're running an older version of FreeBSD then you'll have to add the following lines to your kernel configuration file and compile a new kernel. @@ -2094,18 +2094,18 @@ a new kernel. See the Handbook entry on configuring the kernel if you've no experience with building kernels. - + Once you have a kernel detecting psm0 correctly at boot time, make sure that an entry for psm0 exists in /dev. You can do this by typing: - + cd /dev; sh MAKEDEV psm0 - + when logged in as root. - + use a mouse pointer in text consoles to cut & paste text. Run the mouse daemon, moused, and turn on the mouse pointer in the virtual console: - + - moused -p /dev/xxxx -t yyyy + moused -p /dev/xxxx -t yyyy vidcontrol -m on - -Where xxxx is the mouse device name and yyyy -is a protocol type for the mouse. See the + +Where xxxx is the mouse device name and yyyy +is a protocol type for the mouse. See the &man.moused.8; man page for supported protocol types. - -You may wish to run the mouse daemon automatically when the + +You may wish to run the mouse daemon automatically when the system starts. In version 2.2.1, set the following variables in /etc/sysconfig. - + mousedtype="yyyy" mousedport="xxxx" mousedflags="" - + In versions 2.2.2 or later, set the following variables in /etc/rc.conf. - + moused_type="yyyy" moused_port="xxxx" moused_flags="" - + In addition, if you would like to be able to use the mouse daemon on all virtual terminals instead of just console at boot-time, add the following to /etc/rc.conf. - + allscreens_flags="-m on" -Staring from FreeBSD 2.2.6, the mouse daemon is capable of -determining the correct protocol type automatically unless the mouse +Staring from FreeBSD 2.2.6, the mouse daemon is capable of +determining the correct protocol type automatically unless the mouse is a relatively old serial mouse model. Specify ``auto'' as the protocol to invoke automatic detection. - + When the mouse daemon is running, access to the mouse needs to be coordinated between the mouse daemon and other programs such as the -X Window. Refer to another section +X Window. Refer to another section on this issue. - + How do I cut and paste text with mouse in the text console? -Once you get the mouse daemon running (see previous section), hold down the button 1 (left button) +Once you get the mouse daemon running (see previous section), hold down the button 1 (left button) and move the mouse to select a region of text. Then, press the button 2 (middle button) or the button 3 (right button) to paste it at the text cursor. - -In versions 2.2.6 and later, pressing the button 2 will paste + +In versions 2.2.6 and later, pressing the button 2 will paste the text. Pressing the button 3 will ``extend'' the selected region of text. If your mouse does not have the middle button, you may wish -to emulate it or remap buttons using moused options. See the +to emulate it or remap buttons using moused options. See the moused(8) man page for details. - + I have a USB mouse. Does FreeBSD support the USB mouse? - + USB device support was added to FreeBSD 3.1. However, it is still in a preliminary state and may not always work as of version @@ -2272,11 +2272,11 @@ Protocol "SysMouse" The answer is, unfortunately, “It depends”. These mice with additional features require specialized driver in most cases. -Unless the mouse device driver or the user program has specific -support for the mouse, it will act just like a standard two, or +Unless the mouse device driver or the user program has specific +support for the mouse, it will act just like a standard two, or three button mouse. - -For the possible usage of wheels in the X Window environment, + +For the possible usage of wheels in the X Window environment, refer to that section. @@ -2287,7 +2287,7 @@ refer to that section. on the screen. The mouse has a wheel and is connected to the PS/2 mouse port. - + The PS/2 mouse driver psm in FreeBSD versions 3.2 or earlier has difficulty with some wheel mice, including Logitech model M-S48 and @@ -2306,10 +2306,10 @@ diff -u -r1.60.2.1 -r1.60.2.2 +++ psm.c 1999/07/12 13:40:52 1.60.2.2 @@ -959,14 +959,28 @@ sc->mode.packetsize = vendortype[i].packetsize; - + /* set mouse parameters */ +#if 0 -+ /* ++ /* + * A version of Logitech FirstMouse+ won't report wheel movement, + * if SET_DEFAULTS is sent... Don't use this command. + * This fix was found by Takashi Nishida. @@ -2320,7 +2320,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 +#endif if (sc->config & PSM_CONFIG_RESOLUTION) { sc->mode.resolution - = set_mouse_resolution(sc->kbdc, + = set_mouse_resolution(sc->kbdc, - (sc->config & PSM_CONFIG_RESOLUTION) - 1); + (sc->config & PSM_CONFIG_RESOLUTION) - 1); + } else if (sc->mode.resolution >= 0) { @@ -2331,7 +2331,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 + sc->mode.rate = set_mouse_sampling_rate(sc->kbdc, sc->dflt_mode.rate); } + set_mouse_scaling(sc->kbdc, 1); - + /* request a data packet and extract sync. bits */ if (get_mouse_status(sc->kbdc, stat, 1, 3) < 3) { @@ -2345,7 +2345,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 Please refer to the answer to the previous question. And check out this note on the Mobile Computing page. - + @@ -2354,10 +2354,10 @@ Computing page. FreeBSD supports SCSI, QIC-36 (with a QIC-02 interface) and QIC-40/80 (Floppy based) tape drives. This includes 8-mm (aka Exabyte) and DAT drives. The QIC-40/80 drives are known to be slow. - + Some of the early 8-mm drives are not quite compatible with SCSI-2, and may not work well with FreeBSD. - + @@ -2370,13 +2370,13 @@ command. The details of how you actually control the changer can be found in the chio(1) man page. - + If you're not using AMANDA or some other product that already understands changers, remember that they're only know how to move a tape from one point to another, so you need to keep track of which slot a tape is in, and which slot the tape currently in the drive needs to go back to. - + @@ -2385,23 +2385,23 @@ tape currently in the drive needs to go back to. 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 +Cards conforming to the Microsoft Sound System specification are also supported through the pcm driver. - + NOTE This is only for sound! This driver does not support CD-ROMs, SCSI or joysticks on these cards, except for the SoundBlaster. The SoundBlaster SCSI interface and some non-SCSI CDROMS are supported, but you can't boot off this device. - + Workarounds for no sound from es1370 with pcm driver? You can run the following command everytime the machine booted up: - + mixer pcm 100 vol 100 cd 100 - + @@ -2409,7 +2409,7 @@ CDROMS are supported, but you can't boot off this device. See the Ethernet cards section of the handbook for a more complete list. - + @@ -2417,25 +2417,25 @@ complete list. Note This will only affect 386/486SX/486SLC owners - other machines will have one built into the CPU. - + In general this will not cause any problems, but there are circumstances where you will take a hit, either in performance or accuracy of the math emulation code (see the section on FP emulation). In particular, drawing arcs in X will be VERY slow. It is highly recommended that you buy a math co-processor; it's well worth it. - + NOTE Some math co-processors are better than others. It pains us to say it, but nobody ever got fired for buying Intel. Unless you're sure it works with FreeBSD, beware of clones. - + What other devices does 2.X support? -See the Handbook +See the Handbook for the list of other devices supported. - + @@ -2443,7 +2443,7 @@ for the list of other devices supported. FreeBSD supports APM on certain machines. Please look in the LINT kernel config file, searching for the APM keyword. - + @@ -2452,11 +2452,11 @@ for the list of other devices supported. Certain Micron motherboards have a non-conforming PCI BIOS implementation that causes grief when FreeBSD boots because PCI devices don't get configured at their reported addresses. - + Disable the "Plug and Play Operating System" flag in the BIOS to work around this problem. More information can be found at http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron - + @@ -2468,7 +2468,7 @@ framework which made it's debut in 3.0. Patches against 2.2-STABLE are in ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/. A CAM-enhanced boot floppy is available at http://people.FreeBSD.org/~abial/cam-boot/. In both cases read the README before beginning. - + @@ -2476,20 +2476,20 @@ beginning. You will need to add the modem's PnP ID to the PnP ID list in the serial driver. -To enable Plug & Play support, compile a new kernel with controller pnp0 in +To enable Plug & Play support, compile a new kernel with controller pnp0 in the configuration file, then reboot the system. The kernel will print the PnP IDs -of all the devices it finds. Copy the PnP ID from the modem to the table in -/sys/i386/isa/sio.c, at about line 2777. Look for the string "SUP1310" -in the structure "siopnp_ids[]" to +of all the devices it finds. Copy the PnP ID from the modem to the table in +/sys/i386/isa/sio.c, at about line 2777. Look for the string "SUP1310" +in the structure "siopnp_ids[]" to find the table. Build the kernel again, install, reboot, and your modem should be found. - -You may have to manually configure the PnP devices using the `pnp' command in the + +You may have to manually configure the PnP devices using the `pnp' command in the boot-time configuration with a command like pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8 to make the modem show. - + @@ -2513,9 +2513,9 @@ to make the modem show. - + See /usr/src/sys/i386/boot/biosboot/README.serial for information. - + @@ -2524,13 +2524,13 @@ to make the modem show. Certain Micron motherboards have a non-conforming PCI BIOS implementation that does not configure PCI devices at the addresses reported. This causes grief when FreeBSD boots. - -To work around this problem, disable the "Plug and Play Operating + +To work around this problem, disable the "Plug and Play Operating System" flag in the BIOS. - + More information on this problem is available at URL: http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron - + @@ -2538,7 +2538,7 @@ System" flag in the BIOS. SMP is supported in 3.0-STABLE and later releases only. - + @@ -2567,90 +2567,90 @@ id="awre"> With SCSI drives, the drive should be capable of re-mapping these automatically. However, many drives are shipped with this feature disabled, for some mysterious reason... - + To enable this, you'll need to edit the first device page mode, which can be done on FreeBSD by giving the command (as root) - + scsi -f /dev/rsd0c -m 1 -e -P 3 - + and changing the values of AWRE and ARRE from 0 to 1:- - + AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 - -The following paragraphs were submitted by + +The following paragraphs were submitted by Ted Mittelstaedt: - + For IDE drives, any bad block is usually a sign of potential trouble. -All modern IDE drives come with internal bad-block remapping turned -on. All IDE hard drive manufacturers today offer extensive +All modern IDE drives come with internal bad-block remapping turned +on. All IDE hard drive manufacturers today offer extensive warranties and will replace drives with bad blocks on them. - + If you still want to attempt to rescue an IDE drive with bad blocks, -you can attempt to download the IDE drive manufacturer's IDE diagnostic -program, and run this against the drive. Sometimes these programs can -be set to force the drive electronics to rescan the drive for bad blocks +you can attempt to download the IDE drive manufacturer's IDE diagnostic +program, and run this against the drive. Sometimes these programs can +be set to force the drive electronics to rescan the drive for bad blocks and lock them out. - -For ESDI, RLL and MFM drives, bad blocks are a normal part of the -drive and are no sign of trouble, generally. With a PC, the disk drive -controller card and BIOS handle the task of locking out bad sectors. -This is fine for operating systems like DOS that use BIOS code to -access the disk. However, FreeBSD's disk driver does not go through -BIOS, therefore a mechanism, bad144, exists that replaces this + +For ESDI, RLL and MFM drives, bad blocks are a normal part of the +drive and are no sign of trouble, generally. With a PC, the disk drive +controller card and BIOS handle the task of locking out bad sectors. +This is fine for operating systems like DOS that use BIOS code to +access the disk. However, FreeBSD's disk driver does not go through +BIOS, therefore a mechanism, bad144, exists that replaces this functionality. bad144 only works with the wd driver, it is NOT able to be used with SCSI. bad144 works by entering all bad sectors found into a special file. - -One caveat with bad144 - the bad block special file is placed on the + +One caveat with bad144 - the bad block special file is placed on the last track of the disk. As this file may possibly contain a listing for -a bad sector that would occur near the beginning of the disk, where the -/kernel file might be located, it therefore must be accessible to the -bootstrap program that uses BIOS calls to read the kernel file. This -means that the disk with bad144 used on it must not exceed 1024 -cylinders, 16 heads, and 63 sectors. This places an effective limit +a bad sector that would occur near the beginning of the disk, where the +/kernel file might be located, it therefore must be accessible to the +bootstrap program that uses BIOS calls to read the kernel file. This +means that the disk with bad144 used on it must not exceed 1024 +cylinders, 16 heads, and 63 sectors. This places an effective limit of 500MB on a disk that is mapped with bad144. - -To use bad144, simply set the "Bad Block" scanning to ON in the -FreeBSD fdisk screen during the initial install. This works up through -FreeBSD 2.2.7. The disk must have less than 1024 cylinders. It is -generally recommended that the disk drive has been in operation for at -least 4 hours prior to this to allow for thermal expansion and track + +To use bad144, simply set the "Bad Block" scanning to ON in the +FreeBSD fdisk screen during the initial install. This works up through +FreeBSD 2.2.7. The disk must have less than 1024 cylinders. It is +generally recommended that the disk drive has been in operation for at +least 4 hours prior to this to allow for thermal expansion and track wandering. - + If the disk has more than 1024 cylinders (such as a large ESDI drive) -the ESDI controller uses a special translation mode to make it work -under DOS. The wd driver understands about these translation modes, -IF you enter the "translated" geometry with the "set geometry" command -in fdisk. You must also NOT use the "dangerously dedicated" mode of -creating the FreeBSD partition, as this ignores the geometry. Also, -even though fdisk will use your overridden geometry, it still knows the -true size of the disk, and will attempt to create a too large FreeBSD -partition. If the disk geometry is changed to the translated geometry, +the ESDI controller uses a special translation mode to make it work +under DOS. The wd driver understands about these translation modes, +IF you enter the "translated" geometry with the "set geometry" command +in fdisk. You must also NOT use the "dangerously dedicated" mode of +creating the FreeBSD partition, as this ignores the geometry. Also, +even though fdisk will use your overridden geometry, it still knows the +true size of the disk, and will attempt to create a too large FreeBSD +partition. If the disk geometry is changed to the translated geometry, the partition MUST be manually created with the number of blocks. - -A quick trick to use is to set up the large ESDI disk with the ESDI + +A quick trick to use is to set up the large ESDI disk with the ESDI controller, boot it with a DOS disk and format it with a DOS partition. -Then, boot the FreeBSD install and in the fdisk screen, read off and -write down the blocksize and block numbers for the DOS partition. Then, -reset the geometry to the same that DOS uses, delete the DOS partition, -and create a "cooperative" FreeBSD partition using the blocksize you -recorded earlier. Then, set the partition bootable and turn on bad -block scanning. During the actual install, bad144 will run first, -before any filesystems are created. (you can view this with an Alt-F2) -If it has any trouble creating the badsector file, you have set too -large a disk geometry - reboot the system and start all over again +Then, boot the FreeBSD install and in the fdisk screen, read off and +write down the blocksize and block numbers for the DOS partition. Then, +reset the geometry to the same that DOS uses, delete the DOS partition, +and create a "cooperative" FreeBSD partition using the blocksize you +recorded earlier. Then, set the partition bootable and turn on bad +block scanning. During the actual install, bad144 will run first, +before any filesystems are created. (you can view this with an Alt-F2) +If it has any trouble creating the badsector file, you have set too +large a disk geometry - reboot the system and start all over again (including repartitioning and reformatting with DOS). - -If remapping is enabled and you are seeing bad blocks, consider + +If remapping is enabled and you are seeing bad blocks, consider replacing the drive. The bad blocks will only get worse as time goes on. - + @@ -2658,7 +2658,7 @@ replacing the drive. The bad blocks will only get worse as time goes on. This info is specific to the 742a but may also cover other Buslogic cards. (Bustek = Buslogic) - + There are 2 general ``versions'' of the 742a card. They are hardware revisions A-G, and revisions H - onwards. The revision letter is located after the Assembly number on the edge of the @@ -2669,33 +2669,33 @@ of firmware chip. Buslogic will send upgrade ROMS out if you call their tech support dept. The BIOS and Firmware chips are shipped as a matched pair. You must have the most current Firmware ROM in your adapter card for your hardware revision. - + The REV A-G cards can only accept BIOS/Firmware sets up to 2.41/2.21. The REV H- up cards can accept the most current BIOS/Firmware sets of 4.70/3.37. The difference between the firmware sets is that the 3.37 firmware supports ``round robin'' - + The Buslogic cards also have a serial number on them. If you have a old hardware revision card you can call the Buslogic RMA department and give them the serial number and attempt to exchange the card for a newer hardware revision. If the card is young enough they will do so. - + 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 AHA1540 ``emulation'' mode. This is not a good thing for an EISA card, however. - + If you have an old hardware revision card and you obtain the 2.21 firmware for it, you will need to check the position of jumper W1 to B-C, the default is A-B. - + The 742a EISA cards never had the ``>16MB'' problem mentioned in the section on >16 MB machines. This is a problem that occurs with the Vesa-Local Buslogic SCSI cards. - + @@ -2708,34 +2708,34 @@ 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 auto-configuration currently cannot handle this situation very well. - + So now, the best you can do is to pretend there is no address range clash :), by bumping the kernel option EISA_SLOTS to a value of 12. Configure and compile a kernel, as described in the Handbook entry on configuring the kernel. - + Of course, this does present you with a chicken-and-egg problem when installing on such a machine. In order to work around this problem, a special hack is available inside UserConfig. Do not use the ``visual'' interface, but the plain command-line interface there. Simply type - + eisa 12 quit - + at the prompt, and install your system as usual. While it's recommended you compile and install a custom kernel anyway, - + Hopefully, future versions will have a proper fix for this problem. - + NOTE: You can not use a dangerously dedicated disk with an HP Netserver. See this note for more info. - + @@ -2743,16 +2743,16 @@ more info. It's broken. It cannot handle commands on both channels simultaneously. - + There's a workaround available now and it is enabled automatically if your system uses this chip. For the details refer to the manual page of the disk driver (man 4 wd). - + If you're already running FreeBSD 2.2.1 or 2.2.2 with a CMD640 IDE controller and you want to use the second channel, build a new kernel with options "CMD640" enabled. This is the default for 2.2.5 and later. - + @@ -2764,24 +2764,24 @@ of this, and the network driver would still function in the presence of IRQ conflicts. However, with 2.0.5R and later, IRQ conflicts are no longer tolerated. Boot with the -c option and change the ed0/de0/... entry to match your board. - + If you're using the BNC connector on your network card, you may also see device timeouts because of bad termination. To check this, attach a terminator directly to the NIC (with no cable) and see if the error messages go away. - -Some NE2000 compatible cards will give this error if there is + +Some NE2000 compatible cards will give this error if there is no link on the UTP port or if the cable is disconnected. - + When I mount a CDROM, I get ``Incorrect super block''. -You have to tell +You have to tell mount -the type of the device that you want to mount. By default, +the type of the device that you want to mount. By default, mount(8) will assume the filesystem is of type ``ufs''. You want to mount @@ -2792,26 +2792,26 @@ URL="http://www.FreeBSD.org/cgi/man.cgi?mount(8)">mount(8) CDROM contains an ISO 9660 filesystem, which is what most CDROMs have. As of 1.1R, FreeBSD automatically understands the Rock Ridge (long filename) extensions as well. - + As an example, if you want to mount the CDROM device, ``/dev/cd0c'', under /mnt, you would execute: - + mount -t cd9660 /dev/cd0c /mnt - + Note that your device name (``/dev/cd0c'' in this example) could be different, depending on the CDROM interface. Note that the ``'' option just causes the ``mount_cd9660'' command to be executed, and so the above example could be shortened to: - + mount_cd9660 /dev/cd0c /mnt - + @@ -2822,17 +2822,17 @@ or the drive is not visible on the bus. Feed the drive something, and/or check its master/slave status if it is IDE (ATAPI). It can take a couple of seconds for a CDROM drive to notice that it's been fed, so be patient. - + Sometimes a SCSI CD-ROM may be missed because it hadn't enough time to answer the bus reset. If you have a SCSI CD-ROM please try to add the following symbol into your kernel configuration file and recompile. - + options "SCSI_DELAY=15" - + @@ -2840,16 +2840,16 @@ and recompile. If it's parallel, and the only problem is that it's terribly slow, try setting your printer port into ``polled'' mode: - + lptcontrol -p - + Some newer HP printers are claimed not to work correctly in interrupt mode, apparently due to some (not yet exactly understood) timing problem. - + @@ -2863,18 +2863,18 @@ to pass all memory tests, yet fail under operating conditions (such as during bus mastering DMA from a SCSI controller like the Adaptec 1542, when you're beating on memory by compiling a kernel, or just when the system's running particularly hot). - + The SIG11 FAQ (listed below) points up slow memory as being the most common problem. Increase the number of wait states in your BIOS setup, or get faster memory. - + For me the guilty party has been bad cache RAM or a bad on-board cache controller. Try disabling the on-board (secondary) cache in the BIOS setup and see if that solves the problem. - + There's an extensive FAQ on this at the SIG11 problem FAQ - + @@ -2888,9 +2888,9 @@ URL="http://www.FreeBSD.org/cgi/man.cgi?sio(4)">sio(4) driver it will touch this port even if you don't have the fourth serial port, and even if you disable sio3 (the fourth port) which normally uses this address. - + Until the bug has been fixed, you can use this workaround: - + @@ -2913,14 +2913,14 @@ into configuration mode). - + If you want to be able to use your serial ports, you'll have to build a new kernel with the following modification: in /usr/src/sys/i386/isa/sio.c find the one occurrence of the string 0x2e8 and remove that string and the preceding comma (keep the trailing comma). Now follow the normal procedure of building a new kernel. - + 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 @@ -2931,7 +2931,7 @@ Mach64 cards and even a dedicated X server for those cards. I have 128 MB of RAM but the system only uses 64 MB. - + Due to the manner in which FreeBSD gets the memory size from the @@ -2939,7 +2939,7 @@ BIOS, it can only detect 16 bits worth of Kbytes in size (65535 Kbytes = 64MB) (or less... some BIOSes peg the memory size to 16M). If you have more than 64MB, FreeBSD will attempt to detect it; however, the attempt may fail. - + To work around this problem, you need to use the kernel option specified below. There is a way to get complete memory information from the BIOS, but we don't have room in the @@ -2947,33 +2947,33 @@ bootblocks to do it. Someday when lack of room in the bootblocks is fixed, we'll use the extended BIOS functions to get the full memory information...but for now we're stuck with the kernel option. - + options "MAXMEM=<n>" - + Where n is your memory in Kilobytes. For a 128 MB machine, you'd want to use 131072. - + FreeBSD 2.0 panics with ``kmem_map too small!'' Note The message may also be ``mb_map too small!'' - + The panic indicates that the system ran out of virtual memory for network buffers (specifically, mbuf clusters). You can increase the amount of VM available for mbuf clusters by adding: - + options "NMBCLUSTERS=<n>" - + to your kernel config file, where <n> is a number in the range 512-4096, depending on the number of concurrent TCP connections you need to support. I'd recommend trying 2048 - this should get rid of the panic completely. You can monitor the number of mbuf clusters allocated/in use on the system with -netstat -m. The default value for NMBCLUSTERS is +netstat -m. The default value for NMBCLUSTERS is 512 + MAXUSERS * 16. - + @@ -2982,33 +2982,33 @@ number of mbuf clusters allocated/in use on the system with The logic that attempts to detect an out of date /var/db/kvm_*.db files sometimes fails and using a mismatched file can sometimes lead to panics. - + If this happens, reboot single-user and do: - + rm /var/db/kvm_*.db - + ahc0: brkadrint, Illegal Host Access at seqaddr 0x0 This is a conflict with an Ultrastor SCSI Host Adapter. - + During the boot process enter the kernel configuration menu and disable uha0, which is causing the problem. - + Sendmail says ``mail loops back to myself'' This is answered in the sendmail FAQ as follows:- - + * I'm getting "Local configuration error" messages, such as: @@ -3025,7 +3025,7 @@ which is causing the problem. to /etc/sendmail.cf. - + The current version of the sendmail FAQ is no longer maintained with the sendmail release. It is however regularly posted to comp.mail.sendmail, @@ -3037,7 +3037,7 @@ You can also receive a copy via email by sending a message to mail-server@rtfm.mit.edu with the command "send usenet/news.answers/mail/sendmail-faq" as the body of the message. - + @@ -3045,24 +3045,24 @@ message. The remote machine may be setting your terminal type -to something other than the cons25 terminal type +to something other than the cons25 terminal type required by the FreeBSD console. - + There are a number of possible work-arounds for this problem: -After logging on to the remote machine, set your TERM shell -variable to ansi or +After logging on to the remote machine, set your TERM shell +variable to ansi or sco if the remote machine knows about these terminal types. -Use a VT100 emulator like screen -at the FreeBSD console. -screen offers you the ability to run multiple -concurrent sessions from one terminal, and is a neat program in its own right. +Use a VT100 emulator like screen +at the FreeBSD console. +screen offers you the ability to run multiple +concurrent sessions from one terminal, and is a neat program in its own right. Each screen window behaves like a VT100 terminal, so the TERM variable at the remote end should be set to vt100. @@ -3070,52 +3070,52 @@ vt100. -Install the cons25 terminal database entry on +Install the cons25 terminal database entry on the remote machine. The way to do this depends on the operating system on the remote machine. The system administration manuals for the remote system should be able to help you here. -Fire up an X server at the FreeBSD end and login to the remote machine -using an X based terminal emulator such as xterm or -rxvt. The TERM variable at the remote host +Fire up an X server at the FreeBSD end and login to the remote machine +using an X based terminal emulator such as xterm or +rxvt. The TERM variable at the remote host should be set to xterm or vt100 . - + My machine prints "calcru: negative time..." -This can be caused by various hardware and/or software ailments -relating to interrupts. It may be due to bugs but can also happen -by nature of certain devices. Running TCP/IP over the parallel -port using a large MTU is one good way to provoke this problem. -Graphics accelerators can also get you here, in which case you +This can be caused by various hardware and/or software ailments +relating to interrupts. It may be due to bugs but can also happen +by nature of certain devices. Running TCP/IP over the parallel +port using a large MTU is one good way to provoke this problem. +Graphics accelerators can also get you here, in which case you should check the interrupt setting of the card first. - -A side effect of this problem are dying processes with the + +A side effect of this problem are dying processes with the message "SIGXCPU exceeded cpu time limit". - -For FreeBSD 3.0 and later from Nov 29, 1998 forward: If the -problem cannot be fixed otherwise the solution is to set + +For FreeBSD 3.0 and later from Nov 29, 1998 forward: If the +problem cannot be fixed otherwise the solution is to set this sysctl variable: sysctl -w kern.timecounter.method=1 - - This means a performance impact, but considering the cause of -this problem, you probably will not notice. If the problem -persists, keep the sysctl set to one and set the "NTIMECOUNTER" -option in your kernel to increasingly large values. If by the -time you have reached "NTIMECOUNTER=20" the problem isn't -solved, interrupts are too hosed on your machine for reliable + + This means a performance impact, but considering the cause of +this problem, you probably will not notice. If the problem +persists, keep the sysctl set to one and set the "NTIMECOUNTER" +option in your kernel to increasingly large values. If by the +time you have reached "NTIMECOUNTER=20" the problem isn't +solved, interrupts are too hosed on your machine for reliable timekeeping. - + @@ -3129,10 +3129,10 @@ 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 long-term viability). We encourage commercial software vendors to send their -entries here for inclusion. See +entries here for inclusion. See the Vendors page for a longer list. - + Where can I get Motif for FreeBSD? @@ -3140,7 +3140,7 @@ for a longer list. Contact Apps2go for the least expensive ELF Motif 2.1.20 distribution for FreeBSD (either i386 or Alpha). - + There are two distributions, the "developement edition" and the "runtime edition" (for much less). These distributions includes: @@ -3168,20 +3168,20 @@ and above). - + Be sure to specify that you want the FreeBSD version of Motif when ordering (don't 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. - + More info Apps2go WWW page - + - + @@ -3190,9 +3190,9 @@ This is currently a FTP only download. Sales or Support email addresses. - + - + @@ -3200,15 +3200,15 @@ This is currently a FTP only download. phone (817) 431 8775 or +1 817 431-8775 - + - + Contact Metro Link for an either ELF or a.out Motif 2.1 distribution for FreeBSD. - + This distribution includes: @@ -3240,15 +3240,15 @@ files. - + Be sure to specify that you want the FreeBSD version 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. - + This distribution includes: @@ -3280,12 +3280,12 @@ eariler). - + Be sure to specify that you want the FreeBSD version 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. - + @@ -3293,42 +3293,42 @@ future this will change to a unified CD distribution like their CDE. Xi Graphics used to sell CDE for FreeBSD, but no longer do. - + KDE is an open source X11 desktop which is similar to CDE in many respects. You might also like the look and feel of xfce. KDE and xfce are both in the ports system. - + Are there any commercial high-performance X servers? -Yes, Xi Graphics and +Yes, Xi Graphics and Metro Link sells Accelerated-X product for FreeBSD and other Intel based systems. - + The Metro Link offering is a high performance X Server that offers easy configuration using the FreeBSD Package suite of tools, support for multiple concurrent video boards and is distributed in binary form only, in a convienent FTP download. 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 FreeBSD (see above). - + More info Metro Link WWW page - + - + @@ -3337,9 +3337,9 @@ Link offering is available at the very reasonable price of $39. Sales or Support email addresses. - + - + @@ -3347,31 +3347,31 @@ Link offering is available at the very reasonable price of $39. phone (954) 938-0283 or +1 954 938-0283 - + - + 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 Graphics also offers a high performance X Server taylored for laptop support. - + There is a free "compatibility demo" of version 5.0 available. - + Xi Graphics also sells Motif and CDE for FreeBSD (see above). - + More info Xi Graphics WWW page - + - + @@ -3380,9 +3380,9 @@ laptop support. Sales or Support email addresses. - + - + @@ -3390,21 +3390,21 @@ laptop support. phone (800) 946 7433 or +1 303 298-7478. - + - + Are there any Database systems for FreeBSD? Yes! See the Commercial Vendors section of FreeBSD's Web site. - + Also see the Databases section of the Ports collection. - + @@ -3412,7 +3412,7 @@ laptop support. Yes. The following pages tell you exactly how to setup Linux-Oracle on FreeBSD: - + @@ -3427,7 +3427,7 @@ on FreeBSD: - + @@ -3444,20 +3444,20 @@ FreeBSD. The list currently tops 1800 and is growing daily, so come back to check often or subscribe to the freebsd-announce mailing list for periodic updates on new entries. - + Most ports should be available for the 2.2, 3.x and 4.0 branches, and many of them should work on 2.1.x systems as well. Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release in also included in the ports/ directory. - + We also support the concept of a ``package'', essentially no more than a gzipped binary distribution with a little extra intelligence embedded in it for doing whatever custom installation work is required. A package can be installed and uninstalled again easily without having to know the gory details of which files it includes. - + Use the package installation menu in /stand/sysinstall (under the post-configuration menu item) or invoke the pkg_add(1) command on the specific package files you're @@ -3466,15 +3466,15 @@ their .tgz suffix and CDROM 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 following locations: - + for 2.2.8-RELEASE/2.2.8-STABLE ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/ - + - + @@ -3482,9 +3482,9 @@ of FreeBSD at the following locations: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/ - + - + @@ -3492,7 +3492,7 @@ of FreeBSD at the following locations: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/ - + @@ -3506,14 +3506,14 @@ of FreeBSD at the following locations: - + or your nearest local mirror site. - + Note that all ports may not be available as packages since new ones are constantly being added. It is always a good idea to check back periodically to see which packages are available at the ftp.FreeBSD.org master site. - + @@ -3554,7 +3554,7 @@ at the ftp.FreeBSD.org m You are trying to run a package built on 2.2 and later on a 2.1.x system. Please take a look at the previous section and get the correct port/package for your system. - + I get a message "Error: can't find @@ -3562,7 +3562,7 @@ libc.so.4.0" You accidently downloaded packages meant for 4.X and 5.X -systems and attempted to install them on your 2.X or 3.X FreeBSD system. +systems and attempted to install them on your 2.X or 3.X FreeBSD system. Please download the correct version of the packages. @@ -3576,15 +3576,15 @@ id="emul"> You will need to add the alternative math emulator to your kernel; you do this by adding the following to your kernel config file and it will be compiled in. - + options GPL_MATH_EMULATE - + NOTE You will need to remove the MATH_EMULATE option when you do this. - + @@ -3594,18 +3594,18 @@ option when you do this. You first need to edit the /etc/sysconfig (or /etc/rc.conf) file in the last section to change the following variable to YES: - + # Set to YES if you want ibcs2 (SCO) emulation loaded at startup ibcs2=NO - + It will load the ibcs2 kernel module at startup. - + You'll then need to set up /compat/ibcs2/dev to look like: - + lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 X0R@ -> /dev/null lrwxr-xr-x 1 root wheel 7 Oct 15 22:20 nfsd@ -> socksys @@ -3614,13 +3614,13 @@ lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -> /dev/null crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx - + You just need socksys to go to /dev/null to fake the open & close. The code in -CURRENT will handle the rest. This is much cleaner than the way it was done before. If you want the spx driver for a local socket X connection, define SPX_HACK when you compile the system. - + @@ -3629,7 +3629,7 @@ want the spx driver for a local socket X connectio After installing the inn package or port, an excellent place to start is Dave Barr's INN Page where you'll find the INN FAQ. - + @@ -3637,14 +3637,14 @@ start is Dave Barr's I Use the Port, Luke! A pre-patched version of Apache is available in the ports tree. - + Does FreeBSD support Java? Yes. Please see http://www.FreeBSD.org/java/. - + @@ -3658,7 +3658,7 @@ someone might have committed a change to the port which works for report on this with the send-pr(1) command, since the ports collection is supposed to work for both the -CURRENT and -STABLE branches. - + @@ -3671,7 +3671,7 @@ They are included in the compat22 distribution. Use /stand/sysinstall or install.sh in the compat22 subdirectory and install it. Also read ERRATAs for 3.1-R and 3.2-R. - + @@ -3683,11 +3683,11 @@ id="kernelconfig"> I'd like to customize my kernel. Is it difficult? - + Not at all! Check out the kernel config section of the Handbook. - + NOTE: I recommend making a dated snapshot of your kernel in kernel.YYMMDD after you get it all working, that way if you do something dire the next time you play with your configuration @@ -3695,7 +3695,7 @@ you can boot that kernel instead of having to go all the way back to kernel.GENERIC. This is particularly important if you're now booting off a controller that isn't supported in the GENERIC kernel (yes, personal experience). - + @@ -3707,7 +3707,7 @@ kernel configuration file because you don't have a math co-processor, right? Wrong! :-) The npx0 is MANDATORY. Even if you don't have a mathematic co-processor, you must include the npx0 device. - + @@ -3716,12 +3716,12 @@ device. Q. When I compile a kernel with multi-port serial code, it tells me that only the first port is probed and the rest skipped due to interrupt conflicts. How do I fix this? - + A. The problem here is that FreeBSD 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 a example: - + # # Multiport high-speed serial line - 16550 UARTS @@ -3732,7 +3732,7 @@ on all but one port. Here is a example: device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr - + @@ -3741,7 +3741,7 @@ on all but one port. Here is a example: You need to uncomment the following line in the generic config file (or add it to your config file), add a ``flags 0x1'' on the fdc line and recompile. - + controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 flags 0x1 vector fdintr disk fd0 at fdc0 drive 0 ^^^^^^^^^ @@ -3750,28 +3750,28 @@ disk fd1 at fdc0 drive 1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - + Next, you create a device called /dev/ft0 by going into /dev and run the following command: - + sh ./MAKEDEV ft0 - + for the first device. ft1 for a second one and so on. - + You will have a device called /dev/ft0, which you can write to through a special program to manage it called ``ft'' - see the man page on ft for further details. - + Versions previous to also had some trouble dealing with bad tape media; if you have trouble where ft seems to go back and forth over the same spot, try grabbing the latest version of ft from /usr/src/sbin/ft in and try that. - + @@ -3787,56 +3787,56 @@ id="admin"> /etc/sysconfig. All the options are to be specified in this file and other files such as /etc/rc and /etc/netstart just include it. - + Look in the /etc/sysconfig file and change the value to match your system. This file is filled with comments to show what to put in there. - + In post-2.2.1 and 3.0, /etc/sysconfig was renamed to a more self-describing rc.conf file and the syntax cleaned up a bit in the process. /etc/netstart was also renamed to /etc/rc.network so that all files could be copied with a cp /usr/src/etc/rc* /etc command. - + /etc/rc.local is here as always and may be used to start up additional local services like INN or set custom options. - + The /etc/rc.serial is for serial port initialization (e.g. locking the port characteristics, and so on.). - + The /etc/rc.i386 is for Intel-specifics settings, such as iBCS2 emulation or the PC system console configuration. - + Starting with 2.1.0R, you can also have "local" startup files in a directory specified in /etc/sysconfig (or /etc/rc.conf): - + # Location of local startup files. local_startup=/usr/local/etc/rc.local.d - + Each file ending in .sh will be executed in alphabetical order. - + If you want to ensure a certain execution order without changing all the file names, you can use a scheme similar to the following with digits prepended to each file name to insure the ordering: - + 10news.sh 15httpd.sh 20ssh.sh - + It can be seen as ugly (or SysV :-)) but it provides a simple and regular scheme for locally-added packages without resorting to magical editing of /etc/rc.local. Many of the ports/packages assume that /usr/local/etc/rc.d is a local startup directory. - + @@ -3844,17 +3844,17 @@ assume that /usr/local/etc/rc.d is a local startup director Use the adduser command. For more complicated usage, the pw command. - + To remove the user again, use the rmuser command. - + How can I add my new hard disk to my FreeBSD system? -See the Disk Formatting Tutorial at +See the Disk Formatting Tutorial at www.FreeBSD.org. - + @@ -3865,32 +3865,32 @@ even a floppy, if you want to use it that way), or a new hard disk, once it's installed and recognized by the system, and you have your cartridge/floppy/whatever slotted in, things are pretty much the same for all devices. - + (this section is based on Mark Mayo's ZIP FAQ) - + If it's a ZIP drive or a floppy , you've already got a DOS filesystem on it, you can use a command like this: - + mount -t msdos /dev/fd0c /floppy - + if it's a floppy, or this: - + mount -t msdos /dev/da2s4 /zip - + for a ZIP disk with the factory configuration. - + For other disks, see how they're laid out using fdisk or /stand/sysinstall. - + The rest of the examples will be for a ZIP drive on da2, the third SCSI disk. - + Unless it's a floppy, or a removable you plan on sharing with other people, it's probably a better idea to stick a BSD file system on it. You'll get long filename support, at least a 2X @@ -3900,42 +3900,42 @@ use fdisk or - + dd if=/dev/zero of=/dev/rda2 count=2 disklabel -Brw da2 auto - + You can use disklabel or /stand/sysinstall to create multiple BSD partitions. You'll certainly want to do this if you're adding swap space on a fixed disk, but it's probably irrelevant on a removable drive like a ZIP. - + Finally, create a new file system, this one's on our ZIP drive using the whole disk: - + newfs /dev/rda2c - + and mount it: - + mount /dev/da2c /zip - + and it's probably a good idea to add a line like this to /etc/fstab so you can just type "mount /zip" in the future: - + /dev/da2c /zip ffs rw,noauto 0 0 - + @@ -3945,14 +3945,14 @@ future: partitions. For example, if you have an "E" partition as the second DOS partition on the second SCSI drive, you need to create the special files for "slice 5" in /dev, then mount /dev/da1s5: - + # cd /dev # ./MAKEDEV da1s5 # mount -t msdos /dev/da1s5 /dos/e - + @@ -3962,16 +3962,16 @@ the special files for "slice 5" in /dev, then mount /dev/da1s5: Mounting disk partitions from Digital UNIX and other systems that support UFS may be more complex, depending on the details of the disk partitioning for the operating system in question. - + Linux: 2.2 and later have support for ext2fs partitions. See mount_ext2fs for more information. - - NT: A read-only NTFS driver exists for FreeBSD. For more + + NT: A read-only NTFS driver exists for FreeBSD. For more information, see this tutorial by Mark Ovens at http://ukug.uk.freebsd.org/~mark/ntfs_install.html. - + Any other information on this subject would be appreciated. - + @@ -3986,7 +3986,7 @@ partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: - + [boot loader] timeout=30 @@ -3997,74 +3997,74 @@ something like this: C:\="DOS" - + For 2.2.x systems this procedure assumes that DOS, NT, FreeBSD, or whatever have been installed into their respective fdisk partitions on the same disk. In my case DOS & NT are in the first fdisk partition and FreeBSD is in the second. I also installed FreeBSD to boot from its native partition, not the disk MBR. - + Mount a DOS-formatted floppy (if you've converted to NTFS) or the FAT partition, under, say, /mnt. - + dd if=/dev/rda0a of=/mnt/bootsect.bsd bs=512 count=1 - + Reboot into DOS or NT. NTFS users copy the bootsect.bsd and/or the bootsect.lnx file from the floppy to C:\. Modify the attributes (permissions) on boot.ini with: - + attrib -s -r c:\boot.ini - + Edit to add the appropriate entries from the example boot.ini above, and restore the attributes: - + attrib +s +r c:\boot.ini - + If FreeBSD is booting from the MBR, restore it with the DOS ``fdisk'' command after you reconfigure them to boot from their native partitions. For FreeBSD 3.x systems the procedure is somewhat simpler. -If FreeBSD is installed on the same disk as the NT boot partition -copy /boot/boot1 to c:\bootsect.bsd +If FreeBSD is installed on the same disk as the NT boot partition +copy /boot/boot1 to c:\bootsect.bsd or if FreeBSD is installed on a different disk copy /boot/boot0 to c:\bootsect.bsd. Then edit c:\bootsect.ini as described earlier. - + 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 operating +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 table=/dev/hda label=FreeBSD -(the above assumes that your FreeBSD slice is known to Linux as -/dev/hda2; tailor to suit your setup). Then, +(the above assumes that your FreeBSD 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 -``loader=/boot/chain.b'' to the LILO entry. + +If FreeBSD resides on another disk, you need to add +``loader=/boot/chain.b'' to the LILO entry. For example: other=/dev/dab4 table=/dev/dab @@ -4072,35 +4072,35 @@ For example: label=FreeBSD - -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 + +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 specify: Boot: 1:da(0,a)/kernel - + On FreeBSD 2.2.5 and later, you can configure boot(8) to automatically do this for you at boot time. - + The Linux+FreeBSD mini-HOWTO is a good reference for FreeBSD and Linux interoperability issues. - + How do I boot FreeBSD and Linux using BootEasy? -Install LILO at the start of your Linux boot partition instead of +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're running Windows-95 and Linux this is recommended anyway, to make it simpler to get Linux booting again if you should need to reinstall Windows95 (which is a Jealous Operating System, and will bear no other Operating Systems in the Master Boot Record). - + @@ -4116,7 +4116,7 @@ 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 compatible with other operating systems. - + So why it is called ``dangerous''? A disk in this mode doesn't contain what normal PC utilities would consider a valid fdisk table. Depending on how well they have been @@ -4126,78 +4126,78 @@ damage the BSD bootstrap without even asking or notifying you. In addition, the ``dangerously dedicated'' disk's layout is known to confuse many BIOSsen, including those from AWARD (eg. as found in HP Netserver and Micronics systems as well as -many others) and Symbios/NCR (for the popular 53C8xx range of +many others) and Symbios/NCR (for the popular 53C8xx range of SCSI controllers). This isn't a complete list, there are more. Symptoms of this confusion include the "read error" message printed by the FreeBSD bootstrap when it can't 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 +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 ``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 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 won't be able to boot. - + ``Dangerously dedicated'' mode tries to work around this by making the problem simpler. In some cases, it gets it right. But it's meant to be used as a last-ditch alternative - there are better ways to solve the problem 99 times out of 100. - + So, how do you avoid the need for ``DD'' mode when you're installing? Start by making a note of the geometry that your BIOS claims to be using for your disks. You can arrange to have -the kernel print this as it boots by specifying ``-v'' at the -``boot:'' prompt, or using ``boot -v'' in the loader. Just -before the installer starts, the kernel will print a list of +the kernel print this as it boots by specifying ``-v'' at the +``boot:'' prompt, or using ``boot -v'' in the loader. Just +before the installer starts, the kernel will print a list of BIOS geometries. Don't 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 FreeBSD lists your disks, first IDE, then SCSI. - -When you're slicing up your disk, check that the disk geometry -displayed in the FDISK screen is correct (ie. it matches the BIOS -numbers); if it's wrong, use the ``g'' key to fix it. You may have + +When you're slicing up your disk, check that the disk geometry +displayed in the FDISK screen is correct (ie. it matches the BIOS +numbers); if it's wrong, use the ``g'' key to fix it. You may have to do this if there's absolutely nothing on the disk, or if the -disk has been moved from another system. Note that this is only +disk has been moved from another system. Note that this is only an issue with the disk that you're going to boot from; FreeBSD will sort itself out just fine with any other disks you may have. - -Once you've got the BIOS and FreeBSD agreeing about the -geometry of the disk, your problems are almost guaranteed to be + +Once you've got the BIOS and FreeBSD 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 error'' message -when you try to boot, it's time to cross your fingers and +when you try to boot, it's time to cross your fingers and go for it - there's nothing left to lose. - + To return a ``dangerously dedicated'' disk for normal PC use, there are basically two options. The first is, you write enough NULL bytes over the MBR to make any subsequent installation believe this to be a blank disk. You can do this for example with - + dd if=/dev/zero of=/dev/rda0 count=15 - + Alternatively, the undocumented DOS ``feature'' - + fdisk /mbr - + will to install a new master boot record as well, thus clobbering the BSD bootstrap. - + @@ -4210,47 +4210,47 @@ main memory. However, if you have a very small amount of main memory you may want to configure swap beyond that. It is also a good idea to configure sufficient swap relative to anticipated future memory upgrades so you do not have to futz with your swap configuration later. - + Adding swap onto a separate disk makes things faster than simply adding swap onto the same disk. As an example, if you are compiling source located on one disk, and the swap is on another disk, this is much faster than both swap and compile on the same disk. This is true for SCSI disks specifically. - + When you have several disks, configuring a swap partition on each one is usually beneficial, even if you wind up putting swap on a work disk. Typically, each fast disk in your system should have some -swap configured. FreeBSD supports up to 4 interleaved swap devices by +swap configured. FreeBSD supports up to 4 interleaved swap devices by default. When configuring multiple swap partitions you generally -want to make them all about the same size, but people sometimes make +want to make them all about the same size, but people sometimes make their primary swap parition larger in order to accomodate a kernel core dump. Your primary swap partition must be at least as large as main memory in order to be able to accomodate a kernel core. - + IDE drives are not able to allow access to both drives on the same channel at the same time (FreeBSD doesn't support mode 4, so all IDE disk I/O is ``programmed''). I would still suggest putting your swap on a separate drive however. The drives are so cheap, it is not worth worrying about. - + Swapping over NFS is only recommended if you do not have a local disk to swap to. Swapping over NFS is slow and inefficient in FreeBSD -releases prior to 4.x, but reasonably fast in releases greater or +releases prior to 4.x, but reasonably fast in releases greater or equal to 4.0. Even so, it will be limited to the network bandwidth available and puts an additional burden on the NFS server. - + Here is an example for 64Mb vn-swap (/usr/swap0, though of course you can use any name that you want). - + Make sure your kernel was built with the line - + pseudo-device vn 1 #Vnode driver (turns a file into a device) - + in your config-file. The GENERIC kernel already contains this. - + @@ -4297,14 +4297,14 @@ of course you can use any name that you want). - + To enable the swap file immediately, type - + vnconfig -ce /dev/vn0c /usr/swap0 swap - + @@ -4313,7 +4313,7 @@ of course you can use any name that you want). Please have a look at the Handbook entry on printing. It should cover most of your problem. See the Handbook entry on printing. - + @@ -4322,24 +4322,24 @@ should cover most of your problem. See the The kbdcontrol program has an option to load a keyboard map file. Under /usr/share/syscons/keymaps are a number of map files. Choose the one relevant to your system and load it. - + kbdcontrol -l uk.iso - + Both the /usr/share/syscons/keymaps and the .kbd -extension are assumed by +extension are assumed by kbdcontrol. - + This can be configured in /etc/sysconfig (or rc.conf). See the appropriate comments in this file. - + In 2.0.5R and later, everything related to text fonts, keyboard mapping is in /usr/share/examples/syscons. - + The following mappings are currently supported: - + @@ -4449,7 +4449,7 @@ mapping is in /usr/share/examples/syscons. - + @@ -4477,35 +4477,35 @@ to be enforced on. ie: - + What's inappropriate about my ccd? The symptom of this is: - + # ccdconfig -C ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format # - + This usually happens when you are trying to concatenate the `c' partitions, which default to type `unused'. The ccd driver requires the underlying partition type to be FS_BSDFFS. Edit the disklabel of the disks you are trying to concatenate and change the types of partitions to `4.2BSD'. - + Why can't I edit the disklabel on my ccd? The symptom of this is: - + # disklabel ccd0 (it prints something sensible here, so let's try to edit it) @@ -4516,11 +4516,11 @@ to concatenate and change the types of partitions to # - + This is because the disklabel returned by ccd is actually a `fake' one that is not really on the disk. You can solve this problem by writing it back explicitly, as in: - + # disklabel ccd0 > /tmp/disklabel.tmp # disklabel -Rr ccd0 /tmp/disklabel.tmp @@ -4528,7 +4528,7 @@ this problem by writing it back explicitly, as in: (this will work now) - + @@ -4537,7 +4537,7 @@ this problem by writing it back explicitly, as in: Yes, FreeBSD supports System V-style IPC. This includes shared memory, messages and semaphores. You need to add the following lines to your kernel config to enable them. - + options SYSVSHM options "SHMMAXPGS=64" # 256Kb of sharable memory @@ -4545,13 +4545,13 @@ lines to your kernel config to enable them. options SYSVMSG # enable for messaging - + Recompile and install. - + NOTE: You may need to increase SHMMAXPGS to some ridiculous number like 4096 (16M!) if you want to run GIMP. 256Kb is plenty for X11R6 shared memory. - + suited for sites that connect directly to the Internet. Sites that wish to exchange their mail via UUCP must install another sendmail configuration file. - + Tweaking /etc/sendmail.cf manually is considered something for purists. Sendmail version 8 comes with a -new approach of generating config files via some +new approach of generating config files via some m4 preprocessing, where the actual hand-crafted configuration is on a higher abstraction level. You should use the configuration files under - + /usr/src/usr.sbin/sendmail/cf - + If you didn't install your system with full sources, the sendmail config stuff has been broken out into a separate source distribution tarball just for you. Assuming you've got your CD-ROM mounted, do: @@ -4584,31 +4584,31 @@ tarball just for you. Assuming you've got your CD-ROM mounted, do: Don't panic, this is only a few hundred kilobytes in size. The file README in the cf directory can serve as a basic introduction to m4 configuration. - + For UUCP delivery, you are best advised to use the mailertable feature. This constitutes a database that sendmail can use to base its routing decision upon. - + First, you have to create your .mc file. The directory /usr/src/usr.sbin/sendmail/cf/cf is the home of these files. Look around, there are already a few examples. Assuming you have named your file foo.mc, all you need to do in order to convert it into a valid sendmail.cf is: - + &prompt.root; cd /usr/src/usr.sbin/sendmail/cf/cf &prompt.root; make foo.cf &prompt.root; cp foo.cf /etc/sendmail.cf - + A typical .mc file might look like: - + include(`../m4/cf.m4') VERSIONID(`Your version number') OSTYPE(bsd4.4) - + FEATURE(nodns) FEATURE(nocanonify) FEATURE(mailertable) @@ -4629,11 +4629,11 @@ prevent any usage of the DNS during mail delivery. The don't ask. Simply put an Internet hostname there that is able to handle .UUCP pseudo-domain addresses; most likely, you will enter the mail relay of your ISP there. - + Once you've got this, you need this file called /etc/mailertable. A typical example of this gender again: - + # # makemap hash /etc/mailertable.db < /etc/mailertable # @@ -4645,7 +4645,7 @@ horus.UUCP uucp-dom:horus if-bus.UUCP uucp-dom:if-bus . uucp-dom: - + As you can see, this is part of a real-life file. The first three lines handle special cases where domain-addressed mail should not be sent out to the default route, but instead to @@ -4660,13 +4660,13 @@ serves as your universal mail gateway to the world. All of the node names behind the uucp-dom: keyword must be valid UUCP neighbors, as you can verify using the command uuname. - + As a reminder that this file needs to be converted into a DBM database file before being usable, the command line to accomplish this is best placed as a comment at the top of the mailertable. You always have to execute this command each time you change your mailertable. - + Final hint: if you are uncertain whether some particular mail routing would work, remember the option to sendmail. It starts sendmail in address test mode; @@ -4675,7 +4675,7 @@ test for the mail routing. The last line tells you the used internal mail agent, the destination host this agent will be called with, and the (possibly translated) address. Leave this mode by typing Control-D. - + &prompt.user; sendmail -bt ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) Enter <ruleset> <address> @@ -4686,69 +4686,69 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \ < @ interface-business . de > > ^D - + How do I set up mail with a dialup connection to the 'net? - + If you've got a statically assigned IP number, you should not need to adjust anything from the default. Set your host name up as your assigned internet name and sendmail will do the rest. - + If you've got a dynamically assigned IP number and use a dialup ppp connection to the internet, you will probably be given a mailbox on your ISPs mail server. Lets assume your ISPs domain is myISP.com, and that your user name is user. Lets also assume you've called your machine bsd.home and that your ISP has told you that you may use relay.myISP.com as a mail relay. - + In order to retrieve mail from your mailbox, you'll need to install a retrieval agent. Fetchmail is a good choice as it supports many different protocols. Usually, POP3 will be provided by your ISP. If you've chosen to use user-ppp, you can automatically fetch your mail when a connection to the 'net is established with the following entry in /etc/ppp/ppp.linkup: - + MYADDR: !bg su user -c fetchmail - + If you are using sendmail (as shown below) to deliver mail to non-local accounts, put the command - + !bg su user -c "sendmail -q" - + after the above shown entry. This forces sendmail to process your mailqueue as soon as the connection to the 'net is established. - + I'm assuming that you have an account for user on bsd.home. In the home directory of user on bsd.home, create a .fetchmailrc file: - + poll myISP.com protocol pop3 fetchall pass MySecret; - + Needless to say, this file should not be readable by anyone except user as it contains the password MySecret. - + In order to send mail with the correct from: header, you must tell sendmail to use user@myISP.com rather than user@bsd.home. You may also wish to tell sendmail to send all mail via relay.myISP.com, allowing quicker mail transmission. - + The following .mc file should suffice: - + VERSIONID(`bsd.home.mc version 1.0') OSTYPE(bsd4.4)dnl @@ -4768,25 +4768,25 @@ mail via relay.myISP.com, allowing quicker mail transmissio define(`confDELIVERY_MODE',`deferred')dnl - + Refer to the previous section for details of how to turn this .mc file into a sendmail.cf file. Also, don't forget to restart sendmail after updating sendmail.cf. - + Eek! I forgot the root password! -Don't Panic! Simply restart the system, type boot -s +Don't Panic! Simply restart the system, type boot -s at the Boot: prompt (just -s for FreeBSD releases before 3.2) to enter Single User mode. At the question about the shell to use, hit ENTER. You'll be dropped to a &prompt.root; prompt. Enter mount -u / to -remount your root filesystem read/write, then run mount -a to -remount all the filesystems. Run passwd root to +remount your root filesystem read/write, then run mount -a to +remount all the filesystems. Run passwd root to change the root password then run exit to continue booting. - + @@ -4807,68 +4807,68 @@ use the following kernel configuration line instead: options PCVT_CTRL_ALT_DEL For older versions of FreeBSD, -edit the keymap you are using for the console and replace the -boot keywords with nop. The default keymap is +edit the keymap you are using for the console and replace the +boot keywords with nop. The default keymap is /usr/share/syscons/keymaps/us.iso.kbd. You may have to instruct /etc/rc.conf to load this keymap explicitly for the change to take effect. Of course if you are using an alternate keymap for your country, you should edit that one instead. - + How do I reformat DOS text files to UNIX ones? Simply use this perl command: - + perl -i.bak -npe 's/\r\n/\n/g' file ... - + file is the file(s) to process. The modification is done in-place, with the original file stored with a .bak extension. - + Alternatively you can use the tr command: - + tr -d '\r' < dos-text-file > unix-file - + dos-text-file is the file containing DOS text while -unix-file will contain the converted output. This can +unix-file will contain the converted output. This can be quite a bit faster than using perl. - + How do I kill processes by name? Use killall. - + Why is su bugging me about not being in root's ACL? -The error comes from the Kerberos distributed authentication system. +The error comes from the Kerberos distributed authentication system. The problem isn't fatal but annoying. You can either run su with the -K option, or uninstall Kerberos as described in the next question. - + How do I uninstall Kerberos? To remove Kerberos from the system, reinstall the bin distribution -for the release you are running. If you have the CDROM, you can +for the release you are running. If you have the CDROM, you can mount the cd (we'll assume on /cdrom) and run - + cd /cdrom/bin ./install.sh - + @@ -4876,7 +4876,7 @@ mount the cd (we'll assume on /cdrom) and run If you have lots of telnet, ssh, X, or screen users, you'll probably run out of pseudoterminals. Here's how to add more: - + @@ -4919,7 +4919,7 @@ terminals. They should match the form of the existing entries, i.e. they look li -The order of the letter designations is tty[pqrsPQRS][0-9a-v], +The order of the letter designations is tty[pqrsPQRS][0-9a-v], using a regular expression. @@ -4931,7 +4931,7 @@ using a regular expression. - + @@ -4954,7 +4954,7 @@ using a regular expression. a reboot? Go into single user mode and than back to multi user mode. - + On the console do: # shutdown now (Note: without -r or -h) @@ -4962,14 +4962,14 @@ using a regular expression. # return # exit - + What is a sandbox? "Sandbox" is a security term. It can mean two things: - + @@ -5037,20 +5037,20 @@ that he is sitting in it. - + UNIX implements two core sanboxes. 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 can not 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 patricular 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 on-disk data. - + @@ -5058,11 +5058,11 @@ used to firewall off on-disk data. How do I let ordinary users mount floppies and other removable media? - + Ordinary users can be permitted to mount devices. Here is how: - + As root assign the appropriate @@ -5071,7 +5071,7 @@ used to firewall off on-disk data. For example, to allow users to mount the first floppy drive, use: - + &prompt.root; chmod 777 /dev/fd0 @@ -5079,23 +5079,23 @@ used to firewall off on-disk data. As root set the sysctl variable vfs.usermount to 1. - + &prompt.root; sysctl -w vfs.usermount=1 - + Users can now mount /dev/fd0 onto a directory that they own: - + &prompt.user; mkdir ~/my-mount-point &prompt.user; mount -t msdos /dev/fd0 ~/my-mount-point Unmounting the device is simple: - + &prompt.user; umount ~/my-mount-point - + Enabling vfs.usermount, however, has - negative security implications. A better way to access MSDOS + negative security implications. A better way to access MSDOS formatted media is to use the mtools package in the ports collection. @@ -5115,14 +5115,14 @@ id="x"> The easiest way is to simply specify that you want to run X during the installation process. - + Then read and follow the documentation on the xf86config tool, which assists you in configuring XFree86(tm) for your particular graphics card/mouse/etc. - + You may also wish to investigate the Xaccel server. See the section on Xi Graphics or Metro Link for more details. - + and use X, see and set up moused. - + Then edit /etc/XF86Config and make sure you have the following lines. @@ -5148,27 +5148,27 @@ Device "/dev/sysmouse" ..... The above example is for XFree86 3.3.2 or later. For earlier -versions, the Protocol should be +versions, the Protocol should be MouseSystems. Some people prefer to use ``/dev/mouse'' under X. To make this work, ``/dev/mouse'' should be linked to /dev/sysmouse: - + # cd /dev # rm -f mouse # ln -s sysmouse mouse - + My mouse has a fancy wheel. Can I use it in X? - + Yes. But you need to customize X client programs. See Colas Nahaboo's web page (http://www.inria.fr/koala/colas/mouse-wheel-scroll/). @@ -5377,18 +5377,18 @@ EndSection X Window menus and dialog boxes don't work right! Try turning off the Num Lock key. - + If your Num Lock key is on by default at boot-time, you may add the following line in the ``Keyboard'' section of the XF86Config file. - + # Let the server do the NumLock processing. This should only be # required when using pre-R6 clients ServerNumLock - + @@ -5397,12 +5397,12 @@ the following line in the ``Keyboard'' section of Virtual consoles, put simply, enable you to have several simultaneous sessions on the same machine without doing anything complicated like setting up a network or running X. - + When the system starts, it will display a login prompt on the monitor after displaying all the boot messages. You can then type in your login name and password and start working (or playing!) on the first virtual console. - + At some point, you will probably wish to start another session, perhaps to look at documentation for a program you are running or to read your mail while waiting for an @@ -5410,15 +5410,15 @@ FTP transfer to finish. Just do Alt-F2 (hold down the Alt key and press the F2 key), and you will find a login prompt waiting for you on the second ``virtual console''! When you want to go back to the original session, do Alt-F1. - + The default FreeBSD installation has three virtual consoles enabled (8 starting with 3.3-RELEASE), and Alt-F1, Alt-F2, and Alt-F3 will switch between these virtual consoles. - + To enable more of them, edit /etc/ttys and add entries for ``ttyv4'' to ``ttyvc'' after the comment on ``Virtual terminals'': - + # Edit the existing entry for ttyv3 in /etc/ttys and change # "off" to "on". @@ -5433,72 +5433,72 @@ comment on ``Virtual terminals'': ttyvb "/usr/libexec/getty Pc" cons25 on secure - + Use as many or as few as you want. The more virtual terminals you have, the more resources that are used; this can be important if you have 8MB RAM or less. You may also want to change the ``secure'' to ``insecure''. - + IMPORTANT NOTE if you want to run an X server you MUST leave at least one virtual terminal unused (or turned off) for it to use. That is to say that if you want to have a login prompt pop up for all twelve of your Alt-function keys, you're out of luck - you can only do this for eleven of them if you also want to run an X server on the same machine. - + The easiest way to disable a console is by turning it off. For example, if you had the full 12 terminal allocation mentioned above and you wanted to run X, you would change settings for virtual terminal 12 from: - + ttyvb "/usr/libexec/getty Pc" cons25 on secure - + to: - + ttyvb "/usr/libexec/getty Pc" cons25 off secure - + If your keyboard has only ten function keys, you would end up with: - + ttyv9 "/usr/libexec/getty Pc" cons25 off secure ttyva "/usr/libexec/getty Pc" cons25 off secure ttyvb "/usr/libexec/getty Pc" cons25 off secure - + (You could also just delete these lines.) - + Once you have edited /etc/ttys, the next step is to make sure that you have enough virtual terminal devices. The easiest way to do this is: - + # cd /dev # ./MAKEDEV vty12 # For 12 devices - + Next, the easiest (and cleanest) way to activate the virtual consoles is to reboot. However, if you really don't want to reboot, you can just shut down the X Window system and execute (as root): - + kill -HUP 1 - + It's imperative that you completely shut down X Window if it is running, before running this command. If you don't, your system will probably appear to hang/lock up after executing the kill command. - + @@ -5512,7 +5512,7 @@ virtual terminal or back to X Window. You do not need to also press the Ctrl key. If you use the control key to switch back to X on some older releases, you can find your text console stuck in ``control-lock'' mode. Tap the control key to wake it up again. - + @@ -5520,23 +5520,23 @@ mode. Tap the control key to wake it up again. There are two schools of thought on how to start xdm. One school starts xdm from /etc/ttys using the supplied example, while the other -simply runs xdm from rc.local or +simply runs xdm from rc.local or from a X.sh script in /usr/local/etc/rc.d. -Both are equally valid, and one may work in +Both are equally valid, and one may work in situations where the other doesn't. In both cases the result is the same: X will popup a graphical login: prompt. - + The ttys method has the advantage of documenting which vty X will start on and passing the responsibility of restarting the X server on logout to init. The rc.local method makes it easy to kill xdm if there is a problem starting the X server. - -If loaded from rc.local, xdm should be started without any -arguments (i.e., as a daemon). xdm must start AFTER getty runs, or -else getty and xdm will conflict, locking out the console. The best + +If loaded from rc.local, xdm should be started without any +arguments (i.e., as a daemon). xdm must start AFTER getty runs, or +else getty and xdm will conflict, locking out the console. The best way around this is to have the script sleep 10 seconds or so then launch xdm. - + If you are to start xdm from /etc/ttys, there still is a chance of conflict between xdm and getty. One way to @@ -5544,12 +5544,12 @@ launch xdm. /usr/X11R6/lib/X11/xdm/Xservers file. :0 local /usr/X11R6/bin/X vt4 - + The above example will direct the X server to run in /dev/ttyv3. Note the number is offset by one. The X server counts the vty from one, whereas the FreeBSD kernel numbers the vty from zero. - + @@ -5557,24 +5557,24 @@ launch xdm. If you start X with startx, the permissions on /dev/console will not get changed, resulting in things like xterm -C and xconsole not working. - + This is because of the way console permissions are set by default. On a multi-user system, one doesn't necessarily want just any user to be able to write on the system console. For users who are logging -directly onto a machine with a VTY, the +directly onto a machine with a VTY, the fbtab file exists to solve such problems. - + In a nutshell, make sure an uncommented line of the form - + /dev/ttyv0 0600 /dev/console - + is in /etc/fbtab and it will ensure that whomever logs in on /dev/ttyv0 will own the console. - + @@ -5582,61 +5582,61 @@ file exists to solve such problems. Your mouse and the mouse driver may have somewhat become out of synchronization. - -In versions 2.2.5 and earlier, switching away from X to a -virtual terminal and getting back to X again may make them -re-synchronized. If the problem occurs often, you may add the + +In versions 2.2.5 and earlier, switching away from X to a +virtual terminal and getting back to X again may make them +re-synchronized. If the problem occurs often, you may add the following option in your kernel configuration file and recompile it. - + options PSM_CHECKSYNC - + See the section on building a kernel if you've no experience with building kernels. - + With this option, there should be less chance of synchronization problem between the mouse and the driver. If, however, you still see the problem, click any mouse button while holding the mouse still to re-synchronize the mouse and the driver. - + Note that unfortunately this option may not work with all the systems and voids the ``tap'' feature of the ALPS GlidePoint device attached to the PS/2 mouse port. - + In versions 2.2.6 and later, synchronization check is done in a slightly better way and is standard in the PS/2 mouse driver. It should even work with GlidePoint. (As the check code has become a standard feature, PSM_CHECKSYNC option is not available in these versions.) However, in rare case the driver may erroneously report synchronization problem and you may see the kernel message: - + psmintr: out of sync (xxxx != yyyy) - + and find your mouse doesn't seem to work properly. - + If this happens, disable the synchronization check code by setting the driver flags for the PS/2 mouse driver to 0x100. -Enter UserConfig by giving the ``'' option +Enter UserConfig by giving the ``'' option at the boot prompt: - + boot: -c - + Then, in the UserConfig command line, type: - + UserConfig> flags psm0 0x100 UserConfig> quit - + @@ -5644,15 +5644,15 @@ at the boot prompt: There have been some reports that certain model of PS/2 mouse from MouseSystems works only if it is put into the ``high resolution'' -mode. Otherwise, the mouse cursor may jump to the upper-left +mode. Otherwise, the mouse cursor may jump to the upper-left corner of the screen every so often. - -Unfortunately there is no workaround for versions 2.0.X and -2.1.X. In versions 2.2 through 2.2.5, apply the following patch -to /sys/i386/isa/psm.c and rebuild the kernel. See the + +Unfortunately there is no workaround for versions 2.0.X and +2.1.X. In versions 2.2 through 2.2.5, apply the following patch +to /sys/i386/isa/psm.c and rebuild the kernel. See the section on building a kernel if you've no experience with building kernels. - + diff -u psm.c.orig psm.c @@ -766,6 +766,8 @@ @@ -5666,39 +5666,39 @@ if you've no experience with building kernels. set_mouse_mode(sc->kbdc); /* stream mode */ - + In versions 2.2.6 or later, specify the flags 0x04 to the PS/2 mouse driver to put the mouse into the high resolution mode. -Enter UserConfig by giving the ``'' option +Enter UserConfig by giving the ``'' option at the boot prompt: - + boot: -c - + Then, in the UserConfig command line, type: - + UserConfig> flags psm0 0x04 UserConfig> quit - + See the previous section for another possible cause of mouse problems. - + When building an X app, imake can't find Imake.tmpl. Where is it? -Imake.tmpl is part of the Imake package, a standard X application building tool. -Imake.tmpl, as well as several header files that are required to build X apps, +Imake.tmpl is part of the Imake package, a standard X application building tool. +Imake.tmpl, as well as several header files that are required to build X apps, is contained in the X prog distribution. You can install this from sysinstall or manually from the X distribution files. - + @@ -5706,7 +5706,7 @@ manually from the X distribution files. Run the command xmodmap -e "pointer = 3 2 1" from your .xinitrc or .xsession. - + @@ -5725,12 +5725,12 @@ the VM86 kernel option to be compiled into the kernel. The actual VESA support can either be compiled directly into the kernel with the VESA kernel config option or by loading the VESA kld module during bootup. - + To use a splash screen, you need to modify the startup files that control the boot process for FreeBSD. The files for this changed prior to the release of FreeBSD 3.2, so there are now two ways of loading a splash screen: - + @@ -5805,10 +5805,10 @@ create a /boot/loader.conf that contains: - + Now all you need is a splash screen. For that you can surf on over to the gallery at http://www.cslab.vt.edu/~jobaldwi/splash/. - + @@ -5828,18 +5828,18 @@ on over to the gallery at 115 - Windows(tm) key, between the left-hand Ctrl and Alt keys - + 116 - Windows(tm) key, to the right of the Alt-Gr key - + 117 - Menu key, to the left of the right-hand Ctrl key - + To have the left Windows(tm) key print a comma, try this. @@ -5899,7 +5899,7 @@ id="networking"> network, and reads the necessary files from a server instead of its hard disk. For full details, please read the Handbook entry on diskless booting - + @@ -5910,27 +5910,27 @@ its hard disk. For full details, please read providing packet forwarding by default in FreeBSD. You can however enable this feature by changing the following variable to YES in rc.conf: - + gateway_enable=YES # Set to YES if this host will be a gateway - + This option will put the sysctl variable net.inet.ip.forwarding to 1. - + In most cases, you will also need to run a routing process to tell other systems on your network about your router; FreeBSD -comes with the standard BSD routing daemon +comes with the standard BSD routing daemon routed, or for more complex situations you may want to try GaTeD (available from http://www.gated.org/ ) which supports FreeBSD as of 3_5Alpha7. - + It is our duty to warn you that, even when FreeBSD is configured in this way, it does not completely comply with the Internet standard requirements for routers; however, it comes close enough for ordinary usage. - + @@ -5941,10 +5941,10 @@ with FreeBSD and one with Win95; the idea is to use the FreeBSD box to connect to the Internet and then be able to access the Internet from the Windows95 box through the FreeBSD box. This is really just a special case of the previous question. - + There's a useful document available which explains how to set FreeBSD up as a PPP Dialup Router - + NOTE: This requires having at least two fixed IP addresses available, and possibly three or more, depending on how much work you want to go through to set up the Windows box. As an @@ -5953,9 +5953,9 @@ the private IP subnets and install proxies such as SQUID and the TIS firewall toolkit on your FreeBSD box. - + See also the section on natd. - + @@ -5965,23 +5965,23 @@ on your FreeBSD box. There is a conflict between the ``cdefs.h'' file in the distribution and the one shipped with FreeBSD. Just remove compat/include/sys/cdefs.h. - + Does FreeBSD support SLIP and PPP? -Yes. See the man pages for +Yes. See the man pages for slattach, sliplogin, -pppd and +pppd and ppp. pppd and ppp provide support for both incoming and outgoing connections. Sliplogin deals exclusively with incoming connections and slattach deals exclusively with outgoing connections. - + These programs are described in the following sections of the handbook: - + @@ -6006,12 +6006,12 @@ connections. Sliplogi - + If you only have access to the Internet through a "shell account", you may want to have a look at the slirp package. It can provide you with (limited) access to services such as ftp and http direct from your local machine. - + natd program. Natd allows you to connect an entire subnet to the internet using only a single IP number. - + The ppp program has similar functionality built in via the switch. The alias library is used in both cases. - + @@ -6045,7 +6045,7 @@ 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 Ultrix. - + @@ -6053,24 +6053,24 @@ Ultrix. Add ``netmask 0xffffffff'' to your ifconfig command-line like the following: - + ifconfig ed0 alias 204.141.95.2 netmask 0xffffffff - + How do I get my 3C503 to use the other network port? If you want to use the other ports, you'll have to specify an -additional parameter on the +additional parameter on the ifconfig command line. The default port is ``link0''. To use the AUI port instead of the BNC one, use ``link2''. These flags should be specified using the ifconfig_* variables in /etc/rc.conf. - + @@ -6079,10 +6079,10 @@ using the ifconfig_* variables in the Handbook entry on NFS for more information on this topic. - + @@ -6090,12 +6090,12 @@ for more information on this topic. Some versions of the Linux NFS code only accept mount requests from a privileged port; try - + mount -o -P linuxbox:/blah /mnt - + @@ -6103,12 +6103,12 @@ from a privileged port; try Sun workstations running SunOS 4.X only accept mount requests from a privileged port; try - + mount -o -P sunbox:/blah /mnt - + @@ -6116,41 +6116,41 @@ from a privileged port; try Try disabling the TCP extensions in /etc/rc.conf by changing the following variable to NO: - + tcp_extensions=NO - + Xylogic's Annex boxes are also broken in this regard and you must use the above change to connect thru them. - + How do I enable IP multicast support? Multicast host operations are fully supported in FreeBSD 2.0 and -later by default. If you want your box to run as a multicast router, +later by default. If you want your box to run as a multicast router, you will need to recompile your kernel with the MROUTING option and run mrouted. FreeBSD 2.2 and later will start -mrouted at boot time if the flag mrouted_enable is set +mrouted at boot time if the flag mrouted_enable is set to "YES" in /etc/rc.conf. - -MBONE tools are available in their own ports category, mbone. If -you are looking for the conference tools vic and vat, + +MBONE tools are available in their own ports category, mbone. If +you are looking for the conference tools vic and vat, look there! - -For more information, see the + +For more information, see the Mbone Information Web. - + Which network cards are based on the DEC PCI chipset? Here is a list compiled by Glen Foster, with some more modern additions: - + Vendor Model ---------------------------------------------- @@ -6173,7 +6173,7 @@ look there! ZX444, ZX474, ZX478, ZX212, ZX214 (10mbps/hd) - + @@ -6184,7 +6184,7 @@ domain; for example, if you are in foo.bar.edu and you wish to reach a host called ``mumble'' in the bar.edu domain, you will have to refer to it by the fully-qualified domain name, ``mumble.bar.edu'', instead of just ``mumble''. - + Traditionally, this was allowed by BSD BIND resolvers. However the current version of bind that ships with FreeBSD no longer provides default abbreviations for non-fully @@ -6192,30 +6192,30 @@ qualified domain names other than the domain you are in. So an unqualified host mumble must either be found as mumble.foo.bar.edu, or it will be searched for in the root domain. - + This is different from the previous behavior, where the search continued across mumble.bar.edu, and mumble.edu. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole. - + As a good workaround, you can place the line - + search foo.bar.edu bar.edu - + instead of the previous - + domain foo.bar.edu - + into your /etc/resolv.conf file. However, make sure that the search order does not go beyond the ``boundary between local and public administration'', as RFC 1535 calls it. - + @@ -6225,21 +6225,21 @@ administration'', as RFC 1535 calls it. option, you need to be aware that the default policy as of 2.1.7R (this actually changed during 2.1-STABLE development) is to deny all packets that are not explicitly allowed. - + If you had unintentionally misconfigured your system for firewalling, you can restore network operability by typing the following while logged in as root: - + ipfw add 65534 allow all from any to any - + You can also set "firewall_type='open'" in /etc/rc.conf. - + For further information on configuring a FreeBSD firewall, see the Handbook section. - + @@ -6249,57 +6249,57 @@ see the Handbook section. speed. For most applications dealing with ethernet and small rule sets, the answer is, negligible. For those of you that need actual measurements to satisfy your curiosity, read on. - + The following measurements were made using 2.2.5-STABLE on a 486-66. IPFW was modified to measure the time spent within the ip_fw_chk routine, displaying the results to the console every 1000 packets. - + Two rule sets, each with 1000 rules were tested. The first set was designed to demonstrate a worst case scenario by repeating the rule: - + ipfw add deny tcp from any to any 55555 - + This demonstrates worst case by causing most of IPFW's packet check routine to be executed before finally deciding that the packet does not match the rule (by virtue of the port number). Following the 999th iteration of this rule was an allow ip from any to any. - + The second set of rules were designed to abort the rule check quickly: - + ipfw add deny ip from 1.2.3.4 to 1.2.3.4 - + The nonmatching source IP address for the above rule causes these rules to be skipped very quickly. As before, the 1000th rule was an allow ip from any to any. - + The per-packet processing overhead in the former case was approximately 2.703ms/packet, or roughly 2.7 microseconds per rule. Thus the theoretical packet processing limit with these rules is around 370 packets per second. Assuming 10Mbps ethernet and a ~1500 byte packet size, we would only be able to achieve a 55.5% bandwidth utilization. - + For the latter case each packet was processed in approximately 1.172ms, or roughly 1.2 microseconds per rule. The theoretical packet processing limit here would be about 853 packets per second, which could consume 10Mbps ethernet bandwidth. - + The excessive number of rules tested and the nature of those rules do not provide a real-world scenario -- they were used only to generate the timing information presented here. Here are a few things to keep in mind when building an efficient rule set: - + @@ -6321,7 +6321,7 @@ statistics with ipfw -a l. - + @@ -6329,54 +6329,54 @@ statistics with ipfw -a l. You can redirect FTP (and other service) request with the 'socket' -package, available in the ports tree in category 'sysutils'. +package, available in the ports tree in category 'sysutils'. Simply replace the service's commandline to call socket instead, like so: - + ftp stream tcp nowait nobody /usr/local/bin/socket socket ftp.foo.com ftp - + where 'ftp.foo.com' and 'ftp' are the host and port to redirect to, respectively. - + Where can I get a bandwidth management tool? -There are two bandwidth management tools available for FreeBSD. +There are two bandwidth management tools available for FreeBSD. ALTQ is available for free; Bandwidth Manager from Emerging Technologies is a commercial product. - + Why do I get “/dev/bpf0: device not configured”? The Berkeley Packet Filter (bpf) driver -needs to be enabled before running programs that utilize it. +needs to be enabled before running programs that utilize it. Add this to your kernel config file and build a new kernel: - + pseudo-device bpfilter # Berkeley Packet Filter - + Secondly, after rebooting you will have to create the device node. This can be accomplished by a change to the /dev directory, followed by the execution of: - + # sh MAKEDEV bpf0 - + Please see the handbook's entry on device nodes for more information on creating devices. - + @@ -6402,34 +6402,34 @@ id="userppp"> You should first read the ppp man page and the ppp section of the handbook. Enable logging with the command - + set log Phase Chat Connect Carrier lcp ipcp ccp command - + This command may be typed at the ppp command prompt or it may be entered in the /etc/ppp/ppp.conf configuration file (the start of the default section is the best place to put it). Make sure that /etc/syslog.conf contains the lines - + !ppp *.* /var/log/ppp.log - + and that the file /var/log/ppp.log exists. You can now find out a lot about what's going on from the log file. Don't worry if it doesn't all make sense. If you need to get help from someone, it may make sense to them. - + If your version of ppp doesn't understand the "set log" command, you should download the latest version. It will build on FreeBSD version 2.1.5 and higher. - + Ppp just hangs when I run it @@ -6440,18 +6440,18 @@ consoluted by your resolver first by editing /etc/host.conf and putting the hosts line first. Then, simply put an entry in /etc/hosts for your local machine. If you have no local network, change your localhost line: - + 127.0.0.1 foo.bar.com foo localhost - + Otherwise, simply add another entry for your host. Consult the relevant man pages for more details. - + You should be able to successfully ping -c1 `hostname` when you're done. - + @@ -6459,76 +6459,76 @@ when you're done. First, check that you've got a default route. By running http://www.FreeBSD.org/cgi/man.cgi?netstat name="netstat -rn">, you should see two entries like this: - + Destination Gateway Flags Refs Use Netif Expire default 10.0.0.2 UGSc 0 0 tun0 10.0.0.2 10.0.0.1 UH 0 0 tun0 - + This is assuming that you've used the addresses from the handbook, the man page or from the ppp.conf.sample file. If you haven't got a default route, it may be because you're running an old version of ppp that doesn't understand the word HISADDR in the ppp.conf file. If your version of ppp is from before FreeBSD 2.2.5, change the - + add 0 0 HISADDR - + line to one saying - + add 0 0 10.0.0.2 - + Another reason for the default route line being missing is that you have mistakenly set up a default router in your /etc/rc.conf file (this file was called /etc/sysconfig prior to release 2.2.2), and you have omitted the line saying - + delete ALL - + from ppp.conf. If this is the case, go back to the Final system configuration section of the handbook. - + What does "No route to host" mean This error is usually due to a missing - + MYADDR: delete ALL add 0 0 HISADDR - + section in your /etc/ppp/ppp.linkup file. This is only necessary if you have a dynamic IP address or don't know the address of your gateway. If you're using interactive mode, you can type the following after entering packet mode (packet mode is indicated by the capitalized PPP in the prompt): - + delete ALL add 0 0 HISADDR - + Refer to the PPP and Dynamic IP addresses section of the handbook for further details. - + @@ -6536,12 +6536,12 @@ for further details. The default ppp timeout is 3 minutes. This can be adjusted with the line - + set timeout NNN - + where NNN is the number of seconds of inactivity before the connection is closed. If NNN is zero, the connection is never closed due to a timeout. It is possible to put this command in @@ -6552,7 +6552,7 @@ the line is active by connecting to ppps server so or pppctl. Refer to the ppp man page for further details. - + @@ -6564,12 +6564,12 @@ machine and the peer. Ppp deduces that the line must therefore be bad, and disconnects. Prior to FreeBSD version 2.2.5, LQR was enabled by default. It is now disabled by default. LQR can be disabled with the line - + disable lqr - + @@ -6578,20 +6578,20 @@ LQR can be disabled with the line Sometimes, on a noisy phone line or even on a line with call waiting enabled, your modem may hang up because it thinks (incorrectly) that it lost carrier. - + There's 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 register in tenths of a second. To make your modem more forgiving, you could add the following send-expect sequence to your dial string: - + set dial "...... ATS10=10 OK ......" - + Refer to your modem manual for details. - + @@ -6600,7 +6600,7 @@ add the following send-expect sequence to your dial string: Many people experience hung connections with no apparent explaination. The first thing to establish is which side of the link is hung. - + If you are using an external modem, you can simply try using ping to see if the TD light is flashing when you transmit data. If it flashes (and the RD light doesn't), the @@ -6616,11 +6616,11 @@ local async and use ping from another w use of the link. The async logging will show you the data being transmitted and received on the link. If data is going out and not coming back, the problem is remote. - + Having established whether the problem is local or remote, you now have two possibilities: - + The remote end isn't responding @@ -6631,35 +6631,35 @@ refuse to help if you're not running a Microsoft OS. You can detect the remote failure and hang up, but this detection is relatively slow and therefore not that useful. You may want to avoid telling your ISP that you're running user-ppp.... - + First, try disabling all local compression by adding the following to your configuration: - + disable pred1 deflate deflate24 protocomp acfcomp shortseq vj deny pred1 deflate deflate24 protocomp acfcomp shortseq vj - + Then reconnect to ensure that this makes no difference. If things improve or if the problem is solved completely, determine which setting makes the difference through trial and error. This will provide good amunition when you contact your ISP (although it may make it apparent that you're not running a Microsoft product). - + Before contacting your ISP, enable async logging locally and wait until the connection hangs again. This may use up quite a bit of disk space. The last data read from the port may be of interest. It is usually ascii data, and may even describe the problem (``Memory fault, core dumped'' ?). - + If your ISP is helpful, they should be able to enable logging on their end, then when the next link drop occurs, they may be able to tell you why their side is having a problem. Feel free to send the details to brian@Awfulhak.org, or even to ask your ISP to contact me directly. - + @@ -6671,9 +6671,9 @@ and STRIP= to the end of the Makefile, then doing a ppp hangs, find the ppp process id with ps ajxww | fgrep ppp and run gdb ppp PID. From the gdb prompt, you can then use bt to get a stack trace. - + Send the results to brian@Awfulhak.org. - + @@ -6684,16 +6684,16 @@ and run gdb ppp PID. From the gdb prompt, you can Protocol (LCP). Many ISPs will not initiate negotiations and expect the client to do so. To force ppp to initiate the LCP, use the following line: - + set openmode active - + Note: It usually does no harm if both sides initiate negotiation, so openmode is now active by default. However, the next section explains when it does do some harm. - + @@ -6706,7 +6706,7 @@ exits. Most ppp implementations cannot survive this problem, and even if the link seems to come up, you'll see repeated configure requests and configure acknowledgements in the log file until ppp eventually gives up and closes the connection. - + This normally happens on server machines with slow disks that are spawning a getty on the port, and executing ppp from a login script or program after login. I've also heard reports @@ -6715,7 +6715,7 @@ that in the time taken between getty exiting and ppp starting, the client-side ppp starts sending Line Control Protocol (LCP) packets. Because ECHO is still switched on for the port on the server, the client ppp sees these packets "reflect" back. - + One part of the LCP negotiation is to establish a magic number for each side of the link so that "reflections" can be detected. The protocol says that when the peer tries to negotiate @@ -6731,29 +6731,29 @@ it's flooded with magic number changes and almost immediately decides it's tried enough to negotiate LCP and gives up. Meanwhile, the client, who no longer sees the reflections, becomes happy just in time to see a hangup from the server. - + This can be avoided by allowing the peer to start negotiating with the following line in your ppp.conf file: - + set openmode passive - + This tells ppp to wait for the server to initiate LCP negotiations. Some servers however may never initiate negotiations. If this is the case, you can do something like: - + set openmode active 3 - + This tells ppp to be passive for 3 seconds, and then to start sending LCP requests. If the peer starts sending requests during this period, ppp will immediately respond rather than waiting for the full 3 second period. - + @@ -6766,7 +6766,7 @@ their original requests. As a result, if one ppp implementation is more than 6 seconds slower than the other side, the other side will send two additional LCP configuration requests. This is fatal. - + Consider two implementations, A and B. A starts sending LCP requests immediately after connecting and B takes 7 seconds to start. When B starts, A has sent 3 LCP @@ -6786,39 +6786,39 @@ to the ACK-SENT state and sending another (second) (forth) ACK as per the RFC. A gets the REQ, goes into REQ-SENT and sends another REQ. It immediately receives the following ACK and enters OPENED. - + This goes on 'till one side figures out that they're getting nowhere and gives up. - + The best way to avoid this is to configure one side to be passive - that is, make one side wait for the other to start negotiating. This can be done with the - + set openmode passive - + command. Care should be taken with this option. You should also use the - + set stopped N - + command to limit the amount of time that ppp waits for the peer to begin negotiations. Alternatively, the - + set openmode active N - + command (where N is the number of seconds to wait before starting negotiations) can be used. Check the manual page for details. - + @@ -6831,12 +6831,12 @@ only happen if both sides tried to negotiate different Compression Control Protocols (CCP). This problem is now corrected, but if you're still running an old version of ppp, the problem can be circumvented with the line - + disable pred1 - + @@ -6849,11 +6849,11 @@ to complete before continuing. If you attempt to use the ppp link while running the command, the link will appear to have frozen. This is because ppp is waiting for the command to complete. - + If you wish to execute commands like this, use the !bg command instead. This will execute the given command in the background, and ppp can continue to service the link. - + @@ -6864,14 +6864,14 @@ a direct connection has been dropped. This is due to the lines that are used in a null-modem serial cable. When using this sort of connection, LQR should always be enabled with the line - + enable lqr - + LQR is accepted by default if negotiated by the peer. - + @@ -6879,78 +6879,78 @@ the line If ppp is dialing unexpectedly, you must determine the cause, and set up Dial filters (dfilters) to prevent such dialing. - + To determine the cause, use the following line: - + set log +tcp/ip - + This will log all traffic through the connection. The next time the line comes up unexpectedly, you will see the reason logged with a convenient timestamp next to it. - + You can now disable dialing under these circumstances. Usually, this sort of problem arises due to DNS lookups. To prevent DNS lookups from establishing a connection (this will not prevent ppp from passing the packets through an established connection), use the following: - + set dfilter 1 deny udp src eq 53 set dfilter 2 deny udp dst eq 53 set dfilter 3 permit 0/0 0/0 - + This is not always suitable, as it will effectively break your demand-dial capabilities - most programs will need a DNS lookup before doing any other network related things. - + In the DNS case, you should try to determine what is actually -trying to resolve a host name. A lot of the time, +trying to resolve a host name. A lot of the time, sendmail is the culprit. You should make sure that you tell sendmail not to do any DNS lookups in its configuration file. See the section on Mail Configuration 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 file: - + define(`confDELIVERY_MODE', `d')dnl - + This will make sendmail queue everything until the queue is run (usually, sendmail is invoked with ``-bd -q30m'', telling it to run the queue every 30 minutes) or until a ``sendmail -q'' is done (perhaps from your ppp.linkup file). - + What do these CCP errors mean I keep seeing the following errors in my log file: - + CCP: CcpSendConfigReq CCP: Received Terminate Ack (1) state = Req-Sent (6) - + This is because ppp is trying to negotiate Predictor1 compression, and the peer does not want to negotiate any compression at all. The messages are harmless, but if you wish to remove them, you can disable Predictor1 compression locally too: - + disable pred1 - + @@ -6960,17 +6960,17 @@ locally too: driver that prevents incoming packets of a size larger than the tun interface's MTU size. Receipt of a packet greater than the MTU size results in an IO error being logged via syslogd. - + The ppp specification says that an MRU of 1500 should always be accepted as a minimum, despite any LCP negotiations, therefore it is possible that should you decrease the MTU to less than 1500, your ISP will transmit packets of 1500 regardless, and you will tickle this non-feature - locking up your link. - + The problem can be circumvented by never setting an MTU of less than 1500 under FreeBSD 2.2.2 or before. - + @@ -6978,30 +6978,30 @@ less than 1500 under FreeBSD 2.2.2 or before. In order to log all lines of your modem ``conversation'', you must enable the following: - + set log +connect - -This will make + +This will make ppp log everything up until the last requested "expect" string. - + If you wish to see your connect speed and are using PAP or CHAP (and therefore don't have anything to "chat" after the CONNECT in the dial script - no "set login" script), you must make sure that you instruct ppp to "expect" the whole CONNECT line, something like this: - + set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n" - + Here, we get our CONNECT, send nothing, then expect a line-feed, forcing ppp to read the whole CONNECT response. - + @@ -7012,23 +7012,23 @@ interpret strings such as set phone "123 456 789" (and realize that the number is actually only one argument. In order to specify a “"” character, you must escape it using a backslash (“\”). - + When the chat interpreter parses each argument, it re-interprets the argument in order to find any special escape sequences such as “\P” or “\T” (see the man page). As a result of this double-parsing, you must remember to use the correct number of escapes. - + If you wish to actually send a “\” character to (say) your modem, you'd need something like: - + set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK" - + resulting in the following sequence: - + ATZ OK @@ -7036,24 +7036,24 @@ modem, you'd need something like: OK - + or - + set phone 1234567 set dial "\"\" ATZ OK ATDT\\T" - + resulting in the following sequence: - + ATZ OK ATDT1234567 - + @@ -7067,7 +7067,7 @@ termating due to a segmentation violation or some other signal that normally causes core to be dumped, and you're sure you're using the latest version (see the start of this section), then you should do the following: - + $ tar xfz ppp-*.src.tar.gz $ cd ppp*/ppp @@ -7079,16 +7079,16 @@ section), then you should do the following: # chmod 555 /usr/sbin/ppp - + You will now have a debuggable version of ppp installed. You will have to be root to run ppp as all of its privileges have been revoked. When you start ppp, take a careful note of what your current directory was at the time. - + Now, if and when ppp receives the segmentation violation, it will dump a core file called ppp.core. You should then do the following: - + $ su # gdb /usr/sbin/ppp ppp.core @@ -7102,14 +7102,14 @@ following: ..... - + All of this information should be given alongside your question, making it possible to diagnose the problem. - + If you're familiar with gdb, you may wish to find out some other bits and pieces such as what actually caused the dump and the addresses & values of the relevant variables. - + @@ -7119,7 +7119,7 @@ the addresses & values of the relevant variables. This was a known problem with ppp set up to negotiate a dynamic local IP number with the peer in auto mode. It is fixed in the latest version - search the man page for iface. - + The problem was that when that initial program calls connect(2), the IP number of the tun interface is assigned to the socket endpoint. The kernel creates the first @@ -7130,12 +7130,12 @@ the original socket endpoint will be invalid. Any subsequent packets sent to the peer will usually be dropped. Even if they aren't, any responses will not route back to the originating machine as the IP number is no longer owned by that machine. - + There are several theoretical ways to approach this problem. It would be nicest if the peer would re-assign the same IP number if possible :-) The current version of ppp does this, but most other implementations don't. - + The easiest method from our side would be to never change the tun interface IP number, but instead to change all outgoing packets so that the source IP number is changed from the interface IP to @@ -7144,14 +7144,14 @@ the negotiated IP on the fly. This is essentially what the doing (with the help of libalias(3) and ppp's switch) - it's maintaining all previous interface addresses and NATing them to the last negotiated address. - + Another alternative (and probably the most reliable) would be to implement a system call that changes all bound sockets from one IP to another. Ppp would use this call to modify the sockets of all existing programs when a new IP number is negotiated. The same system call could be used by dhcp clients when they are forced to re-bind() their sockets. - + Yet another possibility is to allow an interface to be brought up without an IP number. Outgoing packets would be given an IP number of 255.255.255.255 up until the first SIOCAIFADDR @@ -7162,7 +7162,7 @@ would need to change. This, however is a bit of a hack as the kernel would be sending bad packets to an improperly configured interface, on the assumption that some other mechanism is capable of fixing things retrospectively. - + @@ -7173,12 +7173,12 @@ in use is that the machine on the outside will try to open a connection or send (unsolicited) UDP packets to the machine on the inside. The NAT software doesn't know that it should send these packets to the interior machine. - + To make things work, make sure that the only thing running is the software that you're having problems with, then either run tcpdump on the tun interface of the gateway or enable ppp tcp/ip logging (``set log +tcp/ip'') on the gateway. - + When you start the offending software, you should see packets passing through the gateway machine. When something comes back from the outside, it'll be dropped (that's the problem). Note @@ -7186,26 +7186,26 @@ the port number of these packets then shut down the offending software. Do this a few times to see if the port numbers are consistent. If they are, then the following line in the relevant section of /etc/ppp/ppp.conf will make the software functional: - + nat port proto internalmachine:port port - + where ``proto'' is either ``tcp'' or ``udp'', ``internalmachine'' is the machine that you want the packets to be sent to and ``port'' is the destination port number of the packets. - + You won't be able to use the software on other machines without changing the above command, and running the software on two internal machines at the same time is out of the question - after all, the outside world is seeing your entire internal network as being just a single machine. - + If the port numbers aren't consistent, there are three more options: - + 1) Submit support in libalias. Examples of ``special cases'' can be found in /usr/src/lib/libalias/alias_*.c (alias_ftp.c is a good prototype). This usually involves reading certain @@ -7214,19 +7214,19 @@ tells the outside machine to initiate a connection back to the internal machine on a specific (random) port and setting up a ``route'' in the alias table so that the subsequent packets know where to go. - + This is the most difficult solution, but it is the best and will make the software work with multiple machines. - + 2) Use a proxy. The application may support socks5 for example, or (as in the ``cvsup'' case) may have a ``passive'' option that avoids ever requesting that the peer open connections back to the local machine. - + 3) Redirect everything to the internal machine using ``nat addr''. This is the sledge-hammer approach. - + Has anybody made a list of useful port numbers ? @@ -7234,7 +7234,7 @@ back to the local machine. Not yet, but this is intended to grow into such a list (if any interest is shown). In each example, internal should be replaced with the IP number of the machine playing the game. - + @@ -7250,7 +7250,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7263,7 +7263,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7278,7 +7278,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7291,7 +7291,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7306,7 +7306,7 @@ be replaced with the IP number of the machine playing the game. - + @@ -7318,14 +7318,14 @@ being received is the data being sent. If the FCS of an incoming packet is incorrect, the packet is dropped and the HDLC FCS count is increased. The HDLC error values can be displayed using the show hdlc command. - + If your link is bad (or if your serial driver is dropping packets), you will see the occasional FCS error. This is not usually worth worrying about although it does slow down the compression protocols substantially. If you have an external modem, make sure your cable is properly shielded from interference - this may eradicate the problem. - + If your link freezes as soon as you've connected and you see a large number of FCS errors, this may be because your link is not 8 bit clean. Make sure your modem is not using software @@ -7333,7 +7333,7 @@ flow control (XON/XOFF). If your datalink must us software flow control, use the command set accmap 0x000a0000 to tell ppp to escape the ^Q and ^S characters. - + Another reason for seeing too many FCS errors may be that the remote end has stopped talking PPP. You may want to enable async logging at this point to determine if the @@ -7342,11 +7342,11 @@ have a shell prompt at the remote end, it's possible to terminate ppp without dropping the line by using the close lcp command (a following term command will reconnect you to the shell on the remote machine. - + If nothing in your log file indicates why the link might have been terminated, you should ask the remote administrator (your ISP?) why the session was terminated. - + @@ -7412,7 +7412,7 @@ the relevant parts of your log file and the output of the freebsd-questions@FreeBSD.org mailing list or the comp.unix.bsd.freebsd.misc news group, and someone should point you in the right direction. - + @@ -7423,7 +7423,7 @@ id="serial"> This section answers common questions about serial communications with FreeBSD. PPP and SLIP are covered in the section. - + How do I tell if FreeBSD found my serial ports? @@ -7432,16 +7432,16 @@ with FreeBSD. PPP and SLIP are covered in the - + dmesg | grep sio - + after your system's up and running. - + Here's some example output from the above command: - + sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -7449,14 +7449,14 @@ run the command sio1: type 16550A - + This shows two serial ports. The first is on irq 4, is using port address 0x3f8, and has a 16550A-type UART chip. The second uses the same kind of chip but is on irq 3 and is at port address 0x2f8. Internal modem cards are treated just like serial ports---except that they always have a modem ``attached'' to the port. - + The GENERIC kernel includes support for two serial ports using the same irq and port address settings in the above example. If these settings aren't right for your system, or if @@ -7464,14 +7464,14 @@ you've added modem cards or have more serial ports than your kernel is configured for, just reconfigure your kernel. See section about building a kernel for more details. - + How do I tell if FreeBSD found my modem cards? Refer to the answer to the previous question. - + @@ -7479,7 +7479,7 @@ more details. Don't worry, they have been merged with the ttydX devices. You'll have to change any old configuration files you have, though. - + @@ -7489,7 +7489,7 @@ You'll have to change any old configuration files you have, though. COM3 in DOS), is on /dev/cuaa2 for dial-out devices, and on /dev/ttyd2 for dial-in devices. What's the difference between these two classes of devices? - + You use ttydX for dial-ins. When opening /dev/ttydX in blocking mode, a process will wait for the corresponding cuaaX device to become inactive, and then wait @@ -7501,7 +7501,7 @@ device doesn't care about carrier detect. With this scheme and an auto-answer modem, you can have remote users log in and you can still dialout with the same modem and the system will take care of all the conflicts. - + @@ -7515,9 +7515,9 @@ specifiers on only one of the entries. All of the ports on the card should share one irq. For consistency, use the last serial port to specify the irq. Also, specify the COM_MULTIPORT option. - + The following example is for an AST 4-port serial card on irq 7: - + options "COM_MULTIPORT" device sio4 at isa? port 0x2a0 tty flags 0x781 @@ -7526,18 +7526,18 @@ option. device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - + The flags indicate that the master port has minor number 7 (0x700), diagnostics enabled during probe (0x080), and all the ports share an irq (0x001). - + Can FreeBSD handle multiport serial cards sharing irqs? Not yet. You'll have to use a different irq for each card. - + @@ -7547,45 +7547,45 @@ all the ports share an irq (0x001). you'll want to open for your applications. When a process opens the device, it'll have a default set of terminal I/O settings. You can see these settings with the command - + stty -a -f /dev/ttyd1 - + When you change the settings to this device, the settings are in effect until the device is closed. When it's reopened, it goes back to the default set. To make changes to the default set, you can open and adjust the settings of the ``initial state'' device. For example, to turn on CLOCAL mode, 8 bits, and XON/XOFF flow control by default for ttyd5, do: - + stty -f /dev/ttyid5 clocal cs8 ixon ixoff - + A good place to do this is in /etc/rc.serial. Now, an application will have these settings by default when it opens ttyd5. It can still change these settings to its liking, though. - + You can also prevent certain settings from being changed by an application by making adjustments to the ``lock state'' device. For example, to lock the speed of ttyd5 to 57600 bps, do - + stty -f /dev/ttyld5 57600 - + Now, an application that opens ttyd5 and tries to change the speed of the port will be stuck with 57600 bps. - + Naturally, you should make the initial state and lock state devices writable only by root. The MAKEDEV script does NOT do this when it creates the device entries. - + @@ -7601,27 +7601,27 @@ flow control or no local flow control at all. Finally, it must use a constant speed between the computer and itself, but (to be nice to your callers) it should negotiate a speed between itself and the remote modem. - + For many Hayes command-set--compatible modems, this command will make these settings and store them in nonvolatile memory: - + AT &C1 &D3 &K3 &Q6 S0=1 &W - + See the section on sending AT commands below for information on how to make these settings without resorting to an MS-DOS terminal program. - + Next, make an entry in /etc/ttys for the modem. This file lists all the ports on which the operating system will await logins. Add a line that looks something like this: - + ttyd1 "/usr/libexec/getty std.57600" dialup on insecure - + This line indicates that the second serial port (/dev/ttyd1) has a modem connected running at 57600 bps and no parity (std.57600, which comes from the file @@ -7629,7 +7629,7 @@ and no parity (std.57600, which comes from the fil ``dialup.'' The port is ``on'' and is ``insecure''---meaning root logins on the port aren't allowed. For dialin ports like this one, use the ttydX entry. - + It's common practice to use ``dialup'' as the terminal type. Many users set up in their .profile or .login files a prompt for the actual terminal type if the starting type is dialup. The @@ -7637,31 +7637,31 @@ example shows the port as insecure. To become root on this port, you have to login as a regular user, then ``su'' to root. If you use ``secure'' then root can login in directly. - + After making modifications to /etc/ttys, you need to send a hangup or HUP signal to the init process: - + kill -HUP 1 - + This forces the init process to reread /etc/ttys. The init process will then start getty processes on all ``on'' ports. You can find out if logins are available for your port by typing - + ps -ax | grep '[t]tyd1' - + You should see something like: - + 747 ?? I 0:00.04 /usr/libexec/getty std.57600 ttyd1 - + @@ -7671,19 +7671,19 @@ You can find out if logins are available for your port by typing system, get a null modem cable to go between the two serial ports. If you're using an actual terminal, see its accompanying instructions. - + Then, modify /etc/ttys, like above. For example, if you're hooking up a WYSE-50 terminal to the fifth serial port, use an entry like this: - + ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure - + This example shows that the port on /dev/ttyd4 has a wyse50 terminal connected at 38400 bps with no parity (std.38400 from /etc/gettytab) and root logins are allowed (secure). - + @@ -7693,16 +7693,16 @@ wyse50 terminal connected at 38400 bps with no parity executable only by uucp and group dialer. You can use the group dialer to control who has access to your modem or remote systems. Just add yourself to group dialer. - + Alternatively, you can let everyone on your system run tip and cu by typing: - + # chmod 4511 /usr/bin/cu # chmod 4511 /usr/bin/tip - + @@ -7711,26 +7711,26 @@ and cu by typing: Actually, the man page for tip is out of date. There is a generic Hayes dialer already built in. Just use ``at=hayes'' in your /etc/remote file. - + The Hayes driver isn't smart enough to recognize some of the advanced features of newer modems---messages like BUSY, NO DIALTONE, or CONNECT 115200 will just confuse it. You should turn those messages off when you use tip (using ATX0&W). - + Also, the dial timeout for tip is 60 seconds. Your modem should use something less, or else tip will think there's a communication problem. Try ATS7=45&W. - + Actually, as shipped tip doesn't yet support it fully. The solution is to edit the file tipconf.h in the directory /usr/src/usr.bin/tip/tip. Obviously you need the source distribution to do this. - + Edit the line ``#define HAYES 0'' to ``#define HAYES 1''. Then ``make'' and ``make install''. Everything works nicely after that. - + /etc/remote file. For example, if your modem's hooked up to the first serial port, /dev/cuaa0, then put in the following line: - + cuaa0:dv=/dev/cuaa0:br#19200:pa=none - + Use the highest bps rate your modem supports in the br capability. Then, type tip cuaa0 and you'll be connected to your modem. - + If there is no /dev/cuaa0 on your system, do this: - + # cd /dev # ./MAKEDEV cuaa0 - + Or use cu as root with the following command: - + # cu -l``line'' -s``speed'' - + with line being the serial port (e.g./dev/cuaa0) and speed being the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit. - + @@ -7780,12 +7780,12 @@ entering the AT commands hit ~. to exit. /etc/phones for a phone number. But the <@> sign is also a special character in capability files like /etc/remote. Escape it with a backslash: - + pn=\@ - + @@ -7793,7 +7793,7 @@ also a special character in capability files like Put what's called a ``generic'' entry in your /etc/remote file. For example: - + tip115200|Dial any phone number at 115200 bps:\ :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: @@ -7801,19 +7801,19 @@ also a special character in capability files like :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: - + Then you can do something like ``tip -115200 5551234''. If you prefer cu over tip, use a generic cu entry: - + cu115200|Use cu to dial any number at 115200bps:\ :dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du: - + and type ``cu 5551234 -s 115200''. - + @@ -7823,7 +7823,7 @@ generic cu entry: use whatever bps rate is appropriate with the br capability. tip thinks a good default is 1200 bps which is why it looks for a ``tip1200'' entry. You don't have to use 1200 bps, though. - + @@ -7833,7 +7833,7 @@ You don't have to use 1200 bps, though. ``CONNECT <host>'' each time, use tip's cm capability. For example, these entries in /etc/remote: - + pain|pain.deep13.com|Forrester's machine:\ :cm=CONNECT pain\n:tc=deep13: @@ -7843,11 +7843,11 @@ capability. For example, these entries in :dv=/dev/cua02:br#38400:at=hayes:du:pa=none:pn=5551234: - + will let you type ``tip pain'' or ``tip muffin'' to connect to the hosts pain or muffin; and ``tip deep13'' to get to the terminal server. - + @@ -7855,10 +7855,10 @@ get to the terminal server. This is often a problem where a university has several modem lines and several thousand students trying to use them... - + Make an entry for your university in /etc/remote and use <\@> for the pn capability: - + big-university:\ :pn=\@:tc=dialout @@ -7866,10 +7866,10 @@ and use <\@> for the pn - + Then, list the phone numbers for the university in /etc/phones: - + big-university 5551111 big-university 5551112 @@ -7877,37 +7877,37 @@ and use <\@> for the pn - + tip will try each one in the listed order, then give up. If you want to keep retrying, run tip in a while loop. - + Why do I have to hit CTRL+P twice to send CTRL+P once? -CTRL+P is the default ``force'' character, used to tell +CTRL+P is the default ``force'' character, used to tell tip that the next character is literal data. You can set the force character to any other character with the ~s escape, which means ``set a variable.'' - + Type ``~sforce=<single-char>'' followed by a newline. <single-char> is any single character. If you leave out <single-char>, then the force character is the nul character, which you can get by typing CTRL+2 or CTRL+SPACE. A pretty good value for <single-char> is SHIFT+CTRL+6, which I've seen only used on some terminal servers. - + You can have the force character be whatever you want by specifying the following in your $HOME/.tiprc file: - + force=<single-char> - + @@ -7918,18 +7918,18 @@ character,'' specially designed for people with broken caps-lock keys. Use ~s as above and set the variable ``raisechar'' to something reasonable. In fact, you can set it to the same as the force character, if you never expect to use either of these features. - + Here's a sample .tiprc file perfect for Emacs users who need to type CTRL+2 and CTRL+A a lot: - + force=^^ raisechar=^^ - + The ^^ is SHIFT+CTRL+6. - + @@ -7939,16 +7939,16 @@ type CTRL+2 and CTRL+A a lot: receive files with ~p (put) and ~t (take). These commands run cat and echo on the remote system to accept and send files. The syntax is: - + ~p <local-file> [<remote-file>] ~t <remote-file> [<local-file>] - + There's no error checking, so you probably should use another protocol, like zmodem. - + @@ -7958,16 +7958,16 @@ protocol, like zmodem. collection (such as one of the two from the comms category, lrzsz and rzsz). - + To receive files, start the sending program on the remote end. Then, press enter and type ``~C rz'' (or ``~C lrz'' if you installed lrzsz) to begin receiving them locally. - + To send files, start the receiving program on the remote end. Then, press enter and type ``~C sz <files>'' (or ``~C lsz <files>'') to send them to the remote system. - + @@ -7975,9 +7975,9 @@ remote system. settings are correct. Motherboards and cards with Acer UARTs do not probe properly under -the FreeBSD sio probe. Obtain a patch from +the FreeBSD sio probe. Obtain a patch from www.lemis.com to fix your problem. - + @@ -7993,16 +7993,16 @@ id="misc"> 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 entirely idle, unused pages -of main memory into swap in order to make more main memory available +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 does not + +Note that while FreeBSD is proactive in this regard, it does not arbitrarily decide to swap pages when the system is truely idle. Thus you will not find your system all paged out when you get up in the morning after leaving it idle overnight. - + @@ -8012,7 +8012,7 @@ morning after leaving it idle overnight. To understand why FreeBSD uses the a.out format, you must first know a little about the 3 currently "dominant" executable formats for UNIX: - + @@ -8057,13 +8057,13 @@ Solaris, SCO) does it hold true. FreeBSD tries to work around this problem somewhat by providing a utility for branding a known ELF executable with information about the ABI it's compliant with. -See the man page for +See the man page for brandelf for more information. - + FreeBSD comes from the "classic" camp and has traditionally used the a.out format, a technology tried and proven through many generations of BSD releases. Though it has also been possible @@ -8079,11 +8079,11 @@ tools available offered a solution to the shared library problem and were generally seen as "the way forward" anyway, the migration cost was accepted as necessary and the transition made. - + In FreeBSD's case, our shared library mechanism is based more closely on Sun's SunOS-style shared library mechanism and, as such, is very -easy to use. +easy to use. However, starting with 3.0, FreeBSD officially supports ELF binaries as the default format. Even though the a.out executable format has served us well, the GNU people, who author the @@ -8093,7 +8093,7 @@ the compler and linker, and has kept us from reaping the benefits of the latest GNU development efforts. Also the demands of ISO-C++, notably contstructors and destructors, has also led to native ELF support in future FreeBSD releases. - + @@ -8107,7 +8107,7 @@ simple system (a PDP-11). As people ported unix from this simple system, they retained the a.out format because it was sufficient for the early ports of unix to architectures like the Motorola 68k, VAXen, etc. - + Then some bright hardware engineer decided that if he could force software to do some sleazy tricks, then he'd be able to shave a few gates off the design and allow his CPU core to run @@ -8118,7 +8118,7 @@ better performance from this hardware than the limited, simple a.out format could offer. Things like COFF, ECOFF, and a few obscure others were invented and their limitations explored before things seemed to settle on ELF. - + In addition, program sizes were getting huge and disks (and physical memory) were still relatively small so the concept of a shared library was born. The VM system also became more @@ -8137,7 +8137,7 @@ While ELF solved many of these problems, it would be painful to switch from the system that basically worked. So ELF had to wait until it was more painful to remain with a.out than it was to migrate to ELF. - + However, as time passed, the build tools that FreeBSD derived their build tools from (the assembler and loader especially) evolved in two parallel trees. The FreeBSD tree added shared @@ -8155,7 +8155,7 @@ binaries, why bother having a.out any more? It is a tired old horse that has proven useful for a long time, but it is time to turn him out to pasture for his long, faithful years of service. - + ELF is more expressive than a.out and will allow more extensibility in the base system. The ELF tools are better maintained, and offer cross compilation support, which is @@ -8167,14 +8167,14 @@ important, but they are differences. In time support for a.out will be moved out of the GENERIC kernel, and eventually removed from the kernel once the need to run legacy a.out programs is past. - + Why won't chmod change the permissions on symlinks? Symlinks do not have permissions, and by default, - &man.chmod.1; will not follow symlinks to change the permissions + &man.chmod.1; will not follow symlinks to change the permissions on the target file. So if you have a file, foo, and a symlink to that file, bar, then this command will always @@ -8184,12 +8184,12 @@ eventually removed from the kernel once the need to run legacy However, the permissions on foo will not have changed. - + You have to use either ``'' or ``'' together with -the ``'' option to make this work. See the chmod and +the ``'' option to make this work. See the chmod and symlink man pages for more info. - + WARNING the ``'' option does a RECURSIVE chmod. Be careful about specifying directories or symlinks to directories to chmod. If you want to change the @@ -8199,16 +8199,16 @@ without any options and follow the symlink with a trailing slash (``/''). For example, if ``foo'' is a symlink to directory ``bar'', and you want to change the permissions of ``foo'' (actually ``bar''), you would do something like: - + chmod 555 foo/ - + With the trailing slash, chmod will follow the symlink, ``foo'', to change the permissions of the directory, ``bar''. - + @@ -8224,13 +8224,13 @@ this get you log files which are trashed (due to variable-length records getting written when fixed records were expected), but it can break Sun's NIS clients and potentially cause other problems in interacting with other UNIX systems. - + In FreeBSD 3.0 and later, the maximum name length has been increased to 16 characters and those various utilities with hard-coded name sizes have been found and fixed. The fact that this touched so many areas of the system is why, in fact, the change was not made until 3.0. - + If you're absolutely confident in your ability to find and fix these sorts of problems for yourself when and if they pop up, you can increase the login name length in earlier releases by editing @@ -8239,7 +8239,7 @@ also update MAXLOGNAME in /usr/include/sys/param.h to match the UT_NAMESIZE change. Finally, if you build from sources, don't forget that /usr/include is updated each time! Change the appropriate files in /usr/src/.. instead. - + @@ -8249,13 +8249,13 @@ files in /usr/src/.. instead. DOS emulation which has been integrated and enhanced. Send mail to The FreeBSD emulation discussion list if you're interested in joining this ongoing effort! - -For pre-3.0 systems, there is a neat utility called + +For pre-3.0 systems, there is a neat utility called pcemu in the ports collection which emulates an 8088 and enough BIOS services to run DOS text mode applications. It requires the X Window System (provided as XFree86). - + @@ -8266,11 +8266,11 @@ System (provided as XFree86). stands for Software Update Protocol, and was developed by CMU for keeping their development trees in sync. We used it to keep remote sites in sync with our central development sources. - + SUP is not bandwidth friendly, and has been retired. The current recommended method to keep your sources up to date is Handbook entry on CVSup - + @@ -8279,7 +8279,7 @@ recommended method to keep your sources up to date is 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 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 @@ -8291,13 +8291,13 @@ volunteers were wandering out of the room during the tests, thus skewing the results. I think most of the volunteers are at Apple now, working on their new ``scratch and sniff'' GUI. It's a funny old business we're in! - + 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 (automatic power management) configured, then FreeBSD can also put the CPU into a low power mode. - + @@ -8308,14 +8308,14 @@ 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 strange scratchy sound emanates from what appears to be the memory banks. - + A. Yes! You'll see frequent references to ``daemons'' in the BSD documentation, and what most people don't know is that this refers to genuine, non-corporeal entities that now possess your computer. The scratchy sound coming from your memory is actually high-pitched whispering exchanged among the daemons as they best decide how to deal with various system administration tasks. - + If the noise gets to you, a good ``fdisk /mbr'' from DOS will get rid of them, but don't be surprised if they react adversely and try to stop you. In fact, if at any point during @@ -8326,7 +8326,7 @@ twin demons of DOS and Windows are often able to re-assert total control over your machine to the eternal damnation of your soul. Given a choice, I think I'd prefer to get used to the scratchy noises, myself! - + @@ -8335,7 +8335,7 @@ noises, myself! MFC is an acronym for 'Merged From -CURRENT.' It's used in the CVS logs to denote when a change was migrated from the CURRENT to the STABLE branches. - + @@ -8346,110 +8346,110 @@ members can know. It doesn't translate literally but its ok 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.' :-) - + 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. - + How many FreeBSD hackers does it take to change a lightbulb? One thousand, one hundred and seventy-two: - + Twenty-three to complain to -CURRENT about the lights being out; - + Four to claim that it is a configuration problem, and that such matters really belong on -questions; - + Three to submit PRs about it, one of which is misfiled under doc and consists only of "it's dark"; - + One to commit an untested lightbulb which breaks buildworld, then back it out five minutes later; - + Eight to flame the PR originators for not including patches in their PRs; - + Five to complain about buildworld being broken; - + Thirty-one to answer that it works for them, and they must have cvsupped at a bad time; - + One to post a patch for a new lightbulb to -hackers; - + One to complain that he had patches for this three years ago, but when he sent them to -CURRENT they were just ignored, and he has had bad experiences with the PR system; besides, the proposed new lightbulb is non-reflexive; - + Thirty-seven to scream that lightbulbs do not belong in the base system, that committers have no right to do things like this without consulting the Community, and WHAT IS -CORE DOING ABOUT IT!? - + Two hundred to complain about the color of the bicycle shed; - + Three to point out that the patch breaks style(9); - + Seventeen to complain that the proposed new lightbulb is under GPL; - + Five hundred and eighty-six to engage in a flame war about the comparative advantages of the GPL, the BSD license, the MIT license, the NPL, and the personal hygiene of unnamed FSF founders; - + Seven to move various portions of the thread to -chat and -advocacy; - + One to commit the suggested lightbulb, even though it 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 with a dim lightbulb; - + Forty-six to argue vociferously about the backing out of the dim lightbulb and demanding a statement from -core; - + Eleven to request a smaller lightbulb so it will fit their Tamagotchi if we ever decide to port FreeBSD to that platform; - + Seventy-three to complain about the SNR on -hackers and -chat and unsubscribe in protest; - + Thirteen to post "unsubscribe", "How do I unsubscribe?", or "Please remove me from the list", followed by the usual footer; - + One to commit a working lightbulb while everybody is too busy flaming everybody else to notice; - + 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 switch to TenDRA instead of EGCS; - + One to complain that the new lightbulb lacks fairings; - + Nine (including the PR originators) to ask "what is MFC?"; - + Fifty-seven to complain about the lights being out two weeks after the bulb has been changed. - + Nik Clayton adds: - + I was laughing quite hard at this. - + And then I thought, "Hang on, shouldn't there be '1 to document it.' in that list somewhere?" - + And then I was enlightened :-) - + This entry is Copyright (c) 1999 Dag-Erling Coïdan Smørgrav. Please do not reproduce without attribution. @@ -8466,7 +8466,7 @@ id="hackers"> There are currently three active/semi-active branches in the FreeBSD CVS Repository: - + @@ -8488,19 +8488,19 @@ id="hackers"> - + HEAD is not an actual branch tag, like the other two, it's simply a symbolic constant for "the current, non-branched development stream" which we simply refer to as . - + Right now, is the 5.0 development stream and the 4-STABLE branch, RELENG_4, forked off from in Mar 2000. - + The 2.2-STABLE branch, RELENG_2_2, departed -CURRENT in November 1996, and has pretty much been retired. - + To make a release you need to do three things: First, you need to be running a kernel with the vn driver configured in. Add this to your kernel config file and build a new kernel: - + pseudo-device vn #Vnode driver (turns a file into a device) - + Second, you have to have the whole CVS repository at hand. To get this you can use CVSUP but in your supfile set the release name to cvs and remove any tag or date fields: - + *default prefix=/home/ncvs *default base=/a @@ -8540,21 +8540,21 @@ date fields: doc-all - + Then run cvsup -g supfile to suck all the good bits onto your box... - + Finally, you need a chunk of empty space to build into. Let's say it's in /some/big/filesystem, and from the example above you've got the CVS repository in /home/ncvs: - + setenv CVSROOT /home/ncvs # or export CVSROOT=/home/ncvs cd /usr/src/release make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release - + An entire release will be built in /some/big/filesystem/release and you will have a full FTP-type installation in /some/big/filesystem/release/R/ftp when you're @@ -8562,7 +8562,7 @@ done. If you want to build your SNAP along some other branch than -CURRENT, you can also add RELEASETAG=SOMETAG to the make release command line above, e.g. RELEASETAG=RELENG_2_2 would build an up-to-the- minute 2.2-STABLE snapshot. - + @@ -8574,7 +8574,7 @@ binary archives is automated by various targets in be enough to get you started. However, it should be said that this involves doing a ``make world'' and will therefore take up a lot of time and disk space. - + @@ -8584,7 +8584,7 @@ time and disk space. ``make world'' rebuilds every system binary from scratch, so you can be certain of having a clean and consistent environment at the end (which is why it takes so long). - + If the environment variable DESTDIR is defined while running ``make world'' or ``make install'', the newly-created binaries will be deposited in a directory tree identical to the @@ -8592,7 +8592,7 @@ installed one, rooted at ${DESTDIR}. Some random combination of shared libraries modifications and program rebuilds can cause this to fail in ``make world'', however. - + @@ -8608,7 +8608,7 @@ configuration option in order to have this take place. Using it on those systems where it works may make your disks run faster, but on those systems where it doesn't, your data could be corrupted. - + Yes, you can do this without downloading the whole source tree by using the CTM facility. - + @@ -8626,9 +8626,9 @@ by using the CTM facility.

Newer BSD based systems have a ``'' option to split that allows them to split files on arbitrary byte boundaries. - + Here is an example from /usr/src/Makefile. - + bin-tarball: (cd ${DISTDIR}; \ @@ -8638,23 +8638,23 @@ allows them to split files on arbitrary byte boundaries. ${RELEASEDIR}/tarballs/bindist/bin_tgz.) - + I've written a kernel extension, who do I send it to? Please take a look at The Handbook entry on how to submit code. - + And thanks for the thought! - + How are Plug N Play ISA cards detected and initialized? By: Frank Durda IV - + In a nutshell, there a few I/O ports that all of the PnP boards respond to when the host asks if anyone is out there. So when the PnP probe routine starts, he asks if there are any PnP boards @@ -8673,30 +8673,30 @@ repeating this semi-binary search of IDs-in-range enough times, the probing code will eventually identify all PnP boards present in a given machine with a number of iterations that is much lower than what 2^64 would take. - + The IDs are two 32-bit fields (hence 2ˆ64) + 8 bit checksum. The first 32 bits are a vendor identifier. They never come out and say it, but it appears to be assumed that different types of boards from the same vendor could have different 32-bit vendor ids. The idea of needing 32 bits just for unique manufacturers is a bit excessive. - + The lower 32 bits are a serial #, ethernet address, something that makes this one board unique. The vendor must never produce a second board that has the same lower 32 bits unless the upper 32 bits are also different. So you can have multiple boards of the same type in the machine and the full 64 bits will still be unique. - + The 32 bit groups can never be all zero. This allows the wired-OR to show non-zero bits during the initial binary search. - + Once the system has identified all the board IDs present, it will reactivate each board, one at a time (via the same I/O ports), and find out what resources the given board needs, what interrupt choices are available, etc. A scan is made over all the boards to collect this information. - + This info is then combined with info from any ECU files on the hard disk or wired into the MLB BIOS. The ECU and BIOS PnP support for hardware on the MLB is usually synthetic, and the @@ -8704,16 +8704,16 @@ peripherals don't really do genuine PnP. However by examining the BIOS info plus the ECU info, the probe routines can cause the devices that are PnP to avoid those devices the probe code cannot relocate. - + Then the PnP devices are visited once more and given their I/O, DMA, IRQ and Memory-map address assignments. The devices will then appear at those locations and remain there until the next reboot, although there is nothing that says you can't move them around whenever you want. - + There is a lot of oversimplification above, but you should get the general idea. - + Microsoft took over some of the primary printer status ports to do PnP, on the logic that no boards decoded those addresses for the opposing I/O cycles. I found a genuine IBM printer board @@ -8722,7 +8722,7 @@ proposal review period, but MS said ``tough''. So they do a write to the printer status port for setting addresses, plus that use that address + 0x800, and a third I/O port for reading that can be located anywhere between 0x200 and 0x3ff. - + @@ -8741,13 +8741,13 @@ number of working ports and packages. FreeBSD/AXP should be considered BETA quality software at this time. For status information, please join the freebsd-alpha@FreeBSD.orgmailing list. - + Interest has also been expressed in a port of FreeBSD to the SPARC architecture, join the freebsd-sparc@FreeBSD.orgmailing list if you are interested in joining that project. For general discussion on new architectures, join the freebsd-platforms@FreeBSD.org mailing list. - + @@ -8763,7 +8763,7 @@ character major number 32 and block major number 8 have been reserved specifically for this purpose; please use them. In any case, we'd appreciate hearing about your driver on freebsd-hackers@FreeBSD.org. - + @@ -8773,34 +8773,34 @@ appreciate hearing about your driver on directories, the scheme that is currently in use is unchanged from what I wrote in 1983. I wrote that policy for the original fast filesystem, and never revisited it. It works well at keeping -cylinder groups from filling up. As several of you have noted, -it works poorly for find. Most filesystems are created from -archives that were created by a depth first search (aka ftw). +cylinder groups from filling up. As several of you have noted, +it works poorly for find. Most filesystems are created from +archives that were created by a depth first search (aka ftw). These directories end up being striped across the cylinder groups -thus creating a worst possible senario for future depth first -searches. If one knew the total number of directories to be -created, the solution would be to create (total / fs_ncg) per -cylinder group before moving on. Obviously, one would have to -create some heuristic to guess at this number. Even using a +thus creating a worst possible senario for future depth first +searches. If one knew the total number of directories to be +created, the solution would be to create (total / fs_ncg) per +cylinder group before moving on. Obviously, one would have to +create some heuristic to guess at this number. Even using a small fixed number like say 10 would make an order of magnitude -improvement. To differentiate restores from normal operation -(when the current algorithm is probably more sensible), you -could use the clustering of up to 10 if they were all done -within a ten second window. Anyway, my conclusion is that this +improvement. To differentiate restores from normal operation +(when the current algorithm is probably more sensible), you +could use the clustering of up to 10 if they were all done +within a ten second window. Anyway, my conclusion is that this is an area ripe for experimentation. - + Kirk McKusick, September 1998 - + Making the most of a kernel panic - + [This section was extracted from a mail written by Bill Paul on the freebsd-current mailing list by Dag-Erling Coïdan Smørgrav, who fixed a few typos and added the bracketed comments] - + From: Bill Paul <wpaul@skynet.ctr.columbia.edu> Subject: Re: the fs fun never stops @@ -8809,7 +8809,7 @@ Date: Sun, 20 Sep 1998 15:22:50 -0400 (EDT) Cc: current@FreeBSD.org - + [<ben@rosengart.com> posted the following panic message] > Fatal trap 12: page fault while in kernel mode @@ -8828,7 +8828,7 @@ message] > panic: page fault - + [When] you see a message like this, it's not enough to just reproduce it and send it in. The instruction pointer value that I highlighted up there is important; unfortunately, it's also @@ -8838,9 +8838,9 @@ using a GENERIC kernel image from one of the snapshots, then it's possible for somebody else to track down the offending function, but if you're running a custom kernel then only you can tell us where the fault occured. - + What you should do is this: - + @@ -8854,7 +8854,7 @@ it's the 0xf0xxxxxx part that we want. When the system reboots, do the following: % nm /kernel.that.caused.the.panic | grep f0xxxxxx - + where f0xxxxxx is the instruction pointer value. The odds are you will not get an exact match since the symbols in the kernel symbol table are for the entry points of @@ -8874,11 +8874,11 @@ failure, but it's better than nothing. - + I see people constantly show panic messages like this but rarely do I see someone take the time to match up the instruction pointer with a function in the kernel symbol table. - + The best way to track down the cause of a panic is by capturing a crash dump, then using gdb(1) to to a stack trace on the crash dump. Of course, this depends on gdb(1) @@ -8887,9 +8887,9 @@ somebody saying that the new ELF-ized gdb(1) didn't handle kernel crash dumps correctly: somebody should check this before 3.0 goes out of beta or there'll be a lot of red faces after the CDs ship). - + In any case, the method I normally use is this: - + @@ -8929,7 +8929,7 @@ some kind.) was installed as /kernel, while kernel.debug can be used as the source of debugging symbols for gdb(1). - + To make sure you capture a crash dump, you need edit /etc/rc.conf and set dumpdev to point to your swap partition. This will cause the rc(8) scripts to use the @@ -8939,7 +8939,7 @@ recovered using savecore(8); if dumpdev/etc/rc.conf, the rc(8) scripts will run savecore(8) automatically and put the crash dump in /var/crash. - + NOTE: FreeBSD crash dumps are usually the same size as the physical RAM size of your machine. That is, if you have 64MB of RAM, you will get a 64MB crash dump. Therefore you must make sure @@ -8952,16 +8952,16 @@ will use to something a little more sensible. For example, if you have 128MB of RAM, you can limit the kernel's memory usage to 16MB so that your crash dump size will be 16MB instead of 128MB. - + Once you have recovered the crash dump, you can get a stack trace with gdb(1) as follows: - + % gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0 (gdb) where - + Note that there may be several screens worth of information; ideally you should use script(1) to capture all of them. Using the unstripped kernel image with all the debug symbols @@ -8971,7 +8971,7 @@ bottom up in order to trace the exact sequence of events that lead to the crash. You can also use gdb(1) to print out the contents of various variables or structures in order to examine the system state at the time of the crash. - + Now, if you're really insane and have a second computer, you can also configure gdb(1) to do remote debugging such that you can use gdb(1) on one system to debug the kernel on @@ -8980,30 +8980,30 @@ through the kernel code, just like you can do with a normal user-mode program. I haven't played with this yet as I don't often have the chance to set up two machines side by side for debugging purposes. - + [Bill adds: "I forgot to mention one thing: if you have DDB enabled and the kernel drops into the debugger, you can force a panic (and a crash dump) just by typing 'panic' at the ddb prompt. It may stop in the debugger again during the panic phase. If it does, type 'continue' and it will finish the crash dump." -ed] - + dlsym() stopped working for ELF executables! -The ELF toolchain does not, by default, make the symbols -defined in an executable visible to the dynamic linker. -Consequently dlsym() searches on handles obtained +The ELF toolchain does not, by default, make the symbols +defined in an executable visible to the dynamic linker. +Consequently dlsym() searches on handles obtained from calls to dlopen(NULL, flags) will fail to find such symbols. - -If you want to search, using dlsym(), for symbols -present in the main executable of a process, you need to link + +If you want to search, using dlsym(), for symbols +present in the main executable of a process, you need to link the executable using the option to the ELF linker. - + @@ -9013,18 +9013,18 @@ the executable using the option to the and 1 GB on FreeBSD 4.x. If you run a network-intensive server (e.g. a large FTP or HTTP server), you might find that 256 MB is not enough. - + So how do you increase the address space? There are two aspects to this. First, you need to tell the kernel to reserve a larger portion of the address space for itself. Second, since the kernel is loaded at the top of the address space, you need to lower the load address so it doesn't bump its head against the ceiling. - + The first goal is achieved by increasing the value of NKPDE in src/sys/i386/include/pmap.h. Here's what it looks like for a 1 GB address space: - + #ifndef NKPDE #ifdef SMP @@ -9035,11 +9035,11 @@ it looks like for a 1 GB address space: #endif - + To find the correct value of NKPDE, divide the desired address space size (in megabytes) by four, then subtract one for UP and two for SMP. - + To achieve the second goal, you need to compute the correct load address: simply subtract the address space size (in bytes) from 0x100100000; the result is 0xc0100000 for a 1 GB address space. @@ -9047,7 +9047,7 @@ Set LOAD_ADDRESS in src/sys/i386/conf/Makefile.i386src/sys/i386/conf/kernel.script to the same value, as follows: - + OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386") OUTPUT_ARCH(i386) @@ -9060,22 +9060,22 @@ SECTIONS .interp : { *(.interp) } - + Then reconfig and rebuild your kernel. You will probably have problems with ps(1), top(1) and the like; make world should take care of it (or a manual rebuild of libkvm, ps and top after copying the patched pmap.h to /usr/include/vm/. - + NOTE: the size of the kernel address space must be a multiple of four megabytes. - + [David Greenman adds: I think the kernel address space needs to be a power of two, but I'm not certain about that. The old(er) boot code used to monkey with the high order address bits and I think expected at least 256MB granularity.] - + @@ -9092,15 +9092,15 @@ id="acknowledgments"> FreeBSD Core Team - + Jordan Hubbard Occasional fits of FAQ-reshuffling and updating. - + - + @@ -9108,9 +9108,9 @@ id="acknowledgments"> Services above and beyond the call of duty on freebsd-questions - + - + @@ -9118,9 +9118,9 @@ id="acknowledgments"> Services above and beyond the call of duty on Usenet - + - + @@ -9128,9 +9128,9 @@ id="acknowledgments"> Networking and formatting - + - + @@ -9138,9 +9138,9 @@ id="acknowledgments"> Multicast information - + - + @@ -9148,9 +9148,9 @@ id="acknowledgments"> FreeBSD FAQ typing machine slavey - + - + @@ -9158,13 +9158,13 @@ id="acknowledgments"> Kvetching, moaning, submitting data - + - + And to any others we've forgotten, apologies and heartfelt thanks! - +