diff --git a/FAQ/admin.sgml b/FAQ/admin.sgml index f913569a8a..2c4c9954e0 100644 --- a/FAQ/admin.sgml +++ b/FAQ/admin.sgml @@ -1,826 +1,827 @@ - + System Administration Where are the system start-up configuration files?

From 2.0.5R to 2.2.1R, the primary configuration file is /etc/sysconfig. All the options are to be specified in this file and other files such as 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 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 /usr/src/etc/rc* /etc command.

/etc/rc.local is here as always and may be used to start up additional local services like 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 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. How do I add a user easily?

Use the command.

There is another package called ``<roberto@FreeBSD.ORG> about it. It is currently undergoing further development.

To remove the user again, use the command. How can I add my new hard disk to my FreeBSD system?

See the Disk Formatting Tutorial at . I have a new removable drive, how do I use it?

Whether it's a removable drive like a ZIP or an EZ drive (or 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.

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/sd2s4 /zip

for a ZIP disk with the factory configuration.

For other disks, see how they're laid out using /stand/sysinstall.

The rest of the examples will be for a ZIP drive on sd2, 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 improvement in performance, and a lot more stability. First, you need to redo the DOS-level partitions/filesystems. You can either use or /stand/sysinstall, or for a small drive that you don't want to bother with multiple operating system support on, just blow away the whole FAT partition table (slices) and just use the BSD partitioning: dd if=/dev/zero of=/dev/rsd2 count=2 disklabel -Brw sd2 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/rsd2c

and mount it: mount /dev/sd2c /zip

and it's probably a good idea to add a line like this to so you can just type "mount /zip" in the future: /dev/sd2c /zip ffs rw,noauto 0 0 How do I mount a secondary DOS partition?

The secondary DOS partitions are found after ALL the primary 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/sd1s5: # cd /dev # ./MAKEDEV sd1s5 # mount -t msdos /dev/sd1s5 /dos/e Can I mount other foreign filesystems under FreeBSD?

for more information.

Any other information on this subject would be appreciated. How can I use the NT loader to boot FreeBSD?

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/NT 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 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.BSD="FreeBSD" C:\="DOS"

This procedure assumes that DOS, NT, FreeBSD, or whatever have been installed into their respective fdisk partitions on the Mount a DOS-formatted floppy (if you've converted to NTFS) or the FAT partition, under, say, /mnt. dd if=/dev/rsd0a of=/mnt/bootsect.bsd bs=512 count=1

Reboot into DOS or NT. NTFS users copy the attrib -s -r c:\boot.ini

Edit to add the appropriate entries from the example attrib -r -s c:\boot.ini

If FreeBSD is booting from the MBR, restore it with the DOS `` 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 system. Very briefly, these are:

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, 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. For example: other=/dev/sdb4 table=/dev/sdb loader=/boot/chain.b 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 disk 1, at the FreeBSD boot loader prompt you need to specify: Boot: 1:sd(0,a)/kernel

On FreeBSD 2.2.5 and later, you can configure to automatically do this for you at boot time.

The 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 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). Will a ``dangerously dedicated'' disk endanger my health?

Now, while this is certainly the common case for people coming from a PC background, those people coming more from a Unix background and who are going to setup a machine just to run FreeBSD and only FreeBSD, are more used to the classic Unix way where the operating system owns the entire disks, from the very first sector through the end. A true fdisk table isn't of any use in this case, the machine is running FreeBSD 24 hours per day, 7 days per week, no other operating system should ever be booted on it. So, if you select ``A)ll FreeBSD'' in sysinstall's fdisk editor, and answer the next question with ``No'', you'll get this mode. Note that this means the BSD bootstrap also forms the MBR for this drive, so there's no space left for anything like a boot manager. Don't ever try to install one, or you'll damage the BSD bootstrap.

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 designed, they might complain at you once they are getting in contact with such a disk, or even worse, they might damage the BSD bootstrap without even asking or notifying you. Some kind of operating system that is in rather widespread use on PCs is known for this kind of user-unfriendliness (of course, it does this in the name of ``user-friendliness''). At least one Award BIOS that is for example used in HP Netservers (but not only there) is known to ignore any harddisk that doesn't have what it believes to be a valid fdisk table. When it comes to booting, it simply ignores such a disk drive, advances to the floppy drive, and barfs at you with just ``Read error''. Very impressive, eh? They probably also call this ``user-friendly'', who knows?

The advantages of this mode are: FreeBSD owns the entire disk, no need to waste several fictitious `tracks' for just nothing but a 1980-aged simplistic partitioning model enforcing some artificial and now rather nonsensical constraints on how this partitioning needs to be done. These constraints often lead to what might be the biggest headaches for OS installations on PCs, geometry mismatch hassles resulting out of two different, redundant ways how to store the partitioning information in the fdisk table. See the chapter about . In ``dangerously dedicated'' mode, the BSD bootstrap starts at sector 0, and this one is the only sector that always translates into the same C/H/S values, regardless of which `translation' your BIOS is using for your disk. Thus, you can also swap disks between systems/controllers that use a different translation scheme, without risking that they won't boot anymore.

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/rsd0 count=15

Alternatively, the undocumented DOS ``feature'' fdisk /mbr

will to install a new master boot record as well, thus clobbering the BSD bootstrap. How can I add more swap space?

The best way is to increase the size of your swap partition, or take advantage of this convenient excuse to add another disk.

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.

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.

