VUELOGIN(1X)

NAME

vuelogin — The HP VUE Login Manager.

SYNOPSIS

vuelogin [-config configuration_file] [-daemon] [-debug debug_level] [-error error_log_file] [-nodaemon] [-resources resource_file] [-server server_entry] [-session session_program]

DESCRIPTION

Vuelogin manages a collection of X displays, both local and possibly remote. The emergence of X terminals guided the design of several parts of this system, along with the development of the X Consortium standard XDMCP ( X Display Manager Control Protocol). Vuelogin provides services similar to those provided by init(1M), getty(1M) and login(1) on character terminals: prompting for login and password, authenticating the user, and running a “session.”

A “session” is defined by the lifetime of a particular process; in the traditional character-based terminal world, it is the user’s login shell process. In the HP VUE context, it is the HP VUE Session Manager. This is because in a windowing environment, a user’s login shell process does not necessarily have any terminal-like interface with which to connect.

If the HP VUE Session Manager is not used, the typical vuelogin substitute is either a window manager with an exit option, or a terminal emulator running a shell, where the lifetime of the terminal emulator is the lifetime of the shell process that it is running; thus reducing the X session to an emulation of the character-based terminal session.

When the session is terminated, vuelogin resets the X server and (optionally) restarts the whole process.

Because vuelogin provides the first interface that users see, it is designed to be simple to use and easy to customize to the needs of a particular site.

OPTIONS

All options, except -config, specify values that can also be specified in the configuration file as resources. Typically, customization is done via the configuration file rather than command line options. The options are most useful for debugging and one-shot tests.

-config configuration_file
Specifies a resource file that specifies the remaining configuration parameters. If no file is specified and the file /usr/lib/X11/vue/Vuelogin/Xconfig exists, vuelogin uses it.

-daemon
Specifies “true” as the value for the daemonMode resource. This makes vuelogin close all file descriptors, disassociate the controlling terminal and put itself in the background when it first starts up (just like the host of other daemons).

-debug debug_level
Specifies the numeric value for the debugLevel resource. A non-zero value causes vuelogin to print piles of debugging statements to the terminal; it also disables the daemonMode resource, forcing vuelogin to run synchronously.

-error error_log_file
Specifies the value for the errorLogFile resource. This file contains errors from vuelogin as well as anything written to stderr by the various scripts and programs run during the progress of the session.

-nodaemon
Specifies “false” as the value for the daemonMode resource.

-resources resource_file
Specifies the value for the resources resource. This file is loaded using xrdb (1) to specify configuration parameters for the authentication screen.

-server server_entry
Specifies the value for the servers resource. See servers below for more detail.

-udpPort port_number
Specifies the value for the requestPort resource. This sets the port-number that vuelogin monitors for XDMCP requests. Since XDMCP uses the registered well-known udp port 177, this resource should probably not be changed except for debugging.

-session session_program
Specifies the value for the session resource. This indicates the program to run when the user has logged in as the session.

CONTROLLING THE SERVER

Vuelogin controls local servers using POSIX signals. SIGHUP is expected to reset the server, closing all client connections and performing other clean up duties. SIGTERM is expected to terminate the server. If these signals do not perform the expected actions, vuelogin does not perform properly.

To control remote servers not using XDMCP, vuelogin searches the window hierarchy on the display and uses the KillClient protocol request in an attempt to clean up the terminal for the next session. This may not actually kill all of the clients, since only those that have created windows are noticed. XDMCP provides a more sure mechanism; when vuelogin closes its initial connection, the session is over and the terminal is required to close all other connections.

CONTROLLING VUELOGIN

Vuelogin responds to two signals: SIGHUP and SIGTERM. When sent a SIGHUP, vuelogin rereads the configuration file and the file specified by the servers resource and determines whether entries have been added or removed. If a new entry has been added, vuelogin starts a session on the associated display. Entries that have been removed are disabled immediately, meaning that any session in progress is terminated without notice, and no new session is started.

When sent a SIGTERM, vuelogin terminates all sessions in progress and exits. This can be used when shutting down the system.

ENVIRONMENT

Vuelogin invokes the user’s session with the following default environment:

