1.\" Copyright (c) 1996 2.\" Mike Pritchard <mpp@FreeBSD.org>. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by Mike Pritchard. 15.\" 4. Neither the name of the author nor the names of its contributors 16.\" may be used to endorse or promote products derived from this software 17.\" without specific prior written permission. 18.\" 19.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 22.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 29.\" SUCH DAMAGE. 30.\" 31.\" $FreeBSD$ 32.\" 33.Dd May 15, 2008 34.Dt MOUSED 8 35.Os 36.Sh NAME 37.Nm moused 38.Nd pass mouse data to the console driver 39.Sh SYNOPSIS 40.Nm 41.Op Fl DPRacdfs 42.Op Fl I Ar file 43.Op Fl F Ar rate 44.Op Fl r Ar resolution 45.Op Fl S Ar baudrate 46.Op Fl VH Op Fl U Ar distance Fl L Ar distance 47.Op Fl A Ar exp Ns Op , Ns Ar offset 48.Op Fl a Ar X Ns Op , Ns Ar Y 49.Op Fl C Ar threshold 50.Op Fl m Ar N=M 51.Op Fl w Ar N 52.Op Fl z Ar target 53.Op Fl t Ar mousetype 54.Op Fl l Ar level 55.Op Fl 3 Op Fl E Ar timeout 56.Op Fl T Ar distance Ns Op , Ns Ar time Ns Op , Ns Ar after 57.Fl p Ar port 58.Pp 59.Nm 60.Op Fl Pd 61.Fl p Ar port 62.Fl i Ar info 63.Sh DESCRIPTION 64The 65.Nm 66utility and the console driver work together to support 67mouse operation in the text console and user programs. 68They virtualize the mouse and provide user programs with mouse data 69in the standard format 70(see 71.Xr sysmouse 4 ) . 72.Pp 73The mouse daemon listens to the specified port for mouse data, 74interprets and then passes it via ioctls to the console driver. 75The mouse daemon 76reports translation movement, button press/release 77events and movement of the roller or the wheel if available. 78The roller/wheel movement is reported as 79.Dq Z 80axis movement. 81.Pp 82The console driver will display the mouse pointer on the screen 83and provide cut and paste functions if the mouse pointer is enabled 84in the virtual console via 85.Xr vidcontrol 1 . 86If 87.Xr sysmouse 4 88is opened by the user program, the console driver also passes the mouse 89data to the device so that the user program will see it. 90.Pp 91If the mouse daemon receives the signal 92.Dv SIGHUP , 93it will reopen the mouse port and reinitialize itself. 94Useful if 95the mouse is attached/detached while the system is suspended. 96.Pp 97If the mouse daemon receives the signal 98.Dv SIGUSR1 , 99it will stop passing mouse events. 100Sending the signal 101.Dv SIGUSR1 102again will resume passing mouse events. 103Useful if your typing on a laptop is 104interrupted by accidentally touching the mouse pad. 105.Pp 106The following options are available: 107.Bl -tag -width indent 108.It Fl 3 109Emulate the third (middle) button for 2-button mice. 110It is emulated 111by pressing the left and right physical buttons simultaneously. 112.It Fl C Ar threshold 113Set double click speed as the maximum interval in msec between button clicks. 114Without this option, the default value of 500 msec will be assumed. 115This option will have effect only on the cut and paste operations 116in the text mode console. 117The user program which is reading mouse data 118via 119.Xr sysmouse 4 120will not be affected. 121.It Fl D 122Lower DTR on the serial port. 123This option is valid only if 124.Ar mousesystems 125is selected as the protocol type. 126The DTR line may need to be dropped for a 3-button mouse 127to operate in the 128.Ar mousesystems 129mode. 130.It Fl E Ar timeout 131When the third button emulation is enabled 132(see above), 133the 134.Nm 135utility waits 136.Ar timeout 137msec at most before deciding whether two buttons are being pressed 138simultaneously. 139The default timeout is 100 msec. 140.It Fl F Ar rate 141Set the report rate (reports/sec) of the device if supported. 142.It Fl L Ar distance 143When 144.Dq Virtual Scrolling 145is enabled, the 146.Fl L 147option can be used to set the 148.Ar distance 149(in pixels) that the mouse must move before a scroll event 150is generated. This effectively controls the scrolling speed. 151The default 152.Ar distance 153is 2 pixels. 154.It Fl H 155Enable 156.Dq Horizontal Virtual Scrolling . 157With this option set, holding the middle mouse 158button down will cause motion to be interpreted as 159horizontal scrolling. 160Use the 161.Fl U 162option to set the distance the mouse must move before the scrolling mode is 163activated and the 164.Fl L 165option to set the scrolling speed. 166This option may be used with or without the 167.Fl V 168option. 169.It Fl I Ar file 170Write the process id of the 171.Nm 172utility in the specified file. 173Without this option, the process id will be stored in 174.Pa /var/run/moused.pid . 175.It Fl P 176Do not start the Plug and Play COM device enumeration procedure 177when identifying the serial mouse. 178If this option is given together with the 179.Fl i 180option, the 181.Nm 182utility will not be able to print useful information for the serial mouse. 183.It Fl R 184Lower RTS on the serial port. 185This option is valid only if 186.Ar mousesystems 187is selected as the protocol type by the 188.Fl t 189option below. 190It is often used with the 191.Fl D 192option above. 193Both RTS and DTR lines may need to be dropped for 194a 3-button mouse to operate in the 195.Ar mousesystems 196mode. 197.It Fl S Ar baudrate 198Select the baudrate for the serial port (1200 to 9600). 199Not all serial mice support this option. 200.It Fl T Ar distance Ns Op , Ns Ar time Ns Op , Ns Ar after 201Terminate drift. 202Use this option if mouse pointer slowly wanders when mouse is not moved. 203Movements up to 204.Ar distance 205(for example 4) pixels (X+Y) in 206.Ar time 207msec (default 500) are ignored, except during 208.Ar after 209msec (default 4000) since last real mouse movement. 210.It Fl V 211Enable 212.Dq Virtual Scrolling . 213With this option set, holding the middle mouse 214button down will cause motion to be interpreted as scrolling. 215Use the 216.Fl U 217option to set the distance the mouse must move before the scrolling mode is 218activated and the 219.Fl L 220option to set the scrolling speed. 221.It Fl U Ar distance 222When 223.Dq Virtual Scrolling 224is enabled, the 225.Fl U 226option can be used to set the 227.Ar distance 228(in pixels) that the mouse must move before the scrolling 229mode is activated. 230The default 231.Ar distance 232is 3 pixels. 233.It Fl A Ar exp Ns Op , Ns Ar offset 234Apply exponential (dynamic) acceleration to mouse movements: 235the faster you move the mouse, the more it will be accelerated. 236That means that small mouse movements are not accelerated, 237so they are still very accurate, while a faster movement will 238drive the pointer quickly across the screen. 239.Pp 240The 241.Ar exp 242value specifies the exponent, which is basically 243the amount of acceleration. Useful values are in the 244range 1.1 to 2.0, but it depends on your mouse hardware 245and your personal preference. A value of 1.0 means no 246exponential acceleration. A value of 2.0 means squared 247acceleration (i.e. if you move the mouse twice as fast, 248the pointer will move four times as fast on the screen). 249Values beyond 2.0 are possible but not recommended. 250A good value to start is probably 1.5. 251.Pp 252The optional 253.Ar offset 254value specifies the distance at which the acceleration 255begins. The default is 1.0, which means that the 256acceleration is applied to movements larger than one unit. 257If you specify a larger value, it takes more speed for 258the acceleration to kick in, i.e. the speed range for 259small and accurate movements is wider. 260Usually the default should be sufficient, but if you're 261not satisfied with the behaviour, try a value of 2.0. 262.Pp 263Note that the 264.Fl A 265option interacts badly with the X server's own acceleration, 266which doesn't work very well anyway. Therefore it is 267recommended to switch it off if necessary: 268.Dq xset m 1 . 269.It Fl a Ar X Ns Op , Ns Ar Y 270Accelerate or decelerate the mouse input. 271This is a linear acceleration only. 272Values less than 1.0 slow down movement, values greater than 1.0 speed it 273up. 274Specifying only one value sets the acceleration for both axes. 275.Pp 276You can use the 277.Fl a 278and 279.Fl A 280options at the same time to have the combined effect 281of linear and exponential acceleration. 282.It Fl c 283Some mice report middle button down events 284as if the left and right buttons are being pressed. 285This option handles this. 286.It Fl d 287Enable debugging messages. 288.It Fl f 289Do not become a daemon and instead run as a foreground process. 290Useful for testing and debugging. 291.It Fl i Ar info 292Print specified information and quit. 293Available pieces of 294information are: 295.Pp 296.Bl -tag -compact -width modelxxx 297.It Ar port 298Port (device file) name, i.e.\& 299.Pa /dev/cuau0 , 300.Pa /dev/mse0 301and 302.Pa /dev/psm0 . 303.It Ar if 304Interface type: serial, bus, inport or ps/2. 305.It Ar type 306Protocol type. 307It is one of the types listed under the 308.Fl t 309option below or 310.Ar sysmouse 311if the driver supports the 312.Ar sysmouse 313data format standard. 314.It Ar model 315Mouse model. 316The 317.Nm 318utility may not always be able to identify the model. 319.It Ar all 320All of the above items. 321Print port, interface, type and model in this order 322in one line. 323.El 324.Pp 325If the 326.Nm 327utility cannot determine the requested information, it prints 328.Dq Li unknown 329or 330.Dq Li generic . 331.It Fl l Ar level 332Specifies at which level 333.Nm 334should operate the mouse driver. 335Refer to 336.Sx Operation Levels 337in 338.Xr psm 4 339for more information on this. 340.It Fl m Ar N=M 341Assign the physical button 342.Ar M 343to the logical button 344.Ar N . 345You may specify as many instances of this option as you like. 346More than one physical button may be assigned to a logical button at the 347same time. 348In this case the logical button will be down, 349if either of the assigned physical buttons is held down. 350Do not put space around 351.Ql = . 352.It Fl p Ar port 353Use 354.Ar port 355to communicate with the mouse. 356.It Fl r Ar resolution 357Set the resolution of the device; in Dots Per Inch, or 358.Ar low , 359.Ar medium-low , 360.Ar medium-high 361or 362.Ar high . 363This option may not be supported by all the device. 364.It Fl s 365Select a baudrate of 9600 for the serial line. 366Not all serial mice support this option. 367.It Fl t Ar type 368Specify the protocol type of the mouse attached to the port. 369You may explicitly specify a type listed below, or use 370.Ar auto 371to let the 372.Nm 373utility automatically select an appropriate protocol for the given 374mouse. 375If you entirely omit this option in the command line, 376.Fl t Ar auto 377is assumed. 378Under normal circumstances, 379you need to use this option only if the 380.Nm 381utility is not able to detect the protocol automatically 382(see 383.Sx "Configuring Mouse Daemon" ) . 384.Pp 385Note that if a protocol type is specified with this option, the 386.Fl P 387option above is implied and Plug and Play COM device enumeration 388procedure will be disabled. 389.Pp 390Also note that if your mouse is attached to the PS/2 mouse port, you should 391always choose 392.Ar auto 393or 394.Ar ps/2 , 395regardless of the brand and model of the mouse. 396Likewise, if your 397mouse is attached to the bus mouse port, choose 398.Ar auto 399or 400.Ar busmouse . 401Serial mouse protocols will not work with these mice. 402.Pp 403For the USB mouse, the protocol must be 404.Ar auto . 405No other protocol will work with the USB mouse. 406.Pp 407Valid types for this option are 408listed below. 409.Pp 410For the serial mouse: 411.Bl -tag -compact -width mousesystemsxxx 412.It Ar microsoft 413Microsoft serial mouse protocol. 414Most 2-button serial mice use this protocol. 415.It Ar intellimouse 416Microsoft IntelliMouse protocol. 417Genius NetMouse, 418.Tn ASCII 419Mie Mouse, 420Logitech MouseMan+ and FirstMouse+ use this protocol too. 421Other mice with a roller/wheel may be compatible with this protocol. 422.It Ar mousesystems 423MouseSystems 5-byte protocol. 4243-button mice may use this protocol. 425.It Ar mmseries 426MM Series mouse protocol. 427.It Ar logitech 428Logitech mouse protocol. 429Note that this is for old Logitech models. 430.Ar mouseman 431or 432.Ar intellimouse 433should be specified for newer models. 434.It Ar mouseman 435Logitech MouseMan and TrackMan protocol. 436Some 3-button mice may be compatible 437with this protocol. 438Note that MouseMan+ and FirstMouse+ use 439.Ar intellimouse 440protocol rather than this one. 441.It Ar glidepoint 442ALPS GlidePoint protocol. 443.It Ar thinkingmouse 444Kensington ThinkingMouse protocol. 445.It Ar mmhitab 446Hitachi tablet protocol. 447.It Ar x10mouseremote 448X10 MouseRemote. 449.It Ar kidspad 450Genius Kidspad and Easypad protocol. 451.It Ar versapad 452Interlink VersaPad protocol. 453.It Ar gtco_digipad 454GTCO Digipad protocol. 455.El 456.Pp 457For the bus and InPort mouse: 458.Bl -tag -compact -width mousesystemsxxx 459.It Ar busmouse 460This is the only protocol type available for 461the bus and InPort mouse and should be specified for any bus mice 462and InPort mice, regardless of the brand. 463.El 464.Pp 465For the PS/2 mouse: 466.Bl -tag -compact -width mousesystemsxxx 467.It Ar ps/2 468This is the only protocol type available for the PS/2 mouse 469and should be specified for any PS/2 mice, regardless of the brand. 470.El 471.Pp 472For the USB mouse, 473.Ar auto 474is the only protocol type available for the USB mouse 475and should be specified for any USB mice, regardless of the brand. 476.It Fl w Ar N 477Make the physical button 478.Ar N 479act as the wheel mode button. 480While this button is pressed, X and Y axis movement is reported to be zero 481and the Y axis movement is mapped to Z axis. 482You may further map the Z axis movement to virtual buttons by the 483.Fl z 484option below. 485.It Fl z Ar target 486Map Z axis (roller/wheel) movement to another axis or to virtual buttons. 487Valid 488.Ar target 489maybe: 490.Bl -tag -compact -width x__ 491.It Ar x 492.It Ar y 493X or Y axis movement will be reported when the Z axis movement is detected. 494.It Ar N 495Report down events for the virtual buttons 496.Ar N 497and 498.Ar N+1 499respectively when negative and positive Z axis movement 500is detected. 501There do not need to be physical buttons 502.Ar N 503and 504.Ar N+1 . 505Note that mapping to logical buttons is carried out after mapping 506from the Z axis movement to the virtual buttons is done. 507.It Ar N1 N2 508Report down events for the virtual buttons 509.Ar N1 510and 511.Ar N2 512respectively when negative and positive Z axis movement 513is detected. 514.It Ar N1 N2 N3 N4 515This is useful for the mouse with two wheels of which 516the second wheel is used to generate horizontal scroll action, 517and for the mouse which has a knob or a stick which can detect 518the horizontal force applied by the user. 519.Pp 520The motion of the second wheel will be mapped to the buttons 521.Ar N3 , 522for the negative direction, and 523.Ar N4 , 524for the positive direction. 525If the buttons 526.Ar N3 527and 528.Ar N4 529actually exist in this mouse, their actions will not be detected. 530.Pp 531Note that horizontal movement or second roller/wheel movement may not 532always be detected, 533because there appears to be no accepted standard as to how it is encoded. 534.Pp 535Note also that some mice think left is the negative horizontal direction; 536others may think otherwise. 537Moreover, there are some mice whose two wheels are both mounted vertically, 538and the direction of the second vertical wheel does not match the 539first one. 540.El 541.El 542.Ss Configuring Mouse Daemon 543The first thing you need to know is the interface type 544of the mouse you are going to use. 545It can be determined by looking at the connector of the mouse. 546The serial mouse has a D-Sub female 9- or 25-pin connector. 547The bus and InPort mice have either a D-Sub male 9-pin connector 548or a round DIN 9-pin connector. 549The PS/2 mouse is equipped with a small, round DIN 6-pin connector. 550Some mice come with adapters with which the connector can 551be converted to another. 552If you are to use such an adapter, 553remember the connector at the very end of the mouse/adapter pair is 554what matters. 555The USB mouse has a flat rectangular connector. 556.Pp 557The next thing to decide is a port to use for the given interface. 558For the bus, InPort and PS/2 mice, there is little choice: 559the bus and InPort mice always use 560.Pa /dev/mse0 , 561and the PS/2 mouse is always at 562.Pa /dev/psm0 . 563There may be more than one serial port to which the serial 564mouse can be attached. 565Many people often assign the first, built-in 566serial port 567.Pa /dev/cuau0 568to the mouse. 569You can attach multiple USB mice to your system or to your USB hub. 570They are accessible as 571.Pa /dev/ums0 , /dev/ums1 , 572and so on. 573.Pp 574You may want to create a symbolic link 575.Pa /dev/mouse 576pointing to the real port to which the mouse is connected, so that you 577can easily distinguish which is your 578.Dq mouse 579port later. 580.Pp 581The next step is to guess the appropriate protocol type for the mouse. 582The 583.Nm 584utility may be able to automatically determine the protocol type. 585Run the 586.Nm 587utility with the 588.Fl i 589option and see what it says. 590If the command can identify 591the protocol type, no further investigation is necessary on your part. 592You may start the daemon without explicitly specifying a protocol type 593(see 594.Sx EXAMPLES ) . 595.Pp 596The command may print 597.Ar sysmouse 598if the mouse driver supports this protocol type. 599.Pp 600Note that the 601.Dv type 602and 603.Dv model 604printed by the 605.Fl i 606option do not necessarily match the product name of the pointing device 607in question, but they may give the name of the device with which it is 608compatible. 609.Pp 610If the 611.Fl i 612option yields nothing, you need to specify a protocol type to the 613.Nm 614utility by the 615.Fl t 616option. 617You have to make a guess and try. 618There is rule of thumb: 619.Pp 620.Bl -enum -compact -width 1.X 621.It 622The bus and InPort mice always use 623.Ar busmouse 624protocol regardless of the brand of the mouse. 625.It 626The 627.Ar ps/2 628protocol should always be specified for the PS/2 mouse 629regardless of the brand of the mouse. 630.It 631You must specify the 632.Ar auto 633protocol for the USB mouse. 634.It 635Most 2-button serial mice support the 636.Ar microsoft 637protocol. 638.It 6393-button serial mice may work with the 640.Ar mousesystems 641protocol. 642If it does not, it may work with the 643.Ar microsoft 644protocol although 645the third (middle) button will not function. 6463-button serial mice may also work with the 647.Ar mouseman 648protocol under which the third button may function as expected. 649.It 6503-button serial mice may have a small switch to choose between 651.Dq MS 652and 653.Dq PC , 654or 655.Dq 2 656and 657.Dq 3 . 658.Dq MS 659or 660.Dq 2 661usually mean the 662.Ar microsoft 663protocol. 664.Dq PC 665or 666.Dq 3 667will choose the 668.Ar mousesystems 669protocol. 670.It 671If the mouse has a roller or a wheel, it may be compatible with the 672.Ar intellimouse 673protocol. 674.El 675.Pp 676To test if the selected protocol type is correct for the given mouse, 677enable the mouse pointer in the current virtual console, 678.Pp 679.Dl "vidcontrol -m on" 680.Pp 681start the mouse daemon in the foreground mode, 682.Pp 683.Dl "moused -f -p <selected_port> -t <selected_protocol>" 684.Pp 685and see if the mouse pointer travels correctly 686according to the mouse movement. 687Then try cut & paste features by 688clicking the left, right and middle buttons. 689Type ^C to stop 690the command. 691.Ss Multiple Mice 692As many instances of the mouse daemon as the number of mice attached to 693the system may be run simultaneously; one 694instance for each mouse. 695This is useful if the user wants to use the built-in PS/2 pointing device 696of a laptop computer while on the road, but wants to use a serial 697mouse when s/he attaches the system to the docking station in the office. 698Run two mouse daemons and tell the application program 699(such as the 700.Tn "X\ Window System" ) 701to use 702.Xr sysmouse 4 , 703then the application program will always see mouse data from either mouse. 704When the serial mouse is not attached, the corresponding mouse daemon 705will not detect any movement or button state change and the application 706program will only see mouse data coming from the daemon for the 707PS/2 mouse. 708In contrast when both mice are attached and both of them 709are moved at the same time in this configuration, 710the mouse pointer will travel across the screen just as if movement of 711the mice is combined all together. 712.Sh FILES 713.Bl -tag -width /dev/consolectl -compact 714.It Pa /dev/consolectl 715device to control the console 716.It Pa /dev/mse%d 717bus and InPort mouse driver 718.It Pa /dev/psm%d 719PS/2 mouse driver 720.It Pa /dev/sysmouse 721virtualized mouse driver 722.It Pa /dev/ttyv%d 723virtual consoles 724.It Pa /dev/ums%d 725USB mouse driver 726.It Pa /var/run/moused.pid 727process id of the currently running 728.Nm 729utility 730.It Pa /var/run/MouseRemote 731UNIX-domain stream socket for X10 MouseRemote events 732.El 733.Sh EXAMPLES 734.Dl "moused -p /dev/cuau0 -i type" 735.Pp 736Let the 737.Nm 738utility determine the protocol type of the mouse at the serial port 739.Pa /dev/cuau0 . 740If successful, the command will print the type, otherwise it will say 741.Dq Li unknown . 742.Bd -literal -offset indent 743moused -p /dev/cuau0 744vidcontrol -m on 745.Ed 746.Pp 747If the 748.Nm 749utility is able to identify the protocol type of the mouse at the specified 750port automatically, you can start the daemon without the 751.Fl t 752option and enable the mouse pointer in the text console as above. 753.Bd -literal -offset indent 754moused -p /dev/mouse -t microsoft 755vidcontrol -m on 756.Ed 757.Pp 758Start the mouse daemon on the serial port 759.Pa /dev/mouse . 760The protocol type 761.Ar microsoft 762is explicitly specified by the 763.Fl t 764option. 765.Pp 766.Dl "moused -p /dev/mouse -m 1=3 -m 3=1" 767.Pp 768Assign the physical button 3 (right button) to the logical button 1 769(logical left) and the physical button 1 (left) to the logical 770button 3 (logical right). 771This will effectively swap the left and right buttons. 772.Pp 773.Dl "moused -p /dev/mouse -t intellimouse -z 4" 774.Pp 775Report negative Z axis movement (i.e., mouse wheel) as the button 4 pressed 776and positive Z axis movement (i.e., mouse wheel) as the button 5 pressed. 777.Pp 778If you add 779.Pp 780.Dl "ALL ALL = NOPASSWD: /usr/bin/killall -USR1 moused" 781.Pp 782to your 783.Pa /usr/local/etc/sudoers 784file, and bind 785.Pp 786.Dl "killall -USR1 moused" 787.Pp 788to a key in your window manager, you can suspend mouse events on your laptop if 789you keep brushing over the mouse pad while typing. 790.Sh SEE ALSO 791.Xr kill 1 , 792.Xr vidcontrol 1 , 793.Xr xset 1 , 794.Xr keyboard 4 , 795.Xr mse 4 , 796.Xr psm 4 , 797.Xr screen 4 , 798.Xr sysmouse 4 , 799.Xr ums 4 800.Sh STANDARDS 801The 802.Nm 803utility partially supports 804.Dq Plug and Play External COM Device Specification 805in order to support PnP serial mice. 806However, due to various degrees of conformance to the specification by 807existing serial mice, it does not strictly follow the version 1.0 of the 808standard. 809Even with this less strict approach, 810it may not always determine an appropriate protocol type 811for the given serial mouse. 812.Sh HISTORY 813The 814.Nm 815utility first appeared in 816.Fx 2.2 . 817.Sh AUTHORS 818.An -nosplit 819The 820.Nm 821utility was written by 822.An Michael Smith Aq Mt msmith@FreeBSD.org . 823This manual page was written by 824.An Mike Pritchard Aq Mt mpp@FreeBSD.org . 825The command and manual page have since been updated by 826.An Kazutaka Yokota Aq Mt yokota@FreeBSD.org . 827.Sh CAVEATS 828Many pad devices behave as if the first (left) button were pressed if 829the user 830.Dq taps 831the surface of the pad. 832In contrast, some ALPS GlidePoint and Interlink VersaPad models 833treat the tapping action 834as fourth button events. 835Use the option 836.Dq Fl m Li 1=4 837for these models 838to obtain the same effect as the other pad devices. 839.Pp 840Cut and paste functions in the virtual console assume that there 841are three buttons on the mouse. 842The logical button 1 (logical left) selects a region of text in the 843console and copies it to the cut buffer. 844The logical button 3 (logical right) extends the selected region. 845The logical button 2 (logical middle) pastes the selected text 846at the text cursor position. 847If the mouse has only two buttons, the middle, `paste' button 848is not available. 849To obtain the paste function, use the 850.Fl 3 851option to emulate the middle button, or use the 852.Fl m 853option to assign the physical right button to the logical middle button: 854.Dq Fl m Li 2=3 . 855