It is a really bad idea to locate your swap file over NFS unless you are running in a very fast networking environment, with a good 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. create a vn-device cd /dev sh ./MAKEDEV vn0 create a swapfile (/usr/swap0) dd if=/dev/zero of=/usr/swap0 bs=1024k count=64 enable the swap file in /etc/rc.conf swapfile="/usr/swap0" # Set to name of swapfile if aux swapfile desired. reboot the machine

To enable the swap file immediately, type vnconfig -ce /dev/vn0c /usr/swap0 swap I'm having problems setting up my printer.

Please have a look at the Handbook entry on printing. It should cover most of your problem. See the The keyboard mappings are wrong for my system.

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 .

This can be configured in /etc/sysconfig (or ). 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: Belgian ISO-8859-1 Brazilian 275 keyboard Codepage 850 Brazilian 275 keyboard ISO-8859-1 Danish Codepage 865 Danish ISO-8859-1 French ISO-8859-1 German Codepage 850 German ISO-8859-1 Italian ISO-8859-1 Japanese 106 Japanese 106x Latin American Norwegian ISO-8859-1 Polish ISO-8859-2 (programmer's) Russian Codepage 866 (alternative) Russian koi8-r (shift) Russian koi8-r Spanish ISO-8859-1 Swedish Codepage 850 Swedish ISO-8859-1 Swiss-German ISO-8859-1 United Kingdom Codepage 850 United Kingdom ISO-8859-1 United States of America ISO-8859-1 United States of America dvorak United States of America dvorakx I can't get user quotas to work properly.

Don't turn on quotas on '/', Put the quota file on the file system that the quotas are to be enforced on. ie: FS QUOTA FILE /usr /usr/admin/quotas /home /home/admin/quotas ... 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) # disklabel -e ccd0 (edit, save, quit) disklabel: ioctl DIOCWDINFO: No disk label on disk; use "disklabel -r" to install initial label #

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 # disklabel -e ccd0 (this will work now) Does FreeBSD support System V IPC primitives?

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 options SYSVSEM # enable for semaphores options SYSVMSG # enable for messaging

Recompile and install.

How do I use sendmail for mail delivery with UUCP?

The sendmail configuration that ships with FreeBSD is 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 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: cd /usr/src tar -xvzf /cdrom/dists/src/ssmailcf.aa

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: cd /usr/src/usr.sbin/sendmail/cf/cf make foo.cf 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) define(`UUCP_RELAY', your.uucp.relay) define(`UUCP_MAX_SIZE', 200000) MAILER(local) MAILER(smtp) MAILER(uucp) Cw your.alias.host.name Cw youruucpnodename.UUCP

The nodns and nocanonify features will prevent any usage of the DNS during mail delivery. The UUCP_RELAY clause is needed for bizarre reasons, 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 # horus.interface-business.de uucp-dom:horus .interface-business.de uucp-dom:if-bus interface-business.de uucp-dom:if-bus .heep.sax.de smtp8:%1 horus.UUCP uucp-dom:horus if-bus.UUCP uucp-dom:if-bus . uucp-dom:sax

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 some UUCP neighbor in order to ``shortcut'' the delivery path. The next line handles mail to the local Ethernet domain that can be delivered using SMTP. Finally, the UUCP neighbors are mentioned in the .UUCP pseudo-domain notation, to allow for a ``uucp-neighbor!recipient'' override of the default rules. The last line is always a single dot, matching everything else, with UUCP delivery to a UUCP neighbor that 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 -bt option to sendmail. It starts sendmail in address test mode; simply enter ``0 '', followed by the address you wish to 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. j@uriah 191% sendmail -bt ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) Enter

> 0 foo@interface-business.de rewrite: ruleset 0 input: foo @ interface-business . de ... rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \ < @ interface-business . de > > ^D j@uriah 192% 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 In order to retrieve mail from your mailbox, you'll need to install a retrieval agent. /etc/ppp/ppp.linkup: MYADDR: !bg su user -c fetchmail

I'm assuming that you have an account for poll myISP.com protocol pop3 fetchall pass MySecret;