DISPLAYis set to the associated display name
EDITORis set to /usr/bin/vi
HOMEis set to the home directory of the user
LANGis set to the current NLS language (if any)
LOGNAMEis set to the user name
MAILis set to /usr/mail/$USER
PATHis set to the value of the userPath resource
USERis set to the user name
SHELLis set to the user’s default shell (from /etc/passwd)
TERMis set to hpterm
TZis set to the value of the timeZone resource
XAUTHORITYmay be set to an authority file

Three methods are available to modify or add to this list depending on the desired scope of the resulting environment variable.

The environment resource is available in the vuelogin configuration file to allow setting of environment variables on a global or per-display basis. Variables specified by this method are available to both the display’s X server process and the user’s session and override any default settings. The resource accepts a string of <name>=<value> pairs separated by at least one space or tab. The values specified must be constants because no shell is used to parse the string. See the RESOURCES section below for details on setting this resource. For example:

Vuelogin*environment: SB_DISPLAY_ADDR=0xB00000 \
WMSHMSPC=0x200000

Note: The environment variables LANG and TZ have their own dedicated resources in the configuration file and should not be set via environment. Environment variables that require processing by a shell or are dependent on the value of another environment variable can be specified in the startup script Xsession. These variables are loaded into the environment of all users on the display, but not to the X server process. They override any previous settings of the same variable. The Xsession script accepts ksh syntax for setting environment variables. For example.

MAIL=/usr/mail/$USER

Finally, personal environment variables can be set on a per-user basis in the script file $HOME/.vueprofile. Vuelogin accepts either sh, ksh, or csh syntax for the commands in this file. The commands should only be those that set environment variables, not any that perform terminal I/O, excepting tset(1) or stty(1). If the first line of .vueprofile is #!/bin/sh, #!/bin/ksh, or #!/bin/csh, vuelogin uses the appropriate shell to parse .vueprofile. Otherwise, the user’s default shell ($SHELL) is used.

INTERNATIONALIZATION

All labels and messages are localizable. The message catalog vuelogin.cat contains the localized representations of the default labels and messages. Vuelogin reads the appropriate message catalog indicated by the LANG environment variable and displays the localized strings. An option on the authentication screen allows the user to override the default language for the subseqent session. If the authentication screen has been localized for the selected language, it is redisplayed in that language; otherwise, it is displayed in the default language. In either case, the LANG environment variable is set appropriately for the resulting session.

A resource language is available in the vuelogin configuration file to change the default language for a display.

RESOURCES

The actions of vuelogin can be controlled through the use of various configuration files, which are in the X resource format. Some resources control the behavior of vuelogin in general, some can be specified for a particular display, and others control the appearance of the authentication screen. The general and display-specific resources are specified in the configuration file named by the -config command line option. All resources should be prepended with the application name Vuelogin.

Vuelogin General Resource Set
Name	Class	Type	Default
autoRescan	AutoRescan	Boolean	True
daemonMode	DaemonMode	Boolean	False
debugLevel	DebugLevel	Int	0
errorLogFile	ErrorLogFile	String	NULL
keyFile	KeyFile	String	/usr/lib/X11/vue/Vuelogin/Xkeys
lockPidFile	LockPidFile	Boolean	True
pidFile	PidFile	String	NULL
remoteAuthDir	RemoteAuthDir	String	/usr/lib/X11/vue/Vuelogin
removeDomainname	RemoveDomainname	Boolean	True
requestPort	RequestPort	Int	177
servers	Servers	String	:0 Local local /usr/bin/X11/X :0
timeZone	TimeZone	String	MST7MDT

The vuelogin general resources are not display-specific and are applied to all displays where appropriate.

autoRescan
This boolean controls whether vuelogin rescans the configuration file and server file after a session terminates and the files have changed. You can force vuelogin to reread these files by sending a SIGHUP to the main process.

daemonMode
Normally, vuelogin attempts to make itself into an unassociated daemon process. This is accomplished by forking and leaving the parent process to exit, then closing file descriptors and mangling the controlling terminal. This is inconvenient when attempting to debug vuelogin. Setting this resource to "false" disables daemonMode.

debugLevel
A non-zero value specified for this integer resource enables reams of debugging information to be printed. It also disables daemon mode, which redirects the information into the bit-bucket. Specifying a non-zero debug level also allows non-root users to run vuelogin, which is not normally useful.

