This section provides information about how to manage serial devices and USB printers connected to a client.
Device links are created under the dev
directory. A link to each serial node is created in
dev/term
, and a link to each locally
attached printer is created in
dev/printers
.
Typical device links are:
/tmp/SUNWut/units/IEEE802.080020cf428a/dev/term/manufacturer_name
-67a
/tmp/SUNWut/units/IEEE802.080020cf428a/dev/printers/1608b-64
The device link for the first example is
manufacturer_name
-serial_number
index
,
where index
is an increasing
alphabetical character, starting at a
. If the
manufacturer name is not available, the vendor and product ID
numbers are used for the name of the device link.
Here is an example of the dev
directory
from a Sun Ray 3 Client, which has an onboard serial port.
# cd $UTDEVROOT/dev # pwd /tmp/SUNWut/units/IEEE802.002128587259/dev # ls term # cd $UTDEVROOT/dev/term # pwd /tmp/SUNWut/units/IEEE802.002128587259/dev/term # ls -l lrwxrwxrwx 1 root root 22 Jul 28 17:23 a -> ../../devices/serial:a
USB-to-serial adapters are not accessible through the generated device nodes in an Oracle Solaris or Oracle Linux session. You must use USB redirection in a Windows session to access a serial device connected through a USB-to-serial adapter.
In the devices
directory, device nodes are
created for each serial or printer port on an attached USB
device. The device nodes are created in the hub directory
corresponding to the hub to which they are attached. The nodes
are named as follows:
manufacturer_name
,model_name
@upstream_hub_port
If the USB device has multiple identical ports (for example, two
serial ports), the name is followed by
:
where
n
is a numerical
index, starting at n
1
.
The following example is a typical device node:
/tmp/SUNWut/units/IEEE802.MACID
/devices/usb@1/hub@1/manufacturer_name
,model_name
@3:1
Here are the definitions of the naming conventions.
Term | Definition |
---|---|
|
The |
|
The printer and terminal name in the Sun Ray
|
|
The printer and terminal name in the Sun Ray
|
Some device nodes are owned by the user whose session is active on the client, while others might be owned by root or by other users that had previously active sessions on the client. Device permissions, access controls and ownership rules are determined by the class of device. For serial devices, only the user whose session is active on the client or the superuser have permission to use the attached device. If no user has an active session, superuser owns the serial device nodes. This rule might not be applicable for other classes of USB devices connected to the client.
The following description of the behavior of USB devices when sessions are connected and disconnected from a client applies only to serial devices. Other device classes may have different semantics regarding ownership and device lease times.
Changing the active session on a client changes the ownership of the device nodes to the user associated with the new session. A session change occurs whenever a user inserts or removes a smart card from a client or logs into a session.
In a failover environment, you can use the utselect or utswitch command to change a session. A session change causes all devices currently open by a non-root user to be closed after 15 seconds. Any input to or output from any affected device results in an error. For a serial device node, if the original session is restored within 15 seconds, the ownership is not relinquished, and input and output continue uninterrupted.
Devices currently opened by the superuser, including normal printing, remain unaffected by a session change.
To use serial attached devices with a client, you must attach them to the internal serial ports or through a USB-to-serial adaptor. You must use USB redirection in a Windows session to access a serial device connected through a USB-to-serial adapter.
Symbolic links to the serial port device nodes are located under
$UTDEVROOT/dev/term
. Built-in ports are
named "a" or "b".
Serial ports become unowned during hotdesking, so you should make sure any serial port activity is stopped before removing your smart card or resetting the client.
All serial ports except port A on the Sun Ray 170 support full handshaking and standard UNIX semantics. Port A on the Sun Ray 170 has no hardware handshaking pins, so it can't be used when a hardware handshake is required.
This section provides instructions on how to setup PostScript and non-attached PostScript printers that are attached to the Sun Ray Client. For details on how to print from Windows while using the Windows connector, see Chapter 17, Windows Connector.
Sun Ray Software works with PostScript printers connected directly to a USB port on the Sun Ray Client. For non-PostScript printer support, refer to Section 15.4.6.3, “How to Set Up an Attached Non-PostScript Printer”.
The printer naming conventions in Sun Ray Software differ from those in an Oracle Solaris operating environment.
The lp
subsystem opens the device node as
superuser for each print request, so print jobs are not
affected by hotdesking.
Starting a print queue on a printer attached to a Sun Ray Client, either directly or through an adapter, is the same process as starting a print queue in Oracle Solaris.
On the Sun Ray Client where the printer is attached, log in to a new session as superuser (root).
To determine the MAC address of the Sun Ray Client, press Stop-N or Ctrl-Pause-N.
The alphanumeric string displayed below the connection icon is the MAC address.
To locate the Sun Ray Client, type:
# cd /tmp/SUNWut/units/*MAC_address
# pwd /tmp/SUNWut/units/IEEE802.MACID
The path to the extended MAC address for your particular Sun Ray Client is displayed.
Locate the port for the printer by typing:
# cd dev/printers # pwd /tmp/SUNWut/units/IEEE802.MACID
/dev/printers # lsprinter-node-name
In the directory, locate the printer node.
Add the new printer.
Start the Oracle Solaris Print Manager.
# /usr/sbin/printmgr &
Click OK to choose files for repository.
Go to Printer > New Attached Printer.
Type the following information:
Printer name:
printername
Description (optional)
Printer port
Printer make
Printer model
Choose Other to type the printer port path name. To locate the printer port, refer to Step 4.
Verify that the printer has been set up correctly.
# lpstat -d printername
Sun Ray Software works with PostScript printers connected directly to a USB port on the Sun Ray Client. For non-PostScript printer support, refer to Section 15.4.6.3, “How to Set Up an Attached Non-PostScript Printer”.
The lp
subsystem opens the device node as
superuser for each print request, so print jobs are not
affected by hotdesking.
The following generic instructions might vary slightly from one operating system implementation to another, but they should provide enough information to enable an administrator to set up basic printing services.
On the Sun Ray Client where the printer is attached, log in to a new session as superuser (root).
To determine the MAC address of the Sun Ray Client, press Stop-N or Ctrl-Pause-N.
The alphanumeric string displayed below the connection icon is the MAC address.
Locate the Sun Ray Client.
# cd /tmp/SUNWut/units/*MAC_address
# pwd /tmp/SUNWut/units/IEEE802.MACID
The path to the extended MAC address for your particular Sun Ray Client is displayed.
Locate the port for the printer.
# cd dev/printers # pwd /tmp/SUNWut/units/IEEE802.MACID
/dev/printers # lsprinter-node-name
In the directory, locate the printer node.
Use the Oracle Linux administration tools to set up the printer.
Choose Other so that you can provide the device node from Step 4.
Verify that the printer has been set up correctly.
# lpstat -d printername
Create a soft link to the Sun Ray printer node in
/dev/usb
For example, if the device node is
/tmp/SUNWut/units/IEEE802.
,
mac-address
/dev/printers/device_node
you would use the following command:
# ln -s /tmp/SUNWut/units/IEEE802.mac-address
/dev/printers/device_node
/dev/usb/sunray-printer
Use this soft link
(/dev/usb/sunray-printer
) as the
Device URI while creating the print queue.
Update /etc/cups/cupsd.conf
to set
the RunAsUser property to No.
Restart the cups daemon.
# /etc/init.d/cups restart
Printers that do not use PostScript, such as engineering plotters, are best supported by third-party software. Low-cost inkjet printers require third-party software such as the following:
Easy Software's ESP PrintPro, available from http://www.easysw.com
Ghostscript, available from http://www.ghostscript.com
Vividata PShop, available from http://www.vividata.com
Check with the vendors for pricing and the precise printer models supported.