Needless to say, this file should not be readable by anyone except In order to send mail with the correct The following VERSIONID(`bsd.home.mc version 1.0') OSTYPE(bsd4.4)dnl FEATURE(nouucp)dnl MAILER(local)dnl MAILER(smtp)dnl Cwlocalhost Cwbsd.home MASQUERADE_AS(`myISP.com')dnl FEATURE(allmasquerade)dnl FEATURE(masquerade_envelope)dnl FEATURE(nocanonify)dnl FEATURE(nodns)dnl define(SMART_HOST, `relay.myISP.com') Dmbsd.home define(`confDOMAIN_NAME',`bsd.home')dnl define(`confDELIVERY_MODE',`deferred')dnl

Refer to the previous section for details of how to turn this Eek! I forgot the root password!

Don't Panic! Simply restart the system, type -s at the Boot: prompt to enter Single User mode. At the question about the shell to use, hit ENTER. You'll be dropped to a # prompt. Enter mount -u / to - remount your root filesystem read/write, then run How do I keep Control-Alt-Delete from rebooting the system?

Edit the keymap you are using for the console and replace the /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. diff --git a/FAQ/applications.sgml b/FAQ/applications.sgml index 73b7645051..698d4b698f 100644 --- a/FAQ/applications.sgml +++ b/FAQ/applications.sgml @@ -1,131 +1,142 @@ - + User Applications So, where are all the user applications?

Please take a look at for info on software packages ported to FreeBSD. The list currently tops 1000 and is growing daily, so come back to check often or subscribe to the for periodic updates on new entries.

Most ports should be available for both the 2.2 and 3.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 installed and uninstalled + 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 interested in installing. Package files can usually be identified by 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.1.x-release for 2.2.6-release/2.2-stable for 3.0-current

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 master site. Where do I find libc.so.3.0?

You are trying to run a package for 2.2/3.0 on a 2.1.x system. Please take a look at the previous section and get the correct port/package for your system. ghostscript gives lots of errors with my 386/486SX.

You don't have a math co-processor, right? 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

When I run a SCO/iBCS2 application, it bombs on

You first need to edit the /etc/sysconfig (or ) file in the last section to change the following variable to # Set to YES if you want ibcs2 (SCO) emulation loaded at startup ibcs2=NO

It will load the 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 -rw-rw-r-- 1 root wheel 0 Oct 28 12:02 null 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 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 How do I configure INN (Internet News) for my machine?

After installing the inn package or port, an excelent place to start is where you'll find the INN FAQ. + + + + What version of Microsoft FrontPage should I get? + + +

Use the Port, Luke! A pre-patched version of Apache is available in the ports tree. +

+ + + diff --git a/FAQ/hardware.sgml b/FAQ/hardware.sgml index 669ba04bbd..896af48137 100644 --- a/FAQ/hardware.sgml +++ b/FAQ/hardware.sgml @@ -1,334 +1,401 @@ - + Hardware compatibility What kind of hard drives does FreeBSD support?

FreeBSD supports EIDE and SCSI drives (with a compatible controller; see the next section), and all drives using the original "Western Digital" interface (MFM, RLL, ESDI, and of course IDE). A few ESDI controllers that use proprietary interfaces may not work: stick to WD1002/3/6/7 interfaces and clones. Which SCSI controllers are supported?

See the complete list in the . Which CD-ROM drives are supported by FreeBSD?

Any SCSI drive connected to a supported controller is supported.

The following proprietry CD-ROM interfaces are also supported: Mitsumi LU002 (8bit), LU005 (16bit) and FX001D (16bit 2x Speed). Sony CDU 31/33A Sound Blaster Non-SCSI CD-ROM Matsushita/Panasonic CD-ROM ATAPI compatible IDE CD-ROMs

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. Does FreeBSD support ZIP drives?

FreeBSD supports the SCSI ZIP drive out of the box, of course. The ZIP drive can only be set to run at SCSI target IDs 5 or 6, but if your SCSI host adapter's BIOS supports it you can even boot from it. 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 3.0-CURRENT contains support for the parallel Zip However, you will need to build a new kernel with support for ppbus (Parallel Port Bus) in order to use the Zip. See the LINT configuration file for examples.

Also check out , and . Does FreeBSD support JAZ, EZ and other removable drives?

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.

See . Which multi-port serial cards are supported by FreeBSD?

There is a list of these in the section of the handbook.

Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible.

Check the man page to get more information on configuring such cards. I have an unusual bus mouse. How do I set it up?

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. If you are building a custom kernel with the bus mouse driver, make sure to add the following line to the kernel config file: device mse0 at isa? port 0x23c tty irq5 vector mseintr

The bus mouse usually comes with an dedicatd interface card. 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 page for more information. How do I use my PS/2 (``mouse port'' or ``keyboard'') mouse?

If you're running a very recent version of FreeBSD, the necessary 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 FreeBSD then you can simply enable it in the kernel configuration menu at installation time, otherwise later with -c 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: device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr

See the 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. Is it possible to make use of a mouse in any way outside the X Window?

If you are using the default console driver, syscons, you can 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 vidcontrol -m on

Where xxxx is the mouse device name and yyyy is a protocol type for the mouse. See the man page for supported protocol types.

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=""

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 on this issue". How do I cut and paste text with mouse in the text console?

Once you get the mouse daemon running (see ), 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 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 man page for details. My mouse has a fancy wheel and buttons. Can I use them in FreeBSD?

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 three button mouse. How do I use the mouse/trackball/touchpad on my laptop?

Please refer to . And check out on the Mobile Computing page. What types of tape drives are supported?

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. Does FreeBSD support tape changers?

FreeBSD 2.2 supports SCSI changers using the device and the command. The details of how you actually control the changer can be found in the man page.

If you're not using 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. Which sound cards are supported by FreeBSD?

FreeBSD supports the SoundBlaster, SoundBlaster Pro, SoundBlaster 16, Pro Audio Spectrum 16, AdLib and Gravis UltraSound sound cards. There is also limited support for MPU-401 and compatible MIDI cards. Cards conforming to the Microsoft Sound System specification are also supported through the pcm driver.

Which network cards does FreeBSD support?

See the section of the handbook for a more complete list. I don't have a math co-processor - is that bad?

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 ). 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.

What other devices does 2.X support?

See the for the list of other devices supported. Does FreeBSD support power management on my laptop?

FreeBSD supports APM on certain machines. Please look in the keyword. + Workarounds for specific hardware problems +

This section contains workarounds for specific hardware + problems encountered by our users. + + Micron systems hang at boot time +

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 + + + + + + I have a newer Adaptec controller and FreeBSD can't find it. + + +

The newer AIC789x series Adaptec chips are supported under the CAM SCSI + framework making it's debut in 3.0. Patches against 3.0-CURRENT and 2.2-STABLE + are in . + A CAM-enhanced boot floppy is available at . In both cases read the README before + beginning.

+ + + + + I have an internal Plug & Play modem and FreeBSD can't find it. + + +

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 /sys/i386/isa/sio.c, at about line 1200. 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 + boot-time configuration with a command like + + pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8 + + to make the modem show.

+ + + + + How do I get the boot: prompt to show on the serial console? + + +

+ Build a kernel with Create /boot.config and place Unplug the keyboard from the system. +

+ +

See /usr/src/sys/i386/boot/biosboot/README.serial for information.

+ + + + + + Why doesn't my 3Com PCI network card work with my Micron computer?

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 System" flag in the BIOS.

More information on this problem is available at URL: diff --git a/FAQ/install.sgml b/FAQ/install.sgml index 4a85fbe33d..c129709023 100644 --- a/FAQ/install.sgml +++ b/FAQ/install.sgml @@ -1,464 +1,464 @@ - + Installation Which file do I download to get FreeBSD?

You generally need just one floppy image, the floppies/boot.flp file, which you image-copy onto a 1.44MB floppy and then boot it in order to download the rest (and the installation will manage your TCP/IP collection, deal with tapes, CDROMs, floppies, DOS. partitions, whatever's necessary to get the reset of the bits installed).

If you need to download the distributions yourself (for a DOS filesystem install, for instance), below are some recommendations for distributions to grab: bin/ manpages/ compat*/ doc/ src/ssys.*

Full instructions on this procedure and a little bit more about installation issues in general can be found in the Where are the instructions for installing FreeBSD?

Installation instructions can be found in the What do I need in order to run FreeBSD?

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 I have only 4 MB of RAM. Can I install FreeBSD?

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 :-)) How can I make my own custom install floppy?

Currently there's no way to *just* make a custom install floppy. 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 . Can I have more than one operating system on my PC?

Have a look at Can Windows 95 co-exist with FreeBSD?

Install Windows 95 first, after that FreeBSD. FreeBSD's boot 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. Windows 95 killed my boot manager! How do I get it back?

You can reinstall the boot manager FreeBSD comes with in one of two ways: Running DOS, go into the tools/ directory of your FreeBSD distribution and look for bootinst.exe. You run it like so:

bootinst.exe boot.bin

and the boot manager will be reinstalled. Boot the FreeBSD boot floppy again and go to the Custom installation menu item. Choose Partition. Select the drive which used to contain your boot manager (likely the first one) and when you come to the partition editor for it, as the very first thing (e.g. do not make any changes) select (W)rite. This will ask for confirmation, say yes, and when you get the Boot Manager selection prompt, be sure to select "Boot Manager." This will re-write the boot manager to disk. Now quit out of the installation menu and reboot off the hard disk as normal. Can I install on a disk with bad blocks?

FreeBSD's bad block (the command) handling is still not 100% (to put it charitably) and 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 . Strange things happen when I boot the install floppy!

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:- Did you use a new, freshly-formatted, error-free floppy (preferably a brand-new one straight out of the box, as opposed to the magazine coverdisk that's been lying under the bed for the last three years)? Did you download the floppy image in binary (or image) mode? (don't be embarrassed, even the best of us have accidentally downloaded a binary file in ASCII mode at least once!) If you're using one of these new-fangled operating systems like Windows95 or Windows NT, did you shut it down and restart the system in plain, honest DOS? It seems these OS's can interfere with programs that write directly to hardware, which the disk creation program does; even running it inside a DOS 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. Help! I can't install from tape!

If you are installing 2.1.7R from tape, you must create the tape using a tar blocksize of 10 (5120 bytes). The default tar 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. Can I install on my laptop over PLIP (Parallel Line IP)?

Connect the two computers using a Laplink parallel cable to use this feature: +----------------------------------------+ |A-name A-End B-End Descr. Port/Bit | +----------------------------------------+ |DATA0 2 15 Data 0/0x01 | |-ERROR 15 2 1/0x08 | +----------------------------------------+ |DATA1 3 13 Data 0/0x02 | |+SLCT 13 3 1/0x10 | +----------------------------------------+ |DATA2 4 12 Data 0/0x04 | |+PE 12 4 1/0x20 | +----------------------------------------+ |DATA3 5 10 Strobe 0/0x08 | |-ACK 10 5 1/0x40 | +----------------------------------------+ |DATA4 6 11 Data 0/0x10 | |BUSY 11 6 1/0x80 | +----------------------------------------+ |GND 18-25 18-25 GND - | +----------------------------------------+

See also on the Mobile Computing page. Which geometry should I use for a disk drive?

(By the "geometry" of a disk, we mean the number of cylinders, 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 All that matters is the 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 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 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 ``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. Any restrictions on how I divide the disk up?

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. What about disk managers? Or, I have a large drive!

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 You will have to reinstall FreeBSD, but obeying the instructions given above will almost always get you going. I can't get past the boot manager's `F?' prompt.

This is another symptom of the problem described in the preceding 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. I have >16MB of RAM. Will this cause any problems?

Apart from performance issues, no. FreeBSD 2.X comes with bounce buffers which allow your bus mastering controller access to greater than 16MB. (Note that this should only be required if you are using ISA devices, although one or two broken EISA and VLB devices may need it as well).

Also look at the section on if you have that much memory, or if you're using a Compaq or other BIOS that lies about the available memory. Do I need to install the complete sources?

In general, no. However, we would strongly recommend that you install, at a minimum, the ``. With the exception of the kernel sources, our build structure is set up so that you can read-only mount the sources from elsewhere via NFS and still be able to make new binaries. (Because of the kernel-source 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. Do I need to build a kernel?

Building a new kernel was originally pretty much a required step in a FreeBSD installation, but more recent releases have benefited from the introduction of a much friendlier kernel 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. I live outside the US. Can I use DES encryption?

If it is not absolutely imperative that you use DES style encryption, you can use FreeBSD's default encryption for even Since the DES encryption algorithm cannot legally be exported from the US, non-US users should not download this software (as part of the 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: ftp://ftp.internat.freebsd.org/pub/FreeBSD ftp://storm.sea.uct.ac.za/pub/FreeBSD ftp://ftp.iqm.unicamp.br/pub/FreeBSD ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

The non-US 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 for the discussion of non-US encryption software. For more information, send an email message with a single line saying ``<majordomo@braae.ru.ac.za>. The boot floppy starts but hangs at the ``Probing Devices...'' screen.

If you have a IDE Zip or Jaz drive installed, remove it and try again. - The boot floppy has trouble probing these devices and can confuse it. + 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. diff --git a/FAQ/preface.sgml b/FAQ/preface.sgml index e27523ed73..4140e0f6fc 100644 --- a/FAQ/preface.sgml +++ b/FAQ/preface.sgml @@ -1,529 +1,529 @@ - + Preface

Welcome to the FreeBSD 2.X FAQ! What is the purpose of this FAQ?

As is usual with Usenet FAQs, this document aims to cover the most frequently asked questions concerning the FreeBSD operating system (and of course answer them!). Although originally intended to reduce bandwidth and avoid the same old questions being asked over and over again, FAQs have become recognized as valuable information resources.

Every effort has been made to make this FAQ as informative as possible; if you have any suggestions as to how it may be improved, please feel free to mail them to the . What is FreeBSD?

Briefly, FreeBSD 2.X is a UN*X-like operating system based on U.C. Berkeley's 4.4BSD-lite release for the i386 platform. It is also based indirectly on William Jolitz's port of U.C. Berkeley's Net/2 to the i386, known as 386BSD, though very little of the 386BSD code remains. A fuller description of what FreeBSD is and how it can work for you may be found on the .

FreeBSD is used by companies, Internet Service Providers, researchers, computer professionals, students and home users all over the world in their work, education and recreation. See some of them in the

For more detailed information on FreeBSD, please see the What are the goals of FreeBSD?

The goals of the FreeBSD Project are to provide software that may be used for any purpose and without strings attached. Many of us have a significant investment in the code (and project) and would certainly not mind a little financial compensation now and then, but we're definitely not prepared to insist on it. We believe that our first and foremost "mission" is to provide code to any and all comers, and for whatever purpose, so that the code gets the widest possible 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 Public License (GPL) or GNU Library Public License (GLPL) comes with slightly more strings attached, though at least on the side of enforced access rather than the usual opposite. Due to the additional complexities that can evolve in the commercial use of GPL software, we do, however, endeavor to replace such software with submissions under the more relaxed BSD copyright whenever possible. Why is it called FreeBSD?

It may be used free of charge, even by commercial users. Full source for the operating system is freely available, and the minimum possible restrictions have been placed upon its use, distribution and incorporation into other work (commercial or non-commercial). Anyone who has an improvement and/or bug fix is free to submit their code and have it added to the source tree (subject to one or two obvious provisos).

For those of our readers whose first language is not English, it may be worth pointing out that the word ``free'' is being used in two ways here, one meaning ``at no cost'', the other meaning ``you can do whatever you like''. Apart from one or two things you What is the latest version of FreeBSD?

Version is the latest stable version; it was released in October, 1997. This is also the latest release version.

Briefly explained, -stable is aimed at the ISP or other corporate user who wants stability and a low change count over the wizzy new features of the latest release. At the moment, these versions are one and the same, but it shouldn't be long before the -current branch is polished enough for general release.

This is not to say that a 3.0-current snapshot is unusable for business services, and many people who need some 3.0 specific feature (newer compiler technology, faster networking code, etc) have decided to take a chance with it with very good results. We simply do not wish to "certify" 3.0 as mission-worthy until it's been better shaken-out. What is FreeBSD-current?

is the development version of the operating system, which will in due course become 3.0-RELEASE. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the in the for details on running -current.

If you are not familiar with the operating system or are not capable of identifying the difference between a real problem and a temporary problem, you should not use FreeBSD-current. This branch sometimes evolves quite quickly and can be un-buildable for a number of days at a time. People that use FreeBSD-current are expected to be able to analyze any problems and only report them if they are deemed to be mistakes rather than ``glitches''. Questions such as ``make world produces some error about groups'' on the -current mailing list are sometimes treated with contempt.

Every now and again, a release is also made of this -current development code, CDROM distributions of the occasional snapshot even now being made available. The goals behind each snapshot release are: To test the latest version of the installation software. To give people who would like to run -current but who don't have the time and/or bandwidth to follow it on a day-to-day basis an easy way of bootstrapping it onto their systems. To preserve a fixed reference point for the code in question, just in case we break something really badly later. (Although CVS normally prevents anything horrible like this happening :) To ensure that any new features in need of testing have the greatest possible number of potential 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 and are generated, on the average, once a day for both the 3.0-current and 2.2-stable branches. What is the FreeBSD-stable concept?

Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD development into two parts. One branch was named , with the intention that only well-tested bug fixes and small incremental enhancements would be made to it (for Internet Service Providers and other commercial enterprises for whom sudden shifts or experimental features are quite undesirable). The other branch was , which essentially has been one unbroken line leading towards 3.0-RELEASE (and beyond) since 2.0 was released. If a little ASCII art would help, this is how it looks: 2.0 | | | [2.1-stable] *BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-stable ends] | (Mar 1997) | | | [2.2-stable] - *BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5-RELEASE -> ... - | (Mar 1997) (Oct 1997) + *BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5 -> 2.2.6 -> 2.2.7 + | (Mar 1997) (Oct 97) (Apr 98) (Jul 98) | | 3.0-SNAPs (started Q1 1997) | | - 3.0.0-RELEASE (Q1 1998) + 3.0.0-RELEASE (Oct 1998) | \|/ + [future 3.x releases]

The -current branch is slowly progressing towards 3.0 and beyond, whereas the previous 2.1-stable branch was superceded by the release of 2.2.0, the new "stability branch" aka 2.2-stable. 3.0-current will continue to be where the active development takes place, up until the actual release of 3.0. At that point, 3.0 will become yet another branch and 3.1-current will become the next "current branch". Why did the 2.1-stable branch end with 2.1.7.1?

While we'd certainly like to be able to continue 3 branches of development, we've found that the version control tools available to us are not particularly well-suited for this; in fact, they quickly result in a maintenance nightmare for any branch which lives much beyond 2-3 months. The 2.1-stable branch has, by contrast, lasted for well over a year and what little sanity the FreeBSD developers have left would be in serious jeopardy if we continued in this way. Perhaps in the future we'll figure out another model which gives everyone what they want, and we are working on such a model, but in the meantime it's probably best to think of the old -stable coming to an end with (the final point release after 2.1.7), and the new -stable beginning with 2.2.2. When are FreeBSD releases made?

As a general principle, the FreeBSD core team only release a new version of FreeBSD when they believe that there are sufficient new features and/or bug fixes to justify one, and are satisfied that the changes made have settled down sufficiently to avoid compromising the stability of the release. Many users regard this caution as one of the best 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 6 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. Is FreeBSD only available for PCs ?

At present, yes, though a port to the and architecture is under way. If your machine has a different architecture and you need something right now, we suggest you look at or . Who is responsible for FreeBSD?

The key decisions concerning the FreeBSD project, such as the overall direction of the project and who is allowed to add code to the source tree, are made by a of some 17 people. There is a much larger team of around 80+ who are authorized to make changes directly to the FreeBSD source tree.

However, most non-trivial changes are discussed in advance in the , and there are no restrictions on who may take part in the discussion. Where can I get FreeBSD?

Every significant release of FreeBSD is available via anonymous ftp from the : For the current 2.2-stable release, 2.2.6R see the directory. For the current 3.0-current release, 3.0-SNAP, see the directory. releases are made once a day along the RELENG_2_2 branch (2.2.6 -> 2.2.x) as it winds its way towards the next point release on the 2.2 branch. With the occasional exception of accidental breakage, the RELENG_2_2 branch is being carefully maintained (no experimental changes, fixes made only after testing in -current). releases are also made once a day for the branch, these being of service purely to bleeding-edge testers and developers.

FreeBSD is also available via CDROM, from the following place(s):

Walnut Creek CDROM 4041 Pike Lane, Suite F Concord, CA 94520 USA Orders: +1 800 786-9907 Questions: +1 925 674-0783 FAX: +1 925 674-0821 email: WWW:

In Australia, you may find it at:

Advanced Multimedia Distributors Factory 1/1 Ovata Drive Tullamarine, Melbourne Victoria Australia Voice: +61 3 9338 6777 CDROM Support BBS 17 Irvine St Peppermint Grove WA 6011 Voice: +61 9 385-3793 Fax: +61 9 385-2360 And in the UK: The Public Domain & Shareware Library Winscombe House, Beacon Rd Crowborough Sussex. TN6 1UL Voice: +44 1892 663-298 Fax: +44 1892 667-473 Where do I find info on the FreeBSD mailing lists?

You can find full information in the What FreeBSD news groups are available?

You can find full information in the Are there FreeBSD IRC (Internet Relay Chat) channels?

Yes, most major IRC networks host a FreeBSD chat channel: Channel #FreeBSD on EFNET is perhaps the most popular. Available at server irc.chat.org. Channel #FreeBSD on DALNET is available at irc.dal.net in the US and irc.eu.dal.net in Europe. Channel #FreeBSD on UNDERNET is available at us.undernet.org in the US and eu.undernet.org in Europe. Finally, you can also join #FreeBSD on BSDNET, a smaller BSD only chat network, at irc.FreeBSD.org.

Each of these channels are distinct and are not connected to each other. Their chat styles also differ, so you may need to try each to find one suited to your chat style. Books on FreeBSD

Greg Lehey's book ``Installing and Running FreeBSD'' is available from Walnut Creek and ships with the 2.2.6 CDROM. There is also a larger book entitled ``The Complete FreeBSD'', which comes with additional printed manpages and includes the 2.2.6 CDROM set. It should be available in most good book shops now.

There is a FreeBSD Documentation Project which you may contact (or even better, join) on the doc mailing list: . This list is for discussion of the FreeBSD documentation. For actual questions about FreeBSD, there is the questions mailing list: .

A FreeBSD ``handbook'' is available, and can be found as: . Note that this is a work in progress, and so parts may be incomplete.

The definitive printed guide on FreeBSD is ``The Complete FreeBSD'', written by Greg Lehey and published by Walnut Creek CDROM Books. Now in its second edition, the book contains 1,750 pages of install & system administration guidance, program setup help, and manual pages. The book (and current FreeBSD release) can be ordered from , , or at your favorite bookstore. The ISBN is 1-57176-227-2.

However, as FreeBSD 2.2.X is based upon Berkeley 4.4BSD-Lite2, most of the 4.4BSD manuals are applicable to FreeBSD 2.2.X. O'Reilly and Associates publishes these manuals: 4.4BSD System Manager's Manual By Computer Systems Research Group, UC Berkeley 1st Edition June 1994, 804 pages : 1-56592-080-5 4.4BSD User's Reference Manual By Computer Systems Research Group, UC Berkeley 1st Edition June 1994, 905 pages : 1-56592-075-9 4.4BSD User's Supplementary Documents By Computer Systems Research Group, UC Berkeley 1st Edition July 1994, 712 pages : 1-56592-076-7 4.4BSD Programmer's Reference Manual By Computer Systems Research Group, UC Berkeley 1st Edition June 1994, 886 pages : 1-56592-078-3 4.4BSD Programmer's Supplementary Documents By Computer Systems Research Group, UC Berkeley 1st Edition July 1994, 596 pages : 1-56592-079-1

A description of these can be found via WWW as: . Due to poor sales, however, these manuals may be hard to get a hold of.

For a more in-depth look at the 4.4BSD kernel organization, you can't go wrong with:

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. 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, 1995 : 0-13-151051-7

This book covers the basics, as well as TCP/IP, DNS, NFS, SLIP/PPP, sendmail, INN/NNTP, printing, etc.. It's expensive (approx. US$45-$55), but worth it. It also includes a CDROM with the sources for various tools; most of these, however, are also on the FreeBSD 2.2.6R CDROM (and the FreeBSD CDROM often has newer versions). How do I access your Problem Report database?

The Problem Report database of all open user change requests may be queried (or submitted to) by using our web-based PR and interfaces. The send-pr(1) command can also be used to submit problem reports and change requests via electronic mail. Other sources of information.

The following newsgroups contain pertinent discussion for FreeBSD users: (moderated)

Web resources: The .

The FreeBSD handbook also has a fairly complete section which is worth reading if you're looking for actual books to buy. diff --git a/FAQ/troubleshoot.sgml b/FAQ/troubleshoot.sgml index 3d1b9712f0..71c455151e 100644 --- a/FAQ/troubleshoot.sgml +++ b/FAQ/troubleshoot.sgml @@ -1,426 +1,427 @@ - + Troubleshooting I have bad blocks on my hard drive!

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

For other drive types, you are dependent on support from the operating system. Unfortunately, the ``bad144'' command that FreeBSD supplies for this purpose needs a considerable amount of work done on it. In other words, it doesn't work. If you're lucky, you can create a file that contains the bad blocks and stuff it away with a name like ".BADBLOCKS". This is how I got 386BSD Patchkit 24 completed. IDE drives are 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. FreeBSD does not recognize my Bustek 742a EISA SCSI!

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 card. The 742a has 2 ROM chips on it, one is the BIOS chip and the other is the Firmware chip. FreeBSD doesn't care what version of BIOS chip you have but it does care about what version 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 . This is a problem that occurs with the Vesa-Local Buslogic SCSI cards. My HP Netserver's SCSI controller is not detected!

This is basically a known problem. The EISA on-board SCSI controller in the HP Netserver machines occupies EISA slot number 11, so all the ``true'' EISA slots are in front of it. Alas, the address space for EISA slots >= 10 collides with the address space assigned to PCI, and FreeBSD's 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 .

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, now also understands to save this value.

Hopefully, future versions will have a proper fix for this problem.

for more info. What's up with this CMD640 IDE controller?

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 I keep seeing messages like ``

This is usually caused by an interrupt conflict (e.g., two boards using the same IRQ). FreeBSD prior to 2.0.5R used to be tolerant 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 cabel) and see if the error messages go away.

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 the type of the device that you want to mount. By default, will assume the filesystem is of type ``. This does, of course, assume that the 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 `` mount_cd9660 /dev/cd0c /mnt When I mount a CDROM, I get ``Device not configured''.

