On 25-Dec-01 Eric Melville wrote:
>> However, perhaps sysinstall should tell the user that if they have a USB
>> mouse, they need do nothing, insetad of think 'Uhh, I don't recognise any of
>> these, lets try this one' and getting it wrong.
>
> Before this menu is presented, sysinstall asks
On 24-Dec-01 William Ward wrote:
> Is /dev/ums0 ommitted from sysinstall for any particular reason? This patch
> adds /dev/ums0 to sysinstall::Configure->Mouse->Port.
Yes, usbd already runs moused for you. (Look at usbd.conf), so putting this in
results in 2 moused's trying to work with /dev/u
> However, perhaps sysinstall should tell the user that if they have a USB
> mouse, they need do nothing, insetad of think 'Uhh, I don't recognise any of
> these, lets try this one' and getting it wrong.
Before this menu is presented, sysinstall asks if there is a usb mouse or
not. I suppose
On Mon, 24 Dec 2001, William Ward wrote:
> A. Thanks for the answer.
>
> /William
You know, replying below the quoted post makes it a lot easier to reply to
both peoples replies, without having to be adept at reading backwards...
> On Mon, Dec 24, 2001 at 12:27:52PM -0800, Eric Melville w
A. Thanks for the answer.
/William
On Mon, Dec 24, 2001 at 12:27:52PM -0800, Eric Melville wrote:
> > Is /dev/ums0 ommitted from sysinstall for any particular reason? This patch
> > adds /dev/ums0 to sysinstall::Configure->Mouse->Port.
>
> This is intentional. In the case of a usb mouse,
> Is /dev/ums0 ommitted from sysinstall for any particular reason? This patch
> adds /dev/ums0 to sysinstall::Configure->Mouse->Port.
This is intentional. In the case of a usb mouse, usbd is responsible for
starting moused.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebs
Thanks Joe. I managed to screw up my first patch posted to any
mailing list. Hehe. Maybe it's supposed to work that way.
--- menus.c.old Mon Dec 24 13:54:18 2001
+++ menus.c Mon Dec 24 13:55:49 2001
@@ -387,6 +387,8 @@
dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT "=/dev/c
