The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

Поиск:  Каталог документации

4. Basic Host Configuration

Assuming that the required software is installed, we need to configure NFS to mount the fonts and operating system for our thin client workstations, configure XFree86 to provide remote display access, and configure our Xsession to deliver our choice of window manager to our client systems.

4.1. Configuring NFS

In order to load the configuration information, base system fonts, and OS image from the host machine using NFS, you need to provide read access to the directory or directories where that data is located. To do this, you will need to edit the /etc/exports file.

/etc/exports is an access control list which provides an entry for any directory that can be exported to an NFS client using the exportfs command. Configuring /etc/exports is easy.

To provide read access to any system which requests resources in /home/ncbridge, you would enter the following line into /etc/exports:

/home/ncbridge *(ro)

For better security, you can also specify access to individual client systems. To do this, simply enter:

/home/ncbridge (ro)
/home/ncbridge (ro)
/home/ncbridge (ro)

/etc/exports also provides facilities such as globbing for grouping like-named groups together. For example, to provide read-only access to similarly named clients:

/home/ncbridge client* (ro)

4.2. Configuring Xaccess

Xaccess is a file which XDM reads to determine which X Terminals can login and access software running on the host machine. An X Terminal sends a request to XDM which in turn runs an Xsetup script which sets up the login screen and displays the xlogin widget which handles authentication, and on successful authentication sets up a session between client applications on a host machine and an X Terminal.

The only configuration changes typically needed here involve setting up the access control to restrict global access to the xserver, and to add individual authorized hosts by IP address. Assuming that you are allowing multiple clients to log in, your configuration should look something like this:

#*                # Allow any X server can get a login window	  # Only allow specific systems to login.
!*  # Prevent all other systems from using XDM

4.3. Configuring Host Access

If you are not running terminals from a DNS server and/or are not allocating IP addresses using DHCP (as we are not), you will need to add an entry for each X Terminal in /etc/hosts on the Linux host machine.       # One system per line with optional 	    # parameters for lprhost and loghost

4.4. Configuring the X Font Server

The X Font Server (XFS) provides system fonts to X display servers. It is the only way to provide anti-aliased fonts such as freetype to most X Terminals.

On most Linux systems, xfs is started from a script in /etc/init.d, and/or on startup from one or more scripts, /etc/rc.d/init.d or in one of the run-level initialization scripts in /etc/rc[0-6].d. The most important thing to verify is that the X Terminal and the X Host are broadcasting and listening on the same port. Some X Terminals use the default XFS port, 7100, for other services, so XFS can be run on an unassigned port, such as 7102, in order to avoid a conflict.

4.5. Configuring the X Session

The Xsession file controls much of the information regarding a particular host machines X environment. Examples of things that might be set in this file include logging, choosing a desktop manager to run, and which keyboard mappings to use. These settings are highly environment specific, and for that reason will not be addressed in this document. Suffice it to say that you will want to decide whether to implement user-level or global preferences for the desktop environment, and that those configuration changes must be made in this file and in a .xsession file in the user's home directory.

Inferno Solutions
Hosting by

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру