| Due to the long version history of CSS,
attempts of setup to recover statistical report information from
the queue control file have been dropped. Queue recovery form the spool
directory works as usual. After successful execution of setup, the final configuration should be done: • Upgrading from a previous CSS version Upgrading with a cssws(U) server program running needs special attention. Since cssws may be invoked from /etc/inittab(4), it is not possible for setup to remove the file. Also killing the process would not help, since the repawn option would cause init(1) to immediately start another copy. The setup program will rename cssws to cssws.old. After the installation, use ps(1) to locate the process id (PID) of cssws and then kill(1) to stop it. If cssws is registered in your /etc/inittab, the new version will be started automatically. If you use another method to start the Windows server process (e.g. through /etc/rc), you can restart it manually. The cssws program is located in the CSS base directory (normally /usr/lib/css). • Deactivate original UNIX spooler In most systems CSS can coexist with the original UNIX spooler. If special preparation is needed, additional information will be supplied in an Installation Note. • Device Definition The basic control parameters will set up CSS to use /dev/lp as output device. With the dv-parameter in css.devices(C) any device- or disk file may be defined as output channel. If you decide to use /dev/lp and such a device does not exist, the major- and minor device numbers must be known to properly create this special file. If no system configuration manual is at hand, you may follow the procedure below: ls -l /dev/tty* example output: crw-rw-rw- 1 root 1, 0 Jan 16 13:27 /dev/tty
crw-rw-rw- 1 root 0, 1 Jan 18 08:24 /dev/tty2
crw-rw-rw- 1 root 0, 2 Sep 14 09:32 /dev/tty3
...
crw-rw-rw- 1 root 0, 7 Aug 30 17:11 /dev/tty8 The first number after the owner name (here root) is the major and the second is the minor device number. If as an example printer 1 shall be installed on the port /dev/tty8 (the same port you could install terminal 8). /etc/mknod /dev/lp c 0 7 # 0 = Major / 7 = Minor To prevent login messages, no getty(1) process should be active on this port. On Xenix and UNIX Version 7 this may be done by deleting the corresponding line in the file /etc/ttys (as an alternative you may set the first character to '0' (zero): 02tty8 Xenix systems feature the utility program disable(1) to just achieve this. On UNIX System V the corresponding getty-line in /etc/inittab has to be deleted or modified: t08:1:respawn:/etc/getty /dev/tty8 ... delete or change to: t08:1:off:/etc/getty /dev/tty8 ... To set special line attributes like baud rate, parity, number of stop bits and so on, the CSS utility setmode(U) may be used. • Name Conflicts If the setup program detects name conflicts, the existing lp- and lpr programs will be renamed to lp.unix and lpr.unix. You will however be prompted to choose different names for the CSS lpr program and thus preserve the original UNIX names. • Integrity To ensure a permanent, consistent operation the following line has to be added to the file /etc/rc: csa -S >/dev/null • Integration CSS is operational immediately after installation (using /dev/lp). To take advantage of all the features of your printers, the device database /etc/css.devices must be extended as described in css.devices(C). To ease this task, several examples of well known printer models are redefined. At least the standard form A has to be defined in the forms database /etc/css.forms. These parameters should be adjusted to the paper size most often used. Any changes become active after a successful compilation by csa -f. To install additional printers, please follow the procedure below: - Printer definition in /etc/css.devices:
e.g. 2|Printer 2:dv=/dev/tty5:# Device '/dev/tty5'
Compilation of the device database with csa -d
- Install the connection Printer « Device
If the device specified in the dv-parameter does not exist, the major- and minor device numbers of the port in question must be determined (as outlined above) and the special file has to be created with /etc/mknod(1). CSS will not be able to send output to a device, if e.g. cat /etc/passwd >/dev/tty5 fails. The user-interface program css(U) uses the terminal definitions of /etc/termcap(5). The environment variable TERM should hold the correct id and must be accessible (sh(1) / export). If the screens do not show correct, the definitions in /etc/termcap(5) must be checked. Please especially review the following values:
Table 2-1: Termcap Names
| bc |
Control sequence for 'Backspace', if not <Ctrl>-H. |
| cd |
Control sequence to clear the screen from the current
position to the bottom (clear to end of display). |
| ce |
Control sequence to clear the screen from the current
position to the end of the line. |
| CF |
Control sequence to turn the cursor off. |
| cl |
Control sequence to clear the screen and move the cursor to
the home position. |
| cm |
Control sequence for direct cursor movements (see termcap(5)). |
| CN |
Control sequence to turn the cursor on (if CO is not defined
/ RM-Cobol standard). |
| CO |
Control sequence to turn the cursor on (Microsoft standard). |
| co |
Number of characters per line (css(U)
requires a minimum of co#80). |
| do |
Control sequence to move the cursor one line down. |
| ho |
Control sequence to move the cursor to the home position. You
can also use the cm sequence for line 1, position 1. |
| li |
Number of screen lines (css(U)
requires at least li#15). |
| pc |
Padding character if different than 0x00. |
| se |
Control sequence for the attribute 'normal video' (delete all
attributes and set 'low intensity'). |
| so |
Control sequence for the attribute 'reverse, low intensity'. |
| ti |
Control sequence to initialize the terminal. |
| te |
Control sequence to invert initialization (reset). |
| up |
Control sequence to move the cursor one line up. |
| us |
Control sequence for the attribute 'underline'. |
| ws |
Control sequence for the attribute 'high intensity'. |
| ys |
Control sequence for the attribute 'blink'. |
Table 2-2: Termcap Line Graphics
| Gx |
Definition of line graphics control by Microsoft standard: |
| GS |
Graphic-Start (enter line graphic mode) |
| GE |
Graphic-End (exit line graphic mode) |
| GH |
horizontal char |
| GV |
vertical char |
| GD |
down tic |
| GU |
up tic |
| GL |
left tic |
| GR |
right tic |
| GC |
junction char |
| G1 |
upper right corner |
| G2 |
upper left corner |
| G3 |
lower left corner |
| G4 |
lower right corner |
| gx |
Definition of line graphics control by Unify standard (only
applicable if the definition following the Microsoft standard is not present): |
| gs |
Graphic-Start (enter line graphic mode) |
| gx |
Graphic-End (exit line graphic mode) |
| gk |
horizontal char |
| gj |
vertical char |
| gn |
down tic |
| go |
up tic |
| gl |
left tic |
| gm |
right tic |
| gi |
junction char |
| gg |
upper right corner |
| gf |
upper left corner |
| ge |
lower left corner |
| gh |
lower right corner |
To make the css(U) program to use
special line graphic characters you need to define the GS, GE
and GH termcap capabilities. The following table lists some of the
values of these capabilities for the most commonly used terminals:
| Terminal |
Definition |
| xterm |
:GS=^N:GE=^O:GH=q:\
if this does not render the desired results, try: |
| xterm |
:GS=\E(B\E)0\E(B\E)U^N:GE=\E(B\E)0^O:GH=q:\ |
| linux |
:GS=\E(0:GE=\E(B:GH=q:\ |
| ansi |
:GS=\E[12m:GE=\E[10m:GH=D:\ |
| vt100, vt220 |
:GS=\E(0:GE=\E(B:GH=q:\ |
Please note the line continuation character '\' at the end of each
definition. It is added here for your convenience and allows you to use
cut and paste. Make sure, that the pasted line is NOT the last line of
your termcap entry or if so, remove the trailing backslash.
|
