NOTE: If you intend to use any of the accelerated servers, read section 10 and follow the instructions. Otherwise the X server will crash when exiting, restarting, or switching VTs.
LD_LIBRARY_PATH, but this is not required for running properly built clients.
idtune, or editing
/etc/conf/cf.d/stune, and rebuilding the kernel with
[HS]FNOLIMhard/soft limit for number of open files
MAXUPmax number of processes per user
ARG_MAXmax length of an arg list
SHMMAXmax size of shared memory segment(in bytes)
Xqueue works. It is also possible to use the standard asy driver directly, but the mouse operation is "jerky".
Xqueue works fine, and the asy driver can also be used directly giving smooth mouse operation.
Xqueuein both the
Pointersections of your
XF86Configfile, and You must have the mouse driver package installed, and must run mouseadmin to set it up for your mouse. If mouseadmin won't work try doing `
touch /dev/gmse' before running it. (Note that mouseadmin will need to be rerun after rebuilding a kernel unless you add an appropriate entry to
NOTE: Many of the accelerated server/drivers have problems when using a HW cursor and Xqueue together. If you have a serial mouse, you can work around this by not using Xqueue. Otherwise the only workaround is to disable the HW cursor. This is done by adding the line:
to the Device section of your XF86Config file. The S3 server is the only one known to not have this problem.
If you have problems with both Xqueue and your standard asy driver with
SVR4, then you should install SAS. When using SAS, set up
you would for the standard driver.
SAS is available from ftp.physics.su.oz.au. When using SAS for a
serial mouse, you will get smoother operation if you change
from 80 to 30 in
sas.h. A couple of details which aren't
in the SAS README are:
- An example of the line you should add to
MAJOR 0 255 ldterm ttcompatwhere
MAJORis replaced by the major number used for SAS devices. To determine what that is, check
/etc/conf/cf.d/mdeviceafter rebuilding the kernel. The major number is the sixth field in the line starting with `sas'. This file must be updated before rebooting with the new kernel.
- The installation instructions omit the following:
3a) Disable the asy driver by either running `
kconfig' or editing
3b) Rebuild the kernel by running
/usr/X11R6/lib/X11/etc/XdmConf.svr4into a temporary directory. The
READMEfile tells where the individual files should be installed. Be sure to read through each file and make any site-specific changes that you need.
NOTE: Some SVR4 versions (one example is Esix 4.0.3) have a default
inittab which runs `vtgetty' on the console. This does not work well
when starting xdm at boot time. The problem is that when you logout
from a vtgetty session it wants to close all the VTs -- including the
one xdm is using for the server. It is recommended that you use
`getty'. If you change
/etc/inittab, remember to also change
/etc/conf/cf.d/init.base or you will lose the changes when you next
rebuild the kernel.
/etc/default/workstationsand change the number there. The device nodes will be created/deleted next time you reboot.
The local connection types available are "
NAMED" (named streams pipe),
PTS" (old-stype USL streams pipe), "
(SCO Xsight streams pipe), and
ISC" (ISC streams pipe). The
environment variable can be used
to set which types of local connection should be used in order of
preference. The default setting is
PTS:NAMED:ISC:SCO. It is
NAMED be used in most cases because it is
PTS, and because using PTS can cause you to run out of
/dev/pts/ devices (each client using PTS requires a
To set up the default local connection type, make sure that
set and exported in your
(when using xinit or startx) or
/usr/X11R6/lib/xdm/Xsession script (when using xdm).