errorLogFile
Error output is normally directed at the system console. To redirect it, set this resource to any file name. A method to send these messages to syslog should be developed for systems that support it; however, the wide variety of "standard" interfaces precludes any system-independent implementation. This file also contains any output directed to stderr by Xstartup, Xsession and Xreset, so it contains descriptions of problems in those scripts as well.

keyFile
XDM-AUTHENTICATION-1 style XDMCP authentication requires that a private key be shared between vuelogin and the terminal. This resource specifies the file containing those values. Each entry in the file consists of a display name and the shared key. By default, vuelogin does not include support for XDM-AUTHENTICATION-1 because it requires DES, which is not generally distributable.

lockPidFile
This is the resource that controls whether vuelogin uses file locking to prevent multiple logins.

pidFile
The filename specified is created to contain an ASCII representation of the process-id of the main vuelogin process. This is quite useful when reinitializing the system. Vuelogin also uses file locking to attempt to prevent more than one daemon running on the same machine.

remoteAuthDir
This is a directory name that vuelogin uses to temporarily store authorization files for displays using XDMCP.

removeDomainname
When computing the display name for XDMCP clients, the resolver typically creates a fully qualified host name for the terminal. As this is sometimes confusing, vuelogin removes the domain name portion of the host name if it is the same as the domain name for the local host when this variable is set.

requestPort
This indicates the UDP port number that vuelogin uses to listen for incoming XDMCP requests. Unless you need to debug the system, leave this with its default value.

servers
This resource either specifies a file name full of server entries, one per line (if the value starts with a slash), or a single server entry. Each entry indicates a display that should constantly be managed and that is not using XDMCP. Each entry consists of at least three parts: a display name, a display class, a display type, and (for local servers) a command line to start the server. A typical entry for local display number 0 is:

:0 Local local /usr/bin/X11/X :0

The display types are:

locala local display, i.e. one that has a server program to run
foreigna remote display, i.e. one that has no server program to run

The display name must be something that can be passed in the -display option to any X program. This string is used in the display-specific resources to specify the particular display, so be careful to match the names (e.g., use ":0 local /usr/bin/X11/X :0" instead of "localhost:0 local /usr/bin/X11/X :0" if your other resources are specified as "Vuelogin._0.session"). The display class portion is also used in the display-specific resources as the class portion of the resource. This is useful if you have a large collection of similar displays (a group of X terminals, for example) and want to set resources for groups of them. When using XDMCP, the display is required to specify the display class, so perhaps your X terminal documentation describes a reasonably standard display class string for your device.

timeZone
This resource specifies the local time zone for vuelogin. It is loaded into the environment of vuelogin as the value of the variable TZ and inherited by all subsequent sessions. Note: The TZ environment variable is often also set in the file /etc/profile for terminal based logins. The system administrator should ensure that the two settings are identical.

Vuelogin Display Resource Set
Name	Class	Type	Default
authorize	Authorize	Boolean	False
authName	AuthName	String	MIT-MAGIC-COOKIE-1
authFile	AuthFile	String	/usr/lib/X11/vue/Vuelogin/auth-server
cpp	Cpp	String	/lib/cpp
environment	Environment	String	NULL
failsafeClient	FailsafeClient	String	/usr/bin/X11/xterm
gettyLine	GettyLine	String	console
gettySpeed	GettySpeed	String	console
grabServer	GrabServer	Boolean	True
grabTimeout	GrabTimeout	Int	3 sec.
language	Language	String	NULL
openDelay	OpenDelay	Int	5 sec.
openRepeat	OpenRepeat	Int	5 sec.
openTimeout	OpenTimeout	Int	30 sec.
pingInterval	PingInterval	Int	5 min.
pingTimeout	PingTimeout	Int	5 min.
reset	Reset	String	NULL
resetForAuth	ResetForAuth	Boolen	False
resetSignal	Signal	Int	1 (SIGHUP)
resources	Resources	String	NULL
session	Session	String	NULL
startAttempts	StartAttempts	Int	4
startup	Startup	String	NULL
systemPath	SystemPath	String	/usr/bin/X11:/bin:/usr/bin:/etc
systemShell	SystemShell	String	/bin/sh
terminateServer	TerminateServer	Boolean	False
termSignal	Signal	Int	15 (SIGTERM)
userAuthDir	UserAuthDir	String	/tmp
userPath	UserPath	String	/usr/bin/X11:/bin:/usr/bin:/usr/contrib/bin:/usr/local/bin
xrdb	Xrdb	String	/usr/bin/X11/xrdb

