|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T V
Length: 81195 (0x13d2b)
Types: TextFile
Names: »V«
└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
└─⟦fc9b38f02⟧ »DATA«
└─⟦8e9e227a9⟧
└─⟦this⟧
with Ftp_Profile;
package Rxi_Install is
------------------------------------------------------------------------------
-- Procedures for installing any RXI-based terminal type in a Rational
-- Environment and for installing the rxi program on a workstation or
-- file-server.
--
-- There are two general classes of RXI-based terminal types and the steps
-- in their installation may differ somewhat.
--
-- A) "Real" workstations. For example, you have a Sun workstation on
-- your desk and that is the workstation that you will be using as an
-- RXI "terminal" when working with an R1000. You would be using the
-- "real" terminal type called Xsun4_X11R5_Sparc (or one of the other
-- Sun variations).
--
-- B) "Parasite" terminals. For example, you have an NCD X Terminal
-- on your desk that keeps its font files and such on the file-system
-- of a nearby DEC Vax running VMS. To use the NCD as your RXI terminal
-- you would use the "parasite" terminal type called
-- Xncd_Vms5_4_Wollongong503 (or one of the other NCD/VMS variations).
--
-- There are three general installation scenarios to consider when installing
-- RXI:
--
-- 1) Your site will be dealing only with "real" workstation terminal types;
-- no "parasite" terminal types. (All R1000 usage will be directly from
-- actual workstations.) Simply pick one (or more) appropriate R1000
-- terminal type(s) and perform all installation steps (for each terminal
-- type).
--
-- 2) Your site will be dealing only with "parasite" terminal types; no "real"
-- workstation users. (All R1000 usage will be directly from X terminals.)
-- Simply pick one (or more) appropriate terminal type(s) and perform all
-- installation steps (for each terminal type).
--
-- 3) You have a mixture; some users will operate from workstations and some
-- from X terminals. If the users with workstations and the users with
-- X terminals use different file systems/servers then you can install
-- the various types of RXI independently; one type on each file system,
-- as in scenarios 1 & 2.
--
-- If more than one type of user uses the same file system then you may
-- want to perform all installation steps except for the workstation step
-- for all of the appropriate R1000 terminal types. Then perform the
-- workstation step for just one of the R1000 terminal types.
--
-- This would install one rxi terminal type on the file system as the
-- "default" terminal type but still allow users of all rxi terminal
-- types to function. Users of the non-default terminal types
-- would then invoke RXI using the "-rcg" switch or else have a
-- "*recognition:" resource in their X Defaults file. (See the RXI
-- documentation for a discussion on "terminal recognition" and how to
-- control it.)
--
-- The general installation steps for the mythical XYZ terminal type are:
--
-- 1) Execute the Rxi_Install.Machine_Editor_Data_Files procedure to install
-- the various XYZ keymap files on your R1000. This automatically
-- enables any product-specific commands contained in the new keymap(s).
-- Commands are enabled if the pertinent product is authorized for
-- this R1000.
--
-- This step also creates XYZ entries in the
-- !Machine.Editor_Data.Terminal_Types and Terminal_Recognition files.
--
-- This step is performed for all "real" and all "parasite" terminal
-- types that will be used to talk to the R1000. It installs the R1000
-- "key map" for this terminal type and it tells the R1000 how to perform
-- auto-recogniton of the new terminal type when a user logs into the
-- R1000.
--
-- This step is performed once for each rxi terminal type that your site
-- will be using, real or parasite.
--
-- 2) Execute the Rxi_Install.Workstation_Files procedure to transfer
-- a full set of RXI source and executable files to the workstation.
-- Follow the instructions attached to the installation procedure down
-- below when performing this step. This step copies, creates, and/or
-- installs the rxi program upon the workstation.
--
-- This step is usally performed once for a particular file system or
-- file server. RXI only needs to be installed once on a file system or
-- file server. It is installed with a system-wide default terminal
-- type corresponding to a single R1000 terminal type. Users with other
-- R1000 terminal types then use the "-rcg" switch (or the "*recognition:
-- resource) when invoking RXI.
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Terminal_Type - Supported terminal/keyboard types.
--
-- These are all of the supported variations for RXI. There are variations
-- in:
-- - workstation/X-terminal vendor
-- - keyboard
-- - X Windows vendor
-- - TCP/IP vendor
------------------------------------------------------------------------------
type Terminal_Type is
(
--\f
------------------------------------------------------------------------------
-- Workstation: Sun Microsystems ("Real" Workstation Terminal Types)
-- Operating System: SunOS 4.1.2
-- Window System: Sun's X11/NeWS V3.0
------------------------------------------------------------------------------
----No longer supported. 06/23/93
-- ----------------------------------------------------------------------
-- -- Sun's type 3 keyboard; shipped with Suns prior to 1989.
-- -- Has the keys: L1..L10 on the left side and R1..R15 on the right.
-- -- Function keys F1..F9 across the top.
-- ----------------------------------------------------------------------
--
-- Xnews3_V3_0, -- M680x0 architecture
-- Xnews3_V3_0_Sparc, -- Sparc architecture
----------------------------------------------------------------------
-- Sun's type 4 keyboard; shipped with Suns starting in 1989.
-- Stop/Again keys on the left side and a numeric keypad on the right.
-- Function keys F1..F12 across the top.
----------------------------------------------------------------------
----No longer supported. 06/23/93
-- Xnews4_V3_0, -- M680x0 architecture
Xnews4_V3_0_Sparc, -- Sparc architecture
----------------------------------------------------------------------
-- Sun's type 101A keyboard; shipped with Suns starting in 1992.
-- IBM PC look-alike.
----------------------------------------------------------------------
Xnews101_V3_0_Sparc, -- Sparc architecture
--\f
------------------------------------------------------------------------------
-- Workstation: Sun Microsystems ("Real" Workstation Terminal Types)
-- Operating System: SunOS 4.1.2
-- Window System: MIT's X11.R5
------------------------------------------------------------------------------
----No longer supported. 06/23/93
-- ----------------------------------------------------------------------
-- -- Sun's type 3 keyboard; shipped with Suns prior to 1989.
-- -- Has the keys: L1..L10 on the left side and R1..R15 on the right.
-- -- Function keys F1..F9 across the top.
-- ----------------------------------------------------------------------
--
-- Xsun3_X11r5, -- M680x0 architecture
-- Xsun3_X11r5_Sparc, -- Sparc architecture
----------------------------------------------------------------------
-- Sun's type 4 keyboard; shipped with Suns starting in 1989.
-- Stop/Again keys on the left side and a numeric keypad on the right.
-- Function keys F1..F12 across the top.
----------------------------------------------------------------------
----No longer supported. 06/23/93
-- Xsun4_X11r5, -- M680x0 architecture
Xsun4_X11r5_Sparc, -- Sparc architecture
----------------------------------------------------------------------
-- Sun's type 101A keyboard; shipped with Suns starting in 1992.
-- IBM PC look-alike.
----------------------------------------------------------------------
Xsun101_X11r5_Sparc, -- Sparc architecture
--\f
------------------------------------------------------------------------------
-- Workstation: Macintosh ("Real" Workstation Terminal Types)
-- Operating System: AUX 4.0
-- Window System: AUX/R??? X-Windows ????
------------------------------------------------------------------------------
----------------------------------------------------------------------
-- Apple's ???? United States keyboard
----------------------------------------------------------------------
Xapus_Aux4_0,
--\f
------------------------------------------------------------------------------
-- Workstation: IBM RS/6000 ("Real" Workstation Terminal Types)
-- Operating System: AIX 3.1
-- Window System: AIX/R2 X-Windows 3.1
------------------------------------------------------------------------------
----------------------------------------------------------------------
-- IBM's R/6000 United States keyboard
----------------------------------------------------------------------
Xr6us_Aix3_1,
--\f
------------------------------------------------------------------------------
-- Workstation: DEC ("Real" Workstation Terminal Types)
-- Operating System: VMS 5.4
-- Window_System: DECwindows
------------------------------------------------------------------------------
----------------------------------------------------------------------
-- DEC's LK201 keyboard; United States configuration
----------------------------------------------------------------------
----No longer supported. 06/23/93
-- Xdecus_Vms5_4_Multinet203, -- TCP/IP software is Excelan MultiNet
-- -- release 2.0.3 Rev. D
Xdecus_Vms5_4_Wollongong502, -- TCP/IP software is Wollongong
-- WIN TCP/IP release 5.0.2
Xdecus_Vms5_4_Ultrixconnection13a,-- TCP/IP software is DEC
-- ULTRIXConnection TCP/IP
-- release 1.3A
--\f
------------------------------------------------------------------------------
-- Workstation: DEC ("Real" Workstation Terminal Types)
-- Operating System: Ultrix v4.1
-- Window_System: DECwindows
------------------------------------------------------------------------------
----------------------------------------------------------------------
-- DEC's LK201 keyboard; United States configuration
----------------------------------------------------------------------
Xultus_Ds_Ultrix4_1, -- DECstation Ultrix (MIPS architecture)
Xultus_Vs_Ultrix4_1, -- VAXstation Ultrix (VAX architecture)
--\f
------------------------------------------------------------------------------
-- Workstation: HP ("Real" Workstation Terminal Types)
-- Operating System: HP-UX 8.0
-- Window_System: X Window System
------------------------------------------------------------------------------
----------------------------------------------------------------------
-- HP's 46021A keyboard; United States configuration
----------------------------------------------------------------------
Xhp46021a_Hpux8_0,
--\f
----No longer supported. 06/23/93
-- ------------------------------------------------------------------------------
-- -- Workstation: Apollo ("Real" Workstation Terminal Types)
-- -- Operating System: Domain/OS SR10.2 (BSD Unix)
-- -- Window System: Domain/X11 V1.2
-- ------------------------------------------------------------------------------
--
-- ----------------------------------------------------------------------
-- -- Apollo's keyboard 3 (model 7121)
-- -- Has arrows on the left, numbers on the right, and F0..F9 across the
-- -- top.
-- ----------------------------------------------------------------------
--
-- Xapollo3_Sr10_2_Unix,
--
-- ----------------------------------------------------------------------
-- -- Apollo's keyboard 3 (Motif Compliant model nnnn)
-- -- Has arrows on the left, numbers on the right, and F0..F9 across the
-- -- top. Has Alt/Meta keys on either side of the space bar.
-- ----------------------------------------------------------------------
--
-- Xapollom_Sr10_2_Unix,
--\f
------------------------------------------------------------------------------
-- X Terminal: NCD ("Parasite" Non-Workstation Terminal Types)
-- Keyboard: NCD's United State Configuration
------------------------------------------------------------------------------
----------------------------------------------------------------------
-- Host Workstation: Sun Microsystems
-- Operating System: SunOS 4.1.2
-- Window System: Sun's X11/NeWS V3.0
----------------------------------------------------------------------
----No longer supported. 06/23/93
-- Xncd_Xnews_V3_0, -- M680x0 architectures
Xncd_Xnews_V3_0_Sparc, -- Sparc architecture
----------------------------------------------------------------------
-- Host Workstation: Sun Microsystems
-- Operating System: SunOS 4.1.2
-- Window System: MIT's X11.R5
----------------------------------------------------------------------
----No longer supported. 06/23/93
-- Xncd_Sun_X11r5, -- M680x0 architectures
Xncd_Sun_X11r5_Sparc, -- Sparc architecture
----------------------------------------------------------------------
-- Host Workstation: IBM RS/6000
-- Operating System: AIX 3.1
-- Window System: AIX/R2 X-Windows 3.1
----------------------------------------------------------------------
Xncd_Aix3_1,
----------------------------------------------------------------------
-- Host Workstation: DEC
-- Operating System: VMS 5.4
-- Window_System: DECwindows
----------------------------------------------------------------------
----No longer supported. 06/23/93
-- Xncd_Vms5_4_Multinet203, -- TCP/IP software is Excelan MultiNet
-- -- release 2.0.3 Rev. D
Xncd_Vms5_4_Wollongong502, -- TCP/IP software is Wollongong
-- WIN TCP/IP release 1.3A
Xncd_Vms5_4_Ultrixconnection13a, -- TCP/IP software is DEC
-- ULTRIXConnection TCP/IP
-- release 1.3A
----------------------------------------------------------------------
-- Host Workstation: DEC
-- Operating System: Ultrix 4.1
-- Window_System: DECwindows
----------------------------------------------------------------------
Xncd_Ds_Ultrix4_1, -- DECstation Ultrix (MIPS architecture)
Xncd_Vs_Ultrix4_1, -- DECstation Ultrix (VAX architecture)
----------------------------------------------------------------------
-- Host Workstation: HP
-- Operating System: HP-UX 8.0
-- Window_System: X Window System
----------------------------------------------------------------------
Xncd_Hpux8_0
----No longer supported. 06/23/93
-- ----------------------------------------------------------------------
-- -- Host Workstation: APOLLO
-- -- Operating System: SR10.2 (BSD Unix)
-- -- Window_System: Domain/X11 V1.2
-- ----------------------------------------------------------------------
--
-- Xncd_Sr10_2_Unix
);
--\f
procedure Machine_Editor_Data_Files
(Keyboard : Terminal_Type;
Suppress_Rxi_Files : Boolean := False;
Overrides : String := "foo=>FALSE,bar=>true");
------------------------------------------------------------------------------
-- Keyboard - Specifies the RXI-based terminal type being installed.
-- Suppress_Rxi_Files - Specifies TRUE if the RXI files are not to be
-- included in the installation; perhaps they are already there.
-- Overrides - Specifies any authorization parameters that you may
-- wish to use for overrides in the
-- Enable_Product_Keymaps step.
--
-- Used to perform two tasks in the !Machine.Editor_Data area on the local
-- R1000.
--
-- 1) Copies the appropriate files from the release area over to the local
-- !Machine.Editor_Data area. The files are:
--
-- - XYZ_Key_Names - defines the key names for the XYZ terminal type
-- - XYZ_Keys - defines the recognition sequences for the XYZ keys
-- - XYZ_Commands - defines the environmental keybindings for XYZ
-- - XYZ_User_Commands- users can Compilation.Parse this to obtain an "empty"
-- XYZ_Commands in their home area
--
-- and optionally :
--
-- - RXI_Key_Names - defines the key names for the generic RXI terminal
-- - RXI_Keys - defines the recognition sequences for the RXI keys
-- - RXI_Commands - defines the environmental keybindings for RXI
-- - RXI_User_Commands - users can Compilation.Parse this to obtain an "empty"
-- RXI_Commands in their home area
--
-- This command copies these files. If any of these files already exist in
-- !Machine.Editor_Data then they are replaced by the copy. The Key_Names
-- and Commands files will be promoted to Installed automatically.
-- The Enable_Product_Keymaps utility is used to "enable" all product
-- specific keybindings. They are enabled according to the product
-- authorizations in-effect at the time this procedure is executed.
--
-- 2) Installs a line like the following in the local !Machine.Editor_Data.
-- Terminal_Types file:
--
-- XYZ XRTERM 80 80
--
-- and one like this in the local !Machine.Editor_Data.Terminal_Recognition
-- file:
--
-- XYZ [[?1;nnnc
--
-- (the nnn is determined by the XYZ Release.Info.Keyboard_Id; (id*8+2)).
--
-- If either file does not currently exist then it is created.
-- If either file exists then the appropriate line is appended to the end of
-- the file.
--
-- This command only needs to be done one time for a particular terminal type
-- upon a particular R1000. No damage will result if it is performed more than
-- one time; it will however cause the repeated demotion and repromotion of any
-- units that refer to any XYZ_Key_Names that already exists and it will result
-- in unnecessary (and harmless) duplicate entries in the Terminal_Types and
-- Terminal_Recognition files.
--
-- Individual sites may wish to change the default screen size for different
-- terminal types as specified by the numeric values in the Terminal_Types
-- file.
------------------------------------------------------------------------------
--\f
procedure Workstation_Files
(Keyboard : Terminal_Type;
On_Machine : String := Ftp_Profile.Remote_Machine;
Username : String := Ftp_Profile.Username;
Password : String := Ftp_Profile.Password;
Account : String := Ftp_Profile.Account;
Rxi_Source_Directory : String := ">/src/x/mit/clients/rxi<");
------------------------------------------------------------------------------
-- Keyboard - Specifies the RXI-based terminal type being installed.
-- On_Machine - Specifies the name of the workstation
-- Username - Specifies a username valid on the workstation
-- Password - Specifies the password for the username
-- Account - Specifies the account to use on the workstation
-- Rxi_Source_Directory- Specifies the directory to contain the RXI C source
-- code
--
-- Used to install a full-source version of RXI on a workstation/file-server.
-- This can then be used to compile, link, and install rxi with full
-- customization using local shared-libraries (and local X Windows bug fixes).
------------------------------------------------------------------------------
--\f
----No longer supported. 06/23/93
-- ------------------------------------------------------------------------------
-- -- Installation using Apollo Domain/OS and Domain/X11 :
-- --
-- -- The steps involved in getting the rxi program running on a workstation/file-
-- -- server are (we assume that you are using a Unix shell and not a Domain/Aegis
-- -- shell):
-- --
-- -- 1) Create a source directory for the rxi program on the workstation/file-
-- -- server. For example, if program sources are usually kept in a
-- -- directory called /src then within this directory create a directory
-- -- called /src/rxi.
-- --
-- -- 2) Run the Rxi_Install.Workstaion_Files procedure; this gets the files copied
-- -- to the workstation/file-server from the R1000. eg.
-- --
-- -- Rxi_Install.Workstaion_Files
-- -- (Keyboard => Rxi_Install.XApollo3_Sr10_2_Unix,
-- -- On_Machine => "My_Machine",
-- -- Username => "MyName",
-- -- Password => "MyPassword",
-- -- Account => "",
-- -- Rxi_Source_Directory => "/src/rxi");
-- --
-- -- 3) Connect to the source directory on the workstation and do the command
-- -- "make restore". This unpacks rxi and makes it available for complete
-- -- installation. eg.
-- --
-- -- cd /src/rxi
-- -- make restore
-- --
-- -- 4) If this site has some or all of the optional licensed Rational products
-- -- then edit the RXI_Env_Menu file. It's format is that of a C source
-- -- file so it should look familiar. There is a #define line for each
-- -- licensed product. For each licensed product at this site, set the
-- -- corresponding #define to be equal to 1. This activates the rxi
-- -- Environment menu entries for that product.
-- --
-- -- 5) Edit the file called Makefile. A particular site may wish to change
-- -- the places where rxi, its fonts, and/or its man page are installed.
-- -- These can be changed by changing the definition of:
-- --
-- -- BINDIR - where the rxi program goes; this is the twin
-- -- to the xterm program;
-- -- usually /usr/bin/X11
-- -- XBINDIR - where the various Apollo-supplied X11 programs
-- -- can be found; we'll need them for the installation;
-- -- usually /usr/bin/X11
-- -- XAPPLOADDIR - where the default resource file goes;
-- -- usually /usr/lib/X11/app-defaults
-- -- FONTDIR - where the system-wide X11 misc. fonts live;
-- -- usually /usr/lib/X11/fonts/misc
-- -- MANDIR - where the system-wide "new" man pages live;
-- -- usually /usr/new/mann
-- --
-- -- 6) You now have three more choices. A) Install the Rational-supplied rxi
-- -- as-is, or, B) relink to use local (possibly shared) libraries, or C)
-- -- completely recompile and recreate rxi using all local definitions.
-- -- The supplied version of rxi should be able to execute on your system.
-- -- However, it will not use any shared libraries, nor will it incorporate
-- -- any local library fixes, extensions, or modifications that may exist.
-- --
-- -- 6a) If you wish to just use rxi as supplied then skip this step.
-- --
-- -- 6b) If you wish to simple relink rxi so that it uses local libraries
-- -- then do a "make relink" command and proceed to the next step.
-- --
-- -- 6c) If you wish to recreate rxi from scratch then do a "make clean" command
-- -- followed by a "make all".
-- --
-- -- 7) Turn yourself into "super-user" and do a "make install.all"; this will:
-- --
-- -- a) Install the rxi program, the RXI default resource file, and any
-- -- support programs needed by RXI users. (The command "make install"
-- -- performs just this step.)
-- --
-- -- b) Install the rxi man page. (The command "make install.man" performs
-- -- just this step.)
-- --
-- -- c) Install the rxi terminfo description. This allows terminfo-using
-- -- programs (such as vi) to operate within an rxi window. (The
-- -- command "make install.terminfo" performs just this step.)
-- --
-- -- d) Compile the various fonts (fixed-*.bdf into the $(FONTDIR)
-- -- directory. These are the normal and bold-fase fonts used by rxi.
-- -- (The command "make install.fonts" performs just this step.)
-- --
-- -- Some sites may not want to use the Rational supplied fonts. They can
-- -- skip the install.man and install.fonts steps if they wish. They will
-- -- want to edit the RXI.Xdefaults file to change the names of the default
-- -- rxi fonts.
-- --
-- -- Some sites may not have the "man" pages installed and they can skip
-- -- the install.man step.
-- --
-- -- 8) Run rxi and decide whether or not the default font is too small.
-- -- Some Apollo displays have a very small pixel size. This can make the
-- -- default font too small for many users. RXI comes with several different
-- -- fonts. They are:
-- --
-- -- fixed-screen-{r,b}-11 - default font - smallest "thin" font
-- -- fixed-screen-{r,b}-12
-- -- fixed-screen-{r,b}-13
-- -- fixed-screen-{r,b}-14 - largest "thin" font - 1 pixel line thickness
-- -- fixed-screen-{wr,wb}-15 - smallest "thick" font - > 1 pixel thickness
-- -- fixed-screen-{wr,wb}-16
-- -- fixed-screen-{wr,wb}-17 - largest "thick" font
-- -- fixed-screen-{wr,wb}-22 - largest "thick" font
-- --
-- -- You can try out the different fonts with command lines like these;
-- -- restart your X server or use the xset command before trying this:
-- --
-- -- shell> xset fp rehash # Tell server to read new RXI fonts.
-- -- shell> rxi -fn fixed-screen-r-13 -fb fixed-screen-b-13 &
-- -- shell> rxi -fn fixed-screen-wr-15 -fb fixed-screen-wb-15 &
-- --
-- -- Always use matching normal (-fn) and bold (-fb) fonts or your rxi
-- -- window may be unreadable when connected to an R1000.
-- --
-- -- If you decide to change the system-wide default font then edit the
-- -- RXI.Xdefaults file. Change the "*font:" and "*boldFont:" lines to
-- -- reference the new font. You may also want to change then
-- -- "*menu.menuFont:" line if you find the menus to be unreadable as well.
-- -- Then do a "make install" to install the new system-wide defaults.
-- --
-- --
-- ------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using SunOS with MIT X11.R5 :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Pick an RXI terminal type to install.
--
-- If all of the Sun workstations that will be using RXI to connect to
-- R1000's have the Type 4 keyboard then install the XSun4_X11R5_Sparc.
-- If they all have the new Type 101A keyboard then install the
-- XSun101_X11R5_Sparc terminal type.
--
-- If you will have a mixture of keyboard types, that will all be using
-- the same installed binary executable for RXI, you will have to do one
-- of two things. Either install RXI as, primarily, an XSun4 terminal
-- type or as an XSun101 terminal type.
--
-- If you install RXI as an XSun4 then:
-- - Type 4 keyboard users do nothing extra.
-- - Type 101A keyboard users should edit their ~/.Xdefaults file to
-- contain a line that looks like this: "RXI*recognition:xsun101".
--
-- If you install RXI as an XSun101 then:
-- - Type 4 keyboard users should edit their ~/.Xdefaults file to add
-- a line that looks like this: "RXI*recognition:xsun4".
-- - Type 101A keyboard users do nothing extra.
--
-- The line "RXI*recognition:xsun101" or "RXI*recognition:xsun4" tells
-- RXI that when an R1000 asks the question "What type of terminal are
-- you?", it should answer "xsun101" or "xsun4". RXI is built with a
-- default answer that is determined by the Rxi_Install.XSun?_X11R?_Sparc
-- terminal type that you chose to install. This is a way to override
-- that default.
--
-- Note: If the Type 4 keyboards are using one file server and the Type
-- 101A keyboards are using another, you can simply install RXI as an
-- XSun101 on the one server and as an XSun4 on the other server. Treat
-- the two servers as two separate RXI installations as shown above. The
-- R1000's should all have both the XSun101 and the XSun4 Editor_Data files
-- installed.
--
-- NOTE to type 101A keyboard users:
--
-- MIT has made certain pairs of keys the same:
-- Escape and F1
-- F11 and Pause
-- You can make F1 into a real F1 key, and Pause into a real Pause key,
-- by placing this command into your .xinitrc file and restarting your
-- server, you can also issue this command manually. It will need to
-- be executed every time you restart your server:
--
-- xmodmap -e 'keycode 12 = F1' -e 'keycode 8 = Pause'
--
-- Also, the arrow keys at the bottom of the keyboard are undefined.
-- This can be fixed by use of these commands:
--
-- xmodmap -e 'keycode 27 = Up'
-- xmodmap -e 'keycode 31 = Left'
-- xmodmap -e 'keycode 34 = Down'
-- xmodmap -e 'keycode 35 = Right'
--
-- You may also wish to change the numeric keypad so that it always
-- transmits keypad numbers instead of sometimes numbers and sometimes
-- arrows:
--
-- xmodmap -e 'keycode 101 = KP_0'
-- xmodmap -e 'keycode 119 = KP_1'
-- xmodmap -e 'keycode 120 = KP_2'
-- xmodmap -e 'keycode 121 = KP_3'
-- xmodmap -e 'keycode 98 = KP_4'
-- xmodmap -e 'keycode 99 = KP_5'
-- xmodmap -e 'keycode 100 = KP_6'
-- xmodmap -e 'keycode 75 = KP_7'
-- xmodmap -e 'keycode 76 = KP_8'
-- xmodmap -e 'keycode 77 = KP_9'
--
-- 2) Create a source directory for the rxi program on the workstation/file-
-- server. For example, if the X11 sources from MIT are located in a
-- directory called /src/x then the suggested place for rxi would be
-- /src/x/mit/clients/rxi. If you would prefer to put the sources into
-- a different place, eg. /vendor/src/rxi, then that works as well.
-- The choice of location is entirely up to you.
--
-- 3) Run the Rxi_Install.Workstation_Files procedure; this gets the files
-- copied to the workstation/file-server from the R1000.
-- Use either the Rxi_Install.XSun4_X11R5_Sparc or XSun101_X11R5_Sparc
-- terminal types.
--
-- 4) Connect to the source directory on the workstation and do the command
-- "make restore". This unpacks rxi and makes it available for complete
-- installation.
--
-- 5) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file in the source area. It's format is
-- that of a C source file so it should look familiar. There is a #define
-- line for each licensed product. For each licensed product at this site,
-- set the corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 6) You may wish to hand-edit the Rational-supplied Makefile. At the top
-- of the Makefile is a list of the source, library, include, and font
-- paths that will be used during installation. If you wish to change
-- any of these default locations please do so now. The defaults are:
--
-- BINDIR - where rxi executables will reside;
-- eg. /usr/bin/X11
-- FONTDIR - where the server fonts reside;
-- eg. /usr/lib/X11/fonts
-- MANDIR - the man page directory for the rxi man page;
-- eg /usr/man/mann
-- XAPPLOADDIR - where application defaults files reside;
-- eg. /usr/lib/X11/app-defaults
-- DESTDIR - the default filesystem to use, eg. /usr, if you
-- have installed X11.R5 somewhere special then just
-- change DESTDIR, eg. DESTDIR=/vendor/X11R5
--
-- If you don't know what your system's standard XAPPLOADDIR is, or,
-- if you don't want to put RXI's files there, have each user define
-- one of the following environment variables in a manner similar
-- to what is shown here. These examples assume that the RXI
-- application defaults files have been placed into a directory named
-- /vendor/RXI/app-defaults
--
-- csh> setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/vendor/RXI/%T/%N%S
-- csh> setenv XAPPLRESDIR /usr/lib/X11:/vendor/RXI
--
-- These two environment variables accomplish basicly the same task.
--
-- If you don't know what directory to use for FONTDIR, run the xdumpfp
-- program in the RXI source area. It will give you a list of all of
-- the font directories being used by your X server.
--
-- If you want to place the RXI fonts into a special directory (eg. so
-- that they are not in one of the normal server directories), you
-- will have to notify the server of their location every time that
-- you log in. This is easily done using the xset program. For
-- example, if you put the RXI fonts into /vendor/RXI/fonts then you
-- would need this command in your .xinitrc startup file (.xinitrc is
-- one of the many names for startup files, see your System Administrator
-- or read your system documentation to determine the proper file name
-- for you to use):
--
-- xset fp+ /vendor/RXI/fonts
--
-- This command tells the server that additional fonts can be found
-- in this directory. If you cannot find the xset program, the RXI
-- source directory contains two programs that can be used to perform
-- this function. They are not normally installed so you will have to
-- copy them, by hand, to an appropriate bin directory. The command
-- that you would use to run these programs is this:
--
-- xsetfp `xdumpfp` /vendor/RXI/fonts/
--
-- (Please notice the extra '/' on the end of the path name.) This
-- command sets the server's font path to what it currently is, plus
-- the new RXI font area.
--
-- 7) You now have three choices.
-- A) Install the Rational-supplied rxi binary as-is, or,
-- B) relink to use local (possibly shared) libraries, or,
-- C) completely recompile and recreate rxi using all local definitions.
--
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
-- It will expect application resource files to exist in
-- /vendor/X11R5/lib/X11/app-defaults, which may not be appropriate for
-- your site (this can be overridded by use of the XFILESEARCHPATH
-- environment variable, see below).
--
-- 7a) If you wish to just use rxi as supplied then skip this step.
--
-- 7b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "make relink" command and proceed to the next step.
-- This assumes that your X libraries are in /usr/lib. If your X libraries
-- are somewhere else, eg. in /vendor/X11R5/lib, then define this
-- environment variable first, eg. using the csh shell:
--
-- SunOS> setenv LD_LIBRARY_PATH /vendor/X11R5/lib:/usr/lib
-- SunOS> make relink
--
-- 7c) If you wish to recreate rxi from scratch then do a "make clean" command
-- followed by a "make all". Set the LD_LIBRARY_PATH environment variable
-- if necessary (see above).
--
-- 8) Turn yourself into "super-user" and do a "make install.all"; this will:
--
-- a) Install the rxi program, the RXI default resource file, and any
-- support programs needed by RXI users.
-- (The command "make install" performs just this step.)
--
-- b) Install the rxi man page. (The command "make install.man"
-- performs just this step.)
--
-- c) Compiles the various fonts (fixed-screen-*.bdf and places them
-- into $(FONTDIR) directory so that the X server can find
-- them. These are the normal and bold-face fonts used by rxi.
-- (The command "make install.fonts" performs just this step.)
--
-- 9) Install the termcap definition for the rxi terminal type into your
-- local termcap database. There is a file called termcap in the rxi
-- source area that contains the termcap definition for rxi. (There is
-- also a terminfo file if you are using terminfo on your system.)
-- The termcap file is inserted into your local /etc/termcap file and
-- the terminfo file is used by issuing the command "tic terminfo".
--
-- 10)If the rxi files were installed in the /src/x/mit/clients/rxi hierarchy
-- as suggested in step #1 then you will probably wish to edit the
-- Makefile in the /src/x/mit/clients directory. Add the rxi
-- directory to the SUBDIRS=... list. This will cause rxi to be remade
-- and reinstalled whenever all MIT X11 clients are remade.
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using SunOS with X11/NeWS :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Pick an RXI terminal type to install.
--
-- If all of the Sun workstations that will be using RXI to connect to
-- R1000's have the Type 4 keyboard then install the XNews4_V3_0_Sparc
-- terminal type.
--
-- If all of the Sun workstations that will be using RXI to connect to
-- R1000's have the Type 101A (IBM PC) keyboard then install the
-- XNews101_V3_0_Sparc terminal type.
--
-- If you will have a mixture of Type 4 and Type 101A keyboards that will
-- all be using the same installed copy of RXI then you will have to
-- do one of two things. Either install RXI as an XNews4 terminal type or
-- as an XNews101 terminal type.
--
-- If you install RXI as an XNews4 then:
-- - Type 4 keyboard users do nothing extra.
-- - Type 101 keyboard users should edit their ~/.Xdefaults file to add
-- a line that looks like this: "RXI*recognition:xnews101".
--
-- If you install RXI as an XNews101 then:
-- - Type 4 keyboard users should edit their ~/.Xdefaults file to add
-- a line that looks like this: "RXI*recognition:xnews4".
-- - Type 101 keyboard users do nothing extra.
--
-- The line "RXI*recognition:xnews4" or "RXI*recognition:xnews101" tells
-- RXI that when an R1000 asks the question "What type of terminal are
-- you?", it should answer "xnews4" or "xnews101". RXI is built with a
-- default answer that is determined by the Rxi_Install.XNews?_V3_0_Sparc
-- terminal type that you chose to install. This is a way to override
-- that default.
--
-- Note: If the Type 4 keyboards are using one file server and the Type
-- 101A keyboards are using another then you can simply install RXI as an
-- xnews4 on the one server and as an xnews101 on the other server. Treat
-- the two servers as two separate RXI installations as shown above. The
-- R1000's should all have both the XNews4 and the XNews101 Editor_Data
-- files installed.
--
-- NOTE to R1000 users using the model 4 keyboard with X11/NeWS:
--
-- Sun has seen fit to make two keys on the keyboard "identical" by
-- default.
--
-- The keys "Help" and "F1" are defined, by the default X11/NeWS startup
-- script, to be the same X "key symbol". This means that the R1000
-- cannot tell the difference between a user typing what he thinks of as
-- "Help" and what he thinks of as "F1". This can be fixed by removing
-- the following command from your .xinitrc file:
--
-- xmodmap -e 'keysym F1 = Help'
--
-- If you have already started NeWS then you can repair this on-the-fly
-- with this command:
--
-- xmodmap -e 'keycode 12 = F1'
--
-- NOTE to R1000 users using the model 101A keyboard with X11/NeWS:
--
-- Sun has seen fit to deny 101A users a META key. Use this command
-- to see whether or not your configuration has a META key.
--
-- xmodmap -pm
--
-- You should see a line that looks something like this in the printout:
--
-- mod1 Meta_L (0x7f)
--
-- "mod1" is the META key for all X window applications. If your mod1
-- key is not set, go read Sun's documentation on how to set up your 101A
-- keyboard for "Sun Compatibility". If you have a file named
-- $OPENWINHOME/lib/Xmodmaprc.101A.sun on your system, the comments in
-- that file will tell you what to do.
--
-- Also, if you cannot find the xmodmap program, then the xallkeys
-- program shipped with RXI can be used similarly. It can be found in
-- the RXI source directory. It should already be compiled, just run it.
--
-- 2) Create a source directory for the rxi program on the workstation/file-
-- server. For example, if your various X11 application sources are
-- located in /src/x then a likely place would be /src/x/rxi.
--
-- 3) Run the Rxi_Install.Workstaion_Files procedure; this gets the files
-- copied to the workstation/file-server from the R1000.
--
-- 4) Connect to the source directory on the workstation and do the command
-- "make restore". This unpacks rxi and makes it available for complete
-- installation.
--
-- 5) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file. It's format is that of a C source
-- file so it should look familiar. There is a #define line for each
-- licensed product. For each licensed product at this site, set the
-- corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 6) Edit the file called Makefile. There are a series of "make" macros
-- at the beginning of the file. These macros tell the installation
-- script where the various pieces of RXI are to be installed. The
-- default values for these macros may be correct for your site but
-- they should be checked. The macros are:
--
-- OPENWIN - the "home" directory for Open Windows (X/NeWS);
-- eg. /vendor/openwin
-- BINDIR - where rxi executables will reside;
-- eg. /vendor/openwin/bin
-- FONTDIR - where the server fonts reside;
-- eg. /vendor/openwin/lib/fonts
-- MANDIR - the man page directory for the rxi man page;
-- eg /vendor//openwin/man/mann
--
-- The following directories may be changed but changes will only
-- actually take effect when rxi is recompiled by performing "make clean"
-- and "make all" steps.
--
-- XAPPLOADDIR - where application defaults files reside;
-- eg. /openwin/etc
--
-- An alternative to recompiling RXI is to have each user define
-- one of the following environment variables in a manner similar
-- to what is shown here. These examples assume that the RXI
-- application defaults files have been placed into a directory named
-- /vendor/RXI/app-defaults
--
-- csh> setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/vendor/RXI/%T/%N%S
-- csh> setenv XAPPLRESDIR /usr/lib/X11:/vendor/RXI
--
-- These two environment variables accomplish basicly the same task.
--
-- If you don't know what directory to use for FONTDIR, run the xdumpfp
-- program in the RXI source area. It will give you a list of all of
-- the font directories being used by your X server.
--
-- If you want to place the RXI fonts into a special directory (eg. so
-- that they are not in one of the normal server directories), you
-- will have to notify the server of their location every time that
-- you log in. This is easily done using the xset program. For
-- example, if you put the RXI fonts into /vendor/RXI/fonts then you
-- would need this command in your .xinitrc startup file (.xinitrc is
-- one of the many names for startup files, see your System Administrator
-- or read your system documentation to determine the proper file name
-- for you to use):
--
-- xset fp+ /vendor/RXI/fonts
--
-- This command tells the server that additional fonts can be found
-- in this directory. If you cannot find the xset program, the RXI
-- source directory contains two programs that can be used to perform
-- this function. They are not normally installed so you will have to
-- copy them, by hand, to an appropriate bin directory. The command
-- that you would use to run these programs is this:
--
-- xsetfp `xdumpfp` /vendor/RXI/fonts/
--
-- (Please notice the extra '/' on the end of the path name.) This
-- command sets the server's font path to what it currently is, plus
-- the new RXI font area.
--
-- 7) You now have three choices.
-- A) Install the Rational-supplied rxi binary executable as-is, or,
-- B) relink to use local (possibly shared) libraries, or,
-- C) completely recompile and recreate rxi using all local definitions.
--
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
--
-- 7a) If you wish to just use rxi as supplied then skip this step.
--
-- 7b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "make relink" command and proceed to the next step.
-- If you have loaded your libraries somewhere other than /usr/lib, then
-- you will need to define the LD_LIBRARY_PATH environment variable to
-- include that library. eg.
--
-- SunOS> setenv LD_LIBRARY_PATH /vendor/openwin/lib:/usr/lib
-- SunOS> make relink
--
-- 7c) If you wish to recreate rxi from scratch then do a "make clean" command
-- followed by a "make all". Set the LD_LIBRARY_PATH environment
-- variable if necessary (see above).
--
-- 8) Turn yourself into "super-user" and do a "make install.all"; this will:
--
-- a) Install the rxi program, the RXI default resource file, and any
-- support programs needed by RXI users.
-- (The command "make install" performs just this step.)
--
-- b) Install the rxi man page. (The command "make install.man"
-- performs just this step.)
--
-- c) Compile the various fonts (fixed-screen-*.bdf into the $(FONTDIR)
-- directory and then does a "bldfamily" there. These are the normal
-- and bold-face fonts used by rxi. (The command "make install.fonts"
-- performs just this step.)
--
-- 9) Install the termcap definition for the rxi terminal type into your
-- local termcap database. There is a file called termcap in the rxi
-- source area that contains the termcap definition for rxi. (There is
-- also a terminfo file if you are using terminfo on your system.)
-- The termcap file is inserted into your local /etc/termcap file and
-- the terminfo file is used by issuing the command "tic terminfo".
--
--
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using AIX and IBM X-Windows :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Create a source directory for the rxi program on the workstation/file-
-- server. For example, if program sources are usually kept in a
-- directory called /src then within this directory create a directory
-- called /src/rxi.
--
-- 2) Run the Rxi_Install.Workstaion_Files procedure; this gets the files copied
-- to the workstation/file-server from the R1000. eg.
--
-- Rxi_Install.Workstaion_Files
-- (Keyboard => Rxi_Install.Xr6us_Aix3_1,
-- On_Machine => "My_Machine",
-- Username => "MyName",
-- Password => "MyPassword",
-- Account => "",
-- Rxi_Source_Directory => "/src/rxi");
--
-- 3) Connect to the source directory on the workstation and do the command
-- "make restore". This unpacks rxi and makes it available for complete
-- installation. eg.
--
-- cd /src/rxi
-- make restore
--
-- 4) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file. It's format is that of a C source
-- file so it should look familiar. There is a #define line for each
-- licensed product. For each licensed product at this site, set the
-- corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 5) Edit the file called Makefile. A particular site may wish to change
-- the places where rxi, its fonts, and/or its man page are installed.
-- These can be changed by changing the definition of:
--
-- BINDIR - where the rxi shell script goes; this is the twin
-- to the aixterm script;
-- usually /usr/bin
-- X11BINDIR - where the real rxi goes; this is where most X11
-- executables go;
-- usually /usr/lpp/X11/bin
-- XAPPLOADDIR - where the default resource file goes;
-- usually /usr/lib/X11/app-defaults
-- FONTDIR - where the system-wide X11 fonts live;
-- usually /usr/lpp/fonts
-- MANDIR - where the system-wide "new" man pages live;
-- usually /usr/man/mann
--
-- If you don't know what your system's standard XAPPLOADDIR is, or,
-- if you don't want to put RXI's files there, have each user define
-- one of the following environment variables in a manner similar
-- to what is shown here. These examples assume that the RXI
-- application defaults files have been placed into a directory named
-- /vendor/RXI/app-defaults
--
-- csh> setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/vendor/RXI/%T/%N%S
-- csh> setenv XAPPLRESDIR /usr/lib/X11:/vendor/RXI
--
-- These two environment variables accomplish basicly the same task.
--
-- If you don't know what directory to use for FONTDIR, run the xdumpfp
-- program in the RXI source area. It will give you a list of all of
-- the font directories being used by your X server.
--
-- If you want to place the RXI fonts into a special directory (eg. so
-- that they are not in one of the normal server directories), you
-- will have to notify the server of their location every time that
-- you log in. This is easily done using the xset program. For
-- example, if you put the RXI fonts into /vendor/RXI/fonts then you
-- would need this command in your .xinitrc startup file (.xinitrc is
-- one of the many names for startup files, see your System Administrator
-- or read your system documentation to determine the proper file name
-- for you to use):
--
-- xset fp+ /vendor/RXI/fonts
--
-- This command tells the server that additional fonts can be found
-- in this directory. If you cannot find the xset program, the RXI
-- source directory contains two programs that can be used to perform
-- this function. They are not normally installed so you will have to
-- copy them, by hand, to an appropriate bin directory. The command
-- that you would use to run these programs is this:
--
-- xsetfp `xdumpfp` /vendor/RXI/fonts/
--
-- (Please notice the extra '/' on the end of the path name.) This
-- command sets the server's font path to what it currently is, plus
-- the new RXI font area.
--
-- 6) You now have three more choices. A) Install the Rational-supplied rxi
-- as-is, or, B) relink to use local (possibly shared) libraries, or C)
-- completely recompile and recreate rxi using all local definitions.
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
--
-- 6a) If you wish to just use rxi as supplied then skip this step.
--
-- 6b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "make relink" command and proceed to the next step.
--
-- 6c) If you wish to recreate rxi from scratch then do a "make clean" command
-- followed by a "make all".
--
-- 7) Turn yourself into "super-user" and do a "make install.all"; this will:
--
-- a) Install the rxi program, the RXI default resource file, and any
-- support programs needed by RXI users. (The command "make install"
-- performs just this step.)
--
-- b) Install the rxi man page. (The command "make install.man" performs
-- just this step.)
--
-- c) Install the rxi terminfo description. This allows terminfo-using
-- programs (such as vi) to operate within an rxi window. (The
-- command "make install.terminfo" performs just this step.)
--
-- d) Compile the various fonts (fixed-*.bdf into the $(FONTDIR)
-- directory. These are the normal and bold-fase fonts used by rxi.
-- (The command "make install.fonts" performs just this step.)
--
-- Some sites may not want to use the Rational supplied fonts. They can
-- skip the install.man and install.fonts steps if they wish. They will
-- want to edit the RXI.Xdefaults file to change the names of the default
-- rxi fonts.
--
-- Some sites may not have the optional licensed IBM "man" product and
-- they can skip the install.man step.
--
-- 8) Run rxi and decide whether or not the default font is too small.
-- Some IBM displays have a very small pixel size. This can make the
-- default font too small for many users. RXI comes with several different
-- fonts. They are:
--
-- fixed-screen-{r,b}-11 - default font - smallest "thin" font
-- fixed-screen-{r,b}-12
-- fixed-screen-{r,b}-13
-- fixed-screen-{r,b}-14 - largest "thin" font - 1 pixel line thickness
-- fixed-screen-{wr,wb}-15 - smallest "thick" font - > 1 pixel thickness
-- fixed-screen-{wr,wb}-16
-- fixed-screen-{wr,wb}-17
-- fixed-screen-{wr,wb}-22 - largest "thick" font
--
-- You can try out the different fonts with command lines like these,
-- restart your X server before trying this:
--
-- aix> rxi -fn fixed-screen-r-13 -fb fixed-screen-b-13 &
-- aix> rxi -fn fixed-screen-wr-15 -fb fixed-screen-wb-15 &
--
-- Always use matching normal (-fn) and bold (-fb) fonts or your rxi
-- window may be unreadable when connected to an R1000.
--
-- If you decide to change the system-wide default font then edit the
-- RXI.Xdefaults file. Change the "*font:" and "*boldFont:" lines to
-- reference the new font. You may also want to change then
-- "*menu.menuFont:" line if you find the menus to be unreadable as well.
-- Then do a "make install" to install the new system-wide defaults.
--
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using Vax VMS and DECwindows :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Create a source directory for the rxi program on the workstation/file-
-- server. For example, User:[Rxi].
--
-- 2) Run the Rxi_Install.Workstaion_Files procedure; this gets the files
-- copied to the workstation/file-server from the R1000. Specify the main
-- directory (eg. User:[Rxi]) as the destination of the transfer.
--
-- 3) Do a SET DEFAULT to the source directory on the workstation and do the
-- command "@makefile restore". This unpacks rxi and makes it available
-- for complete installation.
--
-- 4) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file. It's format is that of a C source
-- file so it should look familiar. There is a #define line for each
-- licensed product. For each licensed product at this site, set the
-- corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 5) Edit the MAKEFILE.COM file in the source area. Follow the editing
-- instructions at the front of the file. You will be asked to specify
-- the TCP/IP library to use (Wollongong WIN TCP/IP or DEC
-- ULTRIXConnection) and to specify the directories containing the library
-- include files and the library .OLB file. This is also the place where
-- you indicate the proper installation directories and protections for
-- the various pieces of the RXI system.
--
-- 6) You now have three more choices.
-- A) Install the Rational-supplied rxi binary executables as-is, or,
-- B) relink to use local (possibly shared) libraries, or,
-- C) completely recompile and recreate rxi using all local definitions.
--
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
--
-- 6a) If you wish to just use rxi as supplied then skip this step.
--
-- 6b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "@makefile relink" command and proceed to the next step.
--
-- 6c) If you wish to recreate rxi from scratch then do a "@makefile clean"
-- command followed by a "@makefile all".
--
-- 7) Enable your privileges; BYPASS should be sufficient. Do an
-- "@makefile install.all"; this will:
--
-- a) Installs the rxi program, its helper program rxi_detached, and the
-- RXI default resource file.
-- (The command "@makefile install" performs just this step.)
--
-- b) Install the rxi help library.
-- (The command "@makefile install.help" performs just this step.)
--
-- c) Compiles and installs the various fonts (fixed-screen-*.bdf in the
-- 'FONTDIR' directory (defaults to SYS$COMMON:[SYSFONT.DECW.
-- USER_75DPI]). These are the normal and bold-face fonts used by rxi.
-- (The command "@makefile install.fonts" performs just this step.)
--
-- 8) Edit the SYS$MANAGER:SYLOGIN.COM file and add a definition for a
-- system-wide symbol named RXI. eg.
--
-- $ RXI :== $ SYS$COMMON:[SYSEXE]RXI_DETACHED.EXE
--
-- This creates a system-wide foreign command that will run rxi as a
-- detached process. You will have to logout and log back in to
-- get it defined for yourself.
--
-- 9) Reboot any and all DECwindows workstations (or just the servers) that
-- need to use rxi. The reboot is necessary in order to cause the
-- servers to recognize the new rxi fonts.
--
-- 10) You may wish to do a PURGE on: SYS$SYSTEM:, DECW$SYSTEM_DEFAULTS:,
-- and SYS$COMMON:[SYSFONT...].
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using DEC Ultrix with DECwindows :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Create a source directory for the rxi program on the workstation/file-
-- server. For example, if most 3rd party X sources are located in a
-- directory called /src/x then the suggested place for rxi would be
-- /src/x/rxi. If you would prefer to put the sources into some
-- different place, eg. /vendor/sources/rxi, then that works as well.
--
-- 2) Run the Rxi_Install.Workstation_Files procedure; this gets the files
-- copied to the workstation/file-server from the R1000.
-- Use the Rxi_Install.XUltUS_Ultrix4_0 terminal type.
--
-- 3) Connect to the source directory on the workstation and do the command
-- "make restore". This unpacks rxi and makes it available for complete
-- installation.
--
-- 4) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file. It's format is that of a C source
-- file so it should look familiar. There is a #define line for each
-- licensed product. For each licensed product at this site, set the
-- corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 5) At the top of the file called Makefile is a list of the source, library,
-- include, and font paths that will be used during installation. If you
-- wish to change any of these default locations please do so now. The
-- defaults are:
--
-- BINDIR - where rxi executables will reside;
-- eg. /usr/bin/X11
-- FONTDIR - where the server fonts reside;
-- eg. /usr/lib/X11/fonts
-- MANDIR - the man page directory for the rxi man page;
-- eg /usr/man/mann
-- XAPPLOADDIR - where application defaults files reside;
-- eg. /usr/lib/X11/app-defaults
--
-- If you don't know what your system's standard XAPPLOADDIR is, or,
-- if you don't want to put RXI's files there, have each user define
-- one of the following environment variables in a manner similar
-- to what is shown here. These examples assume that the RXI
-- application defaults files have been placed into a directory named
-- /vendor/RXI/app-defaults
--
-- csh> setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/vendor/RXI/%T/%N%S
-- csh> setenv XAPPLRESDIR /usr/lib/X11:/vendor/RXI
--
-- These two environment variables accomplish basicly the same task.
--
-- If you don't know what directory to use for FONTDIR, run the xdumpfp
-- program in the RXI source area. It will give you a list of all of
-- the font directories being used by your X server.
--
-- If you want to place the RXI fonts into a special directory (eg. so
-- that they are not in one of the normal server directories), you
-- will have to notify the server of their location every time that
-- you log in. This is easily done using the xset program. For
-- example, if you put the RXI fonts into /vendor/RXI/fonts then you
-- would need this command in your .xinitrc startup file (.xinitrc is
-- one of the many names for startup files, see your System Administrator
-- or read your system documentation to determine the proper file name
-- for you to use):
--
-- xset fp+ /vendor/RXI/fonts
--
-- This command tells the server that additional fonts can be found
-- in this directory. If you cannot find the xset program, the RXI
-- source directory contains two programs that can be used to perform
-- this function. They are not normally installed so you will have to
-- copy them, by hand, to an appropriate bin directory. The command
-- that you would use to run these programs is this:
--
-- xsetfp `xdumpfp` /vendor/RXI/fonts/
--
-- (Please notice the extra '/' on the end of the path name.) This
-- command sets the server's font path to what it currently is, plus
-- the new RXI font area.
--
-- 6) You now have three choices. A) Install the Rational-supplied rxi
-- as-is, or, B) relink to use local (possibly shared) libraries, or C)
-- completely recompile and recreate rxi using all local definitions.
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
--
-- 6a) If you wish to just use rxi as supplied then skip this step.
--
-- 6b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "make relink" command and proceed to the next step.
--
-- 6c) If you wish to recreate rxi from scratch then do a "make clean" command
-- followed by a "make all".
--
-- 7) Turn yourself into "super-user" and do a "make install.all"; this will:
--
-- a) Install the rxi program, the RXI default resource file, and any
-- support programs needed by RXI users.
-- (The command "make install" performs just this step.)
--
-- b) Install the rxi man page. (The command "make install.man"
-- performs just this step.)
--
-- c) Compiles the various fonts (fixed-screen-*.bdf and places them
-- into $(FONTDIR) directory so that the X server can find
-- them. These are the normal and bold-face fonts used by rxi.
-- (The command "make install.fonts" performs just this step.)
--
-- 8) Install the termcap definition for the rxi terminal type into your
-- local termcap database. There is a file called termcap in the rxi
-- source area that contains the termcap definition for rxi. (There is
-- also a terminfo file if you are using terminfo on your system.)
-- The termcap file is inserted into your local /etc/termcap file and
-- the terminfo file is used by issuing the command "tic terminfo".
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using HP-UX and the X Window System :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Create a source directory for the rxi program on the workstation/file-
-- server. For example, if program sources are usually kept in a
-- directory called /src then within this directory create a directory
-- called /src/rxi.
--
-- 2) Run the Rxi_Install.Workstaion_Files procedure; this gets the files copied
-- to the workstation/file-server from the R1000. eg.
--
-- Rxi_Install.Workstaion_Files
-- (Keyboard => Rxi_Install.Xhp46021a_Hpux8_0,
-- On_Machine => "My_Machine",
-- Username => "MyName",
-- Password => "MyPassword",
-- Account => "",
-- Rxi_Source_Directory => "/src/rxi");
--
-- 3) Connect to the source directory on the workstation and do the command
-- "make restore". This unpacks rxi and makes it available for complete
-- installation. eg.
--
-- cd /src/rxi
-- make restore
--
-- 4) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file. It's format is that of a C source
-- file so it should look familiar. There is a #define line for each
-- licensed product. For each licensed product at this site, set the
-- corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 5) Edit the file called Makefile. A particular site may wish to change
-- the places where rxi, its fonts, and/or its man page are installed.
-- These can be changed by changing the definition of:
--
-- BINDIR - where the rxi executable goes; this is probably
-- where most X11 executables go;
-- usually /usr/bin/X11
-- HPBINDIR - where most X11 executables can be found so that we
-- can use them; usually /usr/bin/X11
-- FONTDIR - where the system-wide X11 fonts live;
-- usually /usr/lib/X11/fonts
-- MANDIR - where the system-wide "new" man pages live;
-- usually /usr/man/mann
--
-- If you don't know what directory to use for FONTDIR, run the xdumpfp
-- program in the RXI source area. It will give you a list of all of
-- the font directories being used by your X server.
--
-- If you want to place the RXI fonts into a special directory (eg. so
-- that they are not in one of the normal server directories), you
-- will have to notify the server of their location every time that
-- you log in. This is easily done using the xset program. For
-- example, if you put the RXI fonts into /vendor/RXI/fonts then you
-- would need this command in your .xinitrc startup file (.xinitrc is
-- one of the many names for startup files, see your System Administrator
-- or read your system documentation to determine the proper file name
-- for you to use):
--
-- xset fp+ /vendor/RXI/fonts
--
-- This command tells the server that additional fonts can be found
-- in this directory. If you cannot find the xset program, the RXI
-- source directory contains two programs that can be used to perform
-- this function. They are not normally installed so you will have to
-- copy them, by hand, to an appropriate bin directory. The command
-- that you would use to run these programs is this:
--
-- xsetfp `xdumpfp` /vendor/RXI/fonts/
--
-- (Please notice the extra '/' on the end of the path name.) This
-- command sets the server's font path to what it currently is, plus
-- the new RXI font area.
--
-- The following directories may be changed but changes will only
-- actually take effect when rxi is recompiled by performing "make clean"
-- and "make all" steps.
--
-- XAPPLOADDIR - where the default resource file goes;
-- usually /usr/lib/X11/app-defaults
--
-- An alternative to recompiling RXI is to have each user define
-- one of the following environment variables in a manner similar
-- to what is shown here. These examples assume that the RXI
-- application defaults files have been placed into a directory named
-- /vendor/RXI/app-defaults
--
-- csh> setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/vendor/RXI/%T/%N%S
-- csh> setenv XAPPLRESDIR /usr/lib/X11:/vendor/RXI
--
-- These two environment variables accomplish basicly the same task.
--
-- 6) You now have three more choices. A) Install the Rational-supplied rxi
-- as-is, or, B) relink to use local (possibly shared) libraries, or C)
-- completely recompile and recreate rxi using all local definitions.
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
--
-- 6a) If you wish to just use rxi as supplied then skip this step.
--
-- 6b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "make relink" command and proceed to the next step.
--
-- 6c) If you wish to recreate rxi from scratch then do a "make clean" command
-- followed by a "make all".
--
-- 7) Turn yourself into "super-user" and do a "make install.all"; this will:
--
-- a) Install the rxi program, the RXI default resource file, and any
-- support programs needed by RXI users. (The command "make install"
-- performs just this step.)
--
-- b) Install the rxi man page. (The command "make install.man" performs
-- just this step.)
--
-- c) Compile the various fonts (fixed-*.bdf into the $(FONTDIR)
-- directory. These are the normal and bold-fase fonts used by rxi.
-- (The command "make install.fonts" performs just this step.)
--
-- Some sites may not want to use the Rational supplied fonts. They can
-- skip the install.man and install.fonts steps if they wish. They will
-- want to edit the RXI.Xdefaults file to change the names of the default
-- rxi fonts.
--
------------------------------------------------------------------------------
--\f
------------------------------------------------------------------------------
-- Installation using Apple A/UX and the X Window System :
--
-- The steps involved in getting the rxi program running on a workstation/file-
-- server are:
--
-- 1) Create a source directory for the rxi program on the workstation/file-
-- server. For example, if program sources are usually kept in a
-- directory called /src then within this directory create a directory
-- called /src/rxi.
--
-- 2) Run the Rxi_Install.Workstaion_Files procedure; this gets the files copied
-- to the workstation/file-server from the R1000. eg.
--
-- Rxi_Install.Workstaion_Files
-- (Keyboard => Rxi_Install.Xapus_aux4_0,
-- On_Machine => "My_Machine",
-- Username => "MyName",
-- Password => "MyPassword",
-- Account => "",
-- Rxi_Source_Directory => "/src/rxi");
--
-- 3) Connect to the source directory on the workstation and do the command
-- "make restore". This unpacks rxi and makes it available for complete
-- installation. eg.
--
-- cd /src/rxi
-- make restore
--
-- 4) If this site has some or all of the optional licensed Rational products
-- then edit the RXI_Env_Menu file. It's format is that of a C source
-- file so it should look familiar. There is a #define line for each
-- licensed product. For each licensed product at this site, set the
-- corresponding #define to be equal to 1. This activates the rxi
-- Environment menu entries for that product.
--
-- 5) Edit the file called Makefile. A particular site may wish to change
-- the places where rxi, its fonts, and/or its man page are installed.
-- These can be changed by changing the definition of:
--
-- BINDIR - where the rxi executable goes; this is probably
-- where most X11 executables go;
-- usually /usr/bin/X11
-- AUXBINDIR - where the existing Apple X programs can be found;
-- this is probably the same as BINDIR
-- usually /usr/bin/X11
-- FONTDIR - where the system-wide X11 fonts live;
-- usually /usr/lib/X11/fonts
-- MANDIR - where the system-wide "new" man pages live;
-- usually /usr/catman/x_man/man1
--
-- The following directories may be changed but changes will only
-- actually take effect when rxi is recompiled by performing "make clean"
-- and "make all" steps.
--
-- XAPPLOADDIR - where the default resource file goes;
-- usually /usr/lib/X11/app-defaults
--
-- An alternative to recompiling RXI is to have each user define
-- one of the following environment variables in a manner similar
-- to what is shown here. These examples assume that the RXI
-- application defaults files have been placed into a directory named
-- /vendor/RXI/app-defaults
--
-- csh> setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/vendor/RXI/%T/%N%S
-- csh> setenv XAPPLRESDIR /usr/lib/X11:/vendor/RXI
--
-- These two environment variables accomplish basicly the same task.
--
-- If you don't know what directory to use for FONTDIR, run the xdumpfp
-- program in the RXI source area. It will give you a list of all of
-- the font directories being used by your X server.
--
-- If you want to place the RXI fonts into a special directory (eg. so
-- that they are not in one of the normal server directories), you
-- will have to notify the server of their location every time that
-- you log in. This is easily done using the xset program. For
-- example, if you put the RXI fonts into /vendor/RXI/fonts then you
-- would need this command in your .xinitrc startup file (.xinitrc is
-- one of the many names for startup files, see your System Administrator
-- or read your system documentation to determine the proper file name
-- for you to use):
--
-- xset fp+ /vendor/RXI/fonts
--
-- This command tells the server that additional fonts can be found
-- in this directory. If you cannot find the xset program, the RXI
-- source directory contains two programs that can be used to perform
-- this function. They are not normally installed so you will have to
-- copy them, by hand, to an appropriate bin directory. The command
-- that you would use to run these programs is this:
--
-- xsetfp `xdumpfp` /vendor/RXI/fonts/
--
-- (Please notice the extra '/' on the end of the path name.) This
-- command sets the server's font path to what it currently is, plus
-- the new RXI font area.
--
-- 6) You now have three more choices. A) Install the Rational-supplied rxi
-- as-is, or, B) relink to use local (possibly shared) libraries, or C)
-- completely recompile and recreate rxi using all local definitions.
-- The supplied version of rxi should be able to execute on your system.
-- However, it will not use any shared libraries, nor will it incorporate
-- any local library fixes, extensions, or modifications that may exist.
--
-- 6a) If you wish to just use rxi as supplied then skip this step.
--
-- 6b) If you wish to simple relink rxi so that it uses local libraries
-- then do a "make relink" command and proceed to the next step.
--
-- 6c) If you wish to recreate rxi from scratch then do a "make clean" command
-- followed by a "make all".
--
-- 7) Turn yourself into "super-user" and do a "make install.all"; this will:
--
-- a) Install the rxi program, the RXI default resource file, and any
-- support programs needed by RXI users. (The command "make install"
-- performs just this step.)
--
-- b) Install the rxi man page. (The command "make install.man" performs
-- just this step.)
--
-- c) Compile the various fonts (fixed-*.bdf into the $(FONTDIR)
-- directory. These are the normal and bold-fase fonts used by rxi.
-- (The command "make install.fonts" performs just this step.)
--
-- Some sites may not want to use the Rational supplied fonts. They can
-- skip the install.man and install.fonts steps if they wish. They will
-- want to edit the RXI.Xdefaults file to change the names of the default
-- rxi fonts.
--
------------------------------------------------------------------------------
--\f
end Rxi_Install;