This generally means that there is no CDROM in the CDROM drive, 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. In you have a SCSI CD-ROM please try to add the following symbol into your kernel configuration file and recompile. options "SCSI_DELAY=15" My printer is ridiculously slow. What can I do ?

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. My programs occasionally die with ``Signal 11'' errors.

This can be caused by bad hardware (memory, motherboard, etc.). Try running a memory-testing program on your PC. Note that, even though every memory testing program you try will report your memory as being fine, it's possible for slightly marginal memory 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 When I boot, the screen goes black and loses sync!

This is a known problem with the ATI Mach 64 video card. The problem is that this card uses address driver it will touch this port even if you don't have the fourth serial port, and Until the bug has been fixed, you can use this workaround: Enter Disable no problems. Type exit to continue booting.

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 Even after applying these workarounds, you may still find that X Window does not work properly. Some newer ATI Mach 64 video cards (notably ATI Mach Xpression) do not run with the current version of and following the links to the new beta release. Get the following files:

AccelCards, BetaReport, Cards, Devices, FILES, README.ati, README.FreeBSD, README.Mach64, RELNOTES, VGADriver.Doc, X312BMa64.tgz

Replace the older files with the new versions and make sure you run again. 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 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 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 FreeBSD 2.0 panics with ``kmem_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 . + name="netstat -m">. The default value for NMBCLUSTERS is + ``CMAP busy panic'' when rebooting with a new kernel. -

