diff --git a/FAQ/commercial.sgml b/FAQ/commercial.sgml index f5d73a514d..03dbd58a4d 100644 --- a/FAQ/commercial.sgml +++ b/FAQ/commercial.sgml @@ -1,97 +1,175 @@ - + Commercial Applications

for a longer list. Where can I get Motif for FreeBSD? -

Contact for a Motif 2.0 +

Contact for an ELF Motif 2.1 + distribution for FreeBSD.

This distribution includes: + + OSF/Motif manager, xmbind, panner, wsm. + + Development kit with uil, mrm, xm, xmcxx, include and Imake + files. + + Static and dynamic ELF libraries (for use with FreeBSD 3.0 + and above). + + Demonstration applets. + + +

Be sure to specify that you want the FreeBSD version of Motif + when ordering! Versions for NetBSD and OpenBSD are also sold by + Apps2go. This is currently a FTP only download. + + + + + or + email addresses. + + + +

Contact for an either ELF or + a.out Motif 2.1 distribution for FreeBSD. + +

This distribution includes: + + OSF/Motif manager, xmbind, panner, wsm. + + Development kit with uil, mrm, xm, xmcxx, include and Imake + files. + + Static and dynamic libraries (specify ELF for use with FreeBSD + 3.0 and later; or a.out for use with FreeBSD 2.2.8 and eariler). + + Demonstration applets. + + Preformatted man pages. + + +

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 for an a.out Motif 2.0 distribution for FreeBSD.

This distribution includes: OSF/Motif manager, xmbind, panner, wsm. Development kit with uil, mrm, xm, xmcxx, include and Imake files. - Static and dynamic libraries. + Static and dynamic libraries (for use with FreeBSD 2.2.8 and + eariler). Demonstration applets. Preformatted man pages.

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. Where can I get CDE for FreeBSD?

Contact for a CDE 1.0.10 distribution for FreeBSD. This includes Motif 1.2.5, and can - be used with Motif 2.0. + be used with a.out Motif 2.0.

This is a unified CDROM distribution for FreeBSD and Linux. - Are there any commercial high-performance X servers? -

Yes, sells their +

Yes, and + 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). + + + + + or + email addresses. + + -

This high performance X Server offers easy configuration, support +

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 3.1 available. +

There is a free "compatibility demo" of version 5.0 available.

Xi Graphics also sells Motif and CDE for FreeBSD (see above). or email addresses. Are there any Database systems for FreeBSD?

Yes! Conetic Software Systems has ported their C/base and C/books database systems to FreeBSD 2.0.5 and higher, and Sleepycat Software is selling a commercially supported version of the DB database library. , . diff --git a/FAQ/x.sgml b/FAQ/x.sgml index 640c2cde48..9c8ed247e0 100644 --- a/FAQ/x.sgml +++ b/FAQ/x.sgml @@ -1,369 +1,369 @@ - + 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. +

You may also wish to investigate the Xaccel server. + See the section on or + 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 on boot?

There are two schools of thought on how to start . One school starts xdm from using the supplied example, while the other simply runs xdm from or from a /usr/local/etc/rc.d. 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, A previous version of the FAQ said to add the /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