<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Notes for running XFree86 on SVR4</TITLE>
</HEAD>
<BODY BGCOLOR="#efefef" TEXT="black" LINK="blue" VLINK="#551A8B" ALINK="red">

<A HREF="SVR4.html"><EM>Information for SVR4 Users</EM></A>
 <b>:</b> <EM>Notes for running XFree86 on SVR4</EM><BR>
<b>Previous:</b> <A HREF="SVR44.html"><EM>Notes for building XFree86 on SVR4</EM></A><BR>
<b>Next:</b> <A HREF="SVR46.html"><EM>Building non-core clients with SVR4</EM></A>


<HR NOSHADE>
  <H2><A NAME="5"></A>5. Notes for running XFree86 on SVR4</H2>
<p><b>NOTE:</b> 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.
<ol>
<li>For SVR4, you may also need to add <code>/usr/X11R6/lib</code> to your
<code>LD_LIBRARY_PATH</code>, but this is not required for running properly 
built clients.
</li>
<li>You may want to increase some kernel parameters (either by running
<code>idtune</code>, or editing <code>/etc/conf/cf.d/stune</code>, and 
rebuilding the kernel with <code>idbuild</code>):
<blockquote>
<code>[HS]FNOLIM         </code>hard/soft limit for number of open files<p><code>MAXUP              </code>max number of processes per user</p>
<p><code>ARG_MAX            </code>max length of an arg list</p>
<p><code>SHMMAX             </code>max size of shared memory segment(in bytes)</p>

</blockquote>
</li>
<li>Choose which mouse driver you will use.  For SVR4 the best choice
depends on which version you are using.  If you have a bus mouse then
Xqueue is probably the only option.  For a serial mouse the 
options are as follows:<p>
<dl>
<dt><b>Esix 4.0.3</b><dd><p>Xqueue works.  It is also possible to
use the standard asy driver directly,
but the mouse operation is "jerky".</p>

<dt><b>Microport SVR4 [34].1</b><dd><p>Xqueue works fine, and the asy driver
can also be used directly giving smooth
mouse operation.</p>
</dl>

To use Xqueue, set the <code>Protocol</code> to <code>Xqueue</code> in both the 
<code>Keyboard</code> and
<code>Pointer</code> sections of your <code>XF86Config</code> file, 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 `<code>touch /dev/gmse</code>' 
before
running it.  (Note that mouseadmin will need to be rerun after
rebuilding a kernel unless you add an appropriate entry to
<code>/etc/conf/node.d/gmse.</code>)</p>

<p><b>NOTE</b>: 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:
<blockquote><code>
<pre>
   Option "sw_cursor"
</pre>
</code></blockquote>

to the Device section of your XF86Config file.  The S3 server is the
only one known to not have this problem.</p>
<p>If you have problems with both Xqueue and your standard asy driver with
SVR4, then you should install SAS.  When using SAS, set up <code>XF86Config</code> as
you would for the standard driver.</p>
<p>SAS is available from ftp.physics.su.oz.au.  When using SAS for a
serial mouse, you will get smoother operation if you change 
<code>EVENT_TIME</code>
from 80 to 30 in <code>sas.h</code>.  A couple of details which aren't 
spelled out
in the SAS README are:</p>

<p>- An example of the line you should add to <code>/etc/ap/chan.ap</code> is:
<pre>
      MAJOR    0       255     ldterm ttcompat
</pre>

where <code>MAJOR</code> is replaced by the major number used for SAS 
devices.  To
determine what that is, check <code>/etc/conf/cf.d/mdevice</code> after 
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.</p>
<p>- The installation instructions omit the following:</p>
<p>
<blockquote>
3a) Disable the asy driver by either running `<code>kconfig</code>' or editing
<code>/etc/conf/sdevice.d/asy</code>.<p>3b) Rebuild the kernel by running <code>/etc/conf/bin/idbuild</code></p>

</blockquote>
</p>
</li>
<li>If you want to use xdm with SVR4, extract the files from the shar file
in <code>/usr/X11R6/lib/X11/etc/XdmConf.svr4</code> into a temporary 
directory.  The
<code>README</code> file tells where the individual files should be 
installed.  Be
sure to read through each file and make any site-specific changes that
you need.
<p><b>NOTE:</b> 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 <code>/etc/inittab</code>, remember to also change
<code>/etc/conf/cf.d/init.base</code> or you will lose the changes when you next
rebuild the kernel.</p>


</li>
<li>If you want to change the number of VTs available on SVR4, just edit the
file <code>/etc/default/workstations</code> and change the number there.  
The device
nodes will be created/deleted next time you reboot.
</li>
<li>The default local connection types have changed in X11R6.  Unix domain
sockets are no longer treated as a "local" connection type.  This means
that a client connecting to :0 will use not use a Unix socket for the
connection.  To use the Unix socket connection, the client must connect
to unix:0.
<p>The local connection types available are "<code>NAMED</code>" (named streams pipe),
"<code>PTS</code>" (old-stype USL streams pipe), "<code>SCO</code>" 
(SCO Xsight streams pipe), and
"<code>ISC</code>" (ISC streams pipe).  The <code>XLOCAL</code> 
environment variable can be used
to set which types of local connection should be used in order of
preference.  The default setting is <code>PTS:NAMED:ISC:SCO</code>.  It is
recommended that <code>NAMED</code> be used in most cases because it is 
faster than
the default <code>PTS</code>, and because using PTS can cause you to run out of
<code>/dev/pts/</code> devices (each client using PTS requires a 
<code>/dev/pts</code> device).
To set up the default local connection type, make sure that 
<code>XLOCAL</code> is
set and exported in your <code>.xinitrc</code> file 
(when using xinit or startx) or
your <code>/usr/X11R6/lib/xdm/Xsession</code> script (when using xdm).</p>


</li>
</ol>
</p>

 <HR NOSHADE>
<A HREF="SVR4.html"><EM>Information for SVR4 Users</EM></A>
 <b>:</b> <EM>Notes for running XFree86 on SVR4</EM><BR>
<b>Previous:</b> <A HREF="SVR44.html"><EM>Notes for building XFree86 on SVR4</EM></A><BR>
<b>Next:</b> <A HREF="SVR46.html"><EM>Building non-core clients with SVR4</EM></A>



</BODY>
</HTML>
