From owner-freebsd-current  Fri Jan 24 11:37:09 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA15089
          for current-outgoing; Fri, 24 Jan 1997 11:37:09 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15084
          for <current@freebsd.org>; Fri, 24 Jan 1997 11:37:06 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id LAA16700; Fri, 24 Jan 1997 11:37:02 -0800 (PST)
To: Bill Fenner <fenner@parc.xerox.com>
cc: current@freebsd.org
Subject: Re: 2.2-BETA install failure 
In-reply-to: Your message of "Sun, 05 Jan 1997 12:34:11 PST."
             <97Jan5.123412pst.177481@crevenia.parc.xerox.com> 
Date: Fri, 24 Jan 1997 11:37:01 -0800
Message-ID: <16696.854134621@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> - I was unable to select "Busmouse" in the mouse selection menu,
> even though the probe messages included "mse0 at 0x23c irq 5 on isa".
> Another oddness about the mouse selection menu: when I first selected
> it, I could select "PS/2 mosue", but if I then selected COM1 and then
> went back to "PS/2" I couldn't select PS/2 the second time.

I finally found this one!  readlink() doesn't null append its result
(I must have glossed over this the first time I read the man page) so
the previous value, in this case /dev/cuaa0, was simply overlaid.
That explains why the serial devices, with their longer names, were
displayed but not the Bus or PS/2 mice (which have shorter names :).

> - XF86Setup stopped accepting input from the keyboard after I hit enter
> to "dismiss" the info panel about how to set up the mouse.  I couldn't
> figure out what to do so I went to VTY4 and killed XF86Setup.  After that,
> there was nothing running on any other VTY (hitting ctl-alt-F[124] just
> beeped) and X wasn't responding to ctl-alt-BS so I ended up hitting
> reset.

Hmmm.  I can't reproduce this one, but I've heard enough gritching
about various bogons in the new XF86Setup that I'm going to make
the older XF86Config an option as well.

					Jordan