A Permanent X11 Installation

xmodmap sysmodmap fi if [ −f userresources ]; then xrdb −merge userresources fi if [ −f usermodmap ]; then xmodmap usermodmap fi start some nice programs twm xclock −geometry 50 × 50 − 1 + 1 xterm −geometry 80 × 50 + 494 + 51 xterm −geometry 80 × 20 + 494 − 0 The configuration file supposes the start of the tab window manager twm in the background and launches the clockand two xterm windows. All of the rules related to the .xsession file could be applied to the .xinitrc file; this is why, quite often, the .xinitrc file was simply linked to the .xsession. However, before linking two files, there are three points to be considered: The .xsession file is generally a shell script, but it can actually be any executable file. The .xinitrc file must be a Bourne shell script. 1. The .xsession file must be an executable file. The .xinitrc file does not have to be executable. 2. The .xsession script does not inherit the users login shell environment. The .xinitrc script inherits the environment of the shell from which the xinit was started. 3.

22.5.2 A Permanent X11 Installation

An X11 package today, this is primarily the CDE package is mostly a standard part of a UNIX installation. It means, upon the UNIX installation, X11 is more or less ready for use; of course, site−dependent X11 setting is always assumed, although default X setting works in most cases. For some UNIX platforms, the installation of the X11 package itself could even be skipped, especially if the platform supports the vendor−specific X flavor although, today, it is quite common to have a CDE package installed together with a vendor−specific X flavor, or customized in the vendor−specific way. For others, the X11 could still be treated as optional software. Nevertheless, an installation approach with the X11 is the same as any other software package, and must be configured appropriately for future system rebootings; it means a certain tribute should be paid to the X11 rc startup initialization. In the past, an X11 rc setting was a must; X11 used to be an optional software to be added later, tested, and then integrated into the overall UNIX system. The integration assumed a permanent X11 installation and a corresponding rc startup setting. X11 is started during the system startup through the corresponding rc initialization scripts, as is common for all UNIX daemons. On a typical BSD platform this is the etcrc.local file, while on a System V platform even the etcinittab table could be used. A brief survey of different UNIX flavors follows: 564 ls −li etcinit.d | grep dtlogin 203657 −rwxr−−r−− 4 root sys 2613 Jun 26 1998 dtlogin ls −li etcrc2.d | grep dtlogin 203657 −rwxr−−r−− 4 root sys 2613 Jun 26 1998 S99dtlogin ls −li etcrc0.d | grep dtlogin 203657 −rwxr−−r−− 4 root sys 2613 Jun 26 1998 K10dtlogin On HP−UX platform 9.0x, 10.10, 10.20, 10.30 … the start procedure is the same, except the other file name and locations are used, and symbolic links are implemented: ls −l sbininit.d | grep dtlogin −r−xr−xr−x 1 bin bin 3002 May 30 1998 dtlogin.rc ls −l sbinrc3.d | grep dtlogin lrwxr−xr−x 1 root sys 23 Jun 10 1998 S990dtlogin.rc − sbininit.d dtlogin.rc ls −l sbinrc2.d | grep dtlogin lrwxr−xr−x 1 root sys 23 Jun 10 1998 K100dtlogin.rc − sbininit.d dtlogin.rc • The HP flavor of X, VUE, is started through the etcinittab file: vue:34:respawn:usrvuebinvuerc • On SunOS 4.1.x the etcrc.local script is used; a typical sequence to start the xdm was: if [ −f usrbinX11wdm ]; then usrbinX11xdm; echo −n XDM fi • On IRIX platform etcinittab is used; here is an example with the xdm: xw:23:respawn:usrbinX11xdm −nodaemon • On AIX platform the etcrc.tcpip script is used; for example, an entry to start the xdm looked like: start usrbinX11xdm src_running •

22.5.3 A Few X−Related Commands