The logic that attempts to detect an out of data +

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 , 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: 553 relay.domain.net config error: mail loops back to myself 554 ... Local configuration error How can I solve this problem? You have asked mail to the domain (e.g., domain.net) to be forwarded to a specific host (in this case, relay.domain.net) by using an MX record, but the relay machine doesn't recognize itself as domain.net. Add domain.net to /etc/sendmail.cw (if you are using FEATURE(use_cw_file)) or add "Cw domain.net" to /etc/sendmail.cf.

The current version of the is no longer maintained with the sendmail release. It is however regularly posted to , , , , and . You can also receive a copy via email by sending a message to with the command "send usenet/news.answers/mail/sendmail-faq" as the body of the message. Full screen applications on remote machines misbehave!

The remote machine may be setting your terminal type to something other than the cons25 terminal type used by the FreeBSD console.

There are a number of work-arounds for this problem: After logging on to the remote machine, set your TERM shell variable to either ansi or sco. Use a VT100 emulator like locally. screen offers you the ability to run multiple concurrent sessions from one terminal, and is a neat program in its own right. Install the cons25 terminal database entry on the remote machine. Fire up X and login to the remote machine from an xterm. diff --git a/FAQ/x.sgml b/FAQ/x.sgml index 4a380f50c7..da916b9b0d 100644 --- a/FAQ/x.sgml +++ b/FAQ/x.sgml @@ -1,347 +1,365 @@ - + The X Window System and Virtual Consoles I want to run X, how do I go about it?

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 tool, which assists you in configuring XFree86(tm) for your particular graphics card/mouse/etc.

