This section discusses, in generic terms, the configurations needed to connect a generic X Terminal to a host system.
When an X Terminal is booted from a host on the network, it may either use bootp or rarp to determine IP and host addresses, or it may store those values locally in NVRAM on the terminal. The advantage to using bootp is that the host information and IP addresses may be stored centrally in a single configuration. An advantage to using the values locally on the client system is that it allows for a more fine-grained control over TCP/IP and host information.
Assuming that host and IP address information is properly configured for the X Terminal, step two in the boot process is for the X Terminal to load its operating system and core fonts. In order to do this, the client needs to know the full path to the OS image and system configurations and base fonts. It needs to have a boot method specified for fetching these files. On most systems, that is TFTP or NFS. Last, the X Terminal needs to know which will be managing the XDMCP communication ( e.g. the system from which client applications will be deployed). All of this information is stored in NVRAM on the X Terminal.
Step three in the boot process occurs when the X Terminal connects to the client machine. Most X Terminals can send a direct or indirect query to an XDMCP session manager on a network. In an indirect query, all available XDMCP session managers will respond and display a menu of possible hosts. In the case of a direct query, XDM on the host system runs the Xsetup script to set up the display for the login screen and provides the xlogin widget which requires a valid userid and password to login and start an XDMCP session.
Закладки на сайте
Проследить за страницей
Created 1996-2021 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру