Lines Matching refs:to
34 "hvcs". The IBM hvcs provides a tty driver interface to allow Linux user
35 space applications access to the system consoles of logically partitioned
39 firmware interfaces to virtual terminal devices.
47 This driver was written to operate solely on IBM Power5 ppc64 hardware
48 though some care was taken to abstract the architecture dependent firmware
61 for 64 of these major/minor numbers by default to use for hvcs device node
71 The following menuconfig example demonstrates selecting to build this
83 The following menuconfig example demonstrates selecting to build this
112 to allow. This can always be changed by modifying the constant in the
115 NOTE: The length of time it takes to insmod the driver seems to be related
116 to the number of tty interfaces the registering driver requests.
118 In order to remove the driver module execute the following command:
122 The recommended method for installing hvcs as a module is to use depmod to
128 The modules.dep file indicates that hvcserver.ko needs to be inserted
129 before hvcs.ko and modprobe uses this file to smartly insert the modules in
132 The following modprobe command is used to remove hvcs and hvcserver in the
186 Given the example output above, to manually create a /dev/hvcs* node entry
194 Using mknod to manually create the device entries makes these device nodes
195 persistent. Once created they will exist prior to the driver insmod.
197 Attempting to connect an application to /dev/hvcs* prior to insertion of
198 the hvcs module will result in an error message similar to the following:
211 to provide real time console interaction with a Linux partition's console,
219 ANSI) and expect inbound data to take the form of one of these supported
227 act as a conduit for data transfer to and from the tty device. They do not
228 require inbound data to take the form of a particular terminal type, nor do
229 they cook outbound data to a particular terminal type.
231 In order to ensure proper functioning of console applications one must make
232 sure that once connected to a /dev/hvcs console that the console's $TERM
233 env variable is set to the exact terminal type of the terminal emulator
234 used to launch the interactive I/O application. If one is using xterm and
235 kermit to connect to /dev/hvcs0 when the console prompt becomes available
242 node. If this is not done, the next user to connect to the console will
247 is used to connect to each vty-server adapter. In order to determine which
249 attribute has been added to each vty-server sysfs entry. This entry is
250 called "index" and showing it reveals an integer that refers to the
251 /dev/hvcs* entry to use to connect to that device. For instance cating the
257 This index of '2' means that in order to connect to vty-server adapter
260 It should be noted that due to the system hotplug I/O capabilities of a
262 adapter is not guaranteed to remain the same across system reboots. Look
268 As a security feature to prevent the delivery of stale data to an
272 from a vty following output of data to the vty the vty adapter may not have
274 connection was severed to fetch the data from firmware before the fetch is
277 When hvcs is being used to serve consoles this behavior is not a huge issue
279 almost all data writes. When hvcs is being used as a tty conduit to tunnel
281 because the standard Linux behavior when cat'ing or dd'ing data to a device
282 is to open the tty, send the data, and then close the tty. If this driver
284 the vty-server and vty connection before the target vty has had a chance to
291 Due to this behavioral restriction disconnection of vty-servers from the
292 connected vty is a manual procedure using a write to a sysfs attribute
293 outlined below, on the other hand the initial vty-server connection to a
297 In order to terminate the connection between a vty-server and vty the
300 vty-server adapter. A zero means that the vty-server is not connected to a
303 Writing a '0' (zero) to the vterm_state attribute will disconnect the VTERM
306 read '0' or if any value other than '0' was written to the vterm_state
336 driver manages. Writing a '1' to the attribute triggers the update. An
391 adapter. The first vty partner corresponds to the first clc item, the
392 second vty partner to the second clc item, etc.
394 A vty-server can only be connected to a single vty at a time. The entry,
398 The current_vty can be changed by writing a valid partner clc to the entry
404 Changing the current_vty when a vty-server is already connected to a vty
418 1. The creator of the /dev/hvcs* nodes has the ability to restrict
419 the access of the device entries to certain users or groups. It
420 may be best to create a special hvcs group privilege for providing
421 access to system consoles.
424 suggested that the user connect to the console hosting partition
427 3. Make sure to exit the user session when done with a console or
435 A: You can use "screen" to directly connect to the /dev/hvcs* device and
438 for most terminal emulators to provide adequate character conversion from
439 term type "screen" to others. This means that curses based programs may
451 (vt320) before you and leave the session logged in. The best thing to do
452 is to export TERM to the terminal type of your terminal emulator when you
453 get the console. Additionally make sure to "exit" the console before you
458 Q: When I try to CONNECT kermit to an hvcs device I get:
461 A: Some other Power5 console mechanism has a connection to the vty and
462 isn't giving it up. You can try to force disconnect the consoles from the
464 Otherwise you have to hunt down the people who have console authority. It
467 Power5 systems to determine the many ways a system console can be held.
471 A: Another user may not have a connectivity method currently attached to a
473 vty-server connection established. They need to free this using the method
474 outlined in the section on "Disconnection" in order for others to connect
475 to the target vty.
479 A: The user profile you are using to execute kermit probably doesn't have
480 permissions to use the /dev/hvcs* device.
489 A: There is not a corresponding vty-server device that maps to an existing
493 Q: When I try to CONNECT kermit to an hvcs device I get:
494 "Sorry, write access to UUCP lockfile directory denied."
501 partition to provide the console for the install of a second Linux
504 A: Yes granted that your are connected to the /dev/hvcs* device using
508 Q: Can I connect to more than one partition's console at a time using this
512 configured for this partition and each must point to a disconnected vty.
518 been built into the kernel the hvcs drivers is configured to dynamically
522 Q: For some reason /dev/hvcs* doesn't map to the same vty-server adapter
525 A: Assignment of vty-server adapters to /dev/hvcs* entries is always done
526 in the order that the adapters are exposed. Due to hotplug capabilities of
531 slot between two other vty-server adapters. Refer to the section above
532 on how to determine which vty-server goes with which /dev/hvcs* node.
536 Q: Can I use /dev/hvcs* as a conduit to another partition and use a tty
541 In order to get a tty conduit working between the two partitions the HMC
551 Now a program on the target system can be configured to read or write to
552 /dev/hvc* and another program on the current partition can be configured to
553 read or write to /dev/hvcs*. Now you have a tty conduit between two
560 distribution company that provided your OS or by posting issues to the
565 This request is to provide a documented and searchable public exchange