You may also wish to investigate the Xaccel server, which is available at a very reasonable price. See the section on for more details. Why doesn't my mouse work with X

If you are using syscons (the default console driver), you can configure FreeBSD to support a mouse pointer on each virtual screen. In order to avoid conflicting with X, syscons supports a virtual device called ``/dev/sysmouse''. All mouse events received from the real mouse device are written to the sysmouse device, using the MouseSystems protocol. If you wish to use your mouse on one or more virtual consoles, /etc/rc.conf: moused_type=ps/2 # or whatever your actual type is moused_port=/dev/psm0 # or whatever your real port is moused_flags= /etc/XF86Config Section Pointer Protocol "MouseSystems" Device "/dev/sysmouse" .....

Some people prefer to use ``/dev/mouse'' under X. To make this work, ``/dev/mouse'' should be linked to : # cd /dev # rm -f mouse # ln -s sysmouse mouse 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 `` # Let the server do the NumLock processing. This should only be # required when using pre-R6 clients ServerNumLock What is a virtual console and how do I make more?

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 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, and Alt-F1, Alt-F2, and Alt-F3 will switch between these virtual consoles. To enable more of them, edit and add entries for `` # Edit the existing entry for ttyv3 in /etc/ttys and change # "off" to "on". ttyv3 "/usr/libexec/getty Pc" cons25 on secure ttyv4 "/usr/libexec/getty Pc" cons25 on secure ttyv5 "/usr/libexec/getty Pc" cons25 on secure ttyv6 "/usr/libexec/getty Pc" cons25 on secure ttyv7 "/usr/libexec/getty Pc" cons25 on secure ttyv8 "/usr/libexec/getty Pc" cons25 on secure ttyv9 "/usr/libexec/getty Pc" cons25 on secure ttyva "/usr/libexec/getty Pc" cons25 on secure 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 ``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 , 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 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. How do I access the virtual consoles from X?