vuelogin display resources can be specified for all displays or for a particular display. To specify a particular display, the display name is inserted into the resource name between “Vuelogin” and the final resource name segment. For example, Vuelogin.expo_0.startup is the name of the resource defining the startup shell file on the “expo:0” display. The resource manager separates the name of the resource from its value with colons, and separates resource name parts with dots, so vuelogin uses underscores for the dots and colons when generating the resource name. Resources can also be specified for a class of displays by inserting the class name instead of a display name. A display that is not managed by XDMCP can have its class affiliation specified in the file referenced by the servers resource. A display using XDMCP supplies its class affiliation as part of the XDMCP packet.

authorize
authorize is a boolean resource that controls whether vuelogin generates and uses authorization for the server connections. (See authName.)

authName
If authorize is used, authName specifies the type of authorization to be used. Currently, vuelogin supports only MIT-MAGIC-COOKIE-1 authorization, XDM-AUTHORIZATION-1 could be supported, but DES is not generally distributable. XDMCP connections state which authorization types are supported dynamically, so authName is ignored in this case. (See authorize.)

authFile
This file is used to communicate the authorization data from vuelogin to the server, using the -auth server command line option. It should be kept in a write-protected directory to prevent its erasure, which would disable the authorization mechanism in the server.

cppThis specifies the name of the C preprocessor that is used by xrdb.

environment
This resource can contain a set of <name>=<value> pairs separated by a space or tab. Each item is loaded into the environment of the server and session. See ENVIRONMENT for details.

failsafeClient
If the default session fails to execute, vuelogin falls back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had. (See The Xsession File below.)

gettyLine (See gettySpeed.)

gettySpeed
On local bitmaps, the user may choose a "No Windows" option via the login screen, which temporarily suspends the server and runs a standard login sequence (getty/login) on the bitmap. The user can then log in and perform non-X related tasks. When the user finishes and logs out, the server restarts, and the vuelogin screen is redisplayed. The gettyLine and gettySpeed resources are passed to the /etc/getty process to indicate the desired device for the login sequence. The default value for each is "console." Another typical value for gettyLine is ite[0-3]. See getty(1M) for details.

grabServer (See grabTimeout.)

grabTimeout
To eliminate obvious security shortcomings in the X protocol, vuelogin grabs the server and keyboard while reading the name and password. The grabServer resource specifies if the server should be held while the name and password is read. When FALSE, the server is ungrabbed after the keyboard grab succeeds; otherwise, the server is grabbed until just before the session begins. The grabTimeout resource specifies the maximum time vuelogin will wait for the grab to succeed. The grab may fail if some other client has the server grabbed, or possibly if the network latencies are very high. The grabTimeout resource has a default of 3 seconds; be cautious when using this resource, since a user can be deceived by a look-alike window on the display. If the grab fails, vuelogin kills and restarts the server (if possible) and session.

language
This resource specifies the default setting for the LANG environment variable. If the vuelogin screen is localized for that language, it is displayed appropriately; otherwise, it is displayed in the language "C". The user may temporarily override this setting via an option on the login screen. When the subsequent session terminates, the LANG variable reverts to this setting.

openDelay (See startAttempts.)

openRepeat (See startAttempts.)

openTimeout (See startAttempts.)

pingInterval (See pingTimeout.)

pingTimeout
To discover when remote displays disappear, vuelogin occasionally "pings" them, using an X connection and sending XSync requests. pingInterval specifies the time (in minutes) between successive ping attempts, and pingTimeout specifies the maximum wait time (in minutes) for the terminal to respond to the request. If the terminal does not respond, the session is terminated. Vuelogin does not ping local displays. Although it may seem harmless, it is undesirable when the workstation session is terminated as a result of the server hanging for NFS service and not responding to the ping.

resetThis specifies a program that is run (as root) after the session terminates. By default no program is run. The conventional name is Xreset. See The Xreset File below.

resetForAuth
The original implementation of authorization in the sample server reread the authorization file at server reset time, instead of when checking the initial connection. Since vuelogin generates the authorization information just before connecting to the display, an old server does not get current authorization information. This resource causes vuelogin to send SIGHUP to the server after setting up the file, causing an additional server reset to occur, during which time the new authorization information is read.

