2 Installing the Binaries

1. You must be logged in as root to unpack the archives because several executables are set-user-id. Otherwise the server may abort if you unpack it as an ordinary user. You must also use a ``umask'' value of 022 because the X server requires special permissions.

    % su
    # umask 022
   

2. If you have 52Mb free in the /usr partition ``cd /usr'' and skip to no. 3. Otherwise, create a directory on another partition and sym link it into /usr:

    # cd /usr/local
    # mkdir X11R6
    # ln -s /usr/local/X11R6 /usr/X11R6
   

3. Unpack everything: If you are using sh (as root usually does):

    # for i in X311*.tgz; do
    #   tar -xzf $i
    # done
   

   Else, if you are using csh:

    % foreach i (X311*.tgz)
    %   tar -xzf $i
    % end
   

4. Create a symbolic link ``X'' that points to the server that matches your video card. The XF86_* man pages list which vga chip sets are supported by each server. For example, if you have an ET4000 based card you will use the XF86_SVGA server:

    # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X
   

First do numbers 1 and 2 above. Then unpack the required archives:

 # for i in bin fnts lib xicf; do
 #   tar -xzf  X311$i.tgz
 # done

Then unpack a server archive corresponding to your vga card. The server man pages, X11R6/man/man1/XF86_*, list the vga chip sets supported by each server. For example, if you have an ET4000 based card you will use the XF86_SVGA server:

 # tar -xzf X311SVGA.tgz
 # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X

Add /usr/X11R6/bin to the default path for sh in /etc/profile and for csh in /etc/csh.login if they are not already there:

 # echo 'set path = ($path /usr/X11R6/bin)' >>/etc/csh.login
 # echo 'PATH=$PATH:/usr/X11R6/bin' >>/etc/profile

Or make sure all who use X put /usr/X11R6/bin in their shell's ``path'' variable.

Next either reboot or invoke ldconfig as root to put the shared libraries in ld.so's cache:

 # ldconfig /usr/lib /usr/local/lib /usr/X11R6/lib

If you had already configured X11R6/lib/X11/xinit/xinitrc or X11R6/lib/X11/xdm/* omit the xinit-config or xdm-config archive or unpack it separately and merge in your customizations.

The fscl and f100 archives are optional and can be omitted if you are short on space. The optional link archive allows you to reconfigure and customize a X server binary. The optional prog archive is needed only for writing or compiling X applications. The optional pex archive contains pex clients and libraries for building 3D graphics applications.

NOTE: You don't need to uncompress the font files, but if you uncompress them anyway you must run mkfontdir in the corresponding font directory; otherwise your server will abort with the message ``could not open default font 'fixed'''.

If you are running a stock FreeBSD 1.1.5 system you can ignore the rest of this section. If not, make sure you have a spare virtual console which is running a login process (getty). First check how many virtual consoles you have:

 % dmesg|grep sc
 sc0 at 0x60-0x6f irq 1 on motherboard
 sc0: VGA color <8 virtual consoles>

Then check /etc/ttys to make sure there is at least one ttyv? devices which doesn't have a getty enabled. FreeBSD 1.1.5 has the first three ``on'' and the last ``off'' so that getty runs on only three:

 % grep ttyv /etc/ttys
 ttyv0  "/usr/libexec/getty Pc" cons25  on secure
 ttyv1  "/usr/libexec/getty Pc" cons25  on secure
 ttyv2  "/usr/libexec/getty Pc" cons25  on secure
 ttyv3  "/usr/libexec/getty Pc" cons25  off secure

If your kernel has least 4 VTs and only 3 gettys, this is fine. If not, either disable a getty in /etc/ttys by changing ``on'' to ``off'' or build another kernel with more VTs as described below.