If the console is currently displaying X Window, you can use Ctrl-Alt-F1, etc. to switch to a virtual console. Note, however, that once you've switched away from X Window to a virtual terminal, you may use only the Alt- function key to switch to another 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. How do I start XDM from the /etc/ttys file ?

Starting via is a Start it from your (or even from a /usr/local/etc/rc.d), and be explicit about how it has to start. If this is your last action in /usr/X11R6/lib/X11/xdm/Xservers file. This is not necessary: X will use the first free When I run xconsole, I get ``Couldn't open console''.

If you start with , the permissions on /dev/console will and 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 file exists to solve such problems.

In a nutshell, make sure an uncommented line of the form /dev/ttyv0 0600 /dev/console

is in and it will ensure that whomever logs in on /dev/ttyv0 will own the console. My PS/2 mouse doesn't behave properly under X.

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 following option in your kernel configuration file and recompile it. options PSM_CHECKSYNC

See the section on 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 ``-c'' option at the boot prompt: boot: -c Then, in the UserConfig command line, type: UserConfig> flags psm0 0x100 UserConfig> quit My PS/2 mouse from MouseSystems doesn't seem to work.

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 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 section on if you've no experience with building kernels. diff -u psm.c.orig psm.c @@ -766,6 +766,8 @@ if (verbose >= 2) log(LOG_DEBUG, "psm%d: SET_DEFAULTS return code:%04x\n", unit, i); + set_mouse_resolution(sc->kbdc, PSMD_RES_HIGH); + #if 0 set_mouse_scaling(sc->kbdc); /* 1:1 scaling */ 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 ``-c'' 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.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.

+ + + + + How do I reverse the mouse buttons? + + +

Run the command +