resetSignal
This resource specifies the signal to be sent to vuelogin to cause it to reread the configuration file and the file specified by the servers resource.

resources
This resource specifies the name of the file to be loaded by xrdb (1) as the resource data-base onto the root window of screen 0 of the display. This resource data base is loaded just before the authentication procedure is started, so it can control the appearance of the "login" window. See the section below on the authentication screen, which describes the various resources that are appropriate to place in this file. There is no default value for this resource, but the conventional name is /usr/lib/X11/vue/Vuelogin/Xresources.

session
This specifies the session to be executed (not running as root). By default, /usr/bin/X11/xterm is run. The conventional name is Xsession. See The Xsession File below.

startAttempts
Four numeric resources control the behavior of vuelogin when attempting to open reluctant servers: openDelay, openRepeat, openTimeout, and startAttempts. openDelay is the duration (in seconds) between successive attempts; openRepeat is the number of attempts to make; openTimeout is the amount of time to wait while actually attempting the opening (i.e., the maximum time spent in the connect (2) syscall); and startAttempts is the number of times the entire process occurs before giving up on the server. After openRepeat attempts have been made, or if openTimeout seconds elapse in any particular attempt, vuelogin terminates and restarts the server, attempting to connect again. This process is repeated startAttempts time, at which point the display is declared dead and disabled. (See openDelay, openRepeat, and openTimeout.)

startup
This specifies a program that is run (as root) after the authentication process succeeds. By default, no program is run. The conventional name for a file used here is Xstartup. See the Xstartup section below.

systemPath
Vuelogin sets the PATH environment variable for the startup and reset scripts to the value of this resource. Note the conspicuous absence of "." from this entry. This is a good practice to follow for root; it avoids many system penetration schemes.

systemShell
Vuelogin sets the SHELL environment variable for the startup and reset scripts to the value of this resource.

terminateServer
This boolean resource specifies whether the X server should be terminated when a session terminates (instead of resetting it). This option can be used when the server tends to grow without bound over time in order to limit the amount of time the server is run.

termSignal
This resource specifies the signal to be sent to vuelogin to cause it to terminate all sessions and exit.

userAuthDir
When vuelogin cannot write to the usual user authorization file ($HOME/.Xauthority), it creates a unique file name in this directory and points the environment variable XAUTHORITY at the created file.

userPath
Vuelogin sets the PATH environment variable for the session to this value. It should be a colon-separated list of directories; see sh(1) for a full description.

xrdbSpecifies the program used to load the resources.

AUTHENTICATION SCREEN RESOURCES

The authentication screen reads a name-password pair from the keyboard. As this is a Motif toolkit client, colors, fonts and some layout options can be controlled with resources. Resources for this screen should be put into the file named by the resources resource. The default logo on the authentication screen may be replaced with a bitmap of the user’s choice. The following resources are available in addition to the standard Motif set in order to control positioning of the logo and the drop shadow. The resources should be prefaced with the string Vuelogin*logo* when specified.

Logo Resource Set
Name	Class	Type	Default
bitmapFile	BitmapFile	String	NULL
dropShadowBackground	DropShadowBackground	Pixel	Black
dropShadowForeground	DropShadowForeground	Pixel	White
dropShadowBackgroundPixmap	DropShadowBackgroundPixmap	String	25_foreground
dropShadowThickness	DropShadowThickness	Int	400
verticalOffset	VerticalOffset	Int	20
x	X	Position	-1
y	X	Position	-1

bitmapFile
Specifies the absolute path name to the bitmap file to be used for the logo.

dropShadowBackground
Specifes the background color for the drop shadow.

dropShadowForeground
Specifes the foreground color for the drop shadow.

dropShadowBackgroundPixmap
Specifes the pixmap to be used for the drop shadow. This can either be a built-in Motif pixmap or the absolute path name to a bitmap to be used as the tile for the drop shadow.

dropShadowThickness
Specifes the thickness of the drop shadow in units of 100th_millimeters.

verticalOffset
Specifes the percentage of the logo to be positioned vertically off the main matte. By default the logo is centered horizontally and positioned vertically by this amount above the matte. This resource is ignored if y is specified.

xSpecifes the x origin for the logo in units of 100th_millimeters. This resource overrides the default horizontal centering of the logo.

