9 More Discussions You Might Find Interesting
1. IP Networking
Hi All,
I was told to perform analysis for IP change during a hardware refresh?
Does the IP change when a hardware refresh is performed?
if Yes, why? (5 Replies)
Discussion started by: visitsany
5 Replies
2. SCO
Hello
I'm trying to virtualize an instance of Sco Unix 5.0.5 in VirtualBox (called VM-A) , but sco I have problems set to launch with the new raid controller .
The physical machine has a raid controller adaptec (alad driver) but VirtualBox uses buslogic (blc driver)
What ... (3 Replies)
Discussion started by: flako
3 Replies
3. Hardware
I am now on Kernel 2.6.32-26
For me 16x CD write speed is okay.
I have old hardware which was able to write DVDs at 1x, back in previous linux version.
Now, I dont get speed of less than 4x.
Tested on k3b, xfburn, and brasero. But all start at bottom 4x write speed. k3b forced back to... (0 Replies)
Discussion started by: makh
0 Replies
4. Solaris
Hi all,
I've somehow gained the idea that I _need_ to run at least 1 box with Solaris, but things don't go as I had planned :-)
I pulled this ancient IBM eserver xseries 305 out of the dust, and got myself a fresh copy of the required cd's for Solaris 10u7. FAIL, for some reason the box and the... (7 Replies)
Discussion started by: mr.aart
7 Replies
5. Solaris
Hi,
I need to start the Xserver process in a domain of a E25K which has installed Solaris 8, however this domain doesn't have installed a graphic card, is this possible? Or is there any way to emulate this process?
In fact I don't know how to stop or start the Xserver process, is with... (5 Replies)
Discussion started by: wolf8006
5 Replies
6. Solaris
Hi...all
database - 10g Rs 2 with ASM
platform - Sun Solaris V890 64bit
This is the step i use to auto start the database n ASM: (auto start can start but need to kill lsvcrun first)
1 dbora---script
2 start_shutdown_asm.ksh---script
3. Dbora file must be put under /etc/init.d directory... (0 Replies)
Discussion started by: adzuanamir
0 Replies
7. IP Networking
I have 2 identical printers with the same IP on my network. One is only used as a backup for the primary printer and both are never on line at the same time. The goal was to always keep only 1 on and have an use the other printer as an immediate backup if necessary. But when I switch the cable I... (4 Replies)
Discussion started by: golfs4us
4 Replies
8. UNIX for Advanced & Expert Users
I've recently patched my AIX box from ML02 to ML06 and somehow along the way the monitor no longer starts up in GUI mode.
Running the command xinit gives me the following errros
ioctl Bad file Number
1356- Unable to start the X server
I've checked the path variables, the monitor, the lai0... (0 Replies)
Discussion started by: mahartle
0 Replies
9. HP-UX
Hi, I'm from Venezuela and my English is not so good, please be patient. I got a problem with the machine described above, I tried to to enter in "the apollo" my teacher asked me to do it, because it's a part of an asignment but nobody knows any count to work with it. First my teacher told me to... (1 Reply)
Discussion started by: telesnake45
1 Replies
virtualkm(7D) virtualkm(7D)
NAME
virtualkm - Virtual keyboard and mouse
SYNOPSIS
/dev/kbd
/dev/mouse
A virtual keyboard or mouse is an abstraction of one or more physical keyboards or mice (USB or PS2) connected to a system. Input streams
for these physical devices are coalesced into a single input stream and appear as a single device to the upper layers.
/dev/kbd is the virtual keyboard device file. Inputs from multiple keyboards are coalesced into a single input stream, meaning that all
keyboards appear as a single keyboard to a console or window system and accordingly, are treated as a single device. The virtual keyboard
layout is consistent with the layout of the first keyboard plugged into the system. Note that on x86 platforms, the virtual keyboard layout
can be overloaded by eeprom(1M).
/dev/mouse is the virtual mouse device file. Inputs from multiple mice are coalesced into a single input stream, meaning that all mice
appear as single mouse to the window system.
Commands from applications are dispatched by the virtual keyboard/mouse facility to the underlying physical devices and will succeed pro-
vided that one of the underlying devices responds with success. For example, a single command issued to turn on LED's will turn on corre-
sponding LED's for all underlying physical keyboards.
Although physical keyboards/mice are linked to the virtual keyboard/mouse facility, each may be opened separately by accessing its asso-
ciated device file. (For example, /dev/usb/hid0 for a usb mouse). Directly accessing a device file can be useful for multi-seat, gok(1) or
similar purposes.
When a single physical device is opened via its associated device file, it is automatically removed from the single virtual input stream.
When closed, it is automatically re- coalesced into the single virtual input stream.
Under the virtualkm facility, the PS/2 mouse is coalesced into a virtual mouse single input stream and can be accessed using the /dev/mouse
file. (Note that in previous releases, the PS/2 mouse was accessed via the /dev/kdmouse physical device file). In the current release, you
use the /dev/kdmouse file to directly access the physical PS/2 mouse.
INTERFACES
The virtual mouse provides the following event ID's for mouse capability changes:
MOUSE_CAP_CHANGE_NUM_BUT
This event is reported when the total number of mouse buttons changes. The Firm_event.value is set to the new button total, which is
the maximum number of all mice buttons. Other fields are ignored.
MOUSE_CAP_CHANGE_NUM_WHEEL
This event is reported when the total number of mouse wheels changes. The Firm_event.value is set to the new wheel total. Other fields
are ignored. The event value (Firm_event.value) can be 0 (no wheel), 1 (vertical wheel), or 2 (vertical and horizontal wheel).
The Firm_event structure is described in <sys/vuid_event.h>. As with other events, firm events are received using read(2).
Event ID's are used by applications (including certain mouse demo applications) that are programmed to graphically represent the actual
number of buttons and wheels on a mouse. When an application of this type receives a Firm_event with a ID MOUSE_CAP_CHANGE_NUM_BUT or
MOUSE_CAP_CHANGE_NUM_WHEEL event, it is instructed to update its state information using the new value. Consider, for example, a mouse demo
application whose sole function is to display a mouse with buttons that graphically correspond to the actual number of buttons on the
mouse. If, for example, the system has a single two-button USB mouse attached, the application, by default, will graphically display the
mouse with a left and a right button. However, if a another three-button USB mouse is hot-plugged into the system, a
MOUSE_CAP_CHANGE_NUM_BUT Firm event with Firm_event.value of three instructs the demo application to update the mouse display to indicate
three buttons.
/dev/kbd Virtual Keyboard device file.
/dev/mouse Virtual Mouse device file.
/dev/kdmouse Physical PS/2 mouse device file.
/dev/usb/hid* Physical USB keyboard/mouse device file.
/etc/dacf.conf Device auto-configuration file.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Architecture |SPARC, |
|Availability |SUNWckr, SUNWcsd, SUNWusb, |
| |SUNWpsdcr, SUNWcakr.i |
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
, eeprom(1M), read(2), attributes(5), hid(7D), usba(7D), kb(7M), usbkbm(7M), usbms(7M), vuidmice(7M)
See gok(1) in the GNOME man pages, available in the SUNWgnome package. gok(1) is not a SunOS man page.
DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are formatted in the following man-
ner:
WARNING: Error message...
conskbd: keyboard is not available for system debugging: device_path.
Errors were encountered while entering kmdb during initialization for debugger mode. As a result, the keyboard is not available.
conskbd: keyboard is not available: <device_path>
Errors were encountered while exiting kmdb during un-initialization for debugger mode. As a result, the keyboard is not available.
Failed to relink the mouse <device_path> underneath virtual mouse
An error was encountered and the mouse is unavailable. (When a mouse is physically opened via a physical device file such as
/dev/usb/hid0, it is removed from the single virtual input stream (/dev/mouse). When closed, it is re-coalesced into a single virtual
input stream beneath /dev/mouse. If an error is encountered, (for example, the mouse has been physically removed), it is unavailable
beneath /dev/mouse.
NOTES
Currently, the virtualkm device supports only USB and PS2 keyboards and mice.
The virtualkm device maintains complete compatibility on select legacy systems, (including Ultra 10's), that are equipped with serial key-
board/mouse.
21 June 2005 virtualkm(7D)