From owner-freebsd-current  Wed Feb 12 19:44:04 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA15451
          for current-outgoing; Wed, 12 Feb 1997 19:44:04 -0800 (PST)
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15400
          for <freebsd-current@freebsd.org>; Wed, 12 Feb 1997 19:43:32 -0800 (PST)
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id MAA06983; Thu, 13 Feb 1997 12:42:27 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (5ZWJCf17CO4cIMRAo3lOI0YZaaiVM6qf@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id MAA02775; Thu, 13 Feb 1997 12:42:26 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id MAA23897; Thu, 13 Feb 1997 12:44:53 +0900 (JST)
Message-Id: <199702130344.MAA23897@zodiac.mech.utsunomiya-u.ac.jp>
To: gurney_j@resnet.uoregon.edu
cc: terry@lambert.org, freebsd-current@freebsd.org,
        yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: moused on notebooks... 
In-reply-to: Your message of "Wed, 12 Feb 1997 19:06:21 MST."
             <199702130206.TAA01310@phaeton.artisoft.com> 
References: <199702130206.TAA01310@phaeton.artisoft.com> 
Date: Thu, 13 Feb 1997 12:44:52 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> right now I'm running moused on my notebook w/ a ps/2 mouse...  if I ever
>> have the mouse detacted when the notebook is up and running I will loose
>> the mouse until I restart moused...  
>> 
>> would anybody object to possibly added a signal handler to moused for
>> SIGHUP to force it to reopen the mouse device?  comments?
>
>In the situation you describe, the SIGHUP would arive when you
>unplugged the mouse, not when you plugged it in.  You want it to
>be opened *after* you plug it in.

For the serial mouse, catching SIGHUP is possible. (But, it will be
useless as Terry Lambert points out) But, the PS/2 mouse device (psm)
doesn't generate SIGHUP; the PS/2 mouse interface doesn't have a
mechanism to detect plugging/unplugging action, AFAIK.

In fact, plugging/unplugging the PS/2 mouse, or the keyboard, while
your system's power is on is really, really a bad idea. Your keyboard
controller can easily be fried by the noise caused at the connector.
I know a couple of poor guys who learned this in a hard way...

Maybe some notebook/laptop computers may have an safe-guarded
circuitry and allow this sort of action. I strongly recommend you to
consult the manual of your notebook and find if it is really OK to
attach/detach the PS/2 mouse on the fly.

Kazu