HP Visualize J5000 HP Workstations - Graphics Administration Guide For Red Hat - Page 69

Running from init, init state 3, the following line must be added

Get HP Visualize J5000 - Workstation PDF manuals and user guides View all HP Visualize J5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 69 highlights

property RGB_BEST_MAP root ar property RGB_RED_MAP root ar property RGB_GREEN_MAP root ar property RGB_BLUE_MAP root ar property RGB_GRAY_MAP root ar # To let untrusted clients use the color management database created # by xcmsdb, include these lines. property XDCCC_LINEAR_RGB_CORRECTION root ar property XDCCC_LINEAR_RGB_MATRICES root ar property XDCCC_GRAY_SCREENWHITEPOINT root ar property XDCCC_GRAY_CORRECTION root ar # To let untrusted clients use the overlay visuals that many vendors # support, include this line. property SERVER_OVERLAY_VISUALS root ar # property names and explicit specification of error conditions property "property with spaces" 'property with "' aw er ed # Allow deletion of Woo-Hoo if window also has property OhBoy with value # ending in "son". Reads and writes will cause an error. property Woo-Hoo OhBoy = "*son" ad Running from init To run X directly from init, it is necessary to modify /etc/inittab and /etc/gettydefs. Detailed information on these files may be obtained from the inittab(4) and gettydefs(4) man pages. To run X from init on display 0, with a login xterm running on /dev/ttypf, in init state 3, the following line must be added to /etc/inittab: X0:3:respawn:env PATH=/bin:/usr/bin/X11:/usr/bin xinit -L ttyqf -- :0 To run X with a login hpterm, the following should be used instead: X0:3:respawn:env PATH=/bin:/usr/bin/X11:/usr/bin xinit hpterm =+1+1 -n login -L ttyqf -- :0 In addition, the following line must be added to /etc/gettydefs (this should be a single line): Xwindow# B9600 HUPCL PARENB CS7 # B9600 SANE PARENB CS7 ISTRIP IXANY TAB3 00#X login:#Xwindow There should not be a getty running against the display whenever X is run from xinit. Granting access The sample server implements a simplistic authorization protocol, MITMAGICCOOKIE-1 which uses data private to authorized clients and the server. This is a rather trivial scheme; if the client passes authorization data which is the same as the server has, it is allowed access. This scheme is inferior to host-based access control mechanisms in environments with unsecure networks as it allows any host to connect, given that it has discovered the private key. But in many environments, this level of security is better than the host-based scheme as it allows access control per-user instead of per-host. Graphics Administration Guide For Red Hat Linux 6.2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
property RGB_BEST_MAP
root
ar
property RGB_RED_MAP
root
ar
property RGB_GREEN_MAP
root
ar
property RGB_BLUE_MAP
root
ar
property RGB_GRAY_MAP
root ar
# To let untrusted clients use the color management database created
# by xcmsdb, include these lines.
property XDCCC_LINEAR_RGB_CORRECTION
root
ar
property XDCCC_LINEAR_RGB_MATRICES
root
ar
property XDCCC_GRAY_SCREENWHITEPOINT
root
ar
property XDCCC_GRAY_CORRECTION
root ar
# To let untrusted clients use the overlay visuals that many vendors
# support, include this line.
property SERVER_OVERLAY_VISUALS
root
ar
# property names and explicit specification of error conditions
property "property with spaces" 'property with "' aw er ed
# Allow deletion of Woo-Hoo if window also has property OhBoy with value
# ending in "son". Reads and writes will cause an error.
property Woo-Hoo OhBoy = "*son" ad
Running from
init
To run X directly from
init
, it is necessary to modify
/etc/inittab
and
/etc/gettydefs
. Detailed information on these files may be obtained from the
inittab
(4) and
gettydefs
(4) man pages.
To run X from
init
on display 0, with a login
xterm
running on
/dev/ttypf
, in
init state 3, the following line must be added to
/etc/inittab
:
X0:3:respawn:env PATH=/bin:/usr/bin/X11:/usr/bin xinit -L ttyqf -- :0
To run X with a login
hpterm
, the following should be used instead:
X0:3:respawn:env PATH=/bin:/usr/bin/X11:/usr/bin xinit hpterm =+1+1 -n
login -L ttyqf -- :0
In addition, the following line must be added to
/etc/gettydefs
(this should be a
single line):
Xwindow# B9600 HUPCL PARENB CS7 # B9600 SANE PARENB CS7 ISTRIP IXANY TAB3
00#X login:#Xwindow
There should not be a
getty
running against the display whenever X is run from
xinit
.
Granting access
The sample server implements a simplistic authorization protocol,
MIT-
MAGICCOOKIE-1
which uses data private to authorized clients and the server. This is a
rather trivial scheme; if the client passes authorization data which is the same as the
server has, it is allowed access. This scheme is inferior to host-based access control
mechanisms in environments with unsecure networks as it allows any host to connect,
given that it has discovered the private key. But in many environments, this level of
security is better than the host-based scheme as it allows access control per-user instead
of per-host.
Graphics Administration Guide For Red Hat Linux 6.2