ySpecifes the y origin for the logo in units of 100th_millimeters. This resource overrides the default vertical positioning of the logo.

SESSION STARTUP

Three files are provided to assist in session startup. They can be replaced by other mechanisms via vuelogin resources.

The Xstartup File

This file is typically a shell script. It is run as "root" and should be very careful about security. This is the place to put commands that mount users’ home directories from file servers, display the message of the day, or do other system-level functions on behalf of the user. Various environment variables are set for the use of this script:

DISPLAYis set to the associated display name
HOMEis set to the home directory of the user
PATHis set to the value of the systemPath resource
USERis set to the user name
SHELLis set to the value of the systemShell resource

No arguments of any kind are passed to the script. Vuelogin waits until this script exits before starting the user session. If the exit value of this script is non-zero, vuelogin discontinues the session immediately and starts another authentication cycle.

The Xsession File

This script reads in the user’s personal environment from $HOME/.vueprofile and then invokes the desired session manager. It is run with the permissions of the authorized user, and has several environment variables pre-set. See the ENVIRONMENT section for a list of the pre-set variables.

The Xreset File

Symmetrical with Xstartup, this script is run after the user session has terminated. Run as root, it should probably contain commands that undo the effects of commands in Xstartup, such as unmounting directories from file servers. The collection of environment variables that were passed to Xstartup are also given to Xreset.

TYPICAL USAGE

Vuelogin is designed to operate in a wide variety of environments. The following setup is a good place to start, but may not be "typical" in many environments.

First off, the vuelogin configuration file should be set up. A good thing to do is to make a directory (ex. /usr/lib/X11/vue/Vuelogin) that contains all of the relevant files. Here is a typical configuration file, which could be named Xconfig :

Vuelogin.servers:/usr/lib/X11/vue/Vuelogin/Xservers
Vuelogin.errorLogFile: /usr/lib/X11/vue/Vuelogin/Xerrors
Vuelogin.pidFile:/usr/lib/X11/vue/Vuelogin/Xpid
Vuelogin*resources:/usr/lib/X11/vue/Vuelogin/Xresources
Vuelogin*session:/usr/lib/X11/vue/Vuelogin/Xsession

As you can see, this file simply contains references to other files. Note that some of the resources are specified with “*” separating the components. These resources can be made unique for each different display, by replacing the “*” with the display-name. See RESOURCES earlier for a complete discussion.

The first file /usr/lib/X11/vue/Vuelogin/Xservers contains the list of displays to manage. Most workstations have only one display, numbered 0, so the file looks like this:

:0 Local local /usr/bin/X11/X :0

This keeps /usr/bin/X11/X running on this display and manage a continuous cycle of sessions.

The file /usr/lib/X11/vue/Vuelogin/Xerrors contains error messages from vuelogin and anything output to stderr by Xstartup, Xsession or Xreset. When you have trouble getting vuelogin working, check this file to see if vuelogin has any clues to the trouble. Xerrors can become quite large and should be trimmed periodically.

The next configuration entry, /usr/lib/X11/vue/Vuelogin/Xresources, is loaded onto the display as a resource database using xrdb (1). As the authentication screen reads this database before starting up, it usually contains parameters for that screen.

SOME OTHER POSSIBILITIES

You can also use vuelogin to run a single session at a time by specifying the server on the command line:

vuelogin -server ":0 HP-TVRX local /usr/bin/X11/X :0"

Or, you might have a file server and a collection of X terminals. The configuration for this could look identical to the sample above, except the Xservers file might look like:

extol:0 HP700X foreign
exalt:0 NCD-19 foreign
explode:0 NCR-TOWERVIEW3000 foreign

This directs vuelogin to manage sessions on all three of these terminals. See "Controlling Vuelogin" above for a description of using signals to enable and disable these terminals much like init(1M).

If you have an X terminal that supports the XDMCP protocol, an entry for that terminal in Xservers is not required. If you have a file server and all X terminals support XDMCP, then Xservers would contain no entries.

Configurations may contain combinations of local servers, X terminals without XDMCP, and X terminals with XDCMP.

COPYRIGHT

AUTHOR

Vuelogin is based on the MIT client XDM, authored by Keith Packard. Additional modifications were developed by Hewlett Packard.

ORIGIN

Hewlett-Packard Company ITO.

